Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\baby\Desktop\031315-27253-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 argument when starting the debugger.
using .sympath and .sympath+
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
WARNING: Unable to verify timestamp for ntkrnlpa.exe
ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18741.x86fre.win7sp1_gdr.150202-1526
Machine Name:
Kernel base = 0x84415000 PsLoadedModuleList = 0x8455f5b0
Debug session time: Fri Mar 13 18:27:10.552 2015 (GMT+8)
System Uptime: 0 days 10:17:16.598
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 argument when starting the debugger.
using .sympath and .sympath+
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
WARNING: Unable to verify timestamp for ntkrnlpa.exe
ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
..........
Bugcheck Analysis
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 8, 0}
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
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 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 argument when starting the debugger.
using .sympath and .sympath+
Probably caused by : ntkrnlpa.exe ( nt+40b4f )
