Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


31 Jul 2015   #1
Jacky De

Windows 7 home premium 64bit


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.

My System SpecsSystem Spec
31 Jul 2015   #2

Windows 10 Pro/ Windows 10 Pro Insider

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

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
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.
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
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.
My System SpecsSystem Spec
01 Aug 2015   #3
Jacky De

Windows 7 home premium 64bit
BSOD ntoskrnl.exe 0x0000001e KMODE_EXCEPTION_NOT_HANDLED


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
My System SpecsSystem Spec

01 Aug 2015   #4

Windows 10 Pro/ Windows 10 Pro Insider

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
My System SpecsSystem Spec
07 Aug 2015   #5
Jacky De

Windows 7 home premium 64bit


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


Jacky Deschepper
My System SpecsSystem Spec


Thread Tools

Similar help and support threads
Thread Forum
BSOD error 0x000000C4
My laptop had a BSOD crash last night and one about 3 days ago. The one three days ago I just ignored because it had happened once about 6 months ago, but never since then. I thought it might be nothing. When it happened again last night, I started looking online to see what might be going on. I...
BSOD Help and Support
BSOD after closing game : Driver_Verifier_Detected_Violation
Hello everyone, this is my first discussione here! So I got a new computer 2 weeks ago (i changed everything except the HDD) and it went very smooth with the SSD ;) So on 7/6/2014 and on 11/6/2014 I got two BSOD regarding the "Driver_Verifier_Detected_Violation". I tried to upgrade EVERY...
BSOD Help and Support
BSOD after playing APB, 0x000000C4 and 0x0000004E
I got the PFN corrupt while playing APB: Reloaded got the other two crashes after using driver verifier also BSOD before playing BF4
BSOD Help and Support
BSOD 0x000000c4 and 0x00000101
BSOD 0x000000c4 and 0x00000101
BSOD Help and Support
Over the pass few days I have been having a BSOD, so I downloaded BlueScreenView and saw that it was caused by the driver ntoskrnl.exe with the address ntoskrnl.exe+75c40. So far this error has caused 12 BSoD since the start of the year. However I am not sure what application is causing this BSoD,...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 14:40.
Twitter Facebook Google+