10 BSOD in 24 hours

Page 1 of 8 123 ... LastLast

  1. Posts : 34
    Windows 10
       #1

    10 BSOD in 24 hours


    Windows version 1909, HP Spectre x360

    Alright, so I should preface this by saying I know next to nothing about the internal workings of a computer. It took me over an hour to set up windbg, including having to figure out why the tutorial commands weren't working (TIL: powershell and command prompt aren't the same thing, and are not necessarily interchangeable!)

    After much googling and tutorial-following, I finally got windbg configured, and was able to analyze the most recent crash dump. I analyzed one last night, and the one this morning, and got the following results:

    BSOD crash dump analysis - Google Docs

    Apparently a different driver crash in each of them. Would this signal that it's not actually a driver issue but something else triggering the drivers to crash?

    I already updated my display adapter drivers. Nothing changed.

    The BSOD seems to happen every time Iím running a resource-heavy program, like Adobe Photoshop Lightroom, Adobe Premiere Pro, or LR Timelapse. So far no issue with just running Chrome and a few other small apps like windbg, settings, etc.

    I tried changing my power settings, as some tutorials recommend for the recent driver crash, but for some reason I have limited options compared to what tutorials show that I should have

    10 BSOD in 24 hours-ss3.png

    Reliability report from yesterday

    10 BSOD in 24 hours-ss1.jpg
    10 BSOD in 24 hours-ss2.jpg

    And from today

    10 BSOD in 24 hours-ss4.jpg
    10 BSOD in 24 hours-ss5.jpg

    What is my next step here? Since my partner and I make all of our income with photo and video work, itís essential that we get this fixed ASAP. Any advice is appreciated! Thanks guys :)
      My Computer

  2. FreeBooter's Avatar
    Posts : 3,199
    Windows 10 Pro 64-bit
       #2

    You can turn on Driver Verifier to identify driver causing the BSOD error.

    Enable and Disable Driver Verifier in Windows 10
      My Computer


  3. Posts : 34
    Windows 10
    Thread Starter
       #3

    Okay, did as the tutorial instructed. Here's the results:

    Microsoft Windows [Version 10.0.18363.836]
    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\Users\adrip>verifier /query

    Time Stamp: 05/20/2020 17:29:10.517

    Verifier Flags: 0x00100610

    Standard Flags:

    [ ] 0x00000001 Special pool.
    [ ] 0x00000002 Force IRQL checking.
    [ ] 0x00000008 Pool tracking.
    [X] 0x00000010 I/O verification.
    [ ] 0x00000020 Deadlock detection.
    [ ] 0x00000080 DMA checking.
    [ ] 0x00000100 Security checks.
    [ ] 0x00000800 Miscellaneous checks.
    [ ] 0x00020000 DDI compliance checking.

    Additional Flags:

    [ ] 0x00000004 Randomized low resources simulation.
    [X] 0x00000200 Force pending I/O requests.
    [X] 0x00000400 IRP logging.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x00040000 Systematic low resources simulation.
    [ ] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

    Internal Flags:

    [X] 0x00100000 Extended Verifier flags (internal).

    [X] Indicates flag is enabled.

    Verifier Statistics Summary

    Raise IRQLs: 72256
    Acquire Spin Locks: 28473
    Synchronize Executions: 0
    Trims: 0

    Pool Allocations Attempted: 2685501
    Pool Allocations Succeeded: 2685501
    Pool Allocations Succeeded SpecialPool: 4850
    Pool Allocations With No Tag: 0
    Pool Allocations Not Tracked: 0
    Pool Allocations Failed: 0
    Pool Allocations Failed Deliberately: 0

    Driver Verification List

    MODULE: igdkmd64.sys (load: 1 / unload: 0)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: ish.sys (load: 1 / unload: 0)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: netwtw08.sys (load: 1 / unload: 0)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: ialpss2i_i2c_cnl.sys (load: 1 / unload: 0)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: teedriverw8x64.sys (load: 1 / unload: 0)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: intcaudiobus.sys (load: 1 / unload: 0)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: ialpss2i_gpio2_cnl.sys (load: 1 / unload: 0)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: hpcustomcapdriver.sys (load: 1 / unload: 0)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: wirelessbuttondriver64.sys (load: 1 / unload: 0)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: hideventfilter.sys (load: 1 / unload: 0)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: dptf_acpi.sys (load: 1 / unload: 0)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: eztouchfilter.sys (load: 1 / unload: 0)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: intcoed.sys (load: 1 / unload: 0)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: intcdmic.sys (load: 1 / unload: 0)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: ibtusb.sys (load: 1 / unload: 0)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: dump_dumpstorport.sys (load: 0 / unload: 0)

    MODULE: dump_stornvme.sys (load: 2 / unload: 1)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: dump_dumpfve.sys (load: 2 / unload: 1)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: intcdaud.sys (load: 1 / unload: 0)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: dptf_cpu.sys (load: 2 / unload: 1)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: esif_lf.sys (load: 2 / unload: 1)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: ish_busdriver.sys (load: 1 / unload: 0)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: hid_pci.sys (load: 1 / unload: 0)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    MODULE: tbt100x.sys (load: 2 / unload: 1)

    Pool Allocation Statistics: ( NonPaged / Paged )

    Current Pool Allocations: ( 0 / 0 )
    Current Pool Bytes: ( 0 / 0 )
    Peak Pool Allocations: ( 0 / 0 )
    Peak Pool Bytes: ( 0 / 0 )
    Contiguous Memory Bytes: 0
    Peak Contiguous Memory Bytes: 0

    C:\Users\adrip>
      My Computer

  4. FreeBooter's Avatar
    Posts : 3,199
    Windows 10 Pro 64-bit
       #4

    We need the memory dump file created by Driver Verifier.
      My Computer


  5. Posts : 34
    Windows 10
    Thread Starter
       #5

    FreeBooter said:
    We need the memory dump file created by Driver Verifier.
    Would that be the usual memory dump file? Or is this a different one, located elsewhere on the computer?
      My Computer

  6. FreeBooter's Avatar
    Posts : 3,199
    Windows 10 Pro 64-bit
       #6

    If you have the system set to generate Small Memory Dumps, they will be located in C:\Windows\Minidump directory.
    If you have the system set to generate Kernel Memory Dumps, it will be located in C:\Windows directory and labelled as
    MEMORY.DMP file.


      My Computer



  7. Posts : 34
    Windows 10
    Thread Starter
       #7

    Here's the memory dump. Should I have gotten a Driver Verifier BSOD like it shows in the tutorial? It gave the usual BSOD.

    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffc78890793060, Physical Device Object of the stack
    Arg3: ffffc3090c06f7b0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffc7889b660c20, The blocked IRP

    Debugging Details:
    ------------------

    Implicit thread is now ffffc788`8d8e5040
    Page 3d335f not present in the dump file. Type ".hh dbgerr004" for details
    Page 3d335f not present in the dump file. Type ".hh dbgerr004" for details

    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.Sec
    Value: 3

    Key : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-EH76GAR

    Key : Analysis.DebugData
    Value: CreateObject

    Key : Analysis.DebugModel
    Value: CreateObject

    Key : Analysis.Elapsed.Sec
    Value: 3

    Key : Analysis.Memory.CommitPeak.Mb
    Value: 131

    Key : Analysis.System
    Value: CreateObject


    BUGCHECK_CODE: 9f

    BUGCHECK_P1: 3

    BUGCHECK_P2: ffffc78890793060

    BUGCHECK_P3: ffffc3090c06f7b0

    BUGCHECK_P4: ffffc7889b660c20

    DRVPOWERSTATE_SUBCODE: 3

    FAULTING_THREAD: ffffc7888d8e5040

    ADDITIONAL_DEBUG_TEXT: DXG Power IRP timeout.

    IRP_ADDRESS: ffffc7889b660c20

    DEVICE_OBJECT: ffffc7888d8dc7e0

    DRIVER_OBJECT: ffffc788900f1490

    IMAGE_NAME: ACPI.sys

    MODULE_NAME: ACPI

    FAULTING_MODULE: fffff8000f880000 ACPI

    PROCESS_NAME: System

    STACK_TEXT:
    ffffc309`0c0173f0 fffff800`0e53207d : fffff800`0c738180 00000000`fffffffe fffff800`ffffffff 00000000`00000001 : nt!KiSwapContext+0x76
    ffffc309`0c017530 fffff800`0e530f04 : ffffc788`8d8e5040 ffffc788`00000000 ffffc788`00000000 fffff800`00000000 : nt!KiSwapThread+0xbfd
    ffffc309`0c0175d0 fffff800`0e5306a5 : ffffc788`9f268400 00000000`00000000 ffffc788`9f268400 00000000`00000000 : nt!KiCommitThreadWait+0x144
    ffffc309`0c017670 fffff808`143d29f5 : ffffc309`0c017790 ffffc788`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x255
    ffffc309`0c017750 fffff808`143d2180 : ffffc309`0c017700 00000000`00000008 ffffc788`9b660e10 ffffc788`9b660c20 : dxgkrnl!DpiFdoHandleDevicePower+0x225
    ffffc309`0c0177f0 fffff808`143d3251 : ffffc788`9b660c20 ffffc788`945a2180 ffffc788`945a2030 fffff808`19c2327a : dxgkrnl!DpiFdoDispatchPower+0x20
    ffffc309`0c017820 fffff808`19bf8c83 : 00000000`00000001 ffffc788`9b3bf000 00000000`00000001 ffffc788`9b660c20 : dxgkrnl!DpiDispatchPower+0xe1
    ffffc309`0c017940 fffff808`19bf7d4a : ffffc788`945a2030 00000000`00000000 ffffc788`8d8dc7e0 00000000`00000000 : nvlddmkm+0xd8c83
    ffffc309`0c017a30 fffff800`0e59704f : ffffc788`945a2030 ffffc309`0c017ae0 00000000`00000000 ffffc788`00000000 : nvlddmkm+0xd7d4a
    ffffc309`0c017a60 fffff800`0e488cd5 : 00000000`00000000 ffffc788`8d8e5040 fffff800`0e596e70 00000000`00000000 : nt!PopIrpWorker+0x1df
    ffffc309`0c017b10 fffff800`0e5e6998 : ffff8081`0ba00180 ffffc788`8d8e5040 fffff800`0e488c80 00feffff`ff3f0000 : nt!PspSystemThreadStartup+0x55
    ffffc309`0c017b60 00000000`00000000 : ffffc309`0c018000 ffffc309`0c011000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


    STACK_COMMAND: .thread 0xffffc7888d8e5040 ; kb

    SYMBOL_NAME: ACPI!ACPIDispatchIrp <PERF> (ACPI+0x0)+0

    BUCKET_ID_FUNC_OFFSET: 0

    FAILURE_BUCKET_ID: 0x9F_VRF_3_DXG_POWER_IRP_TIMEOUT_ACPI!ACPIDispatchIrp__PERF__(ACPI+0x0)

    OS_VERSION: 10.0.18362.1

    BUILDLAB_STR: 19h1_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {ea5fd428-4e4b-3e97-79da-b7f86a3dbd1f}

    Followup: MachineOwner
      My Computer

  8. FreeBooter's Avatar
    Posts : 3,199
    Windows 10 Pro 64-bit
       #8

    You need to turn on the Driver Verifier and let the BSOD error happen while Driver Verifier running then upload the memory dump file.
      My Computer


  9. Posts : 394
    W10
       #9

    It's most likely a video issue causing this problem (I say this because of the nVidia video driver in the stack text (nvlddmkm)

    Start by doing a clean install of the video drivers;
    - perform an uninstall of the video drivers, then use DDU to remove any traces (free from here: Display Driver Uninstaller (DDU) | Wagnardsoft )
    - download and install the latest available video drivers from nVidia: Download Drivers | NVIDIA

    Test to see if this helps


    EDITED this out:
    AMD ( https://www.amd.com/en/support/kb/faq/gpu-56 )


    If not, then check:
    - that the fan/cooler is clean and free of dirt, dust or hairballs
    - that the card is firmly seated into the motherboard, and that any other cables are firmly seated into the card.
    - that the slot that the card is in is free of dirt/dust/hairballs (blow it out with canned air - DO NOT USE A VACUUM OR AIR COMPRESSOR!!!)
    - that the fan isn't sticking or sluggish (found by observing the card during operation. If it's sticking, when it sticks it'll cause problems.

    Just FYI - you can zip up the contents of C:\Windows\Minidump and upload/attach it here with your next post.
    If you have problems zipping it there, then copy it to your Desktop and zip it there.

    As for the MEMORY.DMP, it'll be very large so you'll have to:
    - ensure that it's zipped up
    - upload it to a free file-hosting service (I suggest OneDrive or Google Drive)
    - post a link to it here so we can download it.
    Last edited by jdc1; 1 Week Ago at 06:11.
      My Computer


  10. Posts : 34
    Windows 10
    Thread Starter
       #10

    FreeBooter said:
    You need to turn on the Driver Verifier and let the BSOD error happen while Driver Verifier running then upload the memory dump file.
    That's what I did. Turn it on, restart computer when prompted, sign in, open up my video editing program, BSOD within 2 minutes. That's the dump I just posted


    jdc1 said:
    It's most likely a video issue causing this problem (I say this because of the nVidia video driver in the stack text (nvlddmkm)

    Start by doing a clean install of the video drivers;
    - perform an uninstall of the video drivers, then use DDU to remove any traces (free from here: Display Driver Uninstaller (DDU) | Wagnardsoft )
    - download and install the latest available video drivers from AMD ( https://www.amd.com/en/support/kb/faq/gpu-56 )
    Test to see if this helps

    If not, then check:
    - that the fan/cooler is clean and free of dirt, dust or hairballs
    - that the card is firmly seated into the motherboard, and that any other cables are firmly seated into the card.
    - that the slot that the card is in is free of dirt/dust/hairballs (blow it out with canned air - DO NOT USE A VACUUM OR AIR COMPRESSOR!!!)
    - that the fan isn't sticking or sluggish (found by observing the card during operation. If it's sticking, when it sticks it'll cause problems.

    Just FYI - you can zip up the contents of C:\Windows\Minidump and upload/attach it here with your next post.
    If you have problems zipping it there, then copy it to your Desktop and zip it there.

    As for the MEMORY.DMP, it'll be very large so you'll have to:
    - ensure that it's zipped up
    - upload it to a free file-hosting service (I suggest OneDrive or Google Drive)
    - post a link to it here so we can download it.
    I'll give this a shot, thank you!
      My Computer


 

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

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




Windows 10 Forums