Normal XP 2600 Speed?

[ajbrun]

Could someone please tell me what the normal 2600 XP should be without overclocking or anything? I ran prime95 with the setting that I think are "normal", but I keep getting an error on prime after about 5 minutes. I also think that it's the same error (but not certain) because it has the same numbers there (i think) like:

0.4 expected 0.446583658676364.

I looked in the readme about the torture test that came with prime95, and it says that there may have been an update in the program or something, but I only just got it!

So.... right now, I'm running 11.5 multiplier (i think) * 166 MHz FSB = 1.91 GHz

Is this what it should be?

[javalord]

Sped is correct for a barton based CPU. Memory can cause these kind of errors too.

[ajbrun]

OK - what could be the problem?
How can it be fixed?

[ajbrun]

Right, I just ran the test again, and I got this after 4 minutes:

Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
FATAL ERROR: Rounding was 0.5, expected 0.4

What should I do?

[bindo]

I'm using an AMD 2600+ with 512Mb of pc2700 RAM, the RAM is rated at 2.5-3-3-6 and im using the same Mobo. My system defaults at FSB 166Mhz * 12.5 multiplier = 2.02GHz, that's with no overclocking.
I usually set mine at FSB 174Mhz * 12.5 multiplier = 2.17GHz with no problems. Hope that helps.

[ajbrun]

Well I'm definantly sure that my multiplier is 11.5 and it's locked, so how come you're's is 12.5?

Any idea on why it's getting error though?

[bindo]

The old xp's shouldn't be locked, have u looked at all the options in the BIOS? on mine's it's in a menu called "FREQUENCY/VOLTAGE CONTROL"

I haven't a clue about the error in Prime95 sorry.

[ajbrun]

Yeah - I changed that option, and then it wouldn't POST, so I had to reset the BIOS, therefore I presume it's locked. Also, mines quite new (about 4 months old), and those after as certain date, january I think, are locked.

Can anyone else help on the Prime95 error?

[javalord]

Yeah - I changed that option, and then it wouldn't POST, so I had to reset the BIOS, therefore I presume it's locked. Also, mines quite new (about 4 months old), and those after as certain date, january I think, are locked.

Can anyone else help on the Prime95 error?

Prime95 can have errors where:
-CPU overheating
-undervolted CPU (1.65v is standard for these bartons)
-faulty memory (unlikely one)
-aggressive memory timings
-PSU unstable
-inteference (emi)

Soooo, firstly reset your BIOS to standard default settings with default clockspeeds and use SPD for memory, and work from there.

[Rave]

Could easily be a memory error. Slacken off the timings in the bios and see if that's the problem; in some bioses if you have them set to 'optimal' or something they can actually set the timings too fast for the RAM to handle. What RAM and motherboard are you using? Set the timings manually to 2.5-3-3-7 for now.

As for the difference in multiplier between your processor and Bindo's, it's because his is a Tbred whereas yours is a Barton.
Rich :¬)

[ajbrun]

Prime95 can have errors where:
-CPU overheating
-undervolted CPU (1.65v is standard for these bartons)
-faulty memory (unlikely one)
-aggressive memory timings
-PSU unstable
-inteference (emi)

Soooo, firstly reset your BIOS to standard default settings with default clockspeeds and use SPD for memory, and work from there.

OK, I'll set everything to default, even though I'm pretty sure it's "correct", because when at default, it goes to 133 MHz FSB instead of 166. Shouldn't I leave it as it is, since I'm getting "normal" clock speeds?

Also, what's SPD?

Could easily be a memory error. Slacken off the timings in the bios and see if that's the problem; in some bioses if you have them set to 'optimal' or something they can actually set the timings too fast for the RAM to handle. What RAM and motherboard are you using? Set the timings manually to 2.5-3-3-7 for now.

As for the difference in multiplier between your processor and Bindo's, it's because his is a Tbred whereas yours is a Barton.
Rich :¬)

How do I slacken off the memory timings? I've not seen anything in the bios (although I could have missed it). Is it to do with this SPD thing?

Also, my RAM and mobo are as my sig says - I find that easier than having to type it all out whenever someone asks .

[Paul Adams]

CPU support page for your motherboard:
http://www.msi.com.tw/program/produc...UID=436&kind=1

Manual for your motherboard:
http://www.msi.com.tw/program/suppor...UID=436&kind=1

Page 3-12:

System Performance
This field allows users to control the status of system performance. Users may select [Auto] for the most stable settings by SPD. [High Performance] will increase the system performance but may have instabilibity problems.
[Manual] allows full customization of performance options, and is recommended for experts only. Settings: Auto, High Performance, Manual.

Page 3-13:

FSB/DRAM Ratio
This setting controls the ratio of CPU FSB clock & DRAM Frequency to enable the CPU & DRAM to run at different frequency combinations.
Please note that the setting options vary according to the CPU FSB clock preset. Options: By SPD, 2:1, 5:3, 3:2, 4:3, 5:4, 6:5, 1:1, 5:6, 4:5, 3:4, 2:3, 3:5, 1:2.

Current DRAM Clock
It shows the clock frequency of the installed DRAMs. (read only)

Memory Timing
Selects whether DRAM timing is controlled by the SPD (Serial Presence Detect) EEPROM on the DRAM module. Setting to By SPD enables DRAM timings to be determined by BIOS based on the configurations on the SPD.
Selecting Manual allows users to configure the DRAM timings manually.
Options: By SPD, Manual, High Performance.

Useful tools:
CPU-Z: http://www.cpuid.com/cpuz.php (identify CPU & memory settings)
MBM5: http://mbm.livewiredev.com/ (check temps)

[ajbrun]

Right, I did all the above, restarted and I ran the test again, but got another error:

FATAL ERROR: Rounding was 0.4999437332, expected less than 0.4
Hardware failure detected, consult stress.txt file.

What's wrong? I should also point out that the vcore setting isn't on a number like 1.70, it's on H/W which I'm not sure what it means, but it's the default. So have you got any other suggestions?

Thanks

[Firelord]

Don't rely on prime95 as good as it is on testing stability its not always stable on some systems

Myself I can run countless loops of sandra sys burn in, 3D Mark, Commanche 4 bench, F@H and video encoding at 2.8GHz but prime dies after 10-15mins with errors. Now its been proven by people such as marci at O-cUk that primne is not the be all and end all of system stability.

Basically if your system is stable for everything you do ie gaming etc but can not complete prime then don't worry. Real world testings far better

[ajbrun]

Are you sure? I can tell there's going to be a big argument soon about this .

I'd just rather have my system completely stable, because then I know there's NOTHING wrong with it. It also means that if I decide to overclock then I've got something to test that too. I can't overclock until it's stable as it is now.

[Firelord]

Can you do everything else without crashes or restarts?

My A64 didn't run prime @ stock but at 2.6GHz so go figure?