Solved BSOD on return from sleep mode

[HairyScot]

Recently reinstalled Windows 7.
Since then have encountered BSOD on two occasions when bring PC out of sleep.

 

[koolkat77]

Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

Perform a Clean Boot:

• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Caused by StorageCraft Volume Snap-Shot or Symantec/Norton Backup Exec. Suggest uninstalling everything related to this program and see if the problem comes back. Then get latest version/drivers if possible:

fffff880`0bdf0d98  fffff880`0139d994Unable to load image \SystemRoot\system32\DRIVERS\symsnap.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for symsnap.sys
*** ERROR: Module load completed but symbols could not be loaded for symsnap.sys
 symsnap+0x10994
.................................................................................................................
0: kd> lmvm symsnap
start             end                 module name
fffff880`0138d000 fffff880`013bb000   symsnap  T (no symbols)           
    Loaded symbol image file: symsnap.sys
    Image path: \SystemRoot\system32\DRIVERS\symsnap.sys
    Image name: symsnap.sys
    Timestamp:        Wed Sep 16 03:02:11 2009 (4AB000D3)
    CheckSum:         00034921
    ImageSize:        0002E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Caused by SCSI Pass Through Direct Host - Daemon Tools (known BSOD issues with Win7)

fffff880`0bdf0948  fffff880`0107b601*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
 sptd+0x4a601

Please uninstall DAEMON Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7. Uninstall the software using Add/Remove Programs. Reboot the system. Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.

As an alternative, many people recommend the use of Total Mounter or Magic ISO

Caused by AMD SATA Controller AHCI 1.2 Device Driver . Install fresh version, see if the problem persists.

fffff880`0bdf0798  fffff880`01312272*** WARNING: Unable to verify timestamp for amd_sata.sys
*** ERROR: Module load completed but symbols could not be loaded for amd_sata.sys
 amd_sata+0xb272

Run these tools and delete anything they may find:

• Anti-rootkit utility TDSSKiller

ESET online scanner:

• Free Online Virus Scanner | ESET

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• Click on the rb:
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow

Full tutorial here:

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

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Summary

[FONT="Lucida Console"]STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR 
Usual causes:  Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack
BugCheck 7A, {20, ffffffffc000009d, fffffa80061ce078, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+50040 )
.........................................................................................................
STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR 
Usual causes:  Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack
BugCheck 7A, {fffff6fc400616b0, ffffffffc000009d, 71bc6be0, fffff8800c2d6000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36bea )
........................................................................................................
STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR 
Usual causes:  Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack
BugCheck 7A, {20, ffffffffc000009d, fffffa80061317c8, 0}
*** WARNING: Unable to verify timestamp for amd_xata.sys
*** ERROR: Module load completed but symbols could not be loaded for amd_xata.sys
Probably caused by : amd_xata.sys ( amd_xata+1d06 )
[/FONT]

Hope this helps.

 

[HairyScot]

Thank you for the swift response.

I do have Norton Ghost 15 installed.
Don't have daemon tools but do have Alcohol120 and Virtual Clone Drive.
As far as I know all drivers are up to date, but I will recheck.
Recently ran chkdsk and SFC Scannow, but will do so again..
I have aVast internet security installed, but will run the checks you suggest.

I'll only ever use manual sleep so perhaps I should discontinue that just shutdown instead.

 

[koolkat77]

Thank you.

You may want to replace Alchohol with either of these:

• Total Mounter
• Magic ISO

OR, Prefer 7zip out of all:
Download and install 7-Zip, it is free +it can extract any iso file. So you can use it the way you want to. At a max you'll miss some chapter chooser screen of a DVD title.

Free up the start-up:

• http://www.sevenforums.com/tutorials/1401-startup-programs-change.html
• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Uninstall these programs:

Start Menu	Default:Start Menu	Default
Start Menu\Programs\GIGABYTE	Public:Start Menu\Programs\GIGABYTE	Public
Start Menu\Programs\GIGABYTE\DMIView	Public:Start Menu\Programs\GIGABYTE\DMIView	Public
Start Menu\Programs\GIGABYTE\EasySaver	Public:Start Menu\Programs\GIGABYTE\EasySaver	Public
Start Menu\Programs\GIGABYTE\ET6	Public:Start Menu\Programs\GIGABYTE\ET6	Public
Start Menu\Programs\GIGABYTE\SmartRecovery	Public:Start Menu\Programs\GIGABYTE\SmartRecovery	Public
Start Menu\Programs\GIGABYTE\UpdManager	Public:Start Menu\Programs\GIGABYTE\UpdManager	Public

They can contribute in the issues. You may install them back later if we know they weren't contributing.

Good luck

 

[HairyScot]

I have been running the same mix of apps for the past 2 years.
The only recent change was the addition of Uniblue Powersuite.
I will remove that and see what transpires.

I have a feeling the issue may be hardware related.
Have been experiencing some other funnies over the past couple of days.
I have 2 HDDs, a 1TB (Windows, apps, docs) and a 2TB which holds my video collection.
Recently when doing restarts the 2TB HDD seems to get lost and I have to power down and up to "find" it.
CHKDSK shows no problems.
Perhaps there is a BIOS problem or maybe it is time for a new PC, or new MB, CPU and RAM.
I will run whatever diagnostics I can find.
Perhaps you can suggest some?
Thanks.

 

[HairyScot]

Removed Alcohol, VCD, and Powersuite.
Ran

Anti-rootkit utility TDSSKiller
and ESET online scanner:

• Free Online Virus Scanner | ESET

Came up clean, as did CHKDSK.

Still get BSOD on return from sleep.
Have attached latest dump.

 

[Britton30]

Could you post a snip of your expanded Disk Management window? Maybe something there about the "ghost" drive.

 

[Arc]

As a test you may try USB selective suspense off.

USB Selective Suspend - Turn On or Off

 

[HairyScot]

Thanks, will give that a try.

Have attached snip of DiskMgmt

 

[HairyScot]

Switched off USB Selective Suspend.
BSOD again, but this one looked slightly different.

 

[koolkat77]

Upload a screenshot of your hard disk using crystal disk info and summary tab using speccy:

• Speccy - System Information - Free Download
• CrystalDiskInfo - Software - Crystal Dew World
• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

PS: Do a fresh install to see how things are.

 

[HairyScot]

This problem started after a fresh install one week ago, so I am understandably reluctant to go back down that route.
Have attached the speccy and crystal info.

 

[koolkat77]

I don't have speccy installed on my computer so can't see the image. It keeps crashing on my PC so I switched to HWinfo.

Can you please upload the speccy screenshot to your next post.

 

[HairyScot]

Do you mean the summary or a shot of each section?

 

[koolkat77]

Summary tab

 

[HairyScot]

Installed HWINFO and generated reports from both 32 and 64 bit versions

 

[koolkat77]

Looks good,

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
• Guide to using Memtest86+ - Geeks to Go Forums

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

:tip: Errors are sometimes found after 8 passes.
:tip: Do this test overnight, before going to bed.

 

[HairyScot]

Thanks for all the help and info.
I will undertake the Memtest exercise as soon as I can, in the meantime I'll just avoid using sleep mode and shut the system down instead.
I had been contemplating treating myself to an Intel I3 or I5, this might just be the time to do it.

 

[koolkat77]

I see, good luck

 

[Britton30]

Plan on backing up what is on the 1TB drive, it is going bad. It can happen at anytime and be unreadable, AKA, data all lost.