Have you ever damaged a CPU from overclocking

[yhelothar]

If so, what was your overclock. What symptoms manifested?

 

[Grooveriding]

4.8ghz on the same CPU in my Sig. Just died one day, system no longer posted.

 

[lavaheadache]

I've been beating the piss out of cpu's for a solid 20 years. Haven't managed to kill one yet.

 

[scannall]

I did damage a motherboard though, changing the clock crystal on an old 386 system. I think I was going from 20 Mhz to 25.

 

[psolord]

Also damaged a mobo, from an old Prescott. cpu never.

 

[nwo]

I managed to brick an i5 4670k about 6 months ago. If I remember correctly, I was trying to use ASUS AISuite extreme OC. Even after resetting the CMOS, I could not get the PC to boot up. Exchanged it with an i7 4770k and everything else was intact.

 

[Tweakin]

I did damage a motherboard though, changing the clock crystal on an old 386 system. I think I was going from 20 Mhz to 25.

Funny, I killed a couple of 486 boards trying to do the same when I was in the Navy!!!

 

[DeathReborn]

I killed a AMD K7-700Mhz (Pluto) using a GFD pushing it to 1.1GHz, it was my 2nd chip which I was ocing for my brother so I had to buy him another and settled at 1GHz on it. The motherboard & 2nd CPU worked flawlessly for nearly 2 years before I built him another system.

I also killed a Opteron 180 but it was an accident, forgot to connect the power to the pump in the water cooler after a PSU upgrade and cooked the chip, again the board took to a new chip just fine.

 

[yhelothar]

I managed to brick an i5 4670k about 6 months ago. If I remember correctly, I was trying to use ASUS AISuite extreme OC. Even after resetting the CMOS, I could not get the PC to boot up. Exchanged it with an i7 4770k and everything else was intact.

What kind of OC settings did you use? Voltage?

 

[ipown1337]

A long time ago when i was unexperienced I had an unstable Athlon XP 2100 +. I noticed that higher voltages made it stable, after running at ??? voltage for about a year it fried. I also had an e6300 that i oc'd to 3.2 GHz, after about 2 years max over clock at the same voltage was 3.0 GHz.

 

[PliotronX]

I attribute my never so much as having a degrading CPU to looking around for average top voltages and heat levels. I've also never damaged a CPU taking the noobshield off. GPU's on the other hand...

 

[ratjacket]

never a cpu

nuked a couple of mobos when i had low xp

 

[rgallant]

voted no
I search the net well before buying the chip for the avg. oc at a sane voltage ,
test the chip to see if it is avg. or better and never try for the crashing max.
-say the ib I have now , I could run it on 4 cores at 4.9 , but I run it at 3.5 to 4.6 until I feel I need it faster to over come a bottle neck.

 

[Denithor]

Never killed a CPU but did have an EVGA motherboard croak when I switched from an i3 dual to an i5 quad. Heavy OC on the i3, i5 was stable at stock, tried a very light OC and it just quit working. Wouldn't post again after that even with the i3. Was most unhappy...

 

[Morbus]

I managed to boot to windows and run a few tests stable on my old E6550 @ 3.2GHz, while pushing my ram, other than that it would crash (two of the DIMMs are 333MHz stock...). That was my most aggressive overclock, but it was on the stock cooler, so I downed it to 2.8GHz. The CPU is 2.33GHz stock, and it doesn't even break a sweat in 2.8GHz, it's like it's made to be there, I simply upped the FSB to 400MHz and off it goes, merrily along.

Fantastic thing.

 

[nwo]

What kind of OC settings did you use? Voltage?

I'm not sure about the voltage since it was an Auto OC and I didn't get a chance to look at it. But when it booted into windows it showed up as 4.5 or 4.6GHz and several moments later the PC shut down and I couldn't get it to boot up even after resetting the CMOS.

 

[BrightCandle]

I have degraded a CPUs maximum overclock, I have blown multiple motherboards but I have never actually made a CPU fail from overclocking.

 

[nurturedhate]

Never anything on accident

 

[Ken g6]

No, and I tried to OC a Cyrix once. (It just didn't boot. Reset the jumper setting and it came back fine.)

 

[Tristor]

I've never killed a CPU unintentionally while overclocking. I do not count the several AMD CPUs I intentionally fried when I no longer wanted them just to see it happen (all of which ended up being jewelry of some sort afterwards). I have killed a motherboard before though (the VRMs went) during my first sub-ambient cooling overclock.

 

[IGemini]

I haven't directly killed a CPU that way.

However, I sold a friend my Conroe E6600 and it spent its life overclocked from 2.4 to 3GHz. After six years of constant use the logic core ultimately decided that 13 wasn't a prime number anymore. Who knows if the OC contributed.

 

[Shawn]

Killed an old Via Cyrix cpu. Had the jumpers set for a pentium (which was around 3v I believe) and the cyrix only used like 1.5v. Filled the room with smoke. System still posted after that but was completely unstable. I think I killed the onboard cache.

 

[richaron]

AMD K6-2 450 & XP 1900+. No Idea of the settings, but nubbery came into it.

Tasted like burning.

 

[FalseChristian]

Fried a Core2Duo E8400 at 3.6GHz after only 1 year. The worst CPU I've ever had. My current i5 2500K has purred along at 4.5GHz for 2 1/2 years now perfectly. The best CPU I've ever had. Go figure.

 

[mcginnis]

Never killed a cpu. I think if you take your time you won't really run into too many issues unless you go ridiculously high.