Windows 7: Bugcheck 0x0000007f crashes driving me crazy

FAE · 14 Dec 2009

This BSOD is driving me crazy.

From the start I get these crashes. All messages are always the same in the eventlog:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007f (0x0000000000000008, 0x0000000080050031, 0x00000000000006f8, 0xfffff80002c457a0).

The only thing that changes is the last parameter.
I removed any add-on card I had. I upgraded bios to the lates version (1102). I checked the CPU by running prime95 with 8 threads for 20hours+
I ran the extended memory test several nights in a row and never found an issue with the memory.

The BSOD occurs randomly (twice a day) but up to now never when there is a lot going on. Usually when surfing, word, excel or something.
I cannot find allot on the internet regarding this error besides double fault and check RAM and update bios. I've done all of that.

Config:
Windows 7 64bit
Intel i7 860 - 2.8Ghz (NO OC)
8GB (4 x 2GB)Kingston 1600Mhz memory but running it at 1333
Enermax EPR625AWT PRO 82+ 625W
MSI 240GT videocard
2xIntel X25-M G2 80GB in raid0 (total 160GB)
1xWD 1TB drive

This should not tax the power supply at all (Fan rarely spins above 800rpm)

FAE · 14 Dec 2009

Some additional info. It was a clean install. I use zonealarm & AVG free as firewall/Antivirus. These are some additional dumps from yesterday and the day before.
The windows software has not yet been activated because I'm reinstalling all the time to try and diagnose this issue.

Anyone any ideas?

usasma · 14 Dec 2009

Which memory test did you run? I recommend this one: Memory Diagnostics
Have you run a hard drive diagnostic? If not, try this link: HD Diagnostic

Even more info on the error message: BSOD Index

4 memory dumps - one blames networking, the others blame Windows components.
Please download a fresh copy of the latest Windows 7 drivers for your networking device(s)
Then uninstall the current networking drivers and install the freshly downloaded one.

Here's the summary of the dump file analysis:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Dec 12 03:47:30.475 2009 (GMT-5)
System Uptime: 1 days 10:18:24.552
BugCheck 7F, {8, 80050031, 6f8, fffff80002c82591}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 13 12:58:08.944 2009 (GMT-5)
System Uptime: 0 days 0:41:15.021
BugCheck 7F, {8, 80050031, 6f8, fffff80002eca591}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 13 11:48:06.648 2009 (GMT-5)
System Uptime: 0 days 0:01:11.614
BugCheck 7F, {8, 80050031, 6f8, fffff80002c457a0}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec 14 12:45:05.260 2009 (GMT-5)
System Uptime: 0 days 9:10:49.226
BugCheck 7F, {8, 80050031, 6f8, fffff80002ed7591}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System

FAE · 15 Dec 2009

Thanks for the tips. I will give them all a try. I'll post the results in a few days when all tests are done. I do remember for the network drivers that windows update replaced them 2 times in just a few days.

FAE · 16 Dec 2009

First round of testing completed.
I have tested twice with Windows memory Diagnostics (Option Extended) for 10 hours. It did 5 full test cycles each time without errors.
I then downloaded memtest iso as you recommended. I took the default options. It is now running over 9 hours and completed 7 cycles without errors.
Combined with my earlier testing and the Prime95 torture tests which ran for over 14 hours and used all 4 cores and nearly 95% of the memory I think we can exclude memory as the source of the blue screens?

I will now try the HD test you propose. I am using 2 Intel SSD drives in RAID0 using the onboard ICH10R controller. This means no TRIM support on the drives eventhough the firmware has been upgraded to support it. Will the tests proposed use all datablocks and slow down the drives/raid array?

FAE · 16 Dec 2009

First HD Check results with HDTune:
HD Tune: Intel Raid 0 Volume Error Scan
Scanned data : 152571 MB
Damaged Blocks : 0.0 %
Elapsed Time : 4:54

HD Tune: Intel Raid 0 Volume Benchmark
Transfer Rate Minimum : 458.7 MB/sec
Transfer Rate Maximum : 531.6 MB/sec
Transfer Rate Average : 515.6 MB/sec
Access Time : 0.1 ms
Burst Rate : 1304.6 MB/sec
CPU Usage : -1.0%

FAE · 16 Dec 2009

I tried some of the other tools to check the harddisk but intel/raid0 tests I cannot find except for the HDTune utility. I tried the hitachi one but it could not find any drive at bootup.

Then I downloaded the Realtek LAN driver for windows 7 from their website. I removed the existing driver from windows 7 in device manager (uninstall). I also removed the Teredo lan driver.

I then installed the Realtek drivers and rebooted. (Note: As expected Windows update now claims to have an updated driver.)

I've done all I can at this time. It is now waiting on the next crash.

FAE · 16 Dec 2009

Again a Blue Screen with the same message:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007f (0x0000000000000008, 0x0000000080050031, 0x00000000000006f8, 0xfffff80002ec09df). A dump was saved in: C:\Windows\Minidump\121609-14211-01.dmp. Report Id: 121609-14211-01.

I was reading/browsing a pdf file. In the background I had several web sessions open and a remote console session.

FAE · 16 Dec 2009

Again a BSOD 7f minidump attached. Just browsing the internet.

usasma · 16 Dec 2009

Please update this older driver: 000.fcl Fri Sep 26 09:11:22 2008

Then, please run Driver Verifier according to these instructions:

Quote:

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.

So, 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 Startup Repair feature).

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"
- Select "Automatically select unsigned drivers" and click "Next"
If no drivers show up, then 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.

Reboot the system and waitfor 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.

Reboot into Windows (after the crash) and turn offDriver 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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Windows 7: Bugcheck 0x0000007f crashes driving me crazy

Bugcheck 0x0000007f crashes driving me crazy problems?