Microsoft (R) Windows Debugger Version 6.11.0001.404 X86Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\100222-17796-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: *** Invalid ******************************************************************************** Symbol loading may be unreliable without a symbol search path. ** Use .symfix to have the debugger choose a symbol path. ** After setting your symbol path, use .reload to refresh symbol locations. *****************************************************************************Executable search path is: ********************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ **********************************************************************Unable to load image ntoskrnl.exe, Win32 error 0n2*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeWindows 7 Kernel Version 19041 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalMachine Name:Kernel base = 0xfffff801`3f000000 PsLoadedModuleList = 0xfffff801`3fc2a2b0Debug session time: Sun Oct 2 17:04:09.107 2022 (GMT+8)System Uptime: 0 days 18:01:27.004********************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ ******************************************************************************************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ **********************************************************************Probably caused by : hardware_ram ( PAGE_NOT_ZERO )Followup: MachineOwner--------- *** Memory manager detected 176679 instance(s) of page corruption, target is likely to have memory corruption.variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ ******************************************************************************************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ **********************************************************************Probably caused by : hardware_ram ( PAGE_NOT_ZERO )Followup: MachineOwner--------- *** Memory manager detected 176679 instance(s) of page corruption, target is likely to have memory corruption. 您好,A&K,前来提供帮助。您提供的结果没有输出正确的信息,请您直接将dump文件通过网盘共享过来,这边帮您看一下。
您好,A&K,前来提供帮助。您提供的结果没有输出正确的信息,请您直接将dump文件通过网盘共享过来,这边帮您看一下。hi,这是我用百度网盘分享的内容~复制这段内容打开「百度网盘」APP即可获取链接:https://pan.baidu.com/s/1kIBqCCYROJ0-j8Ax8Qty_A提取码:yyds此是否有帮助?是否抱歉,这没有帮助。太棒了!感谢你的反馈。你对此的满意度如何?感谢你的反馈,它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
您的dump文件显示了文件系统的问题。这可能是硬盘损坏或者驱动程序故障导致的,我建议您卸载任何存储管理软件(如果安装过),并对您的硬盘进行健康性检查。