Consistant BSOD after sleep/hibernate(driver power state failure

  1. Posts : 12
    Windows 10 Home

    Consistant BSOD after sleep/hibernate(driver power state failure

    I posted here before about this same issue(see this thread). Installing a previous version of my intel HD graphics drivers fixed it for a few days, but in the end it returned. I tried to install those drivers again but it wouldn't work a second time.

    (The file was apparently too big for the forum limit, so I split it using winrar)

    Attachment 133316
    Attachment 133317
    Attachment 133318
      My Computer

  2. Posts : 13,960
    Windows 10 Pro X64 21H1 19043.1503

    If the generated zip file was to big, delete the older (2016) dumps. I was able to recombine them so all is well.

    The 1stMay dump shows a problem wiht your Nvidia card or driver nvlddmkm.sys.
    BugCheck 9F, {3, ffff880018601060, fffff80158c6c960, ffff88001e2545f0}
    Implicit thread is now ffff8800`176ae040
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiFdoHandleDevicePower+1e5 )
    The other two May dumops show only dxgkrnl.sys as a problem:
    BugCheck 9F, {3, ffff8000f4e43060, ffff9401c81f3960, ffff8000f52038e0}
    Implicit thread is now ffff8000`f3eae040
    Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiRequestIoPowerState+a5 )
    dxgkrnl.sys is part of DirectX support, not likely to be the cause. Both these are almost certainly caused by the Nvidia driver/card.

    You have version 378.92. The latest recommended driver for that card is:

    GeForce Game Ready Driver

    Version: 382.05 WHQL
    Release Date: 2017.5.4
    Operating System: Windows 10 64-bit
    Language: English (US)
    File Size: 417.59 MB

    Give it a try.
      My Computers

  3. Posts : 12
    Windows 10 Home
    Thread Starter

    I clean installed the driver and it seemed to work, but since the last time I thought it was fixed but broke a few days later, I decided to wait. So now, 3 days later, it bluescreened again, with the same error message.

    Attachment 134197
    Attachment 134198
      My Computer

  4. Posts : 13,960
    Windows 10 Pro X64 21H1 19043.1503

    Latest dump is another dxgkrnl.sys problem. Nothing else in the dump that I find useful to further id the cause of the problem. Give Driver Verifier a try:

    Driver Verifier
    is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Pay close attention to PART TWO and make sure the correct boxes are checked.

    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier.

    What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun dm_log_collector and upload the resulting zip file.

    Part three of the tutorial tells you how to turn off Driver Verifier if Windows will not boot. Make yourself familiar with this just in case.
      My Computers

  5. Posts : 12
    Windows 10 Home
    Thread Starter

    Sorry for taking so long, I needed the laptop during weekdays so couldn't afford to potentially lose it for 48 hours..
    But after enabling the verifier with the given settings it BSODd when shutting down.. And also while starting up again, so I tried to disable it again using the steps in the guide, all of which ended in another BSOD. In the end I got it to boot again using the steps given by a user:
    jaywalker said:
    was able to get safe mode running by bringing up an admin console window and entering
    bcdedit /set {default} safeboot minimal

    turned off verifier
    turned off safe mode with
    bcdedit /deletevalue {current} safeboot
    So now I ran the tool again and here are the logs, I hope there is still something usefull in there..

    Attachment 134832
    Attachment 134833
    Attachment 134831
      My Computer

  6. Posts : 13,960
    Windows 10 Pro X64 21H1 19043.1503

    I'm having problems reading your dumps. Keep getting wrong symbol files so not a lot aI can do right now, but I did notice in the 5/13 5:20PM dump that ScpVBus.sys is in the stack trace. This driver has been known to cause BSODS. The one you have is dated Sun May 5 17:31:26 2013.

    Driver Description: Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver
    Driver Update Site:

    I believe this may have something to do with an Xbox controller but not sure.

    Neither the 5/12 or 5/13 dump appears to be Driver Verifier induced.
      My Computers

  7. Posts : 14,897
    Windows 10 Pro

    I have no problems running the dumps, so will quickly post something.

    A guess, without diving deep, with the Nvidia driver, this perhaps may be an issue with switchable graphics.
    5: kd> !irp ffff990c104c4010
    Irp is active with 4 stacks 3 is current (= 0xffff990c104c4170)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
         cmd  flg cl Device   File     Completion-Context
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-00000000    
    			Args: 00000000 00000000 00000000 00000000
                0  0 ffff990c038257b0 00000000 fffff803bf89ed60-ffffa9007fe459f0    
    	       \Driver\pci	dxgkrnl!DpiFdoPowerCompletionRoutine
    			Args: 00000000 00000000 00000000 00000002
                0 e1 ffff990c07bd9030 00000000 fffff80304922ff0-ffff990c09d48010 Success Error Cancel pending
    	      *** WARNING: Unable to verify timestamp for igdkmd64.sys
    *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
     \Driver\igfx	nt!PopRequestCompletion
    			Args: 00051100 00000001 00000001 00000002
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-ffff990c09d48010    
    			Args: 00000000 00000000 00000000 00000000
    5: kd> lmvm igdkmd64
    Browse full module list
    start             end                 module name
    fffff803`c1800000 fffff803`c1fc2000   igdkmd64 T (no symbols)           
        Loaded symbol image file: igdkmd64.sys
        Image path: igdkmd64.sys
        Image name: igdkmd64.sys
        Browse all global symbols  functions  data
        Timestamp:        Fri Nov 11 02:58:15 2016 (582525B7)
        CheckSum:         007A604D
        ImageSize:        007C2000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computers

  8. Posts : 12
    Windows 10 Home
    Thread Starter

    I started with trying to delete the driver mentioned, but after a day still gave a BSOD, so then I googled the nvidia switchable graphics and came across a potential fix; disable windows fast boot. This seemed to work but then it BSOD'd again today, and this time my PC wasn't even waking from sleep or hibernate.

    Attachment 135582
    Attachment 135583
      My Computer


  Related Discussions
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 12:12.
Find Us

Windows 10 Forums