low strife

Here is the closest encounter I've had.

I just had gotten my friends computer built after several hours. For the first time, I started it up to check the bios and then get XP installed. After finishing my routine checks, I looked at the PC health status in the motherboard to see what the Q6600 was doing since I was interested in how hot it was running. I freaked, since it was running at over 100c.

Turns out that the motherboard PCI-e wire was stopping the fan on the chip. Thing's fine though, I swapped chips when I built my computer, and it's been running 3.4Ghz without problems.

__________________

Demented

I'm so glad I have absolutely nothing to contribute to this thread.

__________________

arkheii

I vacuumed my old old old PC a long time ago. It fried the mobo. Glad it was under warranty.

__________________
CPU History: Manila -> Brisbane -> Wolfdale
GPU History: RV560 -> G94 -> R700 -> RV770XT

rla4000

I fried my ASUS P5Q-SE as a result of Load Line Calibration while searching for that illusive 3.6 OC on my Q6600.

On the P5Q series at least from my experience the LLC option when enabled gives an enormous V-Rise. it doesnt just stay the same as the Bios setting, it boosts it dramatically.

So, stupid old me put 1.55vcore in the bios (everything else was failing...........this also leads me to another side point that IF your OC is failing it is high chance it is the Motherboard that is not doing its job, rather than the chip itself.) So I thought 1.55 should do it (it was just a stab, I forget what vcore I had prior - would have been high 1.4XXX)

Once I pressed start on Prime I saw the vcore spike to like 1.67.......... !!1111 slowly watched 2 cores hitting 72, then the third, then the fourth....all four were on 72 (with a TJ of 100 at the time...) then count 1.................2....................3.......... .......power off. Black screen. No dice. LED remained on...upon pressing the power, nothing. Power off at wall. Power back on PSU, press button, fans spin once, no dice.

Freaking out, I thought I just fried the Q6600.

out it came, into Dads, e2180 into mine. First I booted Dads to see it start, get halfway through windows load to Die. I was like FTW!!!!!!!!!1111111111111 Then I realised I haddnt seated the stock cooler in Dads properly. Re did it - booted. Sweet. It wasnt the chip.

Then I thought it was the PSU. As the e2180 would not boot in mine.

Switched PSUs with Dads, booted.

Damn. I thought....its the MOBO! All the time I was thinking "which of these is going to be more of a prick to RMA.........originally I was like CRAP! cause I had lapped the Q6600...making it null and void...anyway, the Mobo is on RMA right now- however I feel they will Reject me because The P5q-SE had a PCI-e x16 clip that faced downwards which would LOCK my GTX into the motherboard, thus unable to get it out. (Did it once, took me 1.5 hours to get it out, lots of stress, almost broke the mobo and the card's PCB in the process...moral - cut the x16 clip off if it faces DOWNWARD! The new P5Q that I replaced it with had the clip facing upward toward the NB, thus enabling the card to be removed.)

So yeah, watch LLC! and Cut the clips off.

__________________

KarmaKiller

I was moving a top fan once in my case, with it running.

Got most of the screws out, the 3rd one, I got it loose, then it fell of the end of the screwdriver, bounced off the bottom of the case, and went right through one of the little slots in my (at the time) Antec PSU. Then I got to witness a nice firework show, all while the computer was still on. I freak'd out, and pulled th cord loose from the wall. Unmounted the PSU and shook it around till the screw fell out, hooked it back up, started it up, ran fine. So I shut down the PC then, to finish my fan moving, reinstalling the PSU all the way. When I went to turn the system back on, nothing happened.

Ended up taking out my PSU/RAM/Mobo/and 1 out of 3 HDD's.

I now shut off the PC before I do anything on it.

__________________

RyanRacer48

LOL great stories guys! This thread is becoming a HOW NOT TO for any computer noobs out there LOL .


Keep em comin!

__________________
" A lot of things wouldn't get done if it weren't for the last minute. "

http://www.overclock.net/sale/588228-worldwide-new-hdmi-xbox-360-iz3d.html

MY BUILD THREAD - BONEYARD

m@v3r1ck

This happened to a friend of mine when we both worked as bench techs at a Point of Sale systems repair shop.

I was working beside him on my own system, when he just powered on the till he had just finished repairing. All of a sudden I heard a loud crack and one of the trails on the mobo started on fire and ran from the 20pin power connector to the cpu like a trail of gun powder, sadly without the big "boom" as it reached its end.

The same friend also did something similar with an IDE cable, it burned from the inside out along the red coloured side.

__________________

donk165

I once blew my mates PC by wearing a woolly jacket when they were working on it. They all didn't use a static band so I thought I wont either, and I completely forgot how much static the jacket generates and I touched the motherboard and then booted and there was a loud pop noise and it would not boot anymore. Luckily he didn't mind and we had spare parts and managed to get the PC working again, and it was a fairly crappy build, made from scrap parts only.

Don't wear woolly jackets when touching a computer!

__________________
Google is Awesome!
3dMark06: 18244

Krusher33

Darn it... Was hoping for more stories... guess people don't want to embarrass themselves...

rla4000

agreed, people are always RMAing or complaining about RMA etc every day on here, surely someone fried something.

__________________