Oh, great, a dedicated thread; dunno how I missed this Anyway, I'll include my previous post for good measure:

"Having an SF-22xx drive myself, I've been especially interested in this aspect of the thread. I've owned a Force GT 120GB for a bit more than a month now and I've had crashes with the drive disappearing from BIOS two times only. While not much compared to other folks, it's still annoying, and maybe even more annoying knowing I've got a... fragile... piece of hardware with the potential to cause trouble when it feels like doing so.

So, may we have a recap on the SF issue and can you say anything concrete on the matter in terms of causes/workarounds at this time?

Also, I don't mind helping out if you have some specific BIOS settings/workloads/etc to try out if it brings the world closer to solving the infamous SF problem. This is my only PC tho and it's not running 24/7, so I may not have the same resources but I'll do what I can if needed.

What I have observed around the SF bug myself is that it's only happened during an overclock with an OFFSET vcore while running the BOINC client with the specific settings of 100% CPUs used and 60% CPU time. This configuration results in an erratic load on the processor going literally from 0% to 100% and back down to 0% in under a second with the vcore being thrown around like mad. The first time it crashed within 2 hours of this load and the second time it happened within 10 hours of this load. C3/6 states disabled, altho C1E and EIST have been enabled.

At the moment I'm testing the same CPU workload but with a static vcore."

My system specs are:
2600K
Gigabyte GA-Z68X-UD4-B3 (oROM 10.6.0.1091)
8GB Corsair Vengeance C8
Force GT 120GB (FW 1.3.2) as systemdrive restored from an HDD image of Win7 (alignment is ok)
IRST 10.6.0.1002

I should mention that I haven't experimented with any voodoo like reg hacks, modded BIOSes, uninstalling/disabling MEI or even MS default SATA driver. I've pretty much only updated FW of my drive after the second crash and haven't had any crashes since, but I also have not tried provoking it with the conditions I mentioned earlier.