Solved BSOD first 0x0000007A and now 0x000000F4

[mystifier]

Hello everyone!

It was some days I was getting the 0x000007A BSOD. I looked around for some possible solutions and I just performed a chkdsk.
After the chkdsk, where I got no error, don't ask me why, but I eliminated the 7A BSOD to acquire the second one; the F4.
As in your post on instruction, please find attached the zip file with the information.
If you need some more information or I forgot something, please let me know!

Thanks in advance for your time and effort :grouphug:

 

[koolkat77]

Welcome to the forum.

Those errors sound like hard drive ones.

Perform a Clean boot:

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

Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

• How to Change, Add, or Remove Startup Programs in Windows 7

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 Drive for file system errors and bad sectors on it:

• How to Run Disk Check in Windows 7

Upload a screenshot of your hard disk using Crystal Disk Info:

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

Make a hard drive test from the hard drive manufacturers website:

• Hard Drive Diagnostic Procedure

Test your Hard Drive with SeaTools:

• How to Use SeaTools for DOS and Windows Disk Check Utility

 

[mystifier]

Hello Koolkat77,

thanks for the welcome and your answer.
I followed your procedure step by step, here it is the results:

1. Clean Boot, done as explained in the tutorial you linked to me
2. Reduce item at start-up, done; I disabled all of them to be sure
3. done the SFC /scannow, attached the image.
4. done disk check, no error found. I was not fast enought to collect the screen before the reboot
5. CrystalDiskInfo screenshot, done. Attached.
6. SeaTools Test, done the fast one. No error detected. I made a screen with the info of the SSD.
7. I was not able to find the hard drive test from the manufacturers, but i made an error check by using HD Tune, attache the screen, no error detected.

Do you see something strange?
One thing I forgot to mention, every time i get the BSOD, in order to boot again the pc I NEED to clear CMOS.

Thanks again for your time and effort!

 

[Arc]

0xF4 and 0x7A shares the same source of origin. The disc environment.

Make it sure that your Crucial M4 SSD is having the latest firmware.
How to Upgrade Crucial SSD Firmware | StorageReview.com - Storage Reviews

Let us know.

Further troubleshooting is possible after having this info.

 

[mystifier]

Hi Arc,

thank you for your answer. Looking around I found this:

Crucial stated that the firmware "Corrects a condition where an incorrect response to a SMART counter will cause the m4 drive to become unresponsive after 5184 hours of Power-on time. The drive will recover after a power cycle, however, this failure will repeat once per hour after reaching this point. The condition will allow the end user to successfully update firmware, and poses no risk to user or system data stored on the drive.

This evening when I'll come back home, I will update the firmware as you suggested.

I will let you know. Thanks again!

EDIT:

Firmware Updated, I will let you know If I get new BSOD.

 

[Arc]

EDIT:

Firmware Updated, I will let you know If I get new BSOD.

Well done. We are subscribed to your thread. Update for any further event.

 

[mystifier]

Hi there!

Currently no more BSOD. Before to mark the thread as Solved I will wait today also, just to be sure
I start to thank you so much for your time and effort!

EDIT: Marked as Solved. From yesterday I got no more BSOD, so I think the firmware was the problem.
Thank you so much for your help!!