Share via

Need help tracking down a BSOD

Anonymous
2015-11-10T14:43:19+00:00

I am trying to track down a driver causing a BSOD.

Link to DMP file - https://drive.google.com/file/d/0B\_-LZWgetMc1VmhTOW9iVFNFRVE/view?usp=sharing

I installed and and trying to look in WinDBG, I get:

DRIVER_POWER_STATE_FAILURE (9f)

A driver has failed to complete a power IRP within a specific time.

Arguments:

Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp

subsystem.

Arg2: 0000000000000258, Timeout in seconds.

Arg3: fffffa8006d1ab50, The thread currently holding on to the Pnp lock.

Arg4: fffff80000b9a3d0, nt!TRIAGE_9F_PNP on Win7 and higher

I read that Arg4 is the driver and to run !IRP on it.  When I do that I get:

IRP signature does not match, probably not an IRP.  Use any flag to force.

Thanks for any help!

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2015-11-10T14:56:49+00:00

Kudo's on the debugging.  You cant use !IRP on a TRIAGED ARG.  There are flags to force it but you are probably simply better off running verifier since it is a PNP driver.  I would also updated the below old drivers

1-Driver verifier (for complete directions see our wiki here)

dwvkbd64.sys    4/11/2007 4:22:37 PM     

dfmirage.sys    1/11/2008 4:04:26 PM      

DamewareMini.sys    3/16/2008 1:42:28 PM    

LVPr2M64.sys    4/30/2009 5:42:17 PM   

!IRP FLAGS

https://msdn.microsoft.com/en-us/library/windows/hardware/ff548630%28v=vs.85%29.aspx

https://msdn.microsoft.com/en-us/library/windows/hardware/ff548597%28v=vs.85%29.aspx

Was this answer helpful?

0 comments No comments

4 additional answers

Sort by: Most helpful
  1. Anonymous
    2015-11-10T17:03:14+00:00

    Happy to help and yell if I can be of assistance.  I will stay subscribed to the thread.  Again Kudo's for the WinDbg

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-11-10T16:31:06+00:00

    Dameware drivers get installed from the client on my machine when I try to connect.  Can't really install them in compatibility mode.

    He does have a Logitech webcam connected VIA USB, since the last driver from 2009 is a logitech one, I might start there.  Thanks man!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-11-10T16:00:47+00:00

    You may need to re-install damware in compatibility mode if they do not have a more recent version.  I do not think they are the issue but since BSODS are always a combination of things they might be related.  I suspect it is something else which is why I suggested verifier.

    fffff80000b9a3d0, nt!TRIAGE_9F_PNP on Win7 and higher

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-11-10T15:49:47+00:00

    So it's a PNP device?  The top 3 drivers are Dameware, they are as updated as Dameware has (per my software).  The last one, however, is a logitech camera.

    If it's a PNP device, that might be a good place to start.

    Side note, this user was having issues with windows opening slow.  Not choppy but about 25% the speed.  Found some similar issue and ran this {bcdedit /set useplatformclock true}

    Not sure if that could be causing this?

    Was this answer helpful?

    0 comments No comments