General comments on overclocking and Prime95:
If you're overclocking a CPU, it is a good idea to run the full Prime95 self
test (Options menu) to ensure that the CPU is stable and functional for all
FFT lengths. This is especially important if you are using a Xeon
processor, as there are interesting cache functionality problems that only
appear when a certain percentage of the die is used. Note: This behavior
appears even more often on the latest Intel Coppermine processors -- only
Xeon-like configurations checked so far.
It is also possible to have an overclocked CPU pass the full self test
suite, but later exhibit problems. The likely culprit is simple wearout --
the CPU initially was barely functional at the overclocked speed, but slowed
enough that it no longer runs. If this happens, you usually can still run
the CPU at the rated speed.
Regards,
Ethan
> -----Original Message-----
> From: [EMAIL PROTECTED]
> On Behalf Of Aaron Blosser
>
> > I also got the "illegal sumout" and it locked up my machine. It did it
> > four times in a row at the 6564090 iteration (the lock ups were hard
> > locks - had to recycle power to recover).
> >
> > However, I had my pentium-II 266 overclocked to 333, and when I reset
> > the speed back to 266 the problem went away. I have had it overclocked
> > for about 5 months now with no problems. I have been running prime95 at
> > 333mhz since 16 May 99. After resetting the speed to 266 I went back to
> > an older backup file (and lost about 4 hours work) just to make sure I
> > am still working with good data. Interesting to note -- the average
> > iteration speed at idle (0.275 sec) remained unchanged regardless of the
> > CPU speed change. Does overclocking even help?
> >
> > Maybe this error is a bug, maybe a hardware error, although the latter
> > seems more suspect in my case.
>
> I've seen this happen a lot on computers that are either
> overclocked or just
> have a faulty CPU/memory module.
>
> For instance, I've got a nice IBM PPro 200 machine that's been running
> NTPrime for nearly a year now, rock solid, nary a problem. On a whim, I
> thought I'd see if the machine could handle 233MHz. Everything else ran
> okay, NT, Office, etc. but NTPrime started kicking out errors like a
> banshee.
[SNIP]
> Anyway, long and short is that overclocking might seem to work fine, but a
> really CPU intensive program like NTPrime/Prime95 is likely to show
> problems. Heck, it's a great way to find out if your overclocked
> system is
> really working as well as you thought...just back up any temp files
> beforehand so you can revert back to them when/if you start
> getting errors.
>
[SNIP]
>
> Aaron
>
> ________________________________________________________________
> Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
>
________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
