Microsoft drivers are considered to be sacrosanct and therefore are ruled out as the culprit in a BSOD. In this case it is 0x3, which tells you immediately that the Windbg command !irp can be run, which hopefully will reveal the name of a 3rd party driver (non-Microsoft driver). NOTE: there is no P2 or P3 listed in the parameters of the bugcheck - I simply listed the commas with no values between them where these items would normally be)įor 0x9f bugcheck dumps, first, you look at P1. If you come upon a dump with bugcheck and parms = 0x9f (0x3,fffffa80'0ab61bd0) ¹ (the memory address in P4 is variable - no 2 dumps or systems will contain the exact same memory address). P4 = memory address of the blocked IRP (an I/O Request Packet)Ĭause - A device object has been blocking an IRP for too long a time. In Windows 7 and later, nt!TRIAGE_9F_POWER P3 = memory address of the functional device object (FDO) of the stack. P2 = memory address of the physical device object (PDO) of the stack Every bugcheck has 4 Parameters enclosed by parenthesis following it. P1, P2, P3, P4 = the Parameters (numbers) inside the parenthesis after the bugcheck code. 0x9f=DRIVER_POWER_STATE_FAILURE and indicates that a driver is in an inconsistent or invalid power state.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |