Hi guys,
After a year or so I've finally plucked up the bravery to overclock my E6600. Now with so many new CPUs taking the shine off my little conroe, like a balding man buying a porche I delved into the field of overclocking.
Following a few beginners guides I started with a very modest overclock from 2.4GHz to 2.7GHz.
Basically I just want to know if I've done everything correctly and if my temps are okay (at the bottom). Also my rig is in my sig but just for convenience sake:
Conroe E6600 2.4Ghz, Gigabit DS3
X1800XT 256MB, Gskill 2Gb PC2-6400
160GB WDC, SOHW-832S DVD/RW
Enermax 620W, T.T. Big Typhoon.
These are the steps I took:
disabled CIA2
disabled C1E
disabled EIST
disabled Virtualization Technology
disabled CPUID
disabled No-Execute Memory Protect
set PCI Express (PCI-e) frequency to 100 mhz
-Set Graphics Booster to Auto
-Set CPU Host Clock Control to Enabled
-Set CPU Host Frequency to 300.
-Set System Memory Multiplier to 2.00
-Set DRAM Timing Selectable to Manual
-Set CAS Latency to 5
-Set RAS to CAS to 5
-Set RAS Precharge to 5
-Set tRAS to 15.
-Set DDR2 OverVoltage Control to +0.2v.
-Set MCH Overvoltage to +0.1.
-Left vCORE at 1.325.
The above instructions are supplied in an Overclocking 101 for the Gigabyte DS3 article courtesy of TomsHardware. (can I link it?).
Anyway, here are my temps:
So basically as it's my first overclock and to me the temps look slightly high at idle (40c) I was just hoping for some feedback on anything here.
Just to confirm, I did run an orthos test for 13hours overnight and everything passed.
I'm hoping to pump it up to 3GHz tonight; would it be a bad idea to go straight from 300MHz*9 to 340MHz? and what temp increase should I expect for that?
Thanks in advance,
Regards,
Tig
P.S: sorry for the small pics, the site I uploaded the image to shrunk it. Everything is still visible, it just takes a bit of squinting.
P.P.S: You may have noticed I posted a thread about my Vcore saying 'fail' but that was at stock ie. before this overclock. Since I set the Vcore manually the vcore now says 'ok'.
After a year or so I've finally plucked up the bravery to overclock my E6600. Now with so many new CPUs taking the shine off my little conroe, like a balding man buying a porche I delved into the field of overclocking.
Following a few beginners guides I started with a very modest overclock from 2.4GHz to 2.7GHz.
Basically I just want to know if I've done everything correctly and if my temps are okay (at the bottom). Also my rig is in my sig but just for convenience sake:
Conroe E6600 2.4Ghz, Gigabit DS3
X1800XT 256MB, Gskill 2Gb PC2-6400
160GB WDC, SOHW-832S DVD/RW
Enermax 620W, T.T. Big Typhoon.
These are the steps I took:
disabled CIA2
disabled C1E
disabled EIST
disabled Virtualization Technology
disabled CPUID
disabled No-Execute Memory Protect
set PCI Express (PCI-e) frequency to 100 mhz
-Set Graphics Booster to Auto
-Set CPU Host Clock Control to Enabled
-Set CPU Host Frequency to 300.
-Set System Memory Multiplier to 2.00
-Set DRAM Timing Selectable to Manual
-Set CAS Latency to 5
-Set RAS to CAS to 5
-Set RAS Precharge to 5
-Set tRAS to 15.
-Set DDR2 OverVoltage Control to +0.2v.
-Set MCH Overvoltage to +0.1.
-Left vCORE at 1.325.
The above instructions are supplied in an Overclocking 101 for the Gigabyte DS3 article courtesy of TomsHardware. (can I link it?).
Anyway, here are my temps:
So basically as it's my first overclock and to me the temps look slightly high at idle (40c) I was just hoping for some feedback on anything here.
Just to confirm, I did run an orthos test for 13hours overnight and everything passed.
I'm hoping to pump it up to 3GHz tonight; would it be a bad idea to go straight from 300MHz*9 to 340MHz? and what temp increase should I expect for that?
Thanks in advance,
Regards,
Tig
P.S: sorry for the small pics, the site I uploaded the image to shrunk it. Everything is still visible, it just takes a bit of squinting.
P.P.S: You may have noticed I posted a thread about my Vcore saying 'fail' but that was at stock ie. before this overclock. Since I set the Vcore manually the vcore now says 'ok'.
Last edited: