BSOD getting more Frequeuent BCCode:f4 BCP1:03 BCP2:FFFFFA80060F6

[Bob Myles]

Hello,
Hopefully this is 'just' a driver issue, but which one?
HP Pavilion dv7 Notebook
Win 7 Ent 64-bit
Random and infrequent BSODs started several months ago.. Put new Segate 500GB HDD with fresh install win 7 x64 (Dec 2011). Updated / patched everything. BSODs continued although I did not track frequency to compare, just lived with it as it did not impact too much and the rebooting seemed to help sytem performance a bit. New HDD did not stop the BSODs, so I put old HDD back in (Jan 2012) to use as extra storage and to boot to if the 'new' disk failed.. BSODs continued infrequently for the next two months. BSODs have increased to at least one a day now.. this is impacting...
I assume it is a driver issue, but I cannot figure out which one. Hopefully this information will point in the right direction.

BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA80060F6B30
BCP3: FFFFFA80060F6E10
BCP4: FFFFF8000339E660
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Multiple mini dump files in the attachment...

Thanks for any help as I am not at the level to figure it out...

 

[zigzag3143]

There are two major issues. Both appear to be software. Both are system related.

First lets rule out malware. Please run malwarebytes.

Please download the free version of Malwarebytes.
Update it immediately.
Do a full system scan
Let us know the results at the end.

Malwarebytes : Download free malware, virus and spyware tools to get your computer back in shape!


Only if malwarebytes comes up clean please run a system file check to verify your OS.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

 

[Bob Myles]

Update Frequent BSODS

Thanks zigzag3143, for your insight.
I ran Malware.. it found nothing.. all 0's
I ran the sfc tool and it found 2 corrupted files:
wspsvc.dll and diskmgt.chm
both were replaced in safe mode command prompt..
still crashed.
Ran sfc again and diskmgt.chm showed up, but wspsvc.dll seemed to be ok..
several attempts to fix the diskmgt.chm file, but it showed up as corrupted in sfc even after sfc reported all fixed... the file itself opens and works, just signature or crc or hash something doesn't match
I removed all references to diskmgt.chm in registry. Hard to believe such trouble with a help file??
SFC reports 100% complete and integrity ok..
Had another BSOD about an hour ago, this time with slightly different numbers..
Have cleared all caches and temp files. Ran CCleaner to 'clean registry' as much as that tool does..
Since 'cleaning' up all those temp files, log files etc, this zip file only contains the latest dmp file..
So you see anything else i might try?
Thanks again!

 

[zigzag3143]

Bob

This one was related to a critical process termination of wininit.exe. after an uptime of 1 hour 41 mins it is fairly un-usual for wininit to crash and burn.

There are a couple of old drivers needing updating but nothing other than that jumps out at me.

Old driver

enecir.sys    3/7/2007 4:28:17 AM        fffff880`04200000    fffff880`04215000    0x00015000    0x45ee77a1                        
agrsm64.sys    11/10/2008 11:01:35 AM        fffff880`0669b000    fffff880`067bd000    0x00122000    0x49184ccf                        
mcdbus.sys    2/24/2009 6:34:07 AM        fffff880`03d24000    fffff880`03d60880    0x0003c880    0x49a3cd1f                        
Rt64win7.sys    5/22/2009 10:52:30 AM        fffff880`044f6000    fffff880`0452f000    0x00039000    0x4a16bc2e

How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference "http://www.carrona.org/dvrref.php"]Driver Reference

- - Driver manufacturer links are on this page: "http://www.carrona.org/drvrdown.html"]Drivers and Downloads



If I were you I would run verifier to find the mis-behaving driver and you might also want to run memtest (just in case)




Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html






Driver Verifer

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JGriff2 & Usasma.

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[Bob Myles]

I Give Up

guys,
I downloaded and ran the memtest over the weekend.. no issues.
Ran the HDD diagnostics that this HP has in the BIOS.. no issues on either HDD.. then tried to create a restore point to run the driver verifier, but couldn't even get restore to run..
finally I gave up and formatted the old drive, set up clean install of win 7 updated and patched and its been running fine since Sunday.. today is Tues, so we will have to see, but for now it seems very stable and no BSODs.. Since I have the 'new' drive, i can move all my programs and files to the OS Drive and use the 'new' drive as storage as its OS install is bad..

Thanks for all your help!!
Bob