BSOD DRIVER_POWER_STATE_FAILURE While using Photoshop CC 2015

Page 1 of 2 12 LastLast

  1. Posts : 13
    Microsoft Windows 10 Home 64-bit 10240 Multiprocessor Free
       #1

    BSOD DRIVER_POWER_STATE_FAILURE While using Photoshop CC 2015


    Hi All,

    I have been having an issue where I am received an intermittent blue screen of death with the message DRIVER_POWER_STATE_FAILURE. The issue seems to be occurring when I'm using Adobe Photoshop CC 2015. I have updated my BIOS and graphics card to the most recent version, but this doesn't seem to have remedied the issue.

    If anyone could go through the DMP files and let me know your thoughts on what's causing the issue, I would greatly appreciate it.

    Thanks!
      My Computer


  2. Posts : 14,901
    Windows 10 Pro
       #2

    Hi TyloRen,

    Welcome to the 10forums.

    Please move some files from the C partition to increase the free space to at least 10-15%.
    Every partition needs at least 10-15% free space so Windows can do its thing in the background.
    warning   Warning
    Less free space could cause BSOD's


    Please remove the ASUS software, this software is known for causing BSOD's.

    Please check ASUS for driver updates for the input device
    Driver Reference Table - AsusTP.sys
    Code:
    *** WARNING: Unable to verify timestamp for AsusTP.sys
    *** ERROR: Module load completed but symbols could not be loaded for AsusTP.sys
    
    2: kd> lmvm asustp
    start             end                 module name
    fffff800`2ea60000 fffff800`2eabf000   AsusTP   T (no symbols)           
        Loaded symbol image file: AsusTP.sys
        Image path: \SystemRoot\System32\drivers\AsusTP.sys
        Image name: AsusTP.sys
        Timestamp:        Wed Jun 17 10:27:57 2015 (55812F8D)
        CheckSum:         00026B1C
        ImageSize:        0005F000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Let me know if driver verifier still finds drivers after ASUS software has been removed, files have been moved and the driver has been updated :)

    Old drivers:
    Code:
    ASMMAP64        Thu Jul 02 11:13:26 2009 (4a4c7a36)        ASMMAP64.sys // Lenovo driver also in ASUS software
    GEARAspiWDM        Thu May 03 21:56:17 2012 (4fa2e2e1)        GEARAspiWDM.sys // iTunes
    kbfiltr        Thu Aug 02 05:22:22 2012 (5019f26e)        kbfiltr.sys // Keyboard filter driver
    atkwmiacpi64        Tue Jul 02 10:35:32 2013 (51d290d4)        atkwmiacpi64.sys // ASUS utility driver
    iaStorA        Sat Jun 07 01:20:24 2014 (53924cb8)        iaStorA.sys // Intel Rapid Storage driver
    TeeDriverx64        Mon Aug 25 23:01:32 2014 (53fba42c)        TeeDriverx64.sys // Intel Management driver
    IntelPcc        Fri Sep 05 01:05:04 2014 (5408f020)        IntelPcc.sys // Intel driver
    Note   Note
    Some drivers don't need updating as they should be removed when ASUS software is removed.
    iTunes driver should be updated by updating the software.

    Update links:
    Driver Reference Table - kbfiltr.sys
    Driver Reference Table - iaStorA.sys
    Driver Reference Table - TeeDriverx64.sys
    Driver Reference Table - intelpcc.sys
      My Computers


  3. Posts : 13
    Microsoft Windows 10 Home 64-bit 10240 Multiprocessor Free
    Thread Starter
       #3

    axe0 said:
    Hi TyloRen,

    Welcome to the 10forums.

    Please move some files from the C partition to increase the free space to at least 10-15%.
    Every partition needs at least 10-15% free space so Windows can do its thing in the background.
    warning   Warning
    Less free space could cause BSOD's


    Please remove the ASUS software, this software is known for causing BSOD's.

    Please check ASUS for driver updates for the input device
    Driver Reference Table - AsusTP.sys
    Code:
    *** WARNING: Unable to verify timestamp for AsusTP.sys
    *** ERROR: Module load completed but symbols could not be loaded for AsusTP.sys
    
    2: kd> lmvm asustp
    start             end                 module name
    fffff800`2ea60000 fffff800`2eabf000   AsusTP   T (no symbols)           
        Loaded symbol image file: AsusTP.sys
        Image path: \SystemRoot\System32\drivers\AsusTP.sys
        Image name: AsusTP.sys
        Timestamp:        Wed Jun 17 10:27:57 2015 (55812F8D)
        CheckSum:         00026B1C
        ImageSize:        0005F000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Let me know if driver verifier still finds drivers after ASUS software has been removed, files have been moved and the driver has been updated :)

    Old drivers:
    Code:
    ASMMAP64        Thu Jul 02 11:13:26 2009 (4a4c7a36)        ASMMAP64.sys // Lenovo driver also in ASUS software
    GEARAspiWDM        Thu May 03 21:56:17 2012 (4fa2e2e1)        GEARAspiWDM.sys // iTunes
    kbfiltr        Thu Aug 02 05:22:22 2012 (5019f26e)        kbfiltr.sys // Keyboard filter driver
    atkwmiacpi64        Tue Jul 02 10:35:32 2013 (51d290d4)        atkwmiacpi64.sys // ASUS utility driver
    iaStorA        Sat Jun 07 01:20:24 2014 (53924cb8)        iaStorA.sys // Intel Rapid Storage driver
    TeeDriverx64        Mon Aug 25 23:01:32 2014 (53fba42c)        TeeDriverx64.sys // Intel Management driver
    IntelPcc        Fri Sep 05 01:05:04 2014 (5408f020)        IntelPcc.sys // Intel driver
    Note   Note
    Some drivers don't need updating as they should be removed when ASUS software is removed.
    iTunes driver should be updated by updating the software.

    Update links:
    Driver Reference Table - kbfiltr.sys
    Driver Reference Table - iaStorA.sys
    Driver Reference Table - TeeDriverx64.sys
    Driver Reference Table - intelpcc.sys
    Thanks axe0. I updated the drivers you listed out (except for kbfiltr.sys, since I couldn't find it) and cleared up the appropriate space on my hard drive, but it seems I'm still encountering this error. I have attached an updated
    minidump for reference.
      My Computer


  4. Posts : 14,901
    Windows 10 Pro
       #4

    You are running driver verifier for days according to the dumps.
    It is recommended to run driver verifier for a max of 48h.
    Please disable driver verifier
    • Open an admin command prompt
    • Enter "verifier/reset" (without quotes)


    After driver verifier has been disabled, please test your system.
      My Computers


  5. Posts : 13
    Microsoft Windows 10 Home 64-bit 10240 Multiprocessor Free
    Thread Starter
       #5

    Okay I turned off the driver verifier and everything seemed to be working, but the crash just occurred again. Updated logs attached. Do you know what's causing the issue now?
      My Computer


  6. Posts : 14,901
    Windows 10 Pro
       #6




    Diagnostics Test

     System File Check


    Please try following:
    • Open an admin command prompt
    • Copy/paste "sfc/scannow" (without quotes) and press enter
    • When it finished reboot your system
    • Open again an admin command prompt
    • Enter sfc/scannow again

    If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
    System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.
      My Computers


  7. Posts : 13
    Microsoft Windows 10 Home 64-bit 10240 Multiprocessor Free
    Thread Starter
       #7

    Please see below for a link to the CBS log:

    CBS.log - Google Drive
      My Computer


  8. Posts : 14,901
    Windows 10 Pro
       #8

    The source of SFC is corrupted.

    Please try following command in admin command prompt
    Code:
    DISM /Online /Cleanup-Image /RestoreHealth
    If there are problems with RestoreHealth, please follow step 6 or 7 (depending on the file you have from the download) from the tutorial DISM - Repair Windows 10 Image - Tutorial

    After DISM, try sfc, reboot, sfc 2 times to complete it.
      My Computers


  9. Posts : 13
    Microsoft Windows 10 Home 64-bit 10240 Multiprocessor Free
    Thread Starter
       #9

    Okay I was able to follow those steps and reapir the corrupt files. SFC doesn't find any integrity violations anymore; however, while using Photoshop I got the BSOD again. I have atched the minidump files for the most recent crash.
      My Computer


  10. Posts : 73
    Windows Embedded 8.1 Industry Pro
       #10

    Greetings Tyler ^_^,


    Sorry to jump in the thread.
    I analysed your dump files and below has been provided an analysis of the same for informative purposes :-



    Let's see what the bugcheck is all about -

    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: ffffe000988c1740, Physical Device Object of the stack
    Arg3: ffffd00089f5d990, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe0009d377b10, The blocked IRP

    Let's check what was the driver which blocked the IRP which is mentioned in the last parameter.
    Code:
    2: kd> !irp ffffe0009d377b10
    Irp is active with 6 stacks 4 is current (= 0xffffe0009d377cb8)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    
                Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0 e1 ffffe000988c1740 00000000 fffff800334fcb80-ffffd00089efb8c0 Success Error Cancel pending
               \Driver\pci    dxgkrnl!DpiFdoPowerCompletionRoutine
                Args: 00000000 00000001 00000001 00000000
     [ 16, 2]   0 e1 ffffe0009c0d3160 00000000 fffff80114779d74-ffffe0009dbafea8 Success Error Cancel pending
              Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
     \Driver\nvlddmkm    nt!PopRequestCompletion
                Args: 00000000 00000001 00000001 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-ffffe0009dbafea8    
    
    
                Args: 00000000 00000000 00000000 00000000
    And voila! The culprit is the NVIDIA Driver.
    I see that you have updated the NVIDIA Driver -
    Code:
    2: kd> lmvm nvlddmkm
    start             end                 module name
    fffff800`35cd0000 fffff800`367c4000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Sat Oct 03 07:38:52 2015 (560F38B4)
        CheckSum:         00ABDFB7
        ImageSize:        00AF4000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    For laptops, it is generally not recommended to update the drivers until and unless they updates are from the manufacturer. This is because the manufacturers do certain tweaks to support the instant graphics card switching.

    Kindly follow the below instructions -
    1. Please download the Display Driver Uninstaller from this **LINK** and download the graphics driver from this **LINK**.
    2. Run the DDU and then uninstall the currently installed NVIDIA Graphics driver and then reboot the system.
    3. Now, install the driver which you downloaded in Step 1.


    Following the above steps should resolve the problem.

    Let us know how it goes ^_^


    Regards,
    Pranav
    Last edited by blueelvis; 08 Nov 2015 at 11:54.
      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 13:47.
Find Us




Windows 10 Forums