BSOD DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4

Jacky De · 31 Jul 2015

Hello,

I can't remember when the BSOD have begun(last year). They appear random. Sometimes several a day. I used Memtest86+ 5,01 a whole night without any error. All my drivers are updated.
I ran windows a whole night in safe made (F8) without any BSOD. Today I removed also my graphics card Nvidia Geforce GTX550Ti and removed all the drivers with Display Driver Uninstaller from Nvidia to exclude this card. I'm running intel HD graphics 2000 on board now with the latest drivers. So it seems that the graphic card is not the problem.
I have two minidumps from today after running driver verifier.

Thanks for your help.

essenbe · 31 Jul 2015

Hello, Jacky De. Welcome to the forums. You had 2 dump files, both listing the same cause

Code:

Use !analyze -v to get detailed debugging information.
BugCheck C4, {f6, 270, fffff980442d4b10, fffff800033a6a05}
*** WARNING: Unable to verify timestamp for DrvAgent64.SYS
*** ERROR: Module load completed but symbols could not be loaded for DrvAgent64.SYS
Probably caused by : DrvAgent64.SYS ( DrvAgent64+2512 )
Followup: MachineOwner
 
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: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 0000000000000278, Handle value being referenced.
Arg3: fffff9804d09ab10, Address of the current process.
Arg4: fffff800033aaa05, Address inside the driver that is performing the incorrect reference.
Debugging Details:
------------------
 
BUGCHECK_STR:  0xc4_f6
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  DriverAgent.ex

I suggest you remove DriverAgent. The program itself is suspect. You should never use software to update software. The program does not always download the best drivers and often downloads them from suspect locations. I would suggest you uninstall it and check all of your drivers and always download them yourself from the manufacturer's web site.

Jacky De · 01 Aug 2015

hello,

Luckily I dit not use this program. I have removed it now.
I used Driver Verifier manager for the first time yesterday. Didn't know this program was availabe in windows

It seems almost a year I have Random BSOD ntoskrnl.exe 0x0000001e KMODE_EXCEPTION_NOT_HANDLED

I can't remember when the BSOD have begun(last year). They appear random. Sometimes several a day. I used Memtest86+ 5,01 a whole night without any error. All my drivers are updated.
I ran windows a whole night in safe made (F8) without any BSOD.
I have three minidumps from the 29 and 30 juli. The BSOD doesn't show any specific driver causing the BSOD.
Can you analyse these dumps please because I'm not able to use te debugging tool for reading crashdumps.

Thank you

Jacky Deschepper

essenbe · 01 Aug 2015

Jacky De Ffirst, when you run the BSOD Posting Instructions, please upload the whole file. Do not edit it at all.

Please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Please look in Device Manager and see if there are any yellow triangles on anything there.

Please use the Intel tool box and make sure your SSD is working properly and has the latest firmware. Then please run Seatools on your Mechanical Hard drives. SeaTools for DOS and Windows - How to Use

Jacky De · 07 Aug 2015

hello,

I checked everething you mentioned. Even the full diagnotic tool from Intel SSD toolbox seems fine, but nevertheless very slow. After a fresh install of windows 7 the SSD kept very slowly. After attaching a second SSD with windows 7 it was obvious that my SSD was degrading.

I replaced the SSD with a new one and no more blue screens. Even did the update to windows 10 without any problem.

So thanks for your input. My problem is solved

grz

Jacky Deschepper

BSOD DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4

BSOD DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4

BSOD ntoskrnl.exe 0x0000001e KMODE_EXCEPTION_NOT_HANDLED

Bsod