New XP install and overclocked comp=CCE errors.

[w00t3r]

I recent reinstalled XP and also I took the time to overclock my computer some 200mhz. Well before this CCE ran fine no problem but now I get CRC errors. Is the computer overclocked too much and spitting out bad data? I dont want to put it back down to default since its runing stable and everything (excecpt CCE) runs fine. Anyone overclock and use CCE?

[dvd2svcd]

Overclock = Often CCE crashes. It has been seen many times.

[markrb]

Read this should help. 99% of problems are that you overclocked too much and only a program as demanding as CCE shows any problems.

http://rilanparty.com/vbb/showthread.php?s=&threadid=14336

XP works fine with DVD2SVCD, although many people have been blaming it.

Mark

[w00t3r]

Yep it was the overclocking for sure. CCE encoded fine after i set it back down a little. Its interesting out of all the other benchmarks I ran (SiSoft, 3DMark2K1, Prime95) none of them crapped out but CCE did. CCE is probaly the best stability tester I know of.

[DDogg]

When OC'ing always run the prime95 test until you have no errors. If prime will run (without errors), CCE will run. Choose the torture test and let it run for a day.

ftp://mersenne.org/gimps/p95v21.exe

[24hourloop]

Never overclock. Never, ever overclock. It will work just fine for weeks on end and then you all of a sudden get weird problems you cannot explain and it can take you a long time to figure out.

I used to overclock, I never do anymore. It's really not worth it.

At least now when I run into a problem I know it's not the CPU.

[markrb]

I have been overclocking for years and never had any major problems. If you know what you are doing you will have no problems.
You just need to find the limits. People that figure their system is fine unless it crashes will run into problems. You need to test the subsystem and not rely on the OS to show you the limits.

Mark

[w00t3r]

I started overclocking again, except this time no multiplier change just traight FSB overclock and it seems to be going pretty good. I think the first time I had troubles was because of the multiplier. Increasing by 10mhz a day and then torture testing with prime95 is the best way to make sure the system is stable. If I do get errors, would increasing the voltage on the ram possibly make it run "cleaner"? Or do I have to increase the voltage on the cpu even though the multiplier hasnt changed?

[DDogg]

"If I do get errors, would increasing the voltage on the ram possibly make it run "cleaner"?" Yes, perhaps, but also playing with the ram settings ONE AT A TIME with testing in between using the two programs mentioned is the key. You want to end up CAS 2 instead of 2.5 if at all possible and make sure you have memory interleaving on.

This is getting off topic a bit.

[nsdn]

It is better to use Multiplier to overclock than the FSB since with FSB (or the system clock) your driving the whole board harder...

best way to overclock I have found is to wind the FSB up until the system just becomes unstable then wind it back a few notches...THEN it is time to play with the multiplier and Vcore settings...

CCE runs the CPU at 100%...as a result the CPU will run A LOT hotter than normal applications.....(most apps do not run the CPU at 100%)....it might take an hour or 10 before the CPU/clock speed and temperature combination causes it to fall over but it is at this point u wind the multiplier back a notch.....or two until it becomes stable.

BTW....no point in upping the Vcore volts if your just playing with FSB....invaribly something else in the mobo will give before the CPU does.....(tho not ALWAYS the case)

hardest part is unlocking the XP athlon...grrr....

Athlon XP1700+ (1460M) @ 1800M= XP2000+ with FSB @ 288 (system 144M multiplier@12.5)

yep its off topic sorry...but....anything to lop off that extra hour of encoding...:)

[w00t3r]

I changed some ram timings around so the ram runs faster then o/c it a bit and now I get RT 1.2 in CCE which is up from 1.025 or so so im happy with it.