BSOD while Gaming - DRIVER_POWER_STATE_FAILURE - BasicDisplay.sys

Oh sry, didn't see the posting instruction. I will add the SysnativeFileCollectionApp.zip soon if needed
 
Moin,

your BSOD

Code:
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe001a191f060, Physical Device Object of the stack
Arg3: fffff800f81afad0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe001a3575630, The blocked IRP

The failing device
Code:
Device object (ffffe001a191f060) is for:
 Cannot read info offset from nt!ObpInfoMaskToOffset
 \Driver\BasicDisplay DriverObject ffffe0019fbf8cf0
Current Irp 00000000 RefCount 1 Type 0000001c Flags 00003044
Dacl ffffc1027082f581 DevExt ffffe001a191f1b0 DevObjExt ffffe001a191f588 DevNode ffffe001a1725010 
ExtensionFlags (0000000000)  
Characteristics (0x00000180)  [COLOR=#ff0000]FILE_AUTOGENERATED_DEVICE_NAME[/COLOR], FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffffe001a1748040 \Driver\monitor
Device queue is not busy.

likely your Daemontools, get rid of them, specially in Win10.
Digging into the rest of the reconstructed Stack, a cpu is hindered to do its work, also Daemontools work.

unsure if you need this old driver and for what reason.
Driver Reference Table - KovaPlusFltr.sys

fffff801`7d4a0000 fffff801`7d4a3b00 KovaPlusFltr KovaPlusFltr.sys Mon Jan 25 14:23:58 2010 (4B5D9B6E)


not the newest one?

regards
Michael
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top