Windows 10: How to read output from WinDBG of dump file to determine root cause of recent crash?

Discus and support How to read output from WinDBG of dump file to determine root cause of recent crash? in Windows 10 Gaming to solve the problem; For the past few weeks i've been getting windows crashes, as in the windows would just freeze and stop then i would need to force shutdown the PC.... Discussion in 'Windows 10 Gaming' started by kamaljit SinghBhullar, Nov 23, 2022.

  1. KAMALJIT SINGHBHULLAR
    kamaljit SinghBhullar Win User

    How to read output from WinDBG of dump file to determine root cause of recent crash?


    For the past few weeks i've been getting windows crashes, as in the windows would just freeze and stop then i would need to force shutdown the PC. Using WinDBG with the command `!analyize -v` I'm not able to make heads or tails of the output.Link to dump file: https://1drv.ms/u/s!AtjlWyM0kYB-gZ8VqnSNnF9yYIQtRw?e=wILLUKoutput below: Microsoft R Windows Debugger Version 10.0.25200.1003 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\MEMORY.DMP]

    :)
     
    kamaljit SinghBhullar, Nov 23, 2022
    #1
  2. ALEXONDAX_1
    AlexOnDAX_1 Win User

    How to read output from WinDBG of dump file to determine root cause of recent crash?

    I somewhat frequently have random crashes at night when I'm not using my PC that are unrelated to Windows Update. I check the event log and it's "WER-SystemErrorReporting" - 1001 rebooting from a bugcheck. I built the PC myself and it's 6 months old with
    all brand new top of the line components...no overclocking, vanilla config.

    Using WinDBG with the command `!analyize -v` I'm not able to make heads or tails of the output. It looks like a kernel crash with an invalid pointer. My gut tells me it might be related to my graphics card...but not sure.

    Here is a link to the minidump and the output is below:
    https://1drv.ms/u/s!Apb-0nSp-ptA9V5HgQTPgmtoeVeZ

    Code:
    Microsoft (R) Windows Debugger Version 10.0.18869.1002 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.************* Path validation summary **************Response                         Time (ms)     LocationDeferred                                       srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 18362 MP (32 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 18362.1.amd64fre.19h1_release.190318-1202Machine Name:Kernel base = 0xfffff800`64e00000 PsLoadedModuleList = 0xfffff800`652432b0Debug session time: Thu May 30 21:14:15.127 2019 (UTC - 7:00)System Uptime: 0 days 11:33:17.796Loading Kernel Symbols.......................................................................Page 20434b9 not present in the dump file. Type ".hh dbgerr004" for details..............................................................................................................................................Loading User SymbolsLoading unloaded module list..............For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff800`64fbc8a0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff800`69b00c70=00000000000001ca0: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************SYNTHETIC_WATCHDOG_TIMEOUT (1ca)A system wide watchdog has expired. This indicates that the systemis hung and not processing timer ticks.Arguments:Arg1: 000000001b39cd12, The time since the watchdog was last reset, in interrupt time.Arg2: 00000061186695e2, The current interrupt time.Arg3: 000000611869a42e, The current QPC timestamp.Arg4: 0000000000000004, The index of the clock processor.Debugging Details:------------------KEY_VALUES_STRING: 1    Key  : Analysis.CPU.Sec    Value: 7    Key  : Analysis.Elapsed.Sec    Value: 9    Key  : Analysis.Memory.CommitPeak.Mb    Value: 77PROCESSES_ANALYSIS: 1SERVICE_ANALYSIS: 1STACKHASH_ANALYSIS: 1TIMELINE_ANALYSIS: 1DUMP_CLASS: 1DUMP_QUALIFIER: 401BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202SYSTEM_PRODUCT_NAME:  To Be Filled By O.E.M.SYSTEM_SKU:  To Be Filled By O.E.M.SYSTEM_VERSION:  To Be Filled By O.E.M.BIOS_VENDOR:  American Megatrends Inc.BIOS_VERSION:  P3.30BIOS_DATE:  08/14/2018BASEBOARD_MANUFACTURER:  ASRockBASEBOARD_PRODUCT:  X399 TaichiBASEBOARD_VERSION:                        DUMP_TYPE:  1BUGCHECK_P1: 1b39cd12BUGCHECK_P2: 61186695e2BUGCHECK_P3: 611869a42eBUGCHECK_P4: 4CPU_COUNT: 20CPU_MHZ: da5CPU_VENDOR:  AuthenticAMDCPU_FAMILY: 17CPU_MODEL: 8CPU_STEPPING: 2BLACKBOXBSD: 1 (!blackboxbsd)BLACKBOXNTFS: 1 (!blackboxntfs)BLACKBOXPNP: 1 (!blackboxpnp)BLACKBOXWINLOGON: 1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTBUGCHECK_STR:  0x1CAPROCESS_NAME:  SystemCURRENT_IRQL:  fANALYSIS_SESSION_HOST:  MyComputerNameANALYSIS_SESSION_TIME:  05-31-2019 08:50:54.0461ANALYSIS_VERSION: 10.0.18869.1002 amd64freBAD_STACK_POINTER:  fffff80069b00c68LAST_CONTROL_TRANSFER:  from fffff800658e6315 to fffff80064fbc8a0STACK_TEXT:  fffff800`69b00c68 fffff800`658e6315 : 00000000`000001ca 00000000`1b39cd12 00000061`186695e2 00000061`1869a42e : nt!KeBugCheckExfffff800`69b00c70 fffff800`658d039a : 00000061`1869a42e 00000000`00000001 fffff800`65150614 00000000`00000082 : hal!HalpWatchdogCheckPreResetNMI+0xd5fffff800`69b00cb0 fffff800`650a1e8b : 00000000`00000001 00000061`18483c1b fffff800`62eae180 fffff800`650b2f10 : hal!HalpPreprocessNmi+0x114eafffff800`69b00ce0 fffff800`64fc7d42 : 00000000`00000001 fffff800`69b00ef0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0xcbfffff800`69b00d30 fffff800`64fc7b11 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82fffff800`69b00e70 fffff800`65100bce : 00000000`00000000 00008494`9de72f0a 00000000`00000000 00000061`18483c1b : nt!KiNmiInterrupt+0x211fffff800`69ae77a0 fffff800`64e21cdc : fffff800`65100bf0 00000000`00000000 ffff998b`cc41d060 00000000`00000071 : nt!PpmIdleGuestExecute+0x1efffff800`69ae77e0 fffff800`64e2142e : 00000000`00000003 00000000`00000002 00000000`00000001 00000000`00000000 : nt!PpmIdleExecuteTransition+0x70cfffff800`69ae7b00 fffff800`64fc0328 : 00000000`00000000 fffff800`62eae180 ffff998b`c833e040 00000000`00001784 : nt!PoIdle+0x36efffff800`69ae7c60 00000000`00000000 : fffff800`69ae8000 fffff800`69ae2000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x48THREAD_SHA1_HASH_MOD_FUNC:  cb522721ccf98392c0a19a23914952c2ac4c66ecTHREAD_SHA1_HASH_MOD_FUNC_OFFSET:  820b90a5d7e9eccb2fa0a02e4a9162d0c9225d80THREAD_SHA1_HASH_MOD:  77e3653e8f322fbd447ccc02351d9fed3c4e96beFOLLOWUP_IP: nt!KiProcessNMI+cbfffff800`650a1e8b 488b3dce801a00  mov     rdi,qword ptr [nt!KiNmiCallbackListHead (fffff800`65249f60)]FAULT_INSTR_CODE:  ce3d8b48SYMBOL_STACK_INDEX:  3SYMBOL_NAME:  nt!KiProcessNMI+cbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntIMAGE_NAME:  ntkrnlmp.exeDEBUG_FLR_IMAGE_TIMESTAMP:  0STACK_COMMAND:  .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET:  cbFAILURE_BUCKET_ID:  0x1CA_STACKPTR_ERROR_nt!KiProcessNMIBUCKET_ID:  0x1CA_STACKPTR_ERROR_nt!KiProcessNMIPRIMARY_PROBLEM_CLASS:  0x1CA_STACKPTR_ERROR_nt!KiProcessNMITARGET_TIME:  2019-05-31T04:14:15.000ZOSBUILD:  18362OSSERVICEPACK:  0SERVICEPACK_NUMBER: 0OS_REVISION: 0SUITE_MASK:  272PRODUCT_TYPE:  1OSPLATFORM_TYPE:  x64OSNAME:  Windows 10OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTSOS_LOCALE:  USER_LCID:  0OSBUILD_TIMESTAMP:  unknown_dateBUILDDATESTAMP_STR:  190318-1202BUILDLAB_STR:  19h1_releaseBUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202ANALYSIS_SESSION_ELAPSED_TIME:  25d3ANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:0x1ca_stackptr_error_nt!kiprocessnmiFAILURE_ID_HASH:  {09a889cd-f940-6da5-9668-0c0c98a7d643}Followup:     MachineOwner---------
     
    AlexOnDAX_1, Nov 23, 2022
    #2
  3. VIJAY_VERMA
    Vijay_Verma Win User
    How to read output from WinDBG of dump file to determine root cause of recent crash?

    Hi AlexOnDAX_1

    Greetings! I am Vijay, an Independent Advisor. I am here to work with you on this problem.

    A. Analysis Results

    File Name: 053019-9375-01.dmp

    SYNTHETIC_WATCHDOG_TIMEOUT (1ca)

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    IMAGE_NAME: ntkrnlmp.exe

    B. Third Party Drivers

    None

    C. Recommendations

    1. Create a system restore point so that if something wrong happens you can revert.

    Type restore point in Cortana Search > Create a Restore point > Check whether against your drive, Protection is ON or not. If not ON, click Configure button below to Make it ON > Now press Create to create a restore point

    2. Some third party drivers are causing BSODs. To know if a third party driver is one of the causes - Enable Driver Verifier and generate dump files and upload to Onedrive and share the link here (Don't forget to turn off Driver Verifier after the job is done).
    Do read the instructions carefully particularly how to get back into Windows when you get the crash.

    https://www.tenforums.com/tutorials/5470-enable...

    Disclaimer - This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product
    advertised on the site before you decide to download and install it.

    Do let me know if you have any more question or require further help.
     
    Vijay_Verma, Nov 23, 2022
    #3
  4. BAPTISTE1991
    Baptiste1991 Win User

    How to read output from WinDBG of dump file to determine root cause of recent crash?

    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 dump file, it is like a blank slate as if the file was not loaded at all.

    If someone can tell me how I can bypass that issue in windbg and ultimately also tell me what is wrong with my system through analyzing the dump file I would be grateful.

    OneDrive link to the dump file : https://1drv.ms/u/s!At9piAUd9C7VqSKiMyBQQcEK2BAw?e=C8pL7c
     
    Baptiste1991, Nov 23, 2022
    #4
Thema:

How to read output from WinDBG of dump file to determine root cause of recent crash?

Loading...

  1. How to read output from WinDBG of dump file to determine root cause of recent crash? - Similar Threads - read output WinDBG

  2. Is there a way to identify the root cause of the BSOD when there's no crash dump file?

    in Windows 10 Gaming
    Is there a way to identify the root cause of the BSOD when there's no crash dump file?: Laptop is ASUS TUF FX505DT, bought back in January 2020. Been in use ever since.All parts are the stock parts except for:The monitor - I had it replaced after dead pixels suddenly appeared and covered half of the monitor back in 2021.SSD - I purchased and installed an...

  3. Is there a way to identify the root cause of the BSOD when there's no crash dump file?

    in Windows 10 Software and Apps
    Is there a way to identify the root cause of the BSOD when there's no crash dump file?: Laptop is ASUS TUF FX505DT, bought back in January 2020. Been in use ever since.All parts are the stock parts except for:The monitor - I had it replaced after dead pixels suddenly appeared and covered half of the monitor back in 2021.SSD - I purchased and installed an...

  4. Is there a way to identify the root cause of the BSOD when there's no crash dump file?

    in Windows 10 BSOD Crashes and Debugging
    Is there a way to identify the root cause of the BSOD when there's no crash dump file?: Laptop is ASUS TUF FX505DT, bought back in January 2020. Been in use ever since.All parts are the stock parts except for:The monitor - I had it replaced after dead pixels suddenly appeared and covered half of the monitor back in 2021.SSD - I purchased and installed an...

  5. How to read output from WinDBG of dump file to determine root cause of recent crash?

    in Windows 10 BSOD Crashes and Debugging
    How to read output from WinDBG of dump file to determine root cause of recent crash?: For the past few weeks i've been getting windows crashes, as in the windows would just freeze and stop then i would need to force shutdown the PC. Using WinDBG with the command `!analyize -v` I'm not able to make heads or tails of the output.Link to dump file:...

  6. How to read output from WinDBG of dump file to determine root cause of recent crash?

    in Windows 10 Software and Apps
    How to read output from WinDBG of dump file to determine root cause of recent crash?: For the past few weeks i've been getting windows crashes, as in the windows would just freeze and stop then i would need to force shutdown the PC. Using WinDBG with the command `!analyize -v` I'm not able to make heads or tails of the output.Link to dump file:...

  7. Can't determine root cause of BSOD

    in Windows 10 Gaming
    Can't determine root cause of BSOD: Hi there,I'm getting constant but random BSOD reboots a day. Happens around 5 times a day or so at random intervals. The blue screen error that pops up before reboot only lasts half a second so I can't read the exact error message.I've looked in event viewer, but nothing...

  8. Can't determine root cause of BSOD

    in Windows 10 Software and Apps
    Can't determine root cause of BSOD: Hi there,I'm getting constant but random BSOD reboots a day. Happens around 5 times a day or so at random intervals. The blue screen error that pops up before reboot only lasts half a second so I can't read the exact error message.I've looked in event viewer, but nothing...

  9. Can't determine root cause of BSOD

    in Windows 10 BSOD Crashes and Debugging
    Can't determine root cause of BSOD: Hi there,I'm getting constant but random BSOD reboots a day. Happens around 5 times a day or so at random intervals. The blue screen error that pops up before reboot only lasts half a second so I can't read the exact error message.I've looked in event viewer, but nothing...

  10. How to read output from WinDBG of dump file to determine root cause of recent crash?

    in Windows 10 BSOD Crashes and Debugging
    How to read output from WinDBG of dump file to determine root cause of recent crash?: I somewhat frequently have random crashes at night when I'm not using my PC that are unrelated to Windows Update. I check the event log and it's "WER-SystemErrorReporting" - 1001 rebooting from a bugcheck. I built the PC myself and it's 6 months old with all brand new top of...