Attachment 879391 Details for Bug 1081436 – debuginfo of memory dump

debuginfo of memory dump

debug.txt (text/plain), 8.66 KB, created by Xu Han on 2014-03-27 10:24:03 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Xu Han

Created: 2014-03-27 10:24:03 UTC

Size: 8.66 KB

patch

obsolete

>
>Microsoft (R) Windows Debugger Version 6.2.9200.16384 X86
>Copyright (c) Microsoft Corporation. All rights reserved.
>
>
>Loading Dump File [C:\Users\qiguo\Desktop\crash dump\MEMORY.DMP]
>Kernel Bitmap Dump File: Only kernel address space is 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+                                    *
>*********************************************************************
>*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
>Windows 8 Kernel Version 9200 MP (4 procs) Free x86 compatible
>Product: WinNt, suite: TerminalServer SingleUserTS
>Built by: 9200.16384.x86fre.win8_rtm.120725-1247
>Machine Name:
>Kernel base = 0x80e1d000 PsLoadedModuleList = 0x81007de8
>Debug session time: Thu Mar 27 09:40:55.670 2014 (UTC - 7:00)
>System Uptime: 0 days 0:02:39.580
>*********************************************************************
>* 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+                                    *
>*********************************************************************
>*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
>Loading Kernel Symbols
>...............................................................
>................................................................
>......................................................
>Loading User Symbols
>
>Loading unloaded module list
>..........
>*******************************************************************************
>*                                                                             *
>*                        Bugcheck Analysis                                    *
>*                                                                             *
>*******************************************************************************
>
>Use !analyze -v to get detailed debugging information.
>
>BugCheck D1, {4, 7, 0, 8201a39d}
>
>*** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
>***** Kernel symbols are WRONG. Please fix symbols to do analysis.
>
>*************************************************************************
>***                                                                   ***
>***                                                                   ***
>***    Either you specified an unqualified symbol, or your debugger   ***
>***    doesn't have full symbol information.  Unqualified symbol      ***
>***    resolution is turned off by default. Please either specify a   ***
>***    fully qualified symbol module!symbolname, or enable resolution ***
>***    of unqualified symbols by typing ".symopt- 100". Note that   ***
>***    enabling unqualified symbol resolution with network symbol     ***
>***    server shares in the symbol path may cause the debugger to     ***
>***    appear to hang for long periods of time when an incorrect      ***
>***    symbol name is typed or the network symbol server is down.     ***
>***                                                                   ***
>***    For some commands 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                                     ***
>***                                                                   ***
>*************************************************************************
>*** ERROR: Module load completed but symbols could not be loaded for viorng.sys
>*************************************************************************
>***                                                                   ***
>***                                                                   ***
>***    Either you specified an unqualified symbol, or your debugger   ***
>***    doesn't have full symbol information.  Unqualified symbol      ***
>***    resolution is turned off by default. Please either specify a   ***
>***    fully qualified symbol module!symbolname, or enable resolution ***
>***    of unqualified symbols by typing ".symopt- 100". Note that   ***
>***    enabling unqualified symbol resolution with network symbol     ***
>***    server shares in the symbol path may cause the debugger to     ***
>***    appear to hang for long periods of time when an incorrect      ***
>***    symbol name is typed or the network symbol server is down.     ***
>***                                                                   ***
>***    For some commands 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                                     ***
>***                                                                   ***
>*************************************************************************
>*************************************************************************
>***                                                                   ***
>***                                                                   ***
>***    Either you specified an unqualified symbol, or your debugger   ***
>***    doesn't have full symbol information.  Unqualified symbol      ***
>***    resolution is turned off by default. Please either specify a   ***
>***    fully qualified symbol module!symbolname, or enable resolution ***
>***    of unqualified symbols by typing ".symopt- 100". Note that   ***
>***    enabling unqualified symbol resolution with network symbol     ***
>***    server shares in the symbol path may cause the debugger to     ***
>***    appear to hang for long periods of time when an incorrect      ***
>***    symbol name is typed or the network symbol server is down.     ***
>***                                                                   ***
>***    For some commands 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                                     ***
>***                                                                   ***
>*************************************************************************
>Probably caused by : viorng.sys ( viorng+139d )
>
>Followup: MachineOwner
>---------

Actions: View

Attachments on bug 1081436: 879391 | 879392