Home >
other > Computer blue screen MOMORY. DMP appear this error have great god understand what reason be
Computer blue screen MOMORY. DMP appear this error have great god understand what reason be
Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading the Dump File (C: \ Users \ Administrator \ Desktop \ MEMORY DMP]
The Kernel Summary the Dump File: Only the Kernel address space is
Invalid Symbol search path is: * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* Symbol loading may be unreliable without a Symbol search path. *
* Use symfix and the debugger choose a symbol path. *
* After setting your symbol path, use the reload to refresh symbol locations. *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
The Executable search path is:
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* Symbols can not be the loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the x-y & lt; Symbol_path & gt; Argument the when starting the debugger. *
* using. Sympath and. Sympath + *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * ERROR: Symbol file could not be found. The Defaulted to export symbols for NTKRNLMP. Exe -
Windows 7 the Kernel Version 7601 (Service Pack 1) MP procs (4) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514 amd64fre. Win7sp1_rtm. 101119-1850
The Machine Name:
The Kernel base=0 xfffff800 ` 02 a66000 PsLoadedModuleList=0 xfffff800 ` 02 cabe90
The Debug session time: Thu Aug 15 04:10:48. 885 2019 (GMT + 8)
The System Uptime: 025
0 days 0:51:00.* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* Symbols can not be the loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the x-y & lt; Symbol_path & gt; Argument the when starting the debugger. *
* using. Sympath and. Sympath + *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * ERROR: Symbol file could not be found. The Defaulted to export symbols for NTKRNLMP. Exe -
Loading the Kernel Symbols
...
.
.
Loading User Symbols
PEB is paged out (PEB) Ldr=000007 ff ` fffd8018). Type ". Hh dbgerr001 "for details
Loading unloaded the module list
.
The context is partially valid. Only x86 user - mode context is available.
The wow64exts extension must be The loaded to access 32 - bit state.
. The load wow64exts will do this if you haven 't the loaded it already.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* *
* Bugcheck Analysis *
* *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
The Use! Analyze the -v to get the detailed was debugging information.
BugCheck A, {8, 2, 0, fffff80002a217f7}
* * * * * the Kernel symbols are WRONG. Both 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 (to the 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 * * *
* * * * * *
nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull