Yes, I reset it to stock clocks when my massive overclock got unstable, to try to slow down the spiral. I just got a bluescreen about 15 minutes ago, with a two-day interval between te BSOD and the latest freeze. Funny thing, 30 minutes prior I rebeat the L4D demo and it ran flawlessly...am I seeing a trend here? Runs a Source game flawlessly for as long as I want it to, thirty minutes pass, error. :\\ And no, I haven't run any hdd tests, but I'm also booting off my rather new, <1yr old, WD 160 so I doubt that's the problem...as far as memtest86, might be a good idea and if I can get a bootable flash stick(As I have no functional floppy drives) or if I can remember how to use Vista's dos-based memtest app, I'll probably scan my ram this weekend.
Originally Posted by HothBase
Are you sure it is the CPU that is causing instability? How come? What happened to it?
For two and a half weeks or so, I was running it at 2761mhz and 1.65vcore on air, rock solid too. It started to get unstable, I instantly reset it to stock and it's been useable.
My core is damaged, tho, and I can only hope there's enough of it left come January to try a 2.8 or 3.0 suicide run into Windows. If there is, I will most certainly upload all kinds of pix, bios screens and CPU-z dumps to see what I can get out of it before the core is 100% fubar, provided this xmas I get enough money to replace the platform or CPU.Edited by TestECull - 11/7/08 at 2:03pm