locked
Windows 10 Pro 64 bit have reoccuring Driver Power State Failures after upgrade fro Windows 7 Pro 64 bit RRS feed

  • Question

  • After upgrading to Windows 10 Pro from Windows 7.0 Pro I began getting "Blue Screen of Death" and having the system rebooting with the message  "Driver Power State Failure". I believe this must be related to a device driver that needs to be updated. It happens so fast its hard to read the message before it reboots. How do I find out which driver or drivers are causing the failure? Is there a dump log somewhere? Is there a troubleshooter tool that check drivers?

    I also have many event errors that seem to be related to writing log files and permission problems to write the log file.

    Friday, August 14, 2015 9:57 PM

Answers

  • This one crash was Related to jraid.sys JMB36X RAID Driver from JMicron Technology Corp.  Yours is from 2009

    Completely remove the current driver and install the newest driver available.  For instructions on how to do that Read all about updating drivers by my partner JMH3143 here http://answers.microsoft.com/en-us/windows/wiki/windows_other-hardware/updating-a-driver/a5e6345e-af9b-4099-bef0-8d22254aa1c1?tm=1436753520149

    Microsoft (R) Windows Debugger Version 10.0.10240.9 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\zigza\Desktop\MEMORY.DMP]
    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.
    Windows 10 Kernel Version 10240 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 10240.16430.amd64fre.th1.150807-2049
    Machine Name:
    Kernel base = 0xfffff802`bb010000 PsLoadedModuleList = 0xfffff802`bb335030
    Debug session time: Fri Aug 14 16:46:12.671 2015 (UTC - 4:00)
    System Uptime: 0 days 13:30:50.384
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................................................
    Loading User Symbols
    
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, ffffe0007b279050, fffff802bcdbbad0, ffffe0007b90e010}
    
    *** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys
    *** ERROR: Module load completed but symbols could not be loaded for jraid.sys
    Probably caused by : jraid.sys
    
    Followup:     MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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: ffffe0007b279050, Physical Device Object of the stack
    Arg3: fffff802bcdbbad0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe0007b90e010, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    SYSTEM_SKU:  To Be Filled By O.E.M.
    
    SYSTEM_VERSION:  System Version
    
    BIOS_DATE:  12/30/2009
    
    BASEBOARD_PRODUCT:  P6T
    
    BASEBOARD_VERSION:  Rev 1.xx
    
    BUGCHECK_P1: 3
    
    BUGCHECK_P2: ffffe0007b279050
    
    BUGCHECK_P3: fffff802bcdbbad0
    
    BUGCHECK_P4: ffffe0007b90e010
    
    DRVPOWERSTATE_SUBCODE:  3
    
    DRIVER_OBJECT: ffffe0007d365880
    
    IMAGE_NAME:  jraid.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a1cd217
    
    MODULE_NAME: jraid
    
    FAULTING_MODULE: fffff800ffb90000 jraid
    
    CPU_COUNT: 8
    
    CPU_MHZ: a71
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 1a
    
    CPU_STEPPING: 5
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 10.0.10240.9 amd64fre
    
    STACK_TEXT:  
    fffff802`bcdbba98 fffff802`bb2306ea : 00000000`0000009f 00000000`00000003 ffffe000`7b279050 fffff802`bcdbbad0 : nt!KeBugCheckEx
    fffff802`bcdbbaa0 fffff802`bb23060a : ffffe000`80797010 00000000`00000008 00000000`00000000 fffff802`bb0f9191 : nt!PopIrpWatchdogBugcheck+0xde
    fffff802`bcdbbb00 fffff802`bb05f15a : ffffe000`80797048 fffff802`bcdbbc50 00000000`00000001 ffffd000`00000002 : nt!PopIrpWatchdog+0x32
    fffff802`bcdbbb50 fffff802`bb160a5a : fffff802`bb373180 fffff802`bb373180 fffff802`bb3e9740 ffffe000`8028b080 : nt!KiRetireDpcList+0x42a
    fffff802`bcdbbda0 00000000`00000000 : fffff802`bcdbc000 fffff802`bcdb6000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  0x9F_3_IMAGE_jraid.sys
    
    BUCKET_ID:  0x9F_3_IMAGE_jraid.sys
    
    PRIMARY_PROBLEM_CLASS:  0x9F_3_IMAGE_jraid.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x9f_3_image_jraid.sys
    
    FAILURE_ID_HASH:  {17596a60-2fc7-1a67-6cc2-a60acca3143a}
    
    Followup:     MachineOwner
    ---------
    
    0: kd> lmvm jraid
    Browse full module list
    start             end                 module name
    fffff800`ffb90000 fffff800`ffbad000   jraid      (no symbols)           
        Loaded symbol image file: jraid.sys
        Image path: \SystemRoot\System32\drivers\jraid.sys
        Image name: jraid.sys
        Browse all global symbols  functions  data
        Timestamp:        Wed May 27 01:39:35 2009 (4A1CD217)
        CheckSum:         00024AA3
        ImageSize:        0001D000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    0: kd> !drvobj ffffe0007d365880 f
    


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by Retired Vet Saturday, August 15, 2015 5:48 PM
    Saturday, August 15, 2015 3:24 PM

All replies

  •  
    We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  


    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask


    Wanikiya and Dyami--Team Zigzag

    Saturday, August 15, 2015 10:06 AM
  • I have used winzip and put the Memory.DMP file and event description file here on ONEDRIVE.

    https://onedrive.live.com/?id=F6AC07A4F9CB0025%21176&cid=F6AC07A4F9CB0025&group=0

    Saturday, August 15, 2015 3:11 PM
  • This one crash was Related to jraid.sys JMB36X RAID Driver from JMicron Technology Corp.  Yours is from 2009

    Completely remove the current driver and install the newest driver available.  For instructions on how to do that Read all about updating drivers by my partner JMH3143 here http://answers.microsoft.com/en-us/windows/wiki/windows_other-hardware/updating-a-driver/a5e6345e-af9b-4099-bef0-8d22254aa1c1?tm=1436753520149

    Microsoft (R) Windows Debugger Version 10.0.10240.9 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\zigza\Desktop\MEMORY.DMP]
    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.
    Windows 10 Kernel Version 10240 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 10240.16430.amd64fre.th1.150807-2049
    Machine Name:
    Kernel base = 0xfffff802`bb010000 PsLoadedModuleList = 0xfffff802`bb335030
    Debug session time: Fri Aug 14 16:46:12.671 2015 (UTC - 4:00)
    System Uptime: 0 days 13:30:50.384
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................................................
    Loading User Symbols
    
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, ffffe0007b279050, fffff802bcdbbad0, ffffe0007b90e010}
    
    *** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys
    *** ERROR: Module load completed but symbols could not be loaded for jraid.sys
    Probably caused by : jraid.sys
    
    Followup:     MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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: ffffe0007b279050, Physical Device Object of the stack
    Arg3: fffff802bcdbbad0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe0007b90e010, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    SYSTEM_SKU:  To Be Filled By O.E.M.
    
    SYSTEM_VERSION:  System Version
    
    BIOS_DATE:  12/30/2009
    
    BASEBOARD_PRODUCT:  P6T
    
    BASEBOARD_VERSION:  Rev 1.xx
    
    BUGCHECK_P1: 3
    
    BUGCHECK_P2: ffffe0007b279050
    
    BUGCHECK_P3: fffff802bcdbbad0
    
    BUGCHECK_P4: ffffe0007b90e010
    
    DRVPOWERSTATE_SUBCODE:  3
    
    DRIVER_OBJECT: ffffe0007d365880
    
    IMAGE_NAME:  jraid.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a1cd217
    
    MODULE_NAME: jraid
    
    FAULTING_MODULE: fffff800ffb90000 jraid
    
    CPU_COUNT: 8
    
    CPU_MHZ: a71
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 1a
    
    CPU_STEPPING: 5
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 10.0.10240.9 amd64fre
    
    STACK_TEXT:  
    fffff802`bcdbba98 fffff802`bb2306ea : 00000000`0000009f 00000000`00000003 ffffe000`7b279050 fffff802`bcdbbad0 : nt!KeBugCheckEx
    fffff802`bcdbbaa0 fffff802`bb23060a : ffffe000`80797010 00000000`00000008 00000000`00000000 fffff802`bb0f9191 : nt!PopIrpWatchdogBugcheck+0xde
    fffff802`bcdbbb00 fffff802`bb05f15a : ffffe000`80797048 fffff802`bcdbbc50 00000000`00000001 ffffd000`00000002 : nt!PopIrpWatchdog+0x32
    fffff802`bcdbbb50 fffff802`bb160a5a : fffff802`bb373180 fffff802`bb373180 fffff802`bb3e9740 ffffe000`8028b080 : nt!KiRetireDpcList+0x42a
    fffff802`bcdbbda0 00000000`00000000 : fffff802`bcdbc000 fffff802`bcdb6000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  0x9F_3_IMAGE_jraid.sys
    
    BUCKET_ID:  0x9F_3_IMAGE_jraid.sys
    
    PRIMARY_PROBLEM_CLASS:  0x9F_3_IMAGE_jraid.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x9f_3_image_jraid.sys
    
    FAILURE_ID_HASH:  {17596a60-2fc7-1a67-6cc2-a60acca3143a}
    
    Followup:     MachineOwner
    ---------
    
    0: kd> lmvm jraid
    Browse full module list
    start             end                 module name
    fffff800`ffb90000 fffff800`ffbad000   jraid      (no symbols)           
        Loaded symbol image file: jraid.sys
        Image path: \SystemRoot\System32\drivers\jraid.sys
        Image name: jraid.sys
        Browse all global symbols  functions  data
        Timestamp:        Wed May 27 01:39:35 2009 (4A1CD217)
        CheckSum:         00024AA3
        ImageSize:        0001D000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    0: kd> !drvobj ffffe0007d365880 f
    


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by Retired Vet Saturday, August 15, 2015 5:48 PM
    Saturday, August 15, 2015 3:24 PM
  • Thank you. I was able to update the driver to a Windows 8.0 version.  Rev: 1.17.65.11 Dated: 9/17/2012

    I hope that will fix it!

    Saturday, August 15, 2015 5:51 PM