• 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.

Prime95 - What am I doing wrong?

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Originally posted by: jello
Okay, been bashing on it a while and still nada from Prime. I'm running an athlon xp 1700+ on an abit nfs-7 board. FSB is set to 166, multi to 8.5, vcore to 1.625 (yes, this is slightly underclocked and slightly over volted). Ram is mushkin value set to the most conservative values (7-3-3-2.5) available. Temps range from 40-46c give or take according to the winbond hardware doctor that shipped w/ the board. Prime runs for something like 10-15 seconds before it dies. Someone tell me what the heck might be going on?

It's probably your ram,prime95 catches ram errors also.

run memtest to be sure it's the ram.
 
Nope, doesn't look like it. Memtested for over two hours today and everthing is kosher. Also looped 3dmark while I was at work, 10 hours and it was just fine when I got home a few minutes ago.
 
To rule out the cpu you could try running it stock FSB and multi and see if that works. And was it Memtest86 that you ran?
 
Originally posted by: pelikan
To rule out the cpu you could try running it stock FSB and multi and see if that works. And was it Memtest86 that you ran?

The memtest is the latest version from the hcidesign page, 1.3 (copyright 2003 in the manual). The processor is designed to run at 133x11 (1463) but is currently at 166x8.5 (1411). I didn't think it was possible to be the FSB is the processor itself is clocked at or below stock speed. Is it?

 
Originally posted by: jello
Originally posted by: pelikan
To rule out the cpu you could try running it stock FSB and multi and see if that works. And was it Memtest86 that you ran?

The memtest is the latest version from the hcidesign page, 1.3 (copyright 2003 in the manual). The processor is designed to run at 133x11 (1463) but is currently at 166x8.5 (1411). I didn't think it was possible to be the FSB is the processor itself is clocked at or below stock speed. Is it?

Memtest86 is generally regarded to be a more complete test that can find errors Memtest will miss. As far as the cpu, I think it can't hurt to try Prime95 at stock FSB because cpu's do have FSB limits. While I would be suprised if 166MHz was beyond the limit of your cpu, my thoughts were to completely rule out the possibility of cpu errors.
 
Thanks, memtest86 started turning up errors right away. Not a whole lot, but more than 30 over a 40 minute span. Mushkin has a new stick on the way to me now.
 
Originally posted by: jello
Thanks, memtest86 started turning up errors right away. Not a whole lot, but more than 30 over a 40 minute span. Mushkin has a new stick on the way to me now.

if it errored out when the cpu cache was turned on, it could be the cpu cache causing errors (which means too high of an overclock)

but whtaever...a new stick is always good 🙂
but if it errors out with the new stick, then its the cpu (should lower the oc then)
 
I did the memtesting with the cpu at 133fsb and underclocked, don't remember if I had the cache turned on or not. So it's not overclocking at this point, either way. =)
 
Back
Top