Worst PC Build Screw Ups

Page 26 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Status
Not open for further replies.
I would think that this would be at best a very difficult OC.

Given changes to rotational speed I would think that you would have to do the OC and THEN install OS and follow on utils. Since the writes/reads would still happen at the same timing intervals and the position of the head would be diff erent. based on the rotational speed.

But if you write and read at the same rotational speed as initally started then I think all would be ok...

Just a little brainstorming. Then again the track info for the heads would remain the same and if you missed it on the first rotation the second rotation should find what you are looking for. You would just have the head available for read for the correct duration....

My head hurts :)
 
Not too serious, but I was building a PC and the first thing I did was install my power supply in the case. I just thought I'd check to make sure it would turn on so I plugged it in and turned it on. Nothing. Fans didn't spin up or anything. Returned it to Newegg, they test it and it works fine. Tuns out you have to plug it into the mobo for it to turn on. Doh.
 
Without realizing the ramifications of what I was doing I slapped a 33% overclock on an AMD K6-2 450mhz (using the cheapest motherboard, PSU and HSF I could find at the time). I did this because when I realized I had payed extra for PC133 RAM that, if I didn't OC, was going to run at the same speed as the cheaper PC100 RAM (I had gotten the 133 because I had been told it was a big performance boost) I was annoyed.That was the first PC I ever built from scratch ~6years ago and my mother is still using it to this day. During the summer she takes the side-panel off and points a large household fan at it so she can burn CDs in the morning before it gets too hot to do anything intesive on the PC. By far my cheapest, most stable, and biggest OC ever.
 
I don’t feel bad for people who lose HDD data w/o a backup.
And if I’m not mistaken, its the ball baring motor that explodes.

It says right on the Seagate website: "Do NOT overclock our HDs. 7200 RPM means just that - leave the 10K to the Raptor!"

How the hell might one OC a hard drive?


:trophy: Congradulations on winning todays "didn't read any previous post, but I entend to commment anyway" award.
 
I'm not about to even think of touching my server (the only system I possess which has SCSI) with a mind to OC anything, so that rules out SCSI.

My SATA resources are also too limited (4x250GB and heavily used) to even consider.

Ah, well. Don't overspeed HDDs, people! Dangerous it is, very dangerous.
 
We havent discused SCSI yet. Did you know the further down the scsi chain your drive is, the faster it spins.

"
0 Card
1 14,003rpm
2 14,456rpm
3 14,992rpm
4 15,242rpm
6 15,853rpm
7 16,542rpm
8 17,945rpm
9 19,535rpm
10, 22,242rpm
"

As quoted.
 
I've almost completely lost track of who is joking and who seriously thinks you can just go in and change the rotational speed of your HD...

On a similar note I'd like to point out that it is possible to overclock your PCI and IDE *interfaces*. Modern motherboards lock these frequencies and SATA is fully buffered and just runs happily own it on frequency clock and turns the interface on and off as it pleases (with power-saving settings enabled), but back in the day you had to keep your ratios correct or you could corrupt your data, with occasional claims of HDs being permanently destroyed. You could, in fact, speed up your PCI and IDE bus by a few mhz and still have it function correctly (and people would do this to try and get a few more mhz out of their CPU if they couldn't make the jump to the next ratio), but I don't think anyone ever claimed that it improved performance although, theoretically, the bus could be overclocked by ~3% which should reduce latencies by up to 3% and increased bandwidth by 3% .

But really, for the love of noobs: you CAN'T overclock your HD. It won't melt down, or explode if you do, you simply can't do it in the first place. It's controlled by hardware, it's not a setting. There are power saving, integrity, and tempurature safety settings on some drives that you could disable to try and increase performance while possibly damaging the drive, but not the rotational speed.

Stop trying to confuse the poor noobs 😛
 
guys as one of the youngest ppl on the forum at 12 (don't get me wrong, i know my hardware), you're jinxing me. Im building my first when kentsfeild when it comes out, and i hate u guys for this. lol, well you learn with mistakes so w/e
:twisted: Don't worry if you toast the cpu, there will be a free circus show with fire, sparkles and smoke. Just enjoy it! :twisted: (and don't forgot to write down the story here :wink: )
 
Grats starting young. Thats really the way to do it.

I recomend building it and then right away putting adds in the paper and sell it for more then you payed (not much, but you could).

I started building selling when I was 8 and thats the best way to get the amount of experience you need if you think this is something you want to get payed doing.

Pluss you get endless free upgrades by selling your comptuer and buying a beter one.
 
For me, it would have to be when I fried my brand new Athlon xp 1600+, back in 2001, when it had cost me 150 quid.

I was watching my mates playing GTA3 on my ps2 and I couldnt get the heatsink to go on, so without thinking, I spun the heatsink round and clipped it on easily. Then booted up and within 10 seconds i could smell burning, and that was that, bye bye xp 1600, hello 1Ghz Tbird again. I was so angry, just like lighting up 150 quid, arrgghhh.

Because I'd spun the heatsink round 180 degrees, the lip was on the wrong side and it meant that only half of the core was in contact with the heatsink, whoops!

It happen to me too, but with a tbird 1Ghz, it worked overclocked , but too hot, I opened the case, spun the heatsink, but broke the central hold of the heatsink(it has tree on each side). I don't know why, but I decided to hold the heatsink with the hand to see if the computer still worked. Smoked and ready the toast. :cry:
 
Few month after buying my first pc I put the fsb(66Mhz) to 100Mhz in the bios, no boot, black screen, and i can't open it because of warranty(and I was a noob then ) . Sent in back, got it replaced, no questions.
 
HAHA LOSERS!

Joking of course.
New one for me. One of my co-workers just cracked the mobo trying to install the CPU. Pushing too hard, and forgot some of the support stand-offs.

I have never seen that happen. Well I guess I should be more carefull myself.
 
Has anyone tried to overclock a computer at school and screwed it up?

At high school we got 486s so go figure how much you can overclock that. :lol:
They bought Pentiums MMX when I was finishing the last year. 🙁
 
Okay, here's a *rumour* I heard the other day and I'm not quite sure what to make of it...

Apparently the guy did a major OC without doing the prereading and checking with local gurus and managed to cook the HSF to the point where the aluminium ignited.

Heard this from one of the local linux wizards, who heard it from (fill in the blanks)...
 
I would surely hope so...you can't melt a heatsink before the system would shut off due to other things melting...like the traces in the mobo and the internal workings of the CPU. Plus, I'd imagine the mobo or the PSU failsafes would trigger a shut down. But I'm sure you had some newbs LOLing. 😛
 
Status
Not open for further replies.