• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Can't OC T-Bird with cli

M

Maggotry

Platinum Member
Since switching to cli SETI from gui SETI, I can't oc Grendel anymore. I had a modest oc from 1100 (11x100) to 1320 (12x110). I keep crashing now at 1320 and have had to go back to 1100.🙁

Any ideas on why this would occur?
 
Well, I have heard that SETI@Home tends to exaggerate the problem if a system is unstable. It might just take SETI@Home to push yours over the edge.
 
like steve said...............seti is one of a few programs to test system stabilty....100% cpu usage........if there is a problem with your system......seti will crash it.....back off on your fsb till you can run stable.
 
Wait, so you ran the GUI version while overclocked for a long time and it worked fine, and now you've switched over to the CLI and it's crashing at the same overclocked speed?
 


<< Wait, so you ran the GUI version while overclocked for a long time and it worked fine, and now you've switched over to the CLI and it's crashing at the same overclocked speed? >>



That's right.
 
I think it's because the GUI is designed to interfere less and consume less CPU power. As ShotgunSteve said, SETI is a great stress test, and if you have instability in your overclock, SETI will often show it. You can also try running Prime95 or run a ton of loops of SiSoft Sandra and see if it crashes then, I'm betting it will, your system probably was 99% stable at the overclock, but stressing to to the max causes it to crap out, it's happened to me.
 
I agree with what DarkMajiq said.

You should keep testing other frequencies between 1100 and 1320 MHz. Try 1200, 1250, 1275, and keep testing it out until you find the greatest speed at which your computer will remain stable with the CLI. You'll still probably be better off with the CLI at 1100 than the GUI at 1320.

On my T-Bird 1400, I've tried overclocking to anywhere from 1500 to 1650 MHz. At 1650, I basically killed my processor, but was thankfully able to resuscitate back to life. Right now I've found that the highest stable speed I can get to is 1586 MHz (10.5x151). Anything higher, and it'll last for a little while, but it'll eventually blue screen on me.

It'll just take some patience and some tinkering to find your ideal overclock speed. Keep in mind that upping your FSB helps your SETI times more than upping your clock multiplier, but can make it more unstable.
 
What DM said makes some sense. The gui version doesn't seem as intense as the cli version. I haven't tried any other speeds, but I will as soon as I'm done with my race against EvilWobbles. Can't afford to experiment too much in the heat of battle! 😉
 
Also remember that the higher the FSB the better for SETI. If you can get 10 X 120 it will be better than 11 X 110.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top