BSOD 0x0000007E

Chromana · 10 Aug 2010

I have been getting quite a few BSOD's lately for seemingly no reason. I haven't added any new hardware for a very long time.

I've had 4 major BSOD events, which take several restarts to recover from. A couple of times I had to do a system restore from the installation disk as I couldn't even get to Safe Mode. I'm not totally convinced that the system restore actually fixed anything, I think it might have just been a coincidence that the system then worked.

With or without the Restore the system will work for a while once it has recovered.

I forget what the BSOD said on the first two crashes, but the two latest ones have been 0x0000007E. After the 2nd BSOD the screen said:

The file is possibly corrupt. The file header checksum does not match the computed checksum

After the latest (the 4th) BSOD problems I took out one of my 2 sticks of RAM and the system booted up perfectly. However, I swapped the two sticks around and it booted up fine that time too so I don't think it's a memory problem. I've also run Windows memory diagnostics in standard testing and they both passed. The Extended memory test got stuck around 21% and didn't move for about 40 mins so I aborted. It didn't throw up any errors, though and I could still navigate the diagnostics menu.

I have attached the files as requested. NOTE: I ran the tests with only one stick of RAM in. I'm willing to put them both in to run again if someone thinks it'll make a difference.

Windows 7 . . .
- Ultimate x64
- the original installed OS on the system?
- full retail version

Hardware ranges in age from 1.5 years to 4 months. Laptop chassis + GPU is 4 months, RAM, CPU, HDD 1.5 years
- OS installed around the end of May

ttran · 10 Aug 2010

None of the DMP has stop code 7E. To make sure you've uploaded all of the DMP, please check out minidump folder and upload the rest:

Go to C:\Windows\Minidump and copy all of the dmp files to the desktop. Select all>right-click on one>Send to>New Compressed folder. Then attach the zip file to your next post by use of the paperclip icon in the advanced editor.

The results from the DMP files do not give a definitive answer. While we investigate further here are a few things that you can do.

1-Run a system file check to verify and repair you system files. You do this by typing cmd in search, then right click and run as admin. SFC/ SCANNOW

2-
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
3-Event viewer
Go into event viewer (type eventvwr in search). Go to the windows log>application tab.

You want to look for critical errors (they have red in the left column ).

When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.

When you find them please note the event ID, and the source codes and tell us what they are.

4-Device manager
Please go to start>search>type device manager.
Are there any "unknown devices" with yellow triangles on them?
Is you driver there , listed, and working?

If y our driver is missing, or there is a yellow triangle on it, you will need to update it.

5-Driver verifier
please run Verifier with these settings:
Driver Verifier - Enable and Disable

BUGCHECK SUMMARY:

Code:

BugCheck 3B, {c0000005, fffff80002ece805, fffff8800f3342e0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )

Followup: MachineOwner
---------
PROCESS_NAME:  spotify.exe <---WHAT IS THIS PROCESS?
BugCheck A, {200000, 2, 0, fffff80002e7d9d2}

Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+72 )

Followup: MachineOwner
---------
BugCheck 50, {fffff900c4da0010, 0, fffff80002fbbf8c, 0}


Could not read faulting driver name
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )

Followup: Pool_corruption
---------

What antivirus are you using?

Chromana · 10 Aug 2010

Stop 7E definitely happened at least twice, I took photos of the screen to be sure. I can copy out the entire error codes if you want. I have attached the minidumps.

1. All system files fine. By the way your instructions say to do SFC/ SCANNOW but it should be SFC /SCANNOW

2. I had done a pass of this test before making this thread and it was all ok. But I will leave it to run for 6 passes after I've finished this reply.

3. The only critical error was from back in may and had to do with a Logitec Quickcam program that I do not on the system any more.

4. Nothing wrong in device manager

5. Will report back on this along with results from Memtest86 as this needs a reboot too.

spotify.exe:
Spotify is a P2P music program available in the UK and some other European countries (100% legal I might add!) www.spotify.com
Now that you mention it, I have been using a beta version which was written specifically for Win7. I've been using it for many weeks though and haven't updated it for a while. I will stop using the beta for now and report the possible error to their dev team. Do you think this might be it?
I do recall that I had it running and playing music the last time I BSOD'd. I don't remember if it was running at the time of the other BSOD's.

Thank you for your reply.

Jonathan_King · 10 Aug 2010

I see your Toshiba BlueTooth drivers are older, so please update them:

Code:

tosporte.sys Tue Jun 16 06:48:47 2009 (4A37788F)
tosrfcom.sys Tue Jul 28 06:18:20 2009 (4A6ED06C)

Remove Avast for the time being, with this tool: http://files.avast.com/files/eng/aswclear5.exe

Replace it with MSE (also free): http://www.microsoft.com/security_essentials

Update your nVidia Graphics drivers with this link: Drivers - Download NVIDIA Drivers

Code:

nvlddmkm.sys Tue Mar 16 22:00:40 2010 (4BA037C8)

Your nVidia storage, network and audio drivers are old, and they are not uncommon causes of BSODs:

Code:

nvhda64v.sys Mon Jun 21 18:07:25 2010 (4C1FE29D)
nvmf6264.sys Thu Jul 30 19:48:18 2009 (4A723142)
nvsmu.sys    Mon Jun 29 03:36:37 2009 (4A486F05)
nvstor64.sys Tue Aug 04 20:31:07 2009 (4A78D2CB)

If that doesn't work, enable verifier: Driver Verifier - Enable and Disable

Wait for more BSODs, and then upload the new dumps.

...Summary of the Dumps:

Code:


Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Aug  7 16:20:57.935 2010 (UTC - 4:00)
System Uptime: 0 days 18:20:29.979
BugCheck A, {200000, 2, 0, fffff80002e7d9d2}
Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+72 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Aug  6 21:34:17.377 2010 (UTC - 4:00)
System Uptime: 0 days 10:07:21.421
BugCheck 50, {fffff900c4da0010, 0, fffff80002fbbf8c, 0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Aug 10 08:03:54.193 2010 (UTC - 4:00)
System Uptime: 0 days 0:57:40.112
BugCheck 3B, {c0000005, fffff80002ece805, fffff8800f3342e0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  spotify.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Chromana · 10 Aug 2010

OK, did the Memtest86 and all was fine.

Jonathan, I have the latest bluetooth driver from here Toshiba Europe Bluetooth Information Center I'm not sure where else to get it.

I can't install any newer graphics drivers (even though I REALLY WANT TO) because it breaks my system. When I tried to do the latest one half a month ago I had to do a system restore and then uninstall the drivers in safe mode to get the laptop working again. There aren't any newer drivers since then, but do you think I should try again?

Apparently the latest nVidia HD Audio driver was released 2009.10.01
Latest nForce is from 2009.10.01
I reinstalled them anyway, just in case.

Jonathan_King · 10 Aug 2010

The latest nVidia GFX drivers were released July 9, 2010, if I recall correctly. Go ahead and try to reinstall them, but make sure you create a restore point first: System Restore Point - Create

Chromana · 10 Aug 2010

Yeah, it didn't work properly. Apparently there are some problems with Win7 and Hybrid SLI. I've reverted again, but with less pain than last time. Only had to uninstall in Safe Mode this time.