Windows 10: Multiple BSOD, anyone able to help me read through dumps and attempt troubleshooting?

Discus and support Multiple BSOD, anyone able to help me read through dumps and attempt troubleshooting? in Windows 10 Ask Insider to solve the problem; Having troubles with laptop since purchasing, still within warranty, however I'm doing my best possible not to go through the warranty route. specs:... Discussion in 'Windows 10 Ask Insider' started by /u/Para-Medicine, Jan 15, 2021.

  1. Multiple BSOD, anyone able to help me read through dumps and attempt troubleshooting?


    Having troubles with laptop since purchasing, still within warranty, however I'm doing my best possible not to go through the warranty route.

    specs: Model: fa506iv-br7n12 CPU: AMD Ryzen 7 4800H GPU: Geforce RTX 2060 Windows version: 19042 RAM: 8GB Storage: 512GB ssd

    Purchased laptop from bestbuy approx november 2020, I've had off and on BSOD without being able to track where they are coming from, I've had problems getting minidumps because they will typical stay at 0% and no throw a dumpfile into windows, Occasionally I will get lucky and a dump file will be created (see below for most recent dump file) I've also attempted updates/uninstalls/reinstalls of all the drivers I could think of from manufacturers page. I've tried a clean install of windows as well. Any and all help with be appreciated.

    I get multiple differents BSOD errorchecks as follow: driver irql_less_or_not_equal, Thread stuck in device driver, NO_EXECUTE, attempted execute of noexecute memory, KMODE_exception not handle

    Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Windows\Minidump\011121-9671-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff80150c00000 PsLoadedModuleList = 0xfffff8015182a2b0 Debug session time: Mon Jan 11 19:00:28.021 2021 (UTC - 6:00) System Uptime: 0 days 0:19:56.672 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .................... Loading User Symbols Loading unloaded module list ................... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff80150ff5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffe0621ed7fd0=00000000000000ea 1: kd> !analyze -v

    • *
    • Bugcheck Analysis *
    • * *******************************************************************************

    THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea) The device driver is spinning in an infinite loop, most likely waiting for hardware to become idle. This usually indicates problem with the hardware itself or with the device driver programming the hardware incorrectly. If the kernel debugger is connected and running when watchdog detects a timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx() and detailed message including bugcheck arguments will be printed to the debugger. This way we can identify an offending thread, set breakpoints in it, and hit go to return to the spinning code to debug it further. Because KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck information in this case. The arguments are already printed out to the kernel debugger. You can also retrieve them from a global variable via "dd watchdog!g_WdBugCheckData l5" (use dq on NT64). On MP machines it is possible to hit a timeout when the spinning thread is interrupted by hardware interrupt and ISR or DPC routine is running at the time of the bugcheck (this is because the timeout's work item can be delivered and handled on the second CPU and the same time). If this is the case you will have to look deeper at the offending thread's stack (e.g. using dds) to determine spinning code which caused the timeout to occur. Arguments: Arg1: ffff8b8cca7ec0c0, Pointer to a stuck thread object. Do .thread then kb on it to find the hung location. Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object. Arg3: 0000000000000000, Pointer to offending driver name. Arg4: 0000000000000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

    Debugging Details:


    *** WARNING: Unable to verify checksum for win32k.sys

    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec Value: 4327 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on TNM Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 40261 Key : Analysis.Memory.CommitPeak.Mb Value: 89 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1

    ADDITIONAL_XML: 1

    OS_BUILD_LAYERS: 1

    BUGCHECK_CODE: ea

    BUGCHECK_P1: ffff8b8cca7ec0c0

    BUGCHECK_P2: 0

    BUGCHECK_P3: 0

    BUGCHECK_P4: 0

    FAULTING_THREAD: ffff8b8cca7ec0c0

    BLACKBOXBSD: 1 (!blackboxbsd)

    BLACKBOXNTFS: 1 (!blackboxntfs)

    BLACKBOXPNP: 1 (!blackboxpnp)

    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: System

    STACK_TEXT:
    fffffe0621ed7fc8 fffff80183e4289d : 00000000000000ea ffff8b8cca7ec0c0 0000000000000000 0000000000000000 : nt!KeBugCheckEx fffffe0621ed7fd0 fffff80183e4297e : fffffe0621ed80b0 fffff80183e1727b fffffe0621ed80b0 fffff8018dfbce00 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45 fffffe0621ed8040 fffff8018df18ff0 : 00000002c966e9af fffff8018dfbce00 0000000000000000 ffff8b8cc00e9000 : dxgkrnl!TdrTimedOperationDelay+0xce fffffe0621ed8080 00000002c966e9af : fffff8018dfbce00 0000000000000000 ffff8b8cc00e9000 0000000000989680 : atikmdag+0x68ff0 fffffe0621ed8088 fffff8018dfbce00 : 0000000000000000 ffff8b8cc00e9000 0000000000989680 0000000000000001 : 0x00000002c966e9af fffffe0621ed8090 0000000000000000 : ffff8b8cc00e9000 0000000000989680 0000000000000001 00000000`00000028 : atikmdag+0x10ce00

    STACK_COMMAND: .thread 0xffff8b8cca7ec0c0 ; kb

    SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45

    MODULE_NAME: dxgkrnl

    IMAGE_NAME: dxgkrnl.sys

    IMAGE_VERSION: 10.0.19041.746

    FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys

    OS_VERSION: 10.0.19041.1

    BUILDLAB_STR: vb_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}

    Followup: MachineOwner


    Here's another that I was able to obtain

    Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Windows\Minidump\122220-8906-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available

    ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff80739200000 PsLoadedModuleList = 0xfffff80739e2a2b0 Debug session time: Tue Dec 22 10:17:20.098 2020 (UTC - 6:00) System Uptime: 0 days 1:26:17.749 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .................. Loading User Symbols Loading unloaded module list ........... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff807395f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffd8e264a73f0=000000000000000a 10: kd> !analyze -v

    • *
    • Bugcheck Analysis *
    • * *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: fffffffffffff000, memory referenced Arg2: 00000000000000ff, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff807397610c9, address which referenced memory

    Debugging Details:


    *** WARNING: Unable to verify checksum for win32k.sys

    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec Value: 3703 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on TNM Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 8155 Key : Analysis.Memory.CommitPeak.Mb Value: 81 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1

    ADDITIONAL_XML: 1

    OS_BUILD_LAYERS: 1

    BUGCHECK_CODE: a

    BUGCHECK_P1: fffffffffffff000

    BUGCHECK_P2: ff

    BUGCHECK_P3: 0

    BUGCHECK_P4: fffff807397610c9

    READ_ADDRESS: fffff80739efa390: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd fffff80739e0f330: Unable to get Flags value from nt!KdVersionBlock fffff80739e0f330: Unable to get Flags value from nt!KdVersionBlock unable to get nt!MmSpecialPagesInUse fffffffffffff000

    BLACKBOXBSD: 1 (!blackboxbsd)

    BLACKBOXNTFS: 1 (!blackboxntfs)

    BLACKBOXPNP: 1 (!blackboxpnp)

    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: System

    TRAP_FRAME: fffffd8e264a7530 -- (.trap 0xfffffd8e264a7530) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000006 rbx=0000000000000000 rcx=0000000000000200 rdx=0000000c0e4f955e rsi=0000000000000000 rdi=0000000000000000 rip=fffff807397610c9 rsp=fffffd8e264a76c0 rbp=ffffaf801c100180 r8=0000000000000001 r9=0000000000000007 r10=0000fffff807394e r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up di ng nz na po nc nt!PpmIdleUpdateConcurrency+0x79: fffff807397610c9 488b5c2440 mov rbx,qword ptr [rsp+40h] ss:0018:fffffd8e264a7700=ffffe68613651000 Resetting default scope

    STACK_TEXT:
    fffffd8e264a73e8 fffff80739607769 : 000000000000000a fffffffffffff000 00000000000000ff 0000000000000000 : nt!KeBugCheckEx fffffd8e264a73f0 fffff80739603a69 : 0000000c0e2e80a8 0000000000000000 0000000000000000 fffffd8e264a7560 : nt!KiBugCheckDispatch+0x69 fffffd8e264a7530 fffff807397610c9 : ffffe68613651000 ffffaf801c100180 0000000c0e4f955e 0000000000000002 : nt!KiPageFault+0x469 fffffd8e264a76c0 0000000000000000 : ffffe68613651000 0000000000000000 0000000000000000 fffffd8e264a77c0 : nt!PpmIdleUpdateConcurrency+0x79

    SYMBOL_NAME: nt!PpmIdleUpdateConcurrency+79

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    IMAGE_VERSION: 10.0.19041.685

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 79

    FAILURE_BUCKET_ID: AV_nt!PpmIdleUpdateConcurrency

    OS_VERSION: 10.0.19041.1

    BUILDLAB_STR: vb_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {1e521b51-d14a-dc59-37c3-c21c0b8ec9a6}

    Followup: MachineOwner
    submitted by /u/Para-Medicine
    [link] [comments]

    :)
     
    /u/Para-Medicine, Jan 15, 2021
    #1

  2. BSOD dump

    Hi Damian,

    About your issue regarding BSOD on your PC. We suggest you to run this article:

    Troubleshoot blue screen errors
    . It contains troubleshooting steps to perform to fix that issue.

    We'll look forward to tour response.
     
    Phillip Pio, Jan 15, 2021
    #2
  3. Reading driver verifier crash dump

    Here are the other two images:
    Ill try what you suggested, thank all of you for the help so far.



    Multiple BSOD, anyone able to help me read through dumps and attempt troubleshooting? [​IMG]

    Multiple BSOD, anyone able to help me read through dumps and attempt troubleshooting? [​IMG]
     
    AaronOlson, Jan 15, 2021
    #3
  4. Multiple BSOD, anyone able to help me read through dumps and attempt troubleshooting?

    Multiple BSOD - Please Help

    I've recently ran into multiple BSOD and need assistance in solving them. I've done "chkdsk /f /r", "sfc /scannow" and "mssched.exe" and it says that my system has no errors.

    Here is a link to my dump files. Minidump.zip

    List of Errors:

    PAGE_FAULT_IN_NONPAGED_AREA

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

    SYSTEM_SERVICE_EXCEPTION

    BAD_POOL_HEADER

    BAD_POOL_CALLER

    IRQL_NOT_LESS_OR_EQUAL

    KERNAL_SECURITY_CHECK_FAILURE
     
    William Tea, Jan 15, 2021
    #4
Thema:

Multiple BSOD, anyone able to help me read through dumps and attempt troubleshooting?

Loading...
  1. Multiple BSOD, anyone able to help me read through dumps and attempt troubleshooting? - Similar Threads - Multiple BSOD anyone

  2. Constistant BSOD, need help reading dump files

    in Windows 10 Gaming
    Constistant BSOD, need help reading dump files: Im completely fed up with my pc, no matter what i try these BSOD's wont go away, i work in IT so i am familiar with the standard diagnostic and troubleshooting stuff however im stuck,Hardware stress tests and memory tests give me no errors, the BSOD's are completely...
  3. Help me read Steam's game crush dump

    in Windows 10 Gaming
    Help me read Steam's game crush dump: Hello Can you help me read Steam's game crush dump?The game is crushing but cannot understand why https://answers.microsoft.com/en-us/windows/forum/all/help-me-read-steams-game-crush-dump/566a76b4-f933-42df-85fd-795c68ec7bda
  4. Help me read Steam's game crush dump

    in Windows 10 BSOD Crashes and Debugging
    Help me read Steam's game crush dump: Hello Can you help me read Steam's game crush dump?The game is crushing but cannot understand why https://answers.microsoft.com/en-us/windows/forum/all/help-me-read-steams-game-crush-dump/566a76b4-f933-42df-85fd-795c68ec7bda
  5. Help me read Steam's game crush dump

    in Windows 10 Software and Apps
    Help me read Steam's game crush dump: Hello Can you help me read Steam's game crush dump?The game is crushing but cannot understand why https://answers.microsoft.com/en-us/windows/forum/all/help-me-read-steams-game-crush-dump/566a76b4-f933-42df-85fd-795c68ec7bda
  6. Is anyone able to help with a BSOD - IRQL_NOT_LESS_OR_EQUAL?

    in Windows 10 Gaming
    Is anyone able to help with a BSOD - IRQL_NOT_LESS_OR_EQUAL?: I have recently upgraded my PC to use a 3060ti and a new M.2. Because of this, I did a fresh install of windows 11. During the installation, I suffered a boot loop that lasted for 10 mins until I was able to launch safe mode and it eventally sorted itself out. I then went on...
  7. Is anyone able to help with a BSOD - IRQL_NOT_LESS_OR_EQUAL?

    in Windows 10 Software and Apps
    Is anyone able to help with a BSOD - IRQL_NOT_LESS_OR_EQUAL?: I have recently upgraded my PC to use a 3060ti and a new M.2. Because of this, I did a fresh install of windows 11. During the installation, I suffered a boot loop that lasted for 10 mins until I was able to launch safe mode and it eventally sorted itself out. I then went on...
  8. Can anyone read this dump file for me ?

    in Windows 10 BSOD Crashes and Debugging
    Can anyone read this dump file for me ?: I just got a BSOD and I believe it was bc I had my HDMI unplugged and keyboard and mouse unplugged when i turned my power back on, even though the last time I had the power on all of my external devices were plugged in but I wanna double check it isnt something else ....
  9. Anyone able to read these minidumps to help identify my BSOD issue?

    in Windows 10 Ask Insider
    Anyone able to read these minidumps to help identify my BSOD issue?: https://1drv.ms/u/s!Amnz3b0YgYjlizUQq_iIyW5gBMpU?e=YXFATL I believe I linked the files correctly. The issues happen every day or 2 and it usually happens when I am just idle or watching a Youtube. I can play games just fine but then I will be literally doing nothing when I...
  10. Could somebody help me with reading this dump file?

    in Windows 10 BSOD Crashes and Debugging
    Could somebody help me with reading this dump file?: Hello everyone, It would be much appreciated if someone could help me to figure out what is the cause of my PC freezing under load. This is the .dmp file, which has dxgkrnl.sys and watchdog.sys at the top marked red....