Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Polar\Desktop\082622-24828-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol 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.exe Windows 7 Kernel Version 19041 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff804`49200000 PsLoadedModuleList = 0xfffff804`49e2a250 Debug session time: Fri Aug 26 11:08:38.689 2022 (GMT+8) System Uptime: 1 days 12:50:04.391 ********************************************************************* * 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.exe Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............. Loading User Symbols Loading unloaded module list .................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80445788acb, ffff9e890c4dea10, 0} Unable to load image FLTMGR.SYS, Win32 error 0n2 *** WARNING: Unable to verify timestamp for FLTMGR.SYS *** ERROR: Module load completed but symbols could not be loaded for FLTMGR.SYS ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ********************************************************************* * 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 122563 instance(s) of page corruption, target is likely to have memory corruption. 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80445788acb, Address of the exception record for the exception that caused the bugcheck Arg3: ffff9e890c4dea10, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ********************************************************************* * 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+ * ********************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. FAULTING_MODULE: fffff80449200000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 0 EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%p FAULTING_IP: FLTMGR+8acb fffff804`45788acb 483b7020 cmp rsi,qword ptr [rax+20h] CONTEXT: ffff9e890c4dea10 -- (.cxr 0xffff9e890c4dea10) rax=0800000000000000 rbx=0000000000000000 rcx=ffffa20682312ac0 rdx=ffffa2067ac2ebf0 rsi=ffffa2067ac2ebf0 rdi=0800000000000000 rip=fffff80445788acb rsp=ffff9e890c4df410 rbp=ffffa206669b769c r8=ffffffffffffffff r9=7fffa20682312a88 r10=fffff804494ad910 r11=ffffe58408810110 r12=fffff804457a8060 r13=0000000000000000 r14=ffffa20682312ac0 r15=0000000000004000 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206 FLTMGR+0x8acb: fffff804`45788acb 483b7020 cmp rsi,qword ptr [rax+20h] ds:002b:08000000`00000020=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B CURRENT_IRQL: 0 BAD_PAGES_DETECTED: 1dec3 LAST_CONTROL_TRANSFER: from ffffa20673634710 to fffff80445788acb STACK_TEXT: ffff9e89`0c4df410 ffffa206`73634710 : fffff804`494ad9fe ffffa206`736340c0 ffffa206`82312a88 ffffa206`669b7680 : FLTMGR+0x8acb ffff9e89`0c4df418 fffff804`494ad9fe : ffffa206`736340c0 ffffa206`82312a88 ffffa206`669b7680 ffffa206`7ac2ebf0 : 0xffffa206`73634710 ffff9e89`0c4df420 ffffa206`736340c0 : ffffa206`82312a88 ffffa206`669b7680 ffffa206`7ac2ebf0 ffffa206`82312a20 : nt+0x2ad9fe ffff9e89`0c4df428 ffffa206`82312a88 : ffffa206`669b7680 ffffa206`7ac2ebf0 ffffa206`82312a20 00000000`ffffbfff : 0xffffa206`736340c0 ffff9e89`0c4df430 ffffa206`669b7680 : ffffa206`7ac2ebf0 ffffa206`82312a20 00000000`ffffbfff ffffa206`82312a20 : 0xffffa206`82312a88 ffff9e89`0c4df438 ffffa206`7ac2ebf0 : ffffa206`82312a20 00000000`ffffbfff ffffa206`82312a20 fffff804`457ba857 : 0xffffa206`669b7680 ffff9e89`0c4df440 ffffa206`82312a20 : 00000000`ffffbfff ffffa206`82312a20 fffff804`457ba857 ffffa206`82312a20 : 0xffffa206`7ac2ebf0 ffff9e89`0c4df448 00000000`ffffbfff : ffffa206`82312a20 fffff804`457ba857 ffffa206`82312a20 ffffa206`00000000 : 0xffffa206`82312a20 ffff9e89`0c4df450 ffffa206`82312a20 : fffff804`457ba857 ffffa206`82312a20 ffffa206`00000000 ffff9e89`00000000 : 0xffffbfff ffff9e89`0c4df458 fffff804`457ba857 : ffffa206`82312a20 ffffa206`00000000 ffff9e89`00000000 00000000`ffffbfff : 0xffffa206`82312a20 ffff9e89`0c4df460 ffffa206`82312a20 : ffffa206`00000000 ffff9e89`00000000 00000000`ffffbfff ffffa206`669b7010 : FLTMGR+0x3a857 ffff9e89`0c4df468 ffffa206`00000000 : ffff9e89`00000000 00000000`ffffbfff ffffa206`669b7010 ffffa206`7ac2ebf0 : 0xffffa206`82312a20 ffff9e89`0c4df470 ffff9e89`00000000 : 00000000`ffffbfff ffffa206`669b7010 ffffa206`7ac2ebf0 ffffa206`82312a20 : 0xffffa206`00000000 ffff9e89`0c4df478 00000000`ffffbfff : ffffa206`669b7010 ffffa206`7ac2ebf0 ffffa206`82312a20 fffff804`457ba5e3 : 0xffff9e89`00000000 ffff9e89`0c4df480 ffffa206`669b7010 : ffffa206`7ac2ebf0 ffffa206`82312a20 fffff804`457ba5e3 00000000`00000000 : 0xffffbfff ffff9e89`0c4df488 ffffa206`7ac2ebf0 : ffffa206`82312a20 fffff804`457ba5e3 00000000`00000000 ffffa206`7ac2ebf0 : 0xffffa206`669b7010 ffff9e89`0c4df490 ffffa206`82312a20 : fffff804`457ba5e3 00000000`00000000 ffffa206`7ac2ebf0 ffff9e89`0c4df6f0 : 0xffffa206`7ac2ebf0 ffff9e89`0c4df498 fffff804`457ba5e3 : 00000000`00000000 ffffa206`7ac2ebf0 ffff9e89`0c4df6f0 ffffa206`805640f8 : 0xffffa206`82312a20 ffff9e89`0c4df4a0 00000000`00000000 : ffffa206`7ac2ebf0 ffff9e89`0c4df6f0 ffffa206`805640f8 ffffa206`82312a20 : FLTMGR+0x3a5e3 SYMBOL_NAME: PAGE_NOT_ZERO FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware_ram STACK_COMMAND: .cxr 0xffff9e890c4dea10 ; kb BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- *** Memory manager detected 122563 instance(s) of page corruption, target is likely to have memory corruption. 除此之外前两天还有一段这样：ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. FAULTING_MODULE: fffff8054e800000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUGCHECK_STR: 0x1a_41792 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 0 BAD_PAGES_DETECTED: 26653 LAST_CONTROL_TRANSFER: from fffff8054ea3eb2a to fffff8054ebf88c0 STACK_TEXT: ffff8206`1b826c88 fffff805`4ea3eb2a : 00000000`0000001a 00000000`00041792 fffff6bf`fe651b08 00000000`00001000 : nt+0x3f88c0 ffff8206`1b826c90 00000000`0000001a : 00000000`00041792 fffff6bf`fe651b08 00000000`00001000 00000000`00000000 : nt+0x23eb2a ffff8206`1b826c98 00000000`00041792 : fffff6bf`fe651b08 00000000`00001000 00000000`00000000 00000000`00000000 : 0x1a ffff8206`1b826ca0 fffff6bf`fe651b08 : 00000000`00001000 00000000`00000000 00000000`00000000 ffffc604`e0043700 : 0x41792 ffff8206`1b826ca8 00000000`00001000 : 00000000`00000000 00000000`00000000 ffffc604`e0043700 00000000`00000000 : 0xfffff6bf`fe651b08 ffff8206`1b826cb0 00000000`00000000 : 00000000`00000000 ffffc604`e0043700 00000000`00000000 00000000`00000000 : 0x1000 STACK_COMMAND: kb SYMBOL_NAME: PAGE_NOT_ZERO FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware_ram BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- *** Memory manager detected 157267 instance(s) of page corruption, target is likely to have memory corruption.嗨，保罗，来帮助你解决你的问题的。转储文件报告指示“hardware_ram”。RAM很可能有故障。我建议您使用MEMTest86测试RAM。确保至少有8次完整的通行证，以获得近乎决定性的结果。请按照以下链接中的指南进行操作。https://www-tenforums-com.translate.goog/tutori.让我知道结果。谢谢。
嗨，保罗，来帮助你解决你的问题的。转储文件报告指示“hardware_ram”。RAM很可能有故障。我建议您使用MEMTest86测试RAM。确保至少有8次完整的通行证，以获得近乎决定性的结果。请按照以下链接中的指南进行操作。https://www-tenforums-com.translate.goog/tutori.让我知道结果。谢谢。
微信小程序
微信扫一扫体验
投稿
微信公众账号
微信扫一扫加关注
评论 返回
顶部