Windows 10: DRIVER_VERIFIER_DETECTED_VIOLATION c4

Hi, my computer recently automatically turn off. I have checked the minidump report and it shows as belowRIVER_VERIFIER_DETECTED_VIOLATION c4A device driver attempting to corrupt the system has been caught. This isbecause the driver was specified in the registry as being suspect by theadministrator and the kernel has enabled substantial checking of this driver.If the driver attempts to corrupt the system, BugChecks 0xC4, 0xC1 and 0xA willbe among the most commonly seen crashes.Arguments:Arg1: 0000000000002000, Code Integrity Issue: The caller specified an executable pool t

:)

 

How to fix DRIVER_VERIFIER_DETECTED_VIOLATION (c4)

I recently tried using driver verifier because I was getting various blue screens of death, including bad pool caller and irql_not_less_or_equal. When I turned it on I got stuck in a loop of blue screens with the error DRIVER_VERIFIER_DETECTED_VIOLATION. I entered safe mode, and turned off driver verifier, I tried reading my minidump file for the crash, but whenever I use !verifier 3 drivername,sys, which is what I was told to use, it says "Unable to read driver name at 0000000000000000". I don't know what to do to fix this. Here are all my recent minidump files:

022523-31468-01

022523-31468-01

022523-31468-01

022523-31468-01

022523-31468-01

 

BSOD with Logitech Webcam

The First BSOD dump file>(042017-5125-01.dmp) caused by the driver verifier software , i recommend to disable it.

BugCheck C4, {2004, ffffcc08f196e658, fffff80099a00220, ffffdc81037340a8}

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)

Some developer content:

Bug Check 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION - Windows 10 hardware dev

-----------------------------------------------------------------------------------------------------

The second BSOD cause is same driver verifier.

BugCheck C4, {2004, ffffd302cec376a8, fffff8027c1b0220, ffffbc01cb9640a8}

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)

-----------------------------------------------------------------------------------------------------

The last BSOD cause is also same driver verifier

BugCheck C4, {2004, ffffa2812c748278, fffff8012ec00220, ffffe501f05c50a8}

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)

Regards.

 

DRIVER_VERIFIER_DETECTED_VIOLATION (c4) AmUHubftr.sys (20+ BSODs please help)

Hey yall,

So I followed the driver verifier instructions here after days of BSODs and memory checks, drive checks, driver updates, windows restarts, and still getting crashes. Long story short my PC bluescreened right away after restarting with driver verifier on it poped out a DMP that blames AmUHubftr.sys.

This is some kind of generic USB hub driver from 2013. The file literally says last modified 12/20/2013 and that seems to be the latest version available anywhere. I have already completely reinstalled windows 3 times trying to fix this. Is it possible it is one of my USB devices themselves causing this? Can I just delete the file?

Anyway here's the WinDbg output. Any help would be wonderful I am at my wit's end here.