Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [I:\031423-20265-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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 10240 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10240.16841.amd64fre.th1_st1.160408-1853
Machine Name:
Kernel base = 0xfffff8030ee77000 PsLoadedModuleList = 0xfffff803
0f19c070
Debug session time: Tue Mar 14 16:26:44.967 2023 (GMT+8)
System Uptime: 0 days 2:21:39.740
- 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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...................................
Loading User Symbols
Use !analyze -v to get detailed debugging information.
BugCheck 12B, {ffffffffc00002c4, 710, 89020bd500, ffffd00027b00000}
***** 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 ( REGION_PAGED_OUT )
Followup: MachineOwner