Overclocking Conroe E6700 on eVGA 680i issues

Cyraxx

Supreme [H]ardness
Joined
Feb 21, 2005
Messages
4,144
Hello Everyone :)

Since getting my latest upgrades situated, I have wanted to see how far I can go while still stable.

My Information:
eVGA 680i Mobo
Corsair (2x1GB) XMS2 Dominator 1066 MHz, PC2-8500
Intel Conroe E6700
eVGA 8800GTX
WD Raptor 150GB

I have been taking the advice of Arcygenical's guide to Conroe Overclocking, starting with uping the voltage of my memory to the manufacturer suggested 2.2v from stock 1.8v. I will admit my n00bness in that I am clueless of how memory speed interacts with FSB of processor speed, and what all should be changed from defaults. But anyways, Ill go through the changes that I did do.
1) As I said, upped the voltage of the Corsair memory to 2.2v as suggested.
2) Checked my Load Temps, I get roughly 30 degrees Celcius from the BIOS, and ~33-39 degrees celcius in Intel TAT, so i figure im good to go as far as temps go.
3) Anyways, regardless of the changes I made, I started OCing (atleast, I think i was overclocking :eek: ) increasing the FSB in the evga 680i BIOS from 1066 to 1100, which would equal an overall increase to 2750 mhz, much lower than the much mentioned 3.0-3.5 GHZ. Immediately at trying to boot, it was unable to load windows claiming corrupted data, i restarted, reset BIOS to defaults, and everything was back to normal. Any idea what im doing wrong?


List of things that Im clueless about:
1) How to 'lock' my evga 680i PCIe and PCI busses
2) Making sure my RAM speed is 1:1 - this also confuses me with having it linked, whats the relation?
3) What I did wrong in my little mini-oc attempt above.
 
I read that before and I have to agree that its my own errors. I am not running any Raid, nor is data randomly becoming corrupted, it SAYS its corrupted after I attempt to overclock, but the data is infact perfectly fine when i revert back to defaults. Like i said, I think its in my end due to n00bness.
 
This is a symptom of memory error... well 99% of the time.

Easy to fix really, but we're already working on that.

What you're doing, is setting your RAM speed to 1100mhz, not the actual FSB (if I'm reading that right) as you're running in "linked mode."

bad. :p
 
Back
Top