Occasional BSOD 50% during Hibernation, the rest random. 0x0000007a

Hi there,

I'm getting quite a few BSOD's, half the time it's when I close the lid to my laptop to initiate hibernation. The other half seems to be at completely random times.

This is a Toshiba Qosmio Laptop x505 a bit over a year old. I'm on a new installation of Windows 7 Ultimate x64 (retail).

I've tried:
1. Initial install of Windows 7 32bit home from oem
2. Upgrade to Windows 7 Ult. x64
3. Fresh install to Win 7 ult x64 retail (currently)
4. Changing hard drive from original SSD shipped with laptop to Vertex 3 240GB SSD to Kingston 240GB SSD as in my hardware specs (currently on the Kingston)
5. Almost all the video drivers released for the 360M until my current version of 8.17.12.8562
6. updating all drivers to latest versions on Toshiba's support website for my laptop model.

So far any and every combination has garnered BSOD's and I'm at a loss.
This is the first time I've posted asking for help on a computer so please be gentle with me if I missed something. I bruise easily.

If I listened to my gut instinct I would say there's something inherently wrong with the video card on this laptop model. or maybe I just need to eat something besides styrofoam permeated ramen.

Thank you for any and all help that comes my way!

These crashes were caused by memory corruption (probably a driver).
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!!!


1-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 or 6 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.

RAM - Test with Memtest86+



2-Driver verifier

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/Win7 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 "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- 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 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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

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



Old drivers needing updating

Code:

spldr.sys    5/11/2009 11:56:27 AM    fffff880`01dbf000    fffff880`01dc7000        0x00008000    0x4a0858bb                        
GEARAspiWDM.sys    5/18/2009 7:17:04 AM    fffff880`076b9000    fffff880`076c6000        0x0000d000    0x4a1151c0                        
Tosrfhid.sys    5/19/2009 8:23:51 PM    fffff880`079db000    fffff880`079f0b00        0x00015b00    0x4a135ba7                        
QIOMem.sys    6/15/2009 12:58:48 AM    fffff880`07101000    fffff880`0710b000        0x0000a000    0x4a35e318                        
tosporte.sys    6/16/2009 5:48:47 AM    fffff880`08198000    fffff880`081a9000        0x00011000    0x4a37788f                        
pgeffect.sys    6/22/2009 4:00:11 AM    fffff880`08094000    fffff880`0809ae80        0x00006e80    0x4a3f481b                        
tos_sps64.sys    6/24/2009 12:31:09 AM    fffff880`01d37000    fffff880`01db1000        0x0007a000    0x4a41ba1d                        
thpdrv.sys    6/28/2009 9:02:56 PM    fffff880`01db3000    fffff880`01dbf000        0x0000c000    0x4a4820d0                        
Thpevm.SYS    6/29/2009 3:15:37 AM    fffff880`01db1000    fffff880`01db2f80        0x00001f80    0x4a487829

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 Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Hi zigzag3143,
Thank you for the speedy assistance I really appreciate it.

#1 memtest produced no errors all passes "passed" (no overclocking anything ever on this laptop and/or hardware)

#2 I updated those specific drivers as suggested, however it seems the latest available downloads from the Toshiba site didn't update some of them to newer driver dates so those 'hopefully' are the latest ones.

#3 I ran the Driver Verifier with the suggested settings and it crashed on reboot before logging into windows. BSOD gave a different Stop code: 0x000000C9. This makes me wonder if there is a faulty driver that is causing a problem before it can even get to the one that is causing the initial BSOD?

I uploaded the minidump.

Thank you for your help!

PS. If I could so implore, I would love to know the method of your genius(madness?) in troubleshooting so I may learn to fish. so to speak.

heyshooshy said:

Hi zigzag3143,
Thank you for the speedy assistance I really appreciate it.

#1 memtest produced no errors all passes "passed" (no overclocking anything ever on this laptop and/or hardware)

#2 I updated those specific drivers as suggested, however it seems the latest available downloads from the Toshiba site didn't update some of them to newer driver dates so those 'hopefully' are the latest ones.

#3 I ran the Driver Verifier with the suggested settings and it crashed on reboot before logging into windows. BSOD gave a different Stop code: 0x000000C9. This makes me wonder if there is a faulty driver that is causing a problem before it can even get to the one that is causing the initial BSOD?

I uploaded the minidump.

Thank you for your help!

PS. If I could so implore, I would love to know the method of your genius(madness?) in troubleshooting so I may learn to fish. so to speak.

Not genius (perhaps insanity) itws more an art than science. This one is driver verified (a tool) and Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd. Another fiasco from the makers of daemon tools. You need to remove it

Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads http://duplexsecure.com/faq

when you're done you can use this Freeware:

MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place

http://www.magiciso.com/download.htm

Ok, I think I know what you mean. Artistic Insa*genius...

Daemon lite uninstalled with zsoft killing their reg keys and then I ran the SPTD Uninstall tool but it didn't want to uninstall anything so I'm guessing zsoft removed it.

Ran through the verifier procedures again and came up with an NSFIM64.sys BSOD.
Hopefully we are getting closer.

Thank you yet again for your assistance!

heyshooshy said:

Ok, I think I know what you mean. Artistic Insa*genius...

Daemon lite uninstalled with zsoft killing their reg keys and then I ran the SPTD Uninstall tool but it didn't want to uninstall anything so I'm guessing zsoft removed it.

Ran through the verifier procedures again and came up with an NSFIM64.sys BSOD.
Hopefully we are getting closer.

Thank you yet again for your assistance!

Yep the NSFIM64.sys is from you Panda. Should be removed and replaced with Microsoft Security Essentials and the built in firewall.

Ok Looks like this was the last startup BSOD.
PGP sadly. Ok so I removed Panda Cloud and am using MSE. Also removed PGP_Pretty Good Protection. (I'm guessing this one might be ok for use once I figure out the initial BSOD I was having a problem with, well no choice on that one really, maybe I'll send the minidump to symantec *shiver* since they bought them out.)

Anyway, I will try to get my laptop to do the 0x0000007a.
Thank you so much for your help and I will update here with any new findings.

I uploaded the last minidump for PGP just for completions sake.

This crash was related to PGPfsfd.sys PGP Desktop from PGP Corporation.
Suggest you remove it asap.

Thanks guys,
I can't seem to get it to do any more BSOD's at the moment so looks like everything is ok for now :)
I appreciate it!!

Excellent news.
Thanks for reporting back.
Good luck!