Windows 8 and 8.1 Forums


Symbol Loading Error In WinDBG while debugging dump files

  1. #1


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)

    Symbol Loading Error In WinDBG while debugging dump files


    Hello there,

    I am trying to debug some Crash Dump Files and I have not been able to load the Dump file properly because the WINDBG says the following error :-

    Loading Dump File [C:\Users\Blueelvis_RoXXX\Desktop\030114-6531-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 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    Machine Name:
    Kernel base = 0xfffff800`d808c000 PsLoadedModuleList = 0xfffff800`d8350990
    Debug session time: Sun Mar 2 07:06:49.701 2014 (UTC + 5:30)
    System Uptime: 0 days 0:01:27.385
    *********************************************************************
    * 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
    Loading unloaded module list
    .......


    ************* Symbol Loading Error Summary **************
    Module name Error
    ntoskrnl The system cannot find the file specified


    You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
    You should also verify that your symbol search path (.sympath) is correct.
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************


    Use !analyze -v to get detailed debugging information.


    BugCheck D1, {ffffd0002964b000, 2, 0, fffff800025e9353}


    ***** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    Unable to load image \SystemRoot\system32\DRIVERS\e22w8x64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for e22w8x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e22w8x64.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 : e22w8x64.sys ( e22w8x64+1c353 )


    Followup: MachineOwner
    ---------


    I have downloaded and installed the Symbols file separately and set the Source File Path as well but don't know it is not working still. Any help will be appreciated.

    System Specs :-
    Windows 8 Pro
    Toshiba Satellite C640D
    4 GB RAM
    2.4GhZ Core I5 2430M
    500 GB HDD

      My System SpecsSystem Spec

  2. #2


    Posts : 1,875
    Windows 10 Pro Prieview x64


    In the debugger, add the symbol search path (file > symbol search path) and add

    SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

    You can replace c:\symbols part with another directory if you want. That should help.
      My System SpecsSystem Spec

  3. #3


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi there,

    Thanks for the quick reply. Now the error it is throwing up is

    Use !analyze -v to get detailed debugging information.


    BugCheck D1, {ffffd0002964b000, 2, 0, fffff800025e9353}


    *** WARNING: Unable to verify timestamp for e22w8x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e22w8x64.sys

    Furthermore, the Debugger command prompt is saying Debugee Not Connected.
      My System SpecsSystem Spec

  4. #4


    Posts : 1,875
    Windows 10 Pro Prieview x64


    It looks like this IRQL_NOT_LESS_OR_EQUAL random BSODs

    You could try to update the killer network driver or (disable the service).

    EDIT: If you want more assistance for BSOD please attach the output described here Blue Screen of Death (BSOD) Posting Instructions

    Good luck
      My System SpecsSystem Spec

Symbol Loading Error In WinDBG while debugging dump files
Related Threads
Please help analyse BSoD dump files in BSOD Crashes and Debugging
Recently I have had a few crashes on my windows 8.1 laptop. I have tried to attach the 3 most recent zipped dump files, but they're 100mb and too big to attach, so have uploaded the most recent one to here and the previous crash to here I have attached screen shots of the system information...
Hello! I've done a forum search before opening a new topic, and the solutions I found in other topics are for reading BSOD minidumps, not application dump files, so for example BlueScreenView won't do me any good. I have a 3rd party application that crashes frequently. The last time I created...
Recently, my laptop has run into a multitude of problems, but most of them have been solved by Dell. Today, I checked my device manager and I saw the yield symbol and an error on my monitor (called "Generic PnP Monitor), but nothing seems to be wrong with it as far as I know. I am thinking the...
Solved Unable to make WinDBG analyze the Dump files in BSOD Crashes and Debugging
Hello, I am trying to debug some crash dumps which all point to NTOSKRNL.EXE but I am unable to debug or even analyze it because the WinDBG throws me an error :- ************* Symbol Path validation summary **************Response Time (ms) Location OK ...
Solved How to open .dmp files with WinDbg in BSOD Crashes and Debugging
Is it possible to open .dmp files by double clicking on them? I've associated them with WinDbg.exe but they don't open - I get the error below. I can only open them with ctrl + D. Is it possible?
25954 Hello everyone recently i've been experiencing the happy face blue screen of death... randomly too started yesterday and now one today happened while i was sleeping and the computer was idle. I'm running Windows 8 on the Alienware Aurora R4 the specs are stock but i'll list them anyways I7...
Dump files in BSOD Crashes and Debugging
Where are the dump files stored in Windows 8? I searched the whole drive and I cannot find them, if anyone know the answer please let me know. Thank you.
Eight Forums Android App Eight Forums IOS App Follow us on Facebook