I was overclocking today, and when I was trying to lower vcore on my current overclock, rather than using '1.165' as desired, I accidently typed '1.65' without realizing. I only realized when I booted up and opened CPU-Z. Luckily I didn't press Start on IBT and immediately shut my PC down. Now it's barely stable at my original vcore before I attempted to bring it down a bit, and when I decided to hop back on to the 3570k's default clocks.. I wouldn't say it's unstable. It passed IBT all the way through but when I launched a game and changed a couple settings the game crashed. I tested this with several other games as well, and those crashed within 15-20 min. Curious if accidently bringing the vcore up to 1.65 was the cause of this what I could do about this. Thanks.
post #1 of 14
1/25/13 at 3:46pm