Windows 10 Driver Verifier Detected Violation

I have a driver built with WDK 8.1 which I'm trying to run on Windows 10 with the Verifier. Intel Ironlake Mobile Graphics Chipset Driver Windows 10 64 Bit here. BSOD 0xC4 on Windows 10.

I have a driver built with WDK 8.1 which I'm trying to run on Windows 10 with the Verifier enabled with Code Integrity check. I receive the following BSOD when the driver is started: Do I need to rebuild the Driver with changing any settings. And what is the meaning of 'Arg1: 00002000, subclass of driver violation.' Bugcheck Analysis: DRIVER_VERIFIER_DETECTED_VIOLATION (c4) A device driver attempting to corrupt the system has been caught.

This is because the driver was specified in the registry as being suspect (by the administrator) and the kernel has enabled substantial checking of this driver. If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will be among the most commonly seen crashes. Arguments: Arg1: 00002000, subclass of driver violation. According to arg 0x2000 suggests you are calling StorPortInitialize function please double check that you are using the correct OS symbols otherwise debugger output can be completely wrong! Also include a symbol folder path for your driver (File ->symbol file path). You have here: details on how to use the Microsoft symbols server in order download required OS symbols. You can add to your symbol path something like srv c: MyTempSymbolFolder but be sure to use ';' do delimit symbol paths After doing this should be able to do this commands in windbg successfully:.reload /f nt.reload /f McPvDrv.sys and now rerun the!analyze -v command which might show you a modified call stack. Usb Display Adapter Driver Windows 10.

Comments are closed.