PC blue screened then would not boot.

[CatchPhrase]

I have had my pc overclocked for 4 months. It was a 1.6ghz e2140 overclocked to 3.0. It got some blue screens and then would not boot os (xp) it gave me an error that said system32 something. I got the blue screens while loading a game in crysis. That could not have been a problem because I beat crysis with this pc months ago. Could a ram stick have gone bad? Could I have messed up the os when I ran prefetch and %temp% and deleted everything the system let me. I retrieved all of the data from the hdd and reinstalled the os and now my cpu will not overclock. I tried again with each ram stick and it still would not overclock.
My pc

e2140 1.6 (was 3.0 for monthes)
2x1gb g.skill ram 800mhz
evga 8600gt
wd 160gb
corsair 450w psu

 

[RallyMaster]

I'd say it's the heat. Drop the overclock down?

 

[CatchPhrase]

No my temps were fine for months. I ran orthos for 3 hours and it got to 53c Coretemp (newest version).

 

[BTRY B 529th FA BN]

Sounds like the mobo is the culprit

 

[Zap]

Saw this happen twice in a week. Both times turned out to be the RAM. Incidentally both were using Asus P5K-VM boards. I wonder if these boards have a rep for killing RAM? Anyways, first system was my gaming rig. RAM is 4 sticks of OCZ Reaper, used to Memtest fine at over 800MHz CAS4, now fails at stock speeds (don't know which one yet). The other system has 4 sticks of Crucial Ballistix. Two double sided and two single sided. Was clocked at stock, now has to underclock or fails Memtest. I think I have it narrowed down to one of the single sided modules - figures, as those have a bad rep for failing. I've already had to RMA one of those. Anyways, for the first system Windows was dead from then on. The second system, Windows recovered after RAM set to 667MHz, while before it wouldn't even boot Safe Mode.