Windows 10: WinDBG - The Basics for Debugging Crash Dumps in Windows 10

Discus and support WinDBG - The Basics for Debugging Crash Dumps in Windows 10 in Windows 10 Tutorials to solve the problem; You should download some custom debugger extensions, most of them are build upon the native extensions but add more friendly formatting to the... Discussion in 'Windows 10 Tutorials' started by Boozad, May 9, 2015.

Page 3 of 3
  1. ABACULUS
    Abaculus Win User

    WinDBG - The Basics for Debugging Crash Dumps in Windows 10


    You should download some custom debugger extensions, most of them are build upon the native extensions but add more friendly formatting to the debugging output.

    I've attached the ProcDumpExt file for you.

    ProcDumpExt.zip
     
    Abaculus, Jul 23, 2017
    #31
  2. AXE0
    axe0 New Member

    Can't get it to load, I'm not familiair with loading extensions though.
    Code: 1: kd> !load procdumpext The call to LoadLibrary(procdumpext) failed, Win32 error 0n193 "%1 is not a valid Win32 application." Please check your debugger configuration and/or network access. 1: kd> .extpath Extension search path is: C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\WINXP;C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\winext;C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\winext\arcade;C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\pri;C:\Program Files (x86)\Windows Kits\10\Debuggers\x64;C:\Program Files (x86)\Windows Kits\10\Debuggers\x64;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;G:\Installaties\Skype\Phone\;G:\Installaties\NodeJS\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Android;G:\xampp\php;G:\Installaties\Git\cmd;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\ProgramData\ComposerSetup\bin;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Users\marti\AppData\Local\Microsoft\WindowsApps;C:\Users\marti\AppData\Roaming\npm;C:\Users\marti\AppData\Roaming\Composer\vendor\bin[/quote]
    WinDBG - The Basics for Debugging Crash Dumps in Windows 10 [​IMG]
     
    axe0, Jul 23, 2017
    #32
  3. ABACULUS
    Abaculus Win User
    Move the .dll file into the x86 folder and boot the x86 version of WinDbg, the extension should then load.

    I apoligise for my error, I took the x86 version from Windows 7 machine. I'm not sure if the ProcDumpExt.dll is still available? It was hosted on a Microsoft SkyDrive (OneDrive) account.

    Directory Path:

    Code: C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\ProcDumpExt.dll[/quote]
     
    Abaculus, Jul 23, 2017
    #33
  4. AXE0
    axe0 New Member

    WinDBG - The Basics for Debugging Crash Dumps in Windows 10

    It isn't available anymore, just checked.
     
    axe0, Jul 23, 2017
    #34
  5. AXE0
    axe0 New Member
    Will give it a proper try.

    What is HTCAND64?
    Code: Start memory scan : 0xfffff88003315e28 ($csp) End memory scan : 0xfffff88003317000 (Stack Base) rsp : 0xfffff88003315e28 : 0xfffff88000eb5790 : Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+0x70 rbp : 0xfffff88000ea02e0 : !da ""waiting for all inflight requests to be acknowledged on WDFQUEUE"" r11 : 0xfffff88003315e28 : 0xfffff88000eb5790 : Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+0x70 0xfffff88003315e28 : 0xfffff88000eb5790 : Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+0x70 0xfffff88003315e30 : 0xfffff88000ea0000 : !da ""Thread 0x%p is %s 0x%p."" 0xfffff88003315e40 : 0xfffff88000ea02e0 : !da ""waiting for all inflight requests to be acknowledged on WDFQUEUE"" 0xfffff88003315e68 : 0xfffff88000eb314d : Wdf01000!FxIoQueue::StopProcessingForPower+0x1ed 0xfffff88003315eb8 : 0xfffff88000ebfa6c : Wdf01000!FxPkgIo::StopProcessingForPower+0x22c 0xfffff88003315ec0 : 0xfffffa800c858c50 : dt Wdf01000!FxIoQueue 0xfffff88003315f00 : 0xfffff88000f35e10 : Wdf01000!FxPkgPnp::m_PowerD0ArmedForWakeOtherStates+0x30 0xfffff88003315f28 : 0xfffff88000f282cf : Wdf01000!FxPkgPnp:WinDBG - The Basics for Debugging Crash Dumps in Windows 10 :powerGotoD3Stopped+0x73 0xfffff88003315f38 : 0xfffff88003315f00 : 0xfffff88000f35e10 : Wdf01000!FxPkgPnp::m_PowerD0ArmedForWakeOtherStates+0x30 0xfffff88003315f88 : 0xfffff88000eb60f8 : Wdf01000!FxPkgPnp:WinDBG - The Basics for Debugging Crash Dumps in Windows 10 :powerEnterNewState+0x1d8 0xfffff88003315fa0 : 0xfffff88000f36100 : Wdf01000!FxPkgPnp::m_WdfPowerStates+0x280 0xfffff88003315fb0 : 0xfffff88000f35e10 : Wdf01000!FxPkgPnp::m_PowerD0ArmedForWakeOtherStates+0x30 0xfffff88003316048 : 0xfffff8000317bfea : nt!SeQueryInformationToken+0x4a 0xfffff88003316080 : 0xfffff88003316210 : 0xfffff88000f38910 : Wdf01000!FxPkgPnp::m_WdfPowerPolicyStates+0xb60 0xfffff88003316088 : 0xfffff80003155bb3 : nt!CmpGetValueData+0x73 0xfffff880033160c8 : 0xfffff88000f35e10 : Wdf01000!FxPkgPnp::m_PowerD0ArmedForWakeOtherStates+0x30 0xfffff880033160d8 : 0xfffff88000f35f60 : Wdf01000!FxPkgPnp::m_WdfPowerStates+0xe0 0xfffff880033160e8 : 0xfffff88000eb5da6 : Wdf01000!FxPkgPnp:WinDBG - The Basics for Debugging Crash Dumps in Windows 10 :powerProcessEventInner+0x13e 0xfffff880033160f0 : 0xfffff88000f35f60 : Wdf01000!FxPkgPnp::m_WdfPowerStates+0xe0 0xfffff88003316118 : 0xfffff88000ead027 : Wdf01000!FxWaitLockInternal::AcquireLock+0x47 0xfffff88003316158 : 0xfffff88000eb6627 : Wdf01000!FxPkgPnp:WinDBG - The Basics for Debugging Crash Dumps in Windows 10 :powerProcessEvent+0x1b3 0xfffff880033161a0 : 0xfffff88000f38910 : Wdf01000!FxPkgPnp::m_WdfPowerPolicyStates+0xb60 0xfffff880033161a8 : 0xfffff88003316330 : 0xfffff88000f499b0 : Wdf01000!WPP_GLOBAL_WDF_Control 0xfffff880033161b8 : 0xfffff88000eb0000 : Wdf01000!FxRequest::GetDeviceControlOutputMemoryObject+0x200 0xfffff880033161f0 : 0xfffff88003316330 : 0xfffff88000f499b0 : Wdf01000!WPP_GLOBAL_WDF_Control 0xfffff880033161f8 : 0xfffff88000f2e39f : Wdf01000!FxPkgPnp:WinDBG - The Basics for Debugging Crash Dumps in Windows 10 :powerPolStopping+0x1b 0xfffff88003316210 : 0xfffff88000f38910 : Wdf01000!FxPkgPnp::m_WdfPowerPolicyStates+0xb60 0xfffff88003316228 : 0xfffff88000eb2ae7 : Wdf01000!FxPkgPnp:WinDBG - The Basics for Debugging Crash Dumps in Windows 10 :powerPolicyEnterNewState+0x1d7 0xfffff88003316238 : 0xfffff88003316330 : 0xfffff88000f499b0 : Wdf01000!WPP_GLOBAL_WDF_Control 0xfffff88003316278 : 0xfffff80002fb3360 : nt!ExAllocatePoolWithTag+0x270 0xfffff880033162b8 : 0xfffff80002fb3fcd : nt!ExFreePoolWithTag+0x22d 0xfffff880033162d0 : 0xfffffa800d56e1a0 : !da "HTCAND64" 0xfffff880033162d8 : 0xfffff88000ea2a7a : Wdf01000!FxIFR+0x236 0xfffff880033162e8 : 0xfffff80002fb3fcd : nt!ExFreePoolWithTag+0x22d 0xfffff88003316330 : 0xfffff88000f499b0 : Wdf01000!WPP_GLOBAL_WDF_Control 0xfffff88003316348 : 0xfffff88000eb774c : Wdf01000!WPP_IFR_SF_q+0xb0 0xfffff88003316378 : 0xfffff88000f38a50 : Wdf01000!FxPkgPnp::m_WdfPowerPolicyStates+0xca0 0xfffff88003316388 : 0xfffff88000eb25b9 : Wdf01000!FxPkgPnp:WinDBG - The Basics for Debugging Crash Dumps in Windows 10 :powerPolicyProcessEventInner+0x145 0xfffff88003316390 : 0xfffff88000f38a50 : Wdf01000!FxPkgPnp::m_WdfPowerPolicyStates+0xca0 0xfffff880033163b8 : 0xfffff88000ead027 : Wdf01000!FxWaitLockInternal::AcquireLock+0x47 0xfffff880033163d8 : 0xfffff88000ea2a00 : Wdf01000!FxIFR+0x1bc 0xfffff880033163f8 : 0xfffff88000eb6a01 : Wdf01000!FxPkgPnp:WinDBG - The Basics for Debugging Crash Dumps in Windows 10 :powerPolicyProcessEvent+0x1c1 0xfffff88003316420 : 0xfffff88000f499b0 : Wdf01000!WPP_GLOBAL_WDF_Control 0xfffff88003316448 : 0xfffff88000eb5c44 : Wdf01000!WPP_IFR_SF_qqdd+0x130 0xfffff88003316480 : 0xfffff88000f37178 : Wdf01000!FxPkgPnp::m_PnpHardwareAvailableOtherStates+0x20 0xfffff88003316498 : 0xfffff88000f2bc9a : Wdf01000!FxPkgPnp:WinDBG - The Basics for Debugging Crash Dumps in Windows 10 :pnpEventFailedIoStarting+0xe 0xfffff880033164b8 : 0xfffff80003178246 : nt!ObpFreeObject+0x266 0xfffff880033164c8 : 0xfffff88000ec7df5 : Wdf01000!FxPkgPnp:WinDBG - The Basics for Debugging Crash Dumps in Windows 10 :pnpEnterNewState+0x1a1 0xfffff880033164f0 : 0xfffff88000f37178 : Wdf01000!FxPkgPnp::m_PnpHardwareAvailableOtherStates+0x20 0xfffff88003316538 : 0xfffff800031788f6 : nt!ExDestroyHandle+0x66 0xfffff88003316550 : 0xfffff88000f374d0 : Wdf01000!FxPkgPnp::m_WdfPnpStates+0x320 0xfffff88003316568 : 0xfffff88000ec7ac6 : Wdf01000!FxPkgPnp:WinDBG - The Basics for Debugging Crash Dumps in Windows 10 :pnpProcessEventInner+0x122 0xfffff88003316598 : 0xfffff88000ead027 : Wdf01000!FxWaitLockInternal::AcquireLock+0x47 0xfffff880033165b8 : 0xfffff88000ea2a00 : Wdf01000!FxIFR+0x1bc 0xfffff880033165d8 : 0xfffff88000ec7879 : Wdf01000!FxPkgPnp:WinDBG - The Basics for Debugging Crash Dumps in Windows 10 :pnpProcessEvent+0x18d 0xfffff88003316618 : 0xfffff88000f499b0 : Wdf01000!WPP_GLOBAL_WDF_Control 0xfffff88003316628 : 0xfffff88000ec76d0 : Wdf01000!WPP_IFR_SF_qqcq+0x130 0xfffff88003316678 : 0xfffff88000f2a6bd : Wdf01000!FxPkgFdo::_PnpSurpriseRemoval+0x25 0xfffff880033166a8 : 0xfffff88000ea25d7 : Wdf01000!FxPkgPnp:WinDBG - The Basics for Debugging Crash Dumps in Windows 10 :Dispatch+0x18f 0xfffff880033166d0 : 0xfffff88000f35d80 : Wdf01000!FxPkgPnp::GUID_POWER_THREAD_INTERFACE+0x80 0xfffff88003316708 : 0xfffff88000ea179a : Wdf01000!FxDevice:WinDBG - The Basics for Debugging Crash Dumps in Windows 10 :Dispatch+0x19a 0xfffff88003316748 : 0xfffff88000ea1866 : Wdf01000!FxDevice:WinDBG - The Basics for Debugging Crash Dumps in Windows 10 :DispatchWithLock+0xa6 0xfffff88003316788 : 0xfffff800030e2b11 : nt!IopSynchronousCall+0xe1 0xfffff880033167f8 : 0xfffff80003261791 : nt!IopRemoveDevice+0x101 0xfffff880033168b8 : 0xfffff8000325ffb8 : nt!PnpSurpriseRemoveLockedDeviceNode+0x128 0xfffff880033168e8 : 0xfffff800032189c0 : nt!PnpAllocateCriticalMemory+0x50 0xfffff880033168f8 : 0xfffff800032612d7 : nt!PnpDeleteLockedDeviceNode+0x37 0xfffff88003316928 : 0xfffff800032613f0 : nt!PnpDeleteLockedDeviceNodes+0xa0 0xfffff88003316998 : 0xfffff800032ff17f : nt!PnpProcessQueryRemoveAndEject+0x6cf 0xfffff88003316a88 : 0xfffff800030252f8 : nt!ExWorkerQueue+0x58 0xfffff88003316ad8 : 0xfffff800032ffd3c : nt!PnpProcessTargetDeviceEvent+0x4c 0xfffff88003316b38 : 0xfffff80003177e70 : nt!IopProcessWorkItem 0xfffff88003316b68 : 0xfffff80002e87195 : nt!ExpWorkerThread+0x111 0xfffff88003316b70 : 0xfffff800030e1978 : nt!PnpDeviceEventWorker 0xfffff88003316b80 : 0xfffff800030252f8 : nt!ExWorkerQueue+0x58 0xfffff88003316b88 : 0xfffff800030252f8 : nt!ExWorkerQueue+0x58 0xfffff88003316be0 : 0xfffff80002e87084 : nt!ExpWorkerThread 0xfffff88003316bf8 : 0xfffff80003115f12 : nt!PspSystemThreadStartup+0x5a 0xfffff88003316c38 : 0xfffff80002e6ede6 : nt!KiStartSystemThread+0x16[/quote]
     
    axe0, Jul 23, 2017
    #35
  6. ABACULUS
    Abaculus Win User
    It appears to be a string of some sort.
     
    Abaculus, Apr 4, 2018
    #36
Page 3 of 3
Thema:

WinDBG - The Basics for Debugging Crash Dumps in Windows 10

Loading...

  1. WinDBG - The Basics for Debugging Crash Dumps in Windows 10 - Similar Threads - WinDBG Basics Debugging

  2. Help understanding WinDbg Minidump debug

    in Windows 10 Gaming
    Help understanding WinDbg Minidump debug: 0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************KERNEL_SECURITY_CHECK_FAILURE 139A kernel component has corrupted a...

  3. Help understanding WinDbg Minidump debug

    in Windows 10 Software and Apps
    Help understanding WinDbg Minidump debug: 0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************KERNEL_SECURITY_CHECK_FAILURE 139A kernel component has corrupted a...

  4. Help understanding WinDbg Minidump debug

    in Windows 10 BSOD Crashes and Debugging
    Help understanding WinDbg Minidump debug: 0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************KERNEL_SECURITY_CHECK_FAILURE 139A kernel component has corrupted a...

  5. Windbg crashed while debugging process

    in Windows 10 BSOD Crashes and Debugging
    Windbg crashed while debugging process: Hello eveyone.I tried to debug Notepad.exe using Windbg. I set a breakpoint at Kernel32!CreateFileW, and everything was fine until I clicked on Notepad and the breakpoint was hit.I didn't even click on File-Open in the top left corner, but Windbg became not responding....

  6. Windbg crashed while debugging process

    in Windows 10 Gaming
    Windbg crashed while debugging process: Hello eveyone.I tried to debug Notepad.exe using Windbg. I set a breakpoint at Kernel32!CreateFileW, and everything was fine until I clicked on Notepad and the breakpoint was hit.I didn't even click on File-Open in the top left corner, but Windbg became not responding....

  7. Windbg crashed while debugging process

    in Windows 10 Software and Apps
    Windbg crashed while debugging process: Hello eveyone.I tried to debug Notepad.exe using Windbg. I set a breakpoint at Kernel32!CreateFileW, and everything was fine until I clicked on Notepad and the breakpoint was hit.I didn't even click on File-Open in the top left corner, but Windbg became not responding....

  8. System crashes during game - cannot open dump file with windbg

    in Windows 10 Software and Apps
    System crashes during game - cannot open dump file with windbg: Hello, I have two issues, the main one is that my system crashes when playing video games. When checking the event observer I see a dump file was created so I try opening it with windbg and that leads to my secondary issue. I cannot see anything in windbg when loading the...

  9. Need help Crash Dump Debugging

    in Windows 10 BSOD Crashes and Debugging
    Need help Crash Dump Debugging: So my PC has been BSOD like crazy in windows 10. I have tried debugging using WinDbg, all crash dump errors point towards ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1164c ) Please advice, what am I missing? I have attached the crash dump files. Thanks in advance....

  10. Help needed debugging crash dump file

    in Windows 10 BSOD Crashes and Debugging
    Help needed debugging crash dump file: I've been experiencing some random BSOD and freezes and managed to create crash dump files using driver verifier. Unfortunately I cannot read what driver is causing the BSOD's / freezes. Can someone please help me? Please ignore debug--PC-xxxx.zip The correct file...

Users found this page by searching for:

  1. waiting for all inflight requests to be acknowledged on WDFQUEUE

    ,

  2. windbg win 10 installieren