OC limit / stress.

davg

davg

davg

Associate
Joined
25 Jul 2007
Posts
11
Hello

I have a C2DE6550, GeIL 2GB (2x1GB) PC6400C5 800MHz, and an Asus P5KC MoBo

I have over clocked this to 3.00 GHz and so far it seems stable, by stable I mean that it has not crashed yet. I know that this is not a proper indication of how stable the system is and I feel that a level of stress testing is required but I am not sure what to use and how long for? There are so many tools out there…

Also what would be the safe OC limit,


Regards

Dav
 
Thanks for the reply mate

8 hours, is it safe to do this over night or must it be monitored at all times?

Dav
 
Ok so i ran Orthos and:

Continous bleeps about 3 sec apart and the following log:
--------------------------------------------------------------------------
Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 1791 Time: 15
CPU: 3080MHz FSB: 333MHz [342MHz x 9.0 est.]
CPU: 3080MHz FSB: 333MHz [342MHz x 9.0 est.]
14/08/2007 17:52
Launching 2 threads...
1:Using CPU #0
2:Using CPU #1
1:Beginning a continuous self-test to check your computer.
2:Beginning a continuous self-test to check your computer.
1:Press Stop to end this test.
2:Press Stop to end this test.
1:Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
2:Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
2:Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.
1:Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.
2:FATAL ERROR: Rounding was 0.5, expected less than 0.4
2:Hardware failure detected, consult stress.txt file.
2:Torture Test ran 2 minutes 32 seconds - 1 errors, 0 warnings.
2:Execution halted.

1:Torture Test ran 2 minutes 32 seconds - 0 errors, 0 warnings.
1:Execution halted.
--------------------------------------------------------------------------

whats this all about / the pc did not crash but Orthos just stoped.

help?

Dav
 
Ok will give that a try,

I did run Orthos on the CPU only for about 2 and got no errors.

It may sound silly but what will upping the Vcore do?


Dav
 
Not trying to be patronising but you should really read the stickies before trying to overclock.

There's tons of info in there and they'll walk you through the process from start to finish.

Depending on your mobo there might also be a forum set up by the manufacturer where you can get advice specific to your mobo's bios.

Don't up the voltages at all if you don't know why you're doing it!!!
 
Thank you,
I have read thru the stickles I just wanted a quick and short answer…just trying to learn from people more knowledgeable than me.
 
Simply put increasing the vcore helps improve the stability of your cpu overclock. The same goes for increasing the voltage on the ram and the motherboard chipset but the downside is that it increases heat and will probably shorten the life of the components a bit.

With that in mind, first check your ram and motherboard chipset are set to the correct voltages as setting them too low can cause instability. Also check your starting with your cpu set at the coprrect default voltage as sometimes loading optimised defaults in the bios can apply too low a setting.

When upping voltages to try and stabilise an overclock I always try increasing the ram and chipset voltages before messing with the vcore because you hit the maximum settings with them a lot quicker than with the cpu voltage. If upping these voltages doesn't help then increase the the vcore by 0.05V and run the stress test again. If still no,luck then up it another 0.05V and retest. Repeat until you hit the max safe voltage or the temps get too high - I try not to go over 65C under load.

Write down everything you do so you don't keep trying the same things over and over as it's dead easy to loose track.
 
You must log in or register to reply here.
Back
Top Bottom