Solved BSOD every hour or so

[FirstNameLastNa]

I'm getting BSODs approximately every hour or so, and I think my hard drive or cables are the issue. After the BSOD, one of my hard drives is sometimes unrecognized until a few boots later.

The BSOD error messages vary, but the most common one is 0x0000007A (0x0000000000000020, 0xFFFFFFFFC000009D)

The computer seems to be working fine aside from the BSODs. Memtest86, FurMark, CPU-Z, CrystalDiskMark, prime95, and RealTemp_370 seem to show everything working fine.

I attached the last two SF Diagnostic outputs.

Any help would be greatly appreciated.

 

[Northernsoul55]

Hi,

Please uninstall Daemon tools as it is well known for BSOD.

Start > click on Computer > Uninstall or change a program > choose Daemon tools. Reboot.
Once uninstalled please go here and remove the SPTD driver itself with this tool:

:ar: http://www.duplexsecure.com/en/downloads

If you see an Uninstall option for SPTD, click on it.
Otherwise, go to C:\Windows\System32\drivers, look for and delete SPTD.sys manually. Reboot

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa8007fc9b30, fffffa8007fc9e10, fffff80002de48b0}
Probably caused by : csrss.exe
Client/Server Runtime Subsystem
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.

You have an IO Error. This means that the data can't be read from your HDD.
Your hard drive could be failing.
Check all cables are secure and replace to eliminate as a cause.
I suggest you back up all your important data without fail as a precaution.

Please Run chkdsk /f/r in an elevated command prompt.

Click on the Start > Type in search cmd
Right click cmd at top and Run as Administrator
At the command prompt please type: chkdsk /f/r
(Note: there is a space between chkdsk and /f/r)

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

Also run a SFC offline in order to check the integrity of all Windows 7 system files:

:ar: http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html

And please scan for viruses:

:ar: http://www.sevenforums.com/tutorials/166445-windows-defender-offline.html

Ensure you have all windows updates installed.

Also check out your PSU:
Take a look at the 12v voltage reading in your BIOS, or use CPU-Z. Click on the About tab,
followed by Save Report (TXT). In that log it will contain a 12v reading.
There is usually around 5% tolerance so anything between 11.4v and 12.6v is normally acceptable.

Post back any results / observations
Cheers
Dave

 

[Northernsoul55]

Also please ensure your SSD firmware is up-to-date:

:ar: http://www.crucial.com/support/firmware.aspx

Cheers

Dave

 

[FirstNameLastNa]

Thank you. So far I've uninstalled Daemon Tools, scanned for viruses, and checked the PSU. Will post back with chkdsk and firmware update.

Really appreciate the help.

 

[VistaKing]

I believe updating the firmware wipes the drive

 

[Britton30]

Updating SSD firmware is OK and won't wipe a drive, I have done it twice on two Crucial M4 drives. Follow the manufacturer's instructions to the letter.

 

[Northernsoul55]

Thanks Gary

I have advised the OP as a precaution to "Back up" important data.
The Crucial Web site also advises this.

But your input is reassuring.

 

[VistaKing]

Different SSDs manufactures are different . I know to update OCZ SSDs it requires a wipe .

 

[Britton30]

Different SSDs manufactures are different . I know to update OCZ SSDs it requires a wipe .

When did that start?
EDIT: apparently they swing both ways. http://www.ocztechnology.com/files/..._Update_Guide_10_02_2012_Windows_consumer.pdf

 

[FirstNameLastNa]

It looks like the firmware update solved the issue. Thanks much, friends.

 

[Northernsoul55]

Good news and thanks for the feedback.

cheers

Dave