DRIVER_POWER_STATE_FAILURE question


Hello

We're receiving a recurring Vista32 crash from a customer. WinDbg
analyses the crash dump as follows:

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

It's actually an IRP_MJ_POWER/IRP_MN_SET_POWER for D0 that gets stuck
in the power manager.

Q: How long is too long? What is the time-out period that triggers
this crash?
.

Relevant Pages

  • Re: DRIVER_POWER_STATE_FAILURE question
    ... Please do not send e-mail directly to this alias. ... We're receiving a recurring Vista32 crash from a customer. ... A device object has been blocking an Irp for too long ... Functional Device Object of the stack ...
    (microsoft.public.development.device.drivers)
  • Re: a dozen cpus on a chip
    ... It is still possible to write something that will crash, ... memory, or write to memory it doesn't own should be terminated with a ... I think that hardware designers could do a lot to improve matters. ... Having a call-return stack, a parameter stack, return value area, and ...
    (sci.electronics.design)
  • Re: boot failure, "DWARF2 unwinder stuck at 0xc0100199"
    ... The way that code reads the stack is just ... this unwinder change has been quite problematic. ... add new crashes and the fallback always gives an useful backtrace (that is why I ... Has anyone even tried to reproduce Bruce's crash? ...
    (Linux-Kernel)
  • Re: wuauclt.exe has encountered a problem...
    ... That is the full extent of the message and pop-up detail. ... Have you disabled the Error Reporting Tool? ... to extract from it a list of the modules involved in the call stack at the time ... I'm suggesting only that you find the one entry which represents your crash event. ...
    (microsoft.public.windowsupdate)
  • Re: Bugcheck 101
    ... This is what the stack in the hung processor looks like: ... The bugcheck information should show the hung processor. ... the crash, and all 8 virtual processors are busy at that time. ... waiting for a timer interrupt, and while processor 3 is the timed out ...
    (microsoft.public.development.device.drivers)