The thing about the SandForce BSODs is that they manifested themselves as random F4 errors, which is exactly what you're seeing. It took Anand & crew quite a bit of effort to come up with a reproducible test case for SandForce to actually fix the issue. Ultimately you have some other good suggestions here worth following, but I wouldn't rule out the SandForce BSOD because it's random; you should rule it in because it's random.
My electricity shows a reasonable power of 122.9... not even sure what that means, but the guy said it was good and not an issue of an undercurrent. Guess it's in the case
I'll try the 1.35v setting and the SSD swap next.
You can then check the logs after a BSOD to see if there were power issues on the line at the time.02/06/2012 05:19:20 UPS: No longer on battery power.
02/06/2012 05:19:19 UPS: On battery power in response to an input power problem.
Date Time Vmin Vmax Vout Iout %Wout Freq %Cap Vbat TupsF %VAout
02/12/2012 23:06:32 114.4 115.2 115.2 9.46 38.3 60 100 54.81 81.3 34.4
02/12/2012 22:56:32 114.4 115.2 114.4 9.46 37.7 60 100 54.81 81.3 35.7
02/12/2012 22:46:32 114.4 114.4 114.4 9.46 37.7 60 100 54.81 81.3 35.1
The problem here is the issue is only happening sporadically, so you need to monitor and log the power readings, checking it when you experience a problem. Checking the voltage once is not going to reveal the issue if the issue is with the power.
This is what you want to be able to check for when researching power issues (from a UPS log here in the office):
You can then check the logs after a BSOD to see if there were power issues on the line at the time.
Since you are/were getting a f4 error, as Virge suggested, it would seem like it's pointing to an SSD drive issue, but this is just an opinion.
Try analyzing your dump files with BlueScreenView http://www.nirsoft.net/utils/blue_screen_view.html or Windows Debugging Tools http://www.bleepingcomputer.com/forums/topic176011.html
Sounds like you have some parts that are incompatible, you just going to use the process of elimination and swap them out one by one. And by that I don't mean RMA everything, try a regular hard drive first, then different memory. Microsoft are not set up to help you identify hardware problems over the phone.
I am not going to read through all the posts... maybe this was mentioned.. is your RAM on the motherboards manufacturers certified list?
Just an update... I've been on the Crucial M4 for about a week now and no BSODs. I'm still not 100% sure that it was a SandForce issue but it seems to be pretty likely right now. I'm waiting for a solid 4-5 day uptime to be absolutely certain but I've rebooted a few times and normally do encounter BSODs in the interim, none of which happened with the new SSD. So far, so good.
I never figured out *why* the SandForce chipset is a problem with my various motherboards despite trying a few bugfixes suggested by their support staff, but at this point, I suppose it's a moot issue. Fortunately, OCZ is going to refund me for the Vertex 3 (not the full cost that I paid, but not market value either).
If I have any updates, I'll post.
thanks all for your help.
Getting back to the heat issue....sounds simple, but is there dust build up? Try going into the bios and disabling fan throttling. Being a BSOD it is a harware proble, but overheating could be the issue since it BSODs after running a bit.
Just a thought.