none
DRIVER POWER STATE FAILURE - BSOD. Server 2008 R2 64bit

    Question

  • BlueScreenView points to ntoskrnl.exe.  No problems booting but occasionally crashes when shutting down (always same blue screen).  Updated drivers including BIOS.  Reformatted 2x and problem persists. 
    Wednesday, July 25, 2012 3:37 PM

Answers

  • David,

    The following is the analysis results pointing to ql40xx.sys (QLogic Card) it looks like you can check for updated firmware/drivers for the card and see if there are any available. If none are available you could temporarily remove the card from the system to validate it's the culprit and then potentially replace the card.

    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

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

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


    DRVPOWERSTATE_SUBCODE:  3

    IMAGE_NAME:  ql40xx.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  49e91223

    MODULE_NAME: ql40xx

    FAULTING_MODULE: fffff880014e2000 ql40xx

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT_SERVER

    BUGCHECK_STR:  0x9F

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    STACK_TEXT: 
    fffff800`014da4c8 fffff800`0174d6c2 : 00000000`0000009f 00000000`00000003 fffffa80`048da6a0 fffff800`014da518 : nt!KeBugCheckEx
    fffff800`014da4d0 fffff800`016ede3c : fffff800`014da618 fffff800`014da618 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34050
    fffff800`014da570 fffff800`016edcd6 : fffffa80`07b31d30 fffffa80`07b31d30 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`014da5e0 fffff800`016edbbe : 00000003`0ed05a3c fffff800`014dac58 00000000`00014856 fffff800`01858d48 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`014dac30 fffff800`016ed9a7 : 00000002`ffaa6ac3 fffffa80`00014856 fffffa80`04881558 00000000`00000056 : nt!KiTimerExpiration+0x1be
    fffff800`014dacd0 fffff800`016daeca : fffff800`01855e80 fffff800`01863cc0 00000000`00000000 fffff880`01391810 : nt!KiRetireDpcList+0x277
    fffff800`014dad80 00000000`00000000 : fffff800`014db000 fffff800`014d5000 fffff800`014dad40 00000000`00000000 : nt!KiIdleLoop+0x5a


    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    FAILURE_BUCKET_ID:  X64_0x9F_3_disk_IMAGE_ql40xx.sys

    BUCKET_ID:  X64_0x9F_3_disk_IMAGE_ql40xx.sys

    Followup: MachineOwner


    Doug Kentner


    Wednesday, July 25, 2012 9:49 PM
  • Receive same BSOD after reinstalling OS.  Disabled QLogic adapter and could not replicate issue.  Enabled and got a blue screen on 1st reboot.  Looks like it's the QLogic card.  Opening ticket with vendor.  Thanks guys!
    Tuesday, August 07, 2012 9:32 PM

All replies

  • Sounds likely to be a piece of hardware/driver not handling the system shutdown properly. Do you have a link to a dump you could post?

    Doug Kentner

    Wednesday, July 25, 2012 4:46 PM
  • Sure thing.  Here's a link:

    https://skydrive.live.com/redir?resid=48D26D7CAD3AB249!107&authkey=!AHBiQjr6CnAI2Dw

    Wednesday, July 25, 2012 4:54 PM
  • Hi David, 

    Analyzed dump file"072512-28765-01.dmp" and found below info

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 9F, {3, fffffa80048da6a0, fffff800014da518, fffffa80084abe10}

    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : disk.sys
    Followup: MachineOwner
    ---------
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa80048da6a0, Physical Device Object of the stack
    Arg3: fffff800014da518, Functional Device Object of the stack
    Arg4: fffffa80084abe10, The blocked IRP

    Debugging Details:
    ------------------
    DRVPOWERSTATE_SUBCODE:  3
    IRP_ADDRESS:  fffffa80084abe10
    DEVICE_OBJECT: fffffa8004a26060
    DRIVER_OBJECT: fffffa8004a23d20
    IMAGE_NAME:  disk.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc11d
    MODULE_NAME: disk
    FAULTING_MODULE: fffff88001d18000 disk
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
    BUGCHECK_STR:  0x9F
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    LAST_CONTROL_TRANSFER:  from fffff8000174d6c2 to fffff800016e31c0
    STACK_TEXT:  
    fffff800`014da4c8 fffff800`0174d6c2 : 00000000`0000009f 00000000`00000003 fffffa80`048da6a0 fffff800`014da518 : nt!KeBugCheckEx
    fffff800`014da4d0 fffff800`016ede3c : fffff800`014da618 fffff800`014da618 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34050
    fffff800`014da570 fffff800`016edcd6 : fffffa80`07b31d30 fffffa80`07b31d30 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`014da5e0 fffff800`016edbbe : 00000003`0ed05a3c fffff800`014dac58 00000000`00014856 fffff800`01858d48 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`014dac30 fffff800`016ed9a7 : 00000002`ffaa6ac3 fffffa80`00014856 fffffa80`04881558 00000000`00000056 : nt!KiTimerExpiration+0x1be
    fffff800`014dacd0 fffff800`016daeca : fffff800`01855e80 fffff800`01863cc0 00000000`00000000 fffff880`01391810 : nt!KiRetireDpcList+0x277
    fffff800`014dad80 00000000`00000000 : fffff800`014db000 fffff800`014d5000 fffff800`014dad40 00000000`00000000 : nt!KiIdleLoop+0x5a


    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_disk.sys
    BUCKET_ID:  X64_0x9F_IMAGE_disk.sys
    Followup: MachineOwner
    ---------

    ----------------------------------------------------------------------------------------------------------------------

    Bug Check Code 0x9F:http://msdn.microsoft.com/en-us/library/windows/hardware/ff559329(v=vs.85).aspx

    The errors that cause Parameter 1 to be 0x3, 0x100, or 0x101 only occur in Windows 2000. In Windows XP and later versions of Windows, these errors are superseded by Driver Verifier tests. For more information about Driver Verifier, see the Driver Verifier section of the Windows Driver Kit.

    To read dump files: http://support.microsoft.com/kb/315263



    Regards, Ravikumar P

    Wednesday, July 25, 2012 5:56 PM
  • Thanks Ravikumar,

    Does this point to disk.sys? If so, should I do a repair install or reformat again?

    Wednesday, July 25, 2012 7:32 PM
  • Yes, you can check for HDD errors, if any? 

    I suggest you do this steps one by one.

    1. Run chkdsk once and check for the difference.A useful link for your reference Chkdsk:http://technet.microsoft.com/en-us/library/cc730714(v=ws.10).aspx
    2. Go for disk de-fragmentation once. Refer Defrag:http://technet.microsoft.com/en-us/library/cc731650(v=ws.10)
    3. Run sfc once. For more details refer sfc:http://technet.microsoft.com/en-us/library/ff950779(v=ws.10)
    4. Still problem persists we don't have any other option expect re-installation of OS again.

    Regards, Ravikumar P

    Wednesday, July 25, 2012 8:01 PM
  • David,

    The following is the analysis results pointing to ql40xx.sys (QLogic Card) it looks like you can check for updated firmware/drivers for the card and see if there are any available. If none are available you could temporarily remove the card from the system to validate it's the culprit and then potentially replace the card.

    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

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

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


    DRVPOWERSTATE_SUBCODE:  3

    IMAGE_NAME:  ql40xx.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  49e91223

    MODULE_NAME: ql40xx

    FAULTING_MODULE: fffff880014e2000 ql40xx

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT_SERVER

    BUGCHECK_STR:  0x9F

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    STACK_TEXT: 
    fffff800`014da4c8 fffff800`0174d6c2 : 00000000`0000009f 00000000`00000003 fffffa80`048da6a0 fffff800`014da518 : nt!KeBugCheckEx
    fffff800`014da4d0 fffff800`016ede3c : fffff800`014da618 fffff800`014da618 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34050
    fffff800`014da570 fffff800`016edcd6 : fffffa80`07b31d30 fffffa80`07b31d30 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`014da5e0 fffff800`016edbbe : 00000003`0ed05a3c fffff800`014dac58 00000000`00014856 fffff800`01858d48 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`014dac30 fffff800`016ed9a7 : 00000002`ffaa6ac3 fffffa80`00014856 fffffa80`04881558 00000000`00000056 : nt!KiTimerExpiration+0x1be
    fffff800`014dacd0 fffff800`016daeca : fffff800`01855e80 fffff800`01863cc0 00000000`00000000 fffff880`01391810 : nt!KiRetireDpcList+0x277
    fffff800`014dad80 00000000`00000000 : fffff800`014db000 fffff800`014d5000 fffff800`014dad40 00000000`00000000 : nt!KiIdleLoop+0x5a


    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    FAILURE_BUCKET_ID:  X64_0x9F_3_disk_IMAGE_ql40xx.sys

    BUCKET_ID:  X64_0x9F_3_disk_IMAGE_ql40xx.sys

    Followup: MachineOwner


    Doug Kentner


    Wednesday, July 25, 2012 9:49 PM
  • Hi,

     

    If reinstalling system cannot fix the issue, it mostly can be a hardware issue.

    You may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

    Regards,


    Arthur Li

    TechNet Community Support

    Thursday, July 26, 2012 3:08 AM
    Moderator
  • Ran chkdsk, found no problems.  Defragged then ran sfc; did not find any integrity violations.  Will look in to upgrading the QLogic card or removing it from the system if no further upgrade is available. 

    Thanks for the feedback guys.  I'll let you know how it goes.

    Thursday, July 26, 2012 12:21 PM
  • Hi,

     

    I would like to confirm what is the current situation? If there is anything that I can do for you, please do not hesitate to let me know, and I will be happy to help.

    Regards,


    Arthur Li

    TechNet Community Support

    Monday, August 06, 2012 2:27 AM
    Moderator
  • Thanks for following up Arthur.  Started getting a different Blue Screen; wiped hard drive and started over.  Have not run in to problems yet but need to install updates and drivers to see if the issue has been resolved.
    Monday, August 06, 2012 12:09 PM
  • Receive same BSOD after reinstalling OS.  Disabled QLogic adapter and could not replicate issue.  Enabled and got a blue screen on 1st reboot.  Looks like it's the QLogic card.  Opening ticket with vendor.  Thanks guys!
    Tuesday, August 07, 2012 9:32 PM