E6300 - overclocking advice needed...

Associate
Joined
6 Mar 2007
Posts
113
Hi

I have achieved the rates in the picture below by reading a few guides and adjusting a couple of settings. Is there anything anybody would recommend that I adjust to increase it beyond 3000mhz? I am really only going by what the guides are saying at the moment as I am not really confident experimenting myself.

Thanks

 
Yes for about 1 hour. I am not going to adjust any more settings until I do the full test over night.

I was just wondering if there is anything anybody else would look to adjust if it remains stable and I just wanted a check to make sure I hadn't done something obviously wrong such as having the voltage at the incorrect setting or something.

Thanks
 
The voltage is fine. Just try to keep the core temps below 60c at full load.

I'd try 450x7 and then run tests at that speed.
 
Thanks for the advice - have upped the FSB and now have 3150mhz :)

I have read that Speedfan doesn't give you the temps of the cpu itself. Is there another application I can use in Vista with a Nforce Chipset m/b to check the temp?

I can't seem to get any to work.
 
Well I ran SP2004 for about 10 mins and then it decided to give me the following and stop working:

Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 1789 Time: 15
CPU: 3149MHz FSB: 449MHz [449MHz x 7.0 est.]
11/03/2007 15:36 Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.
Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.
Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length.
Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length.
Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length.
Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Torture Test ran 9 minutes 6 seconds - 1 errors, 0 warnings.
Execution halted.


I can't seem to find the stress.txt file but I did notice that the RAM was stuck at 100% while the program was shutting down and my PC was making a bleeping noise every few seconds. The CPU temperatures seemed fine how at about 50c.

Any ideas?

Thanks
 
Which RAM do you have?

And give the vcore a little bump. At only 50c you still have a bit of room to play with the vcore.
 
might be Vnb as well, 450Mhz is quite high for most motherboards.

What's the complete system config, hardware and BIOS settings? Easier to help if we know more info.

could be CPU, NB or RAM, depends what volts you are on.

Oh, and if you DO get it stable, try dropping your Trc to 2-4 higher than Tras, as close to that as is stable, as it's supposed to be optimal around there. RAM is only as fast as the slowest timing!
 
simonnance said:
Oh, and if you DO get it stable, try dropping your Trc to 2-4 higher than Tras, as close to that as is stable, as it's supposed to be optimal around there. RAM is only as fast as the slowest timing!

Can I just confirm that I should, per the above post, adjust the TRC from 25 down to about 14-16 instead of 25? Therefore I would have 4 4 4 12 14(or 16)?? :confused: Even though this setting is all greyed out separately than the rest in the motherboard, until I make them manual.

Thanks
 
works for me, Memtest stable. I'd try 4-4-4-12-16, most optimal Trc is supposed to be Trp + Tras.

Likewise Tras is supposed to be CAS + Trcd + 2, which'd give 10 as optimal for 4-4-4, making Trc then optimal at 14.

http://www.diy-street.com/forum/showthread.php?t=20823

designed for DDR ram, but the formula still works for DDR2. If in doubt tweak, memtest and tweak some more. Trc and Trfc are down ah havving a large effect on bandwith and stability, so if you are going for uber overclocks you may have to give more slack than the optimal formula.

Shame there isnt an equvilant guide for DDR2 memory and the C2Ds.
 
Dont try an OC the memory/Cpu/Mobo all at the same time.
Find the limits for each indipendantly.
Find the max FSB your Mobo will do then go for the Cpu max whilst keeping your mem at 200 unlinked. once your happy with your Cpu OC, then push the FSB of you Ram, once thats at a stable speed try lowering you mem times.
 
Hmmm

The FSB of the RAM in the Bios saus 800mhz but, as per my picture above, it says 400mhz. Is this because of the dual memory sticks? Also should I then be pushing the 800mhz up in the bios in a similar fashion to what I did with the CPU?

Thanks
 
Really need to know which RAM and motherboard you have.

And yeah 400mhz in CPU-Z means 800mhz. It's because DDR runs at twice the fsb when set at 1:1.
 
GeIL 2GB (2x1GB) PC6400C4 800MHz Ultra Low Latency DDR2 Dual Channel Kit
Asus P5N-E SLi nForce 650 (Socket 775) PCI-Express DDR2 Motherboard 1
Intel Core 2 DUO E6300 "LGA775 Allendale" 1.86GHz (1066FSB)

Any help appreciated :D

Thanks
 
Bigmonty said:
GeIL 2GB (2x1GB) PC6400C4 800MHz Ultra Low Latency DDR2 Dual Channel Kit
Asus P5N-E SLi nForce 650 (Socket 775) PCI-Express DDR2 Motherboard 1
Intel Core 2 DUO E6300 "LGA775 Allendale" 1.86GHz (1066FSB)

Any help appreciated :D

Thanks
You have what is possibly the most common Ram/Cpu/Mobo combination on these threads.
On water you can expect to get to 3.4ghz.
On decent air you need fairly good case cooling and a fan on the NB as you will proboably need to set the NB volts to 1.7.
VDroop will probably cause problems so the pencil Mod will cure that (seee elsware on the forums).
Leave the Ram at stock and unlinked until you have a stable OC then look at raising the Ram speed.
Use Orthos to test and core temp to watch your temps.
 
Thanks for the advice.

However I have Vista so Core Temp does not work - having to use Speedfan only for temps at the moment.

And I've never quite got my head around what the hell VDroop is :confused:

Thanks
 
Bigmonty said:
Thanks for the advice.

However I have Vista so Core Temp does not work - having to use Speedfan only for temps at the moment.

And I've never quite got my head around what the hell VDroop is :confused:

Thanks
Download the latest version of Speedfan and it will give you your core temps.
Vcore is the amount of Voltage that the Mobo allows the Cpu to recieve, there are minor fluctuations but the Mobo regulates, If you want a good OC then the Vcore must remain stable under load and not fluctuate (droop).
This Mobo as with many Asus Mobo's suffers from Vdroop, This can be monitored in speedfan. you will notice that the Vcore droops from its idle level once a demanding App is run (Orthos for example) this means that the Cpu is recieving less Volts under load than when idle (the opposite of ideal).
 
Back
Top Bottom