BSOD - DRIVER_POWER_STATE_FAILURE - 0x0000009f

Monday, August 12, 2019

Posted Today, 02:50 PM
Hi. . .

2 of the 5 dumps you submitted were zero (-0-) bytes in size. This means that Windows came down so fast that it did not have time to write a dump or an "unknown" hardware problem exists and the computer literally shut off/lost power before it could write the dump (akin to someone pulling out the electrical plug on a desktop PC.

BSOD Kernel memory dumps are created to help software developers debug their code, not really to help us with hardware issues. In fact, dump files are incapable of telling us which piece of hardware is/has failed. At best, dumps can point us in a general direction, for example, telling us that an I/O error occurred, which to me means that the system encountered trouble with a hard drive. Again, that was just an example and I was NOT referring to your system.

Of the 3 remaining dumps, 2 of them had bugchecks = 0xc4 which means that Driver Verifier flagged a driver. The driver named was the Microsoft Windows Network I/O Subsystem driver netio.sys

This presents at least 2 problems. The Driver Verifier instructions state to only select 3rd party drivers (non-Microsoft drivers). Did you do this step correctly?

If so, having Driver Verifier list a Microsoft driver leas us to the direction of unknown hardware failure as the probable cause. netio.sys being a Microsoft driver means that it is sacrosanct and could not possibly be the actual cause of the BSOD. If it were, many millions of other people would also be experiencing BSODs because they have the exact same version of that driver that you do.

The 3rd dump had a bugcheck = [0x9f (0x3,,,)[/b] = DRIVER_POWER_STATE_FAILURE; A device has been blocking an IRP for too long a time. (IRP = Input/Output request packets)

Digging deeper into the 0x9f dump reveals the blocked IRP -
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffff8f8a2f2aa030 00000000 fffff8002ab6f520-ffff8f8a329a9ee8 Success Error Cancel pending
        \Driver\nvlddmkm nt!PopRequestCompletion
   Args: 00000000 00000001 00000001 00000000
If you look carefully through that seemingly jumbled mess, you'll see nvlddmkm after the word \driver

nvlddmkm.sys is your NVIDIA video card driver. Your driver is relatively new - just about 1 month old. From your dump file -
nvlddmkm.sys Wed Jul 17 14:04:33 2019 (5D2F8D61)
https://www.sysnative.com/drivers/driver.php?id=nvlddmkm.sys

I would suggest rolling the driver back, but we also need to test your video card.

Run FurMark - https://www.sysnative.com/forums/threads/furmark-display-card-stress-test.3907/

Please post the results.

If Furmark passes, then run Driver Verifier - https://www.bleepingcomputer.com/forums/t/576333/driver-verifier-bsod-related-windows-10-81-8-7-vista/

Driver Verifier must run for at least 24 hours and it's job is to stress-test your 3rd party drivers and force a BSOD if it detects a violation.

Please use these settings - https://www.bleepingcomputer.com/forums/t/576333/driver-verifier-bsod-related-windows-10-81-8-7-vista/

I must admit that after seeing netio.sys, finding NVIDIA in the 0x9f dump threw me for a loop as I was expecting to see either your wifi or Ethernet driver (a networking driver), not your video driver.

And of course, the 2 dumps showing zero bytes in size is bothersome. Also, every file in the Sysnative zip file shows as 1/1/1980 12:00 AM, which I have no idea why the files would display like that (but I have seen this phenomenon before) as I wrote the Sysnative app.

Screenshot of the 5 dump files showing the date and time (timestamp) as well as the two dumps that are -0- bytes in size -

08-12-2019e.PNG 

post-208009-0-61397600-1565635656.png

Regards. . .

jcgriff2

p.s. ntoskrnl.exe (that you mentioned WhoCrashed said was the cause of the 0x9f dump) is the Windows kernel and could not possibly be the cause of your BSODs. ntoskrnl.exe is often named as a default of sorts when the real cause cannot be determined. 
Edited by jcgriff2, Today, 02:51 PM.

244x90_BC_04-04-2019.png

0 comments:

Text

Powered by Blogger.

Search This Blog

Popular Posts