BSOD 0x000000F4 - Occasional momentary hangs, BSODs. Suspect SSD

Hello

In brief:
Getting momentary freezes (during which I can still interact with the computer to some extent), which is sometimes followed by BSOD. Problems started after installing new SSD and re-installing Windows 7 onto it.

------------

I'm running a home built comp which have never given me problem up until a ilttle while ago. The major change was I invested in my first SSD, installed Windows on it and am now running a SSD with OS on it, and a regular SATA HDD with data. due to this, I suspect it's something to do with the SSD or that I've messed up some drivers upon the reinstallation of Windows. I ran same OS and hardware before the new SSD.

I've found several posts and threads were SSDs are suspected culprits and users with similar problems to mine and have tried following the suggested solutions in those threads, but they either end up unsolved or the solution didn't solve my problems.

The hangs/BSODs can happen seemingly anytime. I can play games which are taxing on the hardware, or I can be browsing/watching movies. The "hangs" don't cause the computer to completely freeze up. I can move the mouse and tab between windows and click on things, but it seems nothing new can happen. What I mean is, I can't open a new web page or open a program/window of any sort. Sometimes the computer comes back after maybe half a minute/ a minute, sometimes it BSODs.

I believe I have rrun most tests that have been advised in other threads.
I have run chkdsk and sfc, I have updated/reinstalled many of my drivers, I've made sure SSD firmware is up to date. I've also run memtest without any errors detected. However, memtest was only run for three-four tests, since it only wanted to run one test at a time. As a side question, how do I set it to run tests repeatedly until termination?

I hope I have been somewhat clear in my description and not to wordy. If I've missed any relevant information, please let me know, and thank you for taking a look at this.

Welcome

Sorry that it took a while to answer your thread.

Did you check how your computer performs with this new SSD without any drivers/software installed?

You may want to take tests from this link: Hard Drive Diagnostic Procedure

On a second note, I read somewhere that it's recommended to, in the case of a system SSD and a storage HDD, install Windows on the SSD without the HDD plugged in, and plug it in after system installation. Is there any sense to this?

Does make sense, but you won't know until you try it yourself. Did you? :)

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

STOP 0x000000F4: CRITICAL_OBJECT_TERMINATION
Usual causes: Does not have any

Anyway, lets enable driver verifier rule out buggy drivers.

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

Driver Verifier

I'd suggest that you first backup your data 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/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in verifier 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 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).

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.
Driver Verifier - Enable and Disable

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Capt.Jack Sparrow said:

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

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.

bluedude said:

Roger. Will do when I get home

Edited my post a little.
Take your time

bluedude said:

In reply to your question: No, not yet. First read about it yesterday, and wanted to confirm before I went through another OS installation.

But in that case, I guess I will try that, and at the same time install no drivers whatsoever, to see how that holds up.

Good idea
Update the thread when you're done :)