WinDbg Not Loading Properly


  1. Posts : 42
    Windows 7 64bit
       #1

    WinDbg Not Loading Properly


    Hi,

    I have a new PC and I have installed WinDbg. Although when I open a Crash Dump it doesn't load past
    Code:
    Loading User Symbols
    Loading unloaded module list
    I have set the symbol path to the same as I used to have it when it worked fine.
    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [T:\CF\100614-24835-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: symsrv*symsrv.dll*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
    Machine Name:
    Kernel base = 0x82c08000 PsLoadedModuleList = 0x82d514d0
    Debug session time: Fri Oct  3 15:32:06.397 2014 (UTC + 0:00)
    System Uptime: 0 days 8:29:48.589
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..................................
    Loading User Symbols
    Loading unloaded module list
    ....................
    I have tried a different symbol path (One that I found on here) and that didn't solve the issue either.
    I have also reinstalled it a few times.

    Any help is appreciated!

    Thanks! :)
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hi callumm.

    Have you got windbg installed earlier, later uninstalled it and reinstalled it again?

    If so, uninstall windbg again. Open regedit, search for all windbg entries manually and delete them all, specially all the workspaces and symbol caches entries. Delete the existing symbols folder, too. Then set up windbg from scratch again.

    BTW, sometimes the private symbols are beyond our access. In that case windbg may give such an output. The third dump (stop 0x9F one) of this thread gives symbol error to me, too. It is a private symbol.

    Visit some random threads. Get the dumps. If all are providing symbol errors, follow the first set of the instructions. Otherwise dont worry.
      My Computer


  3. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #3

    How long is WinDBG staying like that? Symbols have to be downloaded all over again if it's a brand new install and sometimes they can take a while. Unless you retained your old Symbols folder you need to download them all over again.
      My Computer


  4. Posts : 42
    Windows 7 64bit
    Thread Starter
       #4

    Arc said:
    Hi callumm.

    Have you got windbg installed earlier, later uninstalled it and reinstalled it again?

    If so, uninstall windbg again. Open regedit, search for all windbg entries manually and delete them all, specially all the workspaces and symbol caches entries. Delete the existing symbols folder, too. Then set up windbg from scratch again.

    BTW, sometimes the private symbols are beyond our access. In that case windbg may give such an output. The third dump (stop 0x9F one) of this thread gives symbol error to me, too. It is a private symbol.

    Visit some random threads. Get the dumps. If all are providing symbol errors, follow the first set of the instructions. Otherwise dont worry.
    Hi,
    Yeah I installed it the first time and opened a Minidump file without settings the symbols
    I can get past by !analyze -v, thanks for your suggestion I will try that :)
      My Computer


  5. Posts : 42
    Windows 7 64bit
    Thread Starter
       #5

    Arc said:
    Hi callumm.

    Have you got windbg installed earlier, later uninstalled it and reinstalled it again?

    If so, uninstall windbg again. Open regedit, search for all windbg entries manually and delete them all, specially all the workspaces and symbol caches entries. Delete the existing symbols folder, too. Then set up windbg from scratch again.

    BTW, sometimes the private symbols are beyond our access. In that case windbg may give such an output. The third dump (stop 0x9F one) of this thread gives symbol error to me, too. It is a private symbol.

    Visit some random threads. Get the dumps. If all are providing symbol errors, follow the first set of the instructions. Otherwise dont worry.
    Ok, it seems to be ok now and will run through! Although I have just opened up a Minidump and this came through
    Code:
    ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
    
    DISK_HARDWARE_ERROR: There was error with disk hardware
    
    BUGCHECK_STR:  0x7a_c000000e
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff8800399c870 -- (.trap 0xfffff8800399c870)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff8a00440c768 rbx=0000000000000000 rcx=fffff8a00440c758
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880019ceba0 rsp=fffff8800399ca08 rbp=fffff8a00440c720
     r8=0000000000000000  r9=0000000000000000 r10=fffff880019ceba0
    r11=fffff8a00440c768 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    rdyboost!SmdEtwEnableCallback:
    fffff880`019ceba0 0000            add     byte ptr [rax],al ds:fffff8a0`0440c768=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002f465d2 to fffff80002ed3540
    
    STACK_TEXT:  
    fffff880`0399c558 fffff800`02f465d2 : 00000000`0000007a fffff6fc`4000ce70 ffffffff`c000000e 00000001`006f7860 : nt!KeBugCheckEx
    fffff880`0399c560 fffff800`02efa56f : fffffa80`03a49010 fffff880`0399c6d0 fffff800`03110540 fffffa80`03a49010 : nt! ?? ::FNODOBFM::`string'+0x36ada
    fffff880`0399c640 fffff800`02ee0bb9 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffffa80`0399d450 : nt!MiIssueHardFault+0x28b
    fffff880`0399c710 fffff800`02ed166e : 00000000`00000008 fffff880`019ceba0 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x1399
    fffff880`0399c870 fffff880`019ceba0 : fffff800`0312de0b fffff8a0`0440c7a0 00000000`00000090 fffffa80`03a35010 : nt!KiPageFault+0x16e
    fffff880`0399ca08 fffff800`0312de0b : fffff8a0`0440c7a0 00000000`00000090 fffffa80`03a35010 00000000`000007ff : rdyboost!SmdEtwEnableCallback
    fffff880`0399ca10 fffff800`032828e6 : fffffa80`03a34750 fffffa80`03a34778 fffffa80`04102c40 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x1215d
    fffff880`0399cac0 fffff800`03321328 : fffffa80`03a32780 fffff8a0`0440c720 00000000`00000000 00000000`00000000 : nt!EtwpDisableTraceProviders+0x1a6
    fffff880`0399cb40 fffff800`0322d616 : fffffa80`03a30000 00000000`00000000 00000000`c0000001 fffffa80`03a8f020 : nt!EtwpStopLoggerInstance+0x58
    fffff880`0399cb80 fffff800`03171d6a : 3b99793d`1f13b925 fffffa80`03a33040 00000000`00000080 fffffa80`0399d450 : nt! ?? ::NNGAKEGL::`string'+0x3f8d3
    fffff880`0399cc00 fffff800`02ec4266 : fffff880`009f1180 fffffa80`03a33040 fffffa80`039ce040 3cca8fdc`ce099bb3 : nt!PspSystemThreadStartup+0x5a
    fffff880`0399cc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !rdyboost
        fffff880019ce000-fffff880019ce03c  61 bytes - rdyboost!SmdContentsUpdateRequestPrepare+a8
    	[ 85 ff 74 09 48 8b cf ff:00 00 00 00 00 00 00 00 ]
        fffff880019ce03f-fffff880019ce055  23 bytes - rdyboost!SmdContentsUpdateRangeConvert+f (+0x3f)
    	[ 23 42 0c 44 0f b6 d8 45:00 00 00 00 00 00 00 00 ]
        fffff880019ce058-fffff880019ce061  10 bytes - rdyboost!SmdContentsUpdateRangeConvert+28 (+0x19)
    	[ 49 c1 e9 0c 4c 8d 94 08:00 00 00 00 00 00 00 00 ]
        fffff880019ce064-fffff880019ce076  19 bytes - rdyboost!SmdContentsUpdateRangeConvert+34 (+0x0c)
    	[ 49 c1 ea 0c 41 8b c2 c1:00 00 00 00 00 00 00 00 ]
        fffff880019ce07b - rdyboost!SmdContentsUpdateRangeConvert+4b (+0x17)
    	[ 01:00 ]
        fffff880019ce07f-fffff880019ce09f  33 bytes - rdyboost!SmdContentsUpdateRangeConvert+4f (+0x04)
    	[ 49 03 c1 48 3b c1 76 0b:00 00 00 00 00 00 00 00 ]
        fffff880019ce0a3-fffff880019ce0de  60 bytes - rdyboost!SmdContentsUpdateRangeConvert+73 (+0x24)
    	[ 41 8b c0 c3 cc cc cc cc:00 00 00 00 00 00 00 00 ]
        fffff880019ce0e2-fffff880019ce0ef  14 bytes - rdyboost!SmdPopulationStoresSpaceCheck+32 (+0x3f)
    	[ 41 d3 e1 41 8b c1 f7 d0:00 00 00 00 00 00 00 00 ]
        fffff880019ce0f2 - rdyboost!SmdPopulationStoresSpaceCheck+42 (+0x10)
    	[ 10:00 ]
        fffff880019ce0f4-fffff880019ce0f8  5 bytes - rdyboost!SmdPopulationStoresSpaceCheck+44 (+0x02)
    	[ 72 0b 83 24 8f:00 00 00 00 00 ]
        fffff880019ce0fa-fffff880019ce10b  18 bytes - rdyboost!SmdPopulationStoresSpaceCheck+4a (+0x06)
    	[ ff 44 8f 20 41 0b f1 45:00 00 00 00 00 00 00 00 ]
        fffff880019ce10e-fffff880019ce124  23 bytes - rdyboost!SmdPopulationStoresSpaceCheck+5e (+0x14)
    	[ 8b 47 44 8b d6 49 8b ce:00 00 00 00 00 00 00 00 ]
        fffff880019ce128-fffff880019ce135  14 bytes - rdyboost!SmdPopulationStoresSpaceCheck+78 (+0x1a)
    	[ e8 ff ee fe ff 44 8b d8:00 00 00 00 00 00 00 00 ]
        fffff880019ce138-fffff880019ce13a  3 bytes - rdyboost!SmdPopulationStoresSpaceCheck+88 (+0x10)
    	[ bb 02 01:00 00 00 ]
        fffff880019ce13d-fffff880019ce14d  17 bytes - rdyboost!SmdPopulationStoresSpaceCheck+8d (+0x05)
    	[ 45 8b e3 45 0f bc d4 41:00 00 00 00 00 00 00 00 ]
        fffff880019ce151-fffff880019ce161  17 bytes - rdyboost!SmdPopulationStoresSpaceCheck+a1 (+0x14)
    	[ 42 f6 44 97 20 0f 4a 8b:00 00 00 00 00 00 00 00 ]
        fffff880019ce165-fffff880019ce167  3 bytes - rdyboost!SmdPopulationStoresSpaceCheck+b5 (+0x14)
    	[ 0f 84 95:00 00 00 ]
        fffff880019ce16b-fffff880019ce16f  5 bytes - rdyboost!SmdPopulationStoresSpaceCheck+bb (+0x06)
    	[ 4c 8b 8a 80 01:00 00 00 00 00 ]
        fffff880019ce172-fffff880019ce176  5 bytes - rdyboost!SmdPopulationStoresSpaceCheck+c2 (+0x07)
    	[ 48 81 c2 a0 01:00 00 00 00 00 ]
        fffff880019ce179-fffff880019ce17c  4 bytes - rdyboost!SmdPopulationStoresSpaceCheck+c9 (+0x07)
    	[ 4c 8d 82 90:00 00 00 00 ]
        fffff880019ce180-fffff880019ce18c  13 bytes - rdyboost!SmdPopulationStoresSpaceCheck+d0 (+0x07)
    	[ 49 3b d0 73 7b 8b 02 83:00 00 00 00 00 00 00 00 ]
        fffff880019ce18e - rdyboost!SmdPopulationStoresSpaceCheck+de (+0x0e)
    	[ 80:00 ]
        fffff880019ce191-fffff880019ce1ab  27 bytes - rdyboost!SmdPopulationStoresSpaceCheck+e1 (+0x03)
    	[ 66 41 85 2c 41 74 02 ff:00 00 00 00 00 00 00 00 ]
        fffff880019ce1b0-fffff880019ce1b5  6 bytes - rdyboost!SmdPopulationStoresSpaceCheck+100 (+0x1f)
    	[ 74 4e 83 ba 30 02:00 00 00 00 00 00 ]
        fffff880019ce1b8-fffff880019ce1c2  11 bytes - rdyboost!SmdPopulationStoresSpaceCheck+108 (+0x08)
    	[ ff 75 04 33 c9 eb 11 8b:00 00 00 00 00 00 00 00 ]
        fffff880019ce1c5-fffff880019ce1c7  3 bytes - rdyboost!SmdPopulationStoresSpaceCheck+115 (+0x0d)
    	[ 8b 8a f8:00 00 00 ]
        fffff880019ce1cb-fffff880019ce1d3  9 bytes - rdyboost!SmdPopulationStoresSpaceCheck+11b (+0x06)
    	[ c1 e0 07 2b c8 44 8b 82:00 00 00 00 00 00 00 00 ]
        fffff880019ce1d7-fffff880019ce1db  5 bytes - rdyboost!SmdPopulationStoresSpaceCheck+127 (+0x0c)
    	[ 48 81 c2 a0 01:00 00 00 00 00 ]
        fffff880019ce1de-fffff880019ce1e1  4 bytes - rdyboost!SmdPopulationStoresSpaceCheck+12e (+0x07)
    	[ 48 8d 82 90:00 00 00 00 ]
        fffff880019ce1e5-fffff880019ce1f9  21 bytes - rdyboost!SmdPopulationStoresSpaceCheck+135 (+0x07)
    	[ eb 0c 83 3a ff 75 03 41:00 00 00 00 00 00 00 00 ]
        fffff880019ce1fc - rdyboost!SmdPopulationStoresSpaceCheck+14c (+0x17)
    	[ 20:00 ]
        fffff880019ce1fe-fffff880019ce204  7 bytes - rdyboost!SmdPopulationStoresSpaceCheck+14e (+0x02)
    	[ 72 15 41 8b ca b8 01:00 00 00 00 00 00 00 ]
        fffff880019ce208-fffff880019ce229  34 bytes - rdyboost!SmdPopulationStoresSpaceCheck+158 (+0x0a)
    	[ d3 e0 f7 d0 44 23 e0 0f:00 00 00 00 00 00 00 00 ]
        fffff880019ce22d-fffff880019ce234  8 bytes - rdyboost!SmdPopulationStoresSpaceCheck+17d (+0x25)
    	[ 45 33 c9 48 8d 84 24 88:00 00 00 00 00 00 00 00 ]
        fffff880019ce238-fffff880019ce272  59 bytes - rdyboost!SmdPopulationStoresSpaceCheck+188 (+0x0b)
    	[ 45 33 c0 41 8d 51 07 49:00 00 00 00 00 00 00 00 ]
        fffff880019ce274-fffff880019ce279  6 bytes - rdyboost!SmdPopulationStoresSpaceCheck+1c4 (+0x3c)
    	[ c0 44 8b 84 24 90:00 00 00 00 00 00 ]
        fffff880019ce27d-fffff880019ce281  5 bytes - rdyboost!SmdPopulationStoresSpaceCheck+1cd (+0x09)
    	[ 0f bc cd ba 01:00 00 00 00 00 ]
        fffff880019ce285-fffff880019ce2aa  38 bytes - rdyboost!SmdPopulationStoresSpaceCheck+1d5 (+0x08)
    	[ 44 01 04 8f d3 e2 f7 d2:00 00 00 00 00 00 00 00 ]
        fffff880019ce2ac-fffff880019ce2db  48 bytes - rdyboost!SmdPopulationStoresSpaceCheck+1fc (+0x27)
    	[ c0 eb c6 33 db eb c2 cc:00 00 00 00 00 00 00 00 ]
        fffff880019ce2de-fffff880019ce2e2  5 bytes - rdyboost!SmdPopulationPerform+22 (+0x32)
    	[ 8b ac 24 f8 01:00 00 00 00 00 ]
        fffff880019ce2e5-fffff880019ce315  49 bytes - rdyboost!SmdPopulationPerform+29 (+0x07)
    	[ 41 8b f9 4d 8b f0 48 8b:00 00 00 00 00 00 00 00 ]
        fffff880019ce318-fffff880019ce31e  7 bytes - rdyboost!SmdPopulationPerform+5c (+0x33)
    	[ 33 d2 48 8d 8c 24 80:00 00 00 00 00 00 00 ]
        fffff880019ce322-fffff880019ce326  5 bytes - rdyboost!SmdPopulationPerform+66 (+0x0a)
    	[ c7 84 24 f8 01:00 00 00 00 00 ]
        fffff880019ce329 - rdyboost!SmdPopulationPerform+6d (+0x07)
    	[ 10:00 ]
        fffff880019ce32d-fffff880019ce33b  15 bytes - rdyboost!SmdPopulationPerform+71 (+0x04)
    	[ 44 8d 42 48 e8 ca 3c ff:00 00 00 00 00 00 00 00 ]
        fffff880019ce33e-fffff880019ce33f  2 bytes - rdyboost!SmdPopulationPerform+82 (+0x11)
    	[ 49 bb:00 00 ]
        fffff880019ce342 - rdyboost!SmdPopulationPerform+86 (+0x04)
    	[ 10:00 ]
        fffff880019ce346 - rdyboost!SmdPopulationPerform+8a (+0x04)
    	[ 10:00 ]
        fffff880019ce348-fffff880019ce34c  5 bytes - rdyboost!SmdPopulationPerform+8c (+0x02)
    	[ 4c 89 9c 24 80:00 00 00 00 00 ]
        fffff880019ce350-fffff880019ce354  5 bytes - rdyboost!SmdPopulationPerform+94 (+0x08)
    	[ 4c 89 9c 24 88:00 00 00 00 00 ]
    WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
    3591 errors : !rdyboost (fffff880019ce000-fffff880019cefff)
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MEMORY_CORRUPTOR:  LARGE_4096
    
    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096
    
    BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096
    
    Followup: memory_corruption
    Not sure if this is a problem with my WinDbg or its part of the error? I didn't type the command
    Code:
    !chkimg -lo 50 -d !rdyboost
    It just did it itself
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    No, it is not the problem of windbg.

    It is the part of analysis. Sometimes, if a minidump contain the data (mostly it does not), it analyzes it all automatically in the !analyze_v output.
      My Computer


  7. Posts : 42
    Windows 7 64bit
    Thread Starter
       #7

    Arc said:
    No, it is not the problem of windbg.

    It is the part of analysis. Sometimes, if a minidump contain the data (mostly it does not), it analyzes it all automatically in the !analyze_v output.
    Ok thanks! :)
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #8

    You are welcome. :)
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 09:38.
Find Us