OMG I screwed up my 3000 venice

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

T101

Senior member
Oct 13, 1999
558
0
76
No, that is not any dangerous temperature. What I meant is that you are running that cpu at 1.536V. If I remember correctly, AMD does not warrant your chip if it has run any higher than 1.45V (I might be wrong there). But the point I was trying to make is that higher voltage kills your CPU faster than running it too hot does. The truth is that overvolting kills semiconductors (the type of circuitry that a CPU are made up of). It is just a matter of time. The greater the overvolting beyond specs, the faster this process occurs.

That is why I said you should keep that in mind, in case you can not live without a working computer.
 

theMan

Diamond Member
Mar 17, 2005
4,386
0
0
1.536 is definately not unsafe. unless you want to have the computer under constant heavy load 24/7 for 7 or 8 years...
 

Muggy

Member
May 14, 2005
52
0
0
Same problem that I had. This happened twice to me - No boot and long beeps. The problem, that I found during the second time this came up was that my ASUS StarIce cooler wasn't properly seated. I removed everything, cleaned the thermal paste, applied fresh paste and used my stock HSF and it worked just fine. But had a real struggle during the first time this came up. I even tried the proccy on another rig and it still wouldn't boot. I left it out for a week and then removed evrything, applied fresh paste and used the stock HSF and it just booted fine. The problem came up the second time coz' I took my rig to a lanparty and the cooler moved while I was travelling and started the problem :disgust: