BSOD on Boot with conservative overclock on E7200

Hello. I just yesturday overclocked my e7200 with the intel stock HSF to 3.16 ghz (333 x 9.5) It seemed to be running fine and i also run prime 95 for like half an hour and it got up to about 56 degrees C. I though everything was fine. I shut it down for the night, and when i started it up this morning, it BSOD'd during the windows boot screen. So i went and downclocked it to the original 2.53 GHz and it booted fine.

What would cause this? Why is this happening?

Thanks,
Will

System:
Vista Home premium sp1
e7200
DFI lanparty x38
radeon x1950xtx
Corsair 750tx
2 gb OCZ crossfire DDR2 800 RAM

one important thing, you don't prime95 for 30mins and call it stable. go for 12 hours.

If you just raised the fsb, your ram is probably clocked too high. Set the ratio so the ram stays at 800mhz.

yeah i set it so the RAM stays at stock speeds, although the RAM should be able to handle an OC

Overclocking isn't a math equation or linear thinking. So just because something works fine for 10 hours, the next day it might only work for 4, etc.

If you changed your FSB from 266 to 333 and didn't change your Vcore, this is more than likely your issue. Also as stated above, 30 minutes in Prime 95 is meaningless. You need atleast 8 hours but I prefer 12.

That voltage you gave of 1.136v is that in bios or from CPUZ after vdroop affects it? If thats bios voltage, i'd up it to 1.1875 or 1.2 and let it run prime over night. If it's CPUZ voltage you will have to go a little higher in bios, like 1.225 or 1.23 etc.

Just another note, gaming does not even stress the CPU as much as Prime95 does. You should do both a Small FTT and Blend testing in Prime.

Once you pass Prime95, both test, on an extended time, like 8hours or more, your system is almost 100% stable for daily/normal usage.