Prime95 giving errors

[SRabbelier]

@MS Dawn: Sorry, what do you mean?
Rather then finding the next Mersenne Prime, I'd like to have it work fully 😛

 

[Fern]

Originally posted by: SRabbelier
Yis saying I'm cooking my CPU? 0.o
Strange thing is, I didn't set it to this, the BIOS, when set to "auto", automagicly picks 1.75V...? Your board's BIOS may be too old to recognize the Sempron properly

[EDIT]
And sorry, what's a "barton"? 0.o
[/EDIT]

The Barton is a CPU core revision of the AMD Athlon skt a CPU series

 

[SRabbelier]

During the night, and the best half of today, I let memtest86 run, (in total some 17 hours, equalling aprox. 37 runs), and it gave no errors.
Asuming it's my cooler, (that came with my previous processor, a AMD Athlon 2600+), I decided to buy a new one, which will be installed soon.

On another note, I was reassured that setting the voltage to 1.6V would allow overclocking, the reason that AMD prevents setting the voltage to below 1.75V.
I have no idea why the guy I asked it thinks that, but he seemed 100% sure, and indeed, when checking the bios, it proved impossible to lower the voltage manually.
Could it be that this guy is right? And if not, what should I do, as said, I can't change the VCORE to below 1.75V in the BIOS..

 

[Fern]

On another note, I was reassured that setting the voltage to 1.6V would allow overclocking, the reason that AMD prevents setting the voltage to below 1.75V.

The above statement makes no sense. When OCing you generally must raise the vcore to higher amount so that the cpu will run stabley at the higher speed. If AMD wanted to prevent us from OCing (and burning up the chip) they would try to prevent us from increasing the vcore, not decreasing the vcore.

Another reason the statement is gibberish is because the CPU manufacturers (e.g., AMD) can't control how much vcore you give to their chips. That's a feature of the motherboard, or one of us enthusiest doing a wire-trick if the mobo manufacturer doesn't include taht feature in their mobo.

Since your mobo apparently lacks the feature to change vcore you might investigate whether a newer BIOS would allow your mobo to properly "recognize" the sempron cpu and apply the proper vcore.

Seems to me the excessive vcore is overhesating the cpu thus making it run unstable.

Fern

 

[SRabbelier]

Mhhh, it didn't add up for me either.
Would a bios update be worth a try?
If so, how should I do that?

 

[Bobthelost]

Head over to the manufacturer's website and search under support for your motherboard model. There should be a copy of the lasted BIOS to download as well as instructions on how to do it there. If not then stick up the details in the motherboard forum and beg for help (or just keep bumping this thread 😉)

 

[Fern]

Originally posted by: SRabbelier
Mhhh, it didn't add up for me either.
Would a bios update be worth a try?
If so, how should I do that?

I suspect you may be able to simply manually change the vcore yourself. The Asus site wasn't working (couldn't d/l the manual), but did find this POST which discusses changing the vcore on your mobo. It says to - change CPU vcore Setting to MANUAL
- decrease vcore to 1.60v

Have a look in BIOS. Changing the setting to "manual" may well bring up another screen so you can change it.

Fern

 

[CuriousMike]

It's been mentioned a couple times in this thread, but let me re-iterate.

According to your sandra dump, you might have 2-256mb memory modules.

Remove one of them, and run the test.
If the error occurs, remove the current memory module, and replace it with the other memory module.
Re-run the test.