Did i kill my Duron?

[DjDan]

Tried to overclock my 700MHz duron this weekend, and after getting it to run stable at 900MHz, I ran "CPU stability test". At the beginning no problems, but when I returned some 10 hours later, it had moved form "Rock stable" to "dangerous", throwing up lots of errors. Vcore was set to 1.750, temp never over 40 degrees C (approx 105 F).

Resetting it to 700MHz doesn't seem to help, it still creates errors. :'(
Any tips on what I can do short of buying a new CPU?

System: MSI Pro2a, Duron 700Mhz w/FOP32, Mira 133mhz ram (256 MB), ATI AIW128

[proze]

have you set any bios tweaks back to normal..? maybe it was your memory that was giving problems and still is. that mira ram is not the best... try other ram and see what happens.

[Vovan]

If there is no messages during the start up like:
BIOS checksum error or others, maybe you CPU is still alive and you should try to set the lower voltage.
If such appear then - sorry - you TRULLY HAD SPOILED YOUR CPU.

I had the same CPU, the same speed and THE SAME PROBLEM!
The technical detail is - NPU BURN!
You will be lucky if the guarantee is be applied!

[DaveB]

It sure sounds like it. Dunno why you guys run these intensive tests for such a long period of time. They all provide a disclaimer stating that such testing stresses components and can lead to damage. There is simply no reason to do this as they do not simulate any normal operating situation. I just run the Burn-in Test and 3DMark 2000 a couple of times and then use the system. I never leave the system alone since it is possible for it to hang in a high current draw state which could lead to damage.