locked
DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time (usually 10 minutes). RRS feed

  • Question

  • Ever since purchasing a HP Pavillion Elite HPE, I've gotten a blue screen error after the machine has been in standby for some period of time. Windows is shut down to apparently prevent possible data loss. I am quite new to Windows debugging and can not proceed beyond: "Arg4: fffffa800badc280, The blocked IRP". Below is the minidump file and I would greatly aappreciate any help in determing which driver is the culprit here.

    Microsoft (R) Windows Debugger Version 6.2.8229.0 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Users\Ron\Downloads\052512-37019-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*c:\symbols*http://microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
    Machine Name:
    Kernel base = 0xfffff800`02e06000 PsLoadedModuleList = 0xfffff800`0304a670
    Debug session time: Fri May 25 12:53:30.857 2012 (UTC - 4:00)
    System Uptime: 0 days 3:58:43.043
    Loading Kernel Symbols
    .

    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.

    ..............................................................
    ................................................................
    ................................................................
    ..
    Loading User Symbols
    Loading unloaded module list
    ....................
    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\oca.ini, error 2
    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\winxp\triage.ini, error 2
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 9F, {3, fffffa800702e500, fffff80000b9c518, fffffa800badc280}

    *** WARNING: Unable to verify timestamp for lvuvc64.sys
    *** ERROR: Module load completed but symbols could not be loaded for lvuvc64.sys
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
    Probably caused by : lvuvc64.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 (usually 10 minutes).
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa800702e500, Physical Device Object of the stack
    Arg3: fffff80000b9c518, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa800badc280, The blocked IRP

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

    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

    DRVPOWERSTATE_SUBCODE:  3

    DEVICE_OBJECT: fffffa8006cf4e10

    DRIVER_OBJECT: fffffa8006f2ae70

    IMAGE_NAME:  lvuvc64.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  46450350

    MODULE_NAME: lvuvc64

    FAULTING_MODULE: fffff88007818000 lvuvc64

    IRP_ADDRESS:  fffffa800badc280

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    BUGCHECK_STR:  0x9F

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    STACK_TEXT:  
    fffff800`00b9c4c8 fffff800`02eef702 : 00000000`0000009f 00000000`00000003 fffffa80`0702e500 fffff800`00b9c518 : nt!KeBugCheckEx
    fffff800`00b9c4d0 fffff800`02e8fe4c : fffff800`00b9c600 fffff800`00b9c600 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x34050
    fffff800`00b9c570 fffff800`02e8fce6 : fffffa80`0a1199a8 fffffa80`0a1199a8 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00b9c5e0 fffff800`02e8fbce : 00000021`59331175 fffff800`00b9cc58 00000000`000e0279 fffff800`02ffb1a8 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9cc30 fffff800`02e8f9b7 : 00000030`497a40c3 00000030`000e0279 00000030`497a405e 00000000`00000079 : nt!KiTimerExpiration+0x1be
    fffff800`00b9ccd0 fffff800`02e7ceca : fffff800`02ff7e80 fffff800`03005cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_lvuvc64.sys

    BUCKET_ID:  X64_0x9F_3_IMAGE_lvuvc64.sys

    Followup: MachineOwner
    ---------

    Friday, May 25, 2012 11:06 PM

Answers

  • The culprit appears to be the lvuvc64.sys:

    BUCKET_ID:  X64_0x9F_3_IMAGE_lvuvc64.sys

    The lvuvc64.sys is a driver for a Logitech camera so try updating or, if necessary, remove the Logitech camera/drivers. 

    • Marked as answer by webdevil1 Monday, May 28, 2012 1:59 PM
    Sunday, May 27, 2012 12:51 AM

All replies

  • The culprit appears to be the lvuvc64.sys:

    BUCKET_ID:  X64_0x9F_3_IMAGE_lvuvc64.sys

    The lvuvc64.sys is a driver for a Logitech camera so try updating or, if necessary, remove the Logitech camera/drivers. 

    • Marked as answer by webdevil1 Monday, May 28, 2012 1:59 PM
    Sunday, May 27, 2012 12:51 AM
  • Removing the Logitech driver has solved the problem. I greatly appreciate your reply.
    Monday, May 28, 2012 2:01 PM
  • You're welcome. Glad that worked.
    Monday, May 28, 2012 11:17 PM