BSOD > restart while loading into OS

[lhf8]

BSOD while booting into OS (HD or OS issue)

Hello All,

The brains of this forum was able to help me out when I first build this computer and all was well for almost a month until now.

Here's my system:

running windows 7 x 64

[FONT=&quot]MSI P67A-G43 (B3)[/FONT]
[FONT=&quot]Intel I5 2500k with a Coolermaster hyper 2x12[/FONT]
[FONT=&quot]Nvidia GTX 560 Ti SC[/FONT]
[FONT=&quot]2x4GB of Patriot G2 DDR3 RAM[/FONT]
[FONT=&quot]PGD38G1600ELK[/FONT]
[FONT=&quot]WD 1TB Model: WDBAAZ0010HNC[/FONT]
[FONT=&quot]ASUS DRW-24B1ST[/FONT]
[FONT=&quot]Antec [/FONT]HCG-750


Here's my problem:

Computer has ran perfectly for 3 weeks, I usually leave it on overnight. I had it clocked to 3.8 and my temps were sitting at 45 degrees Celsius, I highly doubt it's a proc issue.

So one day, when I woke up, the computer was off and when I started it up, it posted and began loading windows 7, after about 5 seconds it blue screens for a split second, then restarts.

Can't boot into safe mode either.

I can get into windows recovery mode and I ran disk check, no issues.
I individually tried both RAM sticks too, and ran memory tests, not the issue.

Something I found interesting but don't know what to make of it, windows gave me this error while it was attempting to repair issues it apparently saw.

Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: unknown
Problem Signature 04 21200396

Problem Signature 05 Autofailover

Problem Signature 06 3

Problem Signature 07 CorruptAcl 6.1.7601.2.1.0.256.
1033

I also tried a previously known good configuration, nothing.

I also threw this into another tower and no blue screen, just automatically restarts and gets the same issues regarding problem signatures.

I stupidly can't get a hold of a boot disk at the moment but I'm working on it, I also don't see this being a windows issue but I may be naive in thinking that.

 

[lhf8]

I've tried three separate towers and get the same issue so what on earth could have gone wrong with windows for this to have been going on?