Windows 10: 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 themse

:)

 

Windows 10 BSOD 0x9C

Two dumps name GigaByte Fusion.

A. Analysis Results

File Name: 071719-8343-01.dmp

MACHINE_CHECK_EXCEPTION (9c)

IMAGE_NAME: intelppm.sys

File Name: 071719-8515-01.dmp

MACHINE_CHECK_EXCEPTION (9c)

IMAGE_NAME: intelppm.sys

File Name: 071719-16921-01.dmp

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)

*** WARNING: Unable to verify timestamp for GVCIDrv64.sys

IMAGE_NAME: GVCIDrv64.sys

File Name: 071719-17390-01.dmp

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)

*** WARNING: Unable to verify timestamp for GVCIDrv64.sys

IMAGE_NAME: GVCIDrv64.sys

B. Third Party Drivers

GVCIDrv64.sys - GigaByte Fusion

Driver date - Mon Jan 14 20:00:52 2019

C. Recommendations

1. Update GigaByte Fusion to latest. If BSOD doesn't go away, uninstall it.

 

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.

 

BSOD - INSTB64.SYS - MmMapLockedPages called without MDL_MAPPING_CAN_FAIL

Hi Guys,

It started about a month back. My laptop keeps getting BSOD every evening roughly between 4 - 6 pm. I've the daily minidump files if anyone needs them. But below is effectively what every dump file has.

==========================

BugCheck C4, {81, ffffcf81c6c7af90, 804, 0}

*** WARNING: Unable to verify timestamp for INSTB64.SYS

*** ERROR: Module load completed but symbols could not be loaded for INSTB64.SYS

Probably caused by : INSTB64.SYS ( INSTB64+1743 )

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: 0000000000000081, MmMapLockedPages called without MDL_MAPPING_CAN_FAIL

Arg2: ffffcf81c6c7af90, MDL address.

Arg3: 0000000000000804, MDL flags.

Arg4: 0000000000000000, 0.

===================================

I'm not able to find INSTB64.SYS on my laptop, so can't update or remove the driver, if I can't find it.

Any help to resolve this issue will be greatly appreciated.

Thanks in advance.