Windows 10: Driver_verifier_iomanager_violation BSOD c9 WUDFRD.sys problem

I have been experiencing a BSOD f9 driver_power_state_failure error when rebooting, but is eventually able to finally restart Windows. I turned to running verifier.exe to troubleshoot it, set to verify all drivers during the next restart, and during the reboot it produced another BSOD, this time c9 driver_verifier_iomanager_violation for the windows driver WUDFRD.sys. Upon reboot again, the computer did a "repair" of windows so that it could restart, but the problem is persisting to report the BSOD f9 error upon restarts.


How can I fix this error, which is reportedly pointing to a problem with wudfrd.sys? (the problem began after the most recent Windows Update this past Tue)

:)

 

Driver Verifier BSOD C9 DRIVER_VERIFIER_IOMANAGER_VIOLATION

Recently while gaming, my applications have been crashing after a period of time. (Usually within the time frame of 15-30 minutes). I have been investigating this for quite some time now, and I've come up with no solutions.

Troubleshooting steps I have done are:

• Tried reverting back to the last "most stable" driver for my GPU (Clean Install)
• Updated video drivers to the latest version (Clean install)
• Checked my SSD for errors using software from the vendor (Don't believe this is an issue because two games are on different disks, and the same thing happens)
• Checked my RAM with memtest86 for 24 hours (Did this twice now)
• Scanned for malware, no threats found
• Used CCleaner to clean **** off of my computer
• Ensured Windows was fully up-to-date with the latest critical and optional patches

Just a bit ago I found a thread recommending that I try to run Driver Verifier. Within a few seconds after the reboot to being running Driver Verifier, I had a BSOD C9 DRIVER_VERIFIER_IOMANAGER_VIOLATION(HIDCLASS.SYS). I have no idea which driver is causing
me troubles, and I'm not that good at understanding dump files.

In the links below are my .dmp files. The first one is from the Driver Verifier, and the other two are BSODs that I occasional get while gaming.

0xC9 DRIVER_VERIFIER_IOMANAGER_VIOLATION dump file

0x1A MEMORY_MANAGEMENT dump file

0x4E PFN_LIST_CORRUPT dump file

Link to Dump files

I also previously posted a question on 10 Forums that might have more helpful information. It can be found in the link below.

PC Crashes While Gaming, error 0xC0000005 - Windows 10 Forums

 

Memory_Management BSOD on Clean boot, VERY specific circumstances


Something else I see in your dump file for 1 Jul is a driver misbehaving. The code suggests you have Driver Verifier running. You should disable this for normal use.

Code:

Code:

BugCheck C9, {228, fffff800781a3074, ffffcf811f40ee10, 0}  *** WARNING: Unable to verify timestamp for PxHlpa64.sys *** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys Probably caused by : PxHlpa64.sys ( PxHlpa64+3074 )  DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9) The IO manager has caught a misbehaving driver.

Having seen that error you should also remove the program that uses that driver which is probably related to anything provided by SONIC

 

BSOD - ntoskrnl.exe & ntkrnlmp.exe


Hello, acfourleaf and welcome to the forums.

Code:

Code:

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9) The IO manager has caught a misbehaving driver. Arguments: Arg1: 0000000000000006, IRP passed to IoCompleteRequest contains invalid status Arg2: 0000000000000103, the status Arg3: ffffe0010349f110, the IRP Arg4: 0000000000000000

You had a hard drive I/O problem according supposedly caused by

Use !analyze -v to get detailed debugging information.
BugCheck C9, {6, 103, ffffe0010349f110, 0}
Code:

Code:

Unable to load image \SystemRoot\System32\drivers\ISCTD64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ISCTD64.sys *** ERROR: Module load completed but symbols could not be loaded for ISCTD64.sys Probably caused by : ntkrnlmp.exe ( nt!IovCompleteRequest+c3 ) Followup:     MachineOwner

That is the driver for the Intel Smart Connect technology. That seems to cause some people a lot of problems. I would suggest disabling it, if you can. If you continue to have problems, Check the hard drives with the manufacturer's diagnostic program. If you need to know what Smart connect does, I will try to explain it for you, but I suspect you know. If your System Specs had listed your hard drives, I could tell you the which test to run probably. If you need to know, just tell me what hard drives you have and I may be able to give you a link.