I7-860 overclock problems

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

medoomi

Distinguished
Dec 16, 2008
70
0
18,640
SYSTEM:
CPU: Intel Core i7-860 Lynnfield 2.8GHz 8MB L3 Cache LGA 1156 95W Quad-Core Processor
MOBO: GIGABYTE GA-P55M-UD2 LGA 1156 Intel P55 Micro ATX Intel Motherboard
RAM: OCZ Platinum 8GB (4 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800)
GPU: EVGA 01G-P3-N964-LR GeForce 9600 GSO 1GB 128-bit DDR2 PCI Express 2.0 x16 HDCP
PSU: SeaSonic X750 Gold 750W ATX12V V2.3/EPS 12V V2.91 SLI Ready 80 PLUS
OS: Windows 7 64 Bit
(Here's the link to the thread for the machine build: http://www.tomshardware.com/forum/275415-31-advice-photoshop-system)

OVERCLOCKING:
At the moment I'm on the following settings:
CPU @ 180Mhz, 20x multiplier = 3600Mhz
Vcore @ 1.2, Vtt/QPI @ 1.190
RAM @ 8x = 1440, timings, 7-7-7-24 (at 1.64V)
CPU temp sits around 70C running Prime95

The system seems stable on Prime95 running small FFT's, however, when I switch over to the Blended test, it shuts down totally after about 5 minutes. Last time it shut down on Prime, I could smell a burnt smell which freaked me out (CPU cores were only around 70C). Once it had crashed, I had to hold down the power button for 5 seconds before it would boot (does that point to a circuit breaker tripping?). I have no BSOD's, no minidumps, and just a generic "Kernel-power" in event viewer as the "critical error" to go on.

Any clues on what I should change first?
 
hmmm, yeah, trouble shooting can be like needle haystack searching.

When I tested out my RAM initially, I was using an older version of memtest, so it didn't fail at all (that was one of my first mistakes). It took the latest version (4.00) to get it to fail. And then, when I re-seated the RAM, it tested 4 modules one night clean, 2 modules the following night clean, and the other two modules the following night clean. It was only after that that they began to fail (just running them overnight for 8 hours or so--not during the day).

So, RAM could be a problem... Or a driver/program conflict.

I also tend to image the drive & re-image it regularly to keep windows up to speed.