What are your worst computing mistakes?


Recommended Posts

Removing a heat sink from a cpu using a butterknife. (Only thing I had to use at the time....butterknife slipped off the retainer clip, and stabbed the motherboard=dead motherboard) Yeah, I know, I know, lol! :pinch:

  • Like 2

My most expensive mistake at work (i'm a techy) but not entirely down to computers... one of our photocopiers stopped working and throwing errors about waste toner. I popped it open and had a look, found something that looked like waste toner in 4 compartments so i proceeded to empty all 4 of them into a bin, i replaced the units and still wasn't fixed so we called an engineer.. He said 'someone' had emptied the fusing/magnetic something or other material out of each toner unit, which was a costly mistake. It was ?250 per unit and 4 units needed replacing so it cost us ?1000, i seriously thought i was going to lose my job but my manager was understanding. In my defence it's my responsibility when i don't know much about photocopiers at all.

Another costly mistake was not having up to date virus software on all of our machines, we got stund with a dodgy USB disk and it ripped through our network infecting every single PC, it didn't really cost us any money but it certainly took me a long time to fix.

Also when i was just curious as a child i was messing around with the insides of my brand new PC and when re-seating the graphics card i pushed too hard and cracked the motherboard.

I was getting jiggy with an ex-girlfriend. I put candles all over my desk and someone knocked the door. Quickly got dressed, hit the pause button and eject cd button at the same time by accident. Came back up stairs and smelled something odd. Turned out it had melted my cd drive. In a panic, I pushed it back in. By the time it had cooled, I imagine it had basically turned into a glue totally sealing it permanently.

It was an eMac so I was fairly screwed.

Oh also, the first real PC I had which was around 1998 and I was 12. I knew nothing of computers really. Messing around with all the buttons and everything, switched the voltage on the PSU and switched it on. There was a loud bang and a puff of green smoke. I'd been waiting for six months to get it. It was Christmas day and I'd had it for a few hours. I cried like a baby.

-Installed Windows 8 :(

-Volt-modded a Radeon 9500 Pro that died after 6 months on a hot summer day (I still have the bookmark :p http://www.xtremesys...=9500Pro%20volt)

-Thought Windows 8 would be an enhanced, better version of Windows 7

-Chose a Voodoo 3 over a TNT2 when I bought my old P3 550MHz. The Voodoo wasn?t a bad card, but the TNT2 was superior

-****** up the line-in jack of a brand new Xonar Essence STX with a bad connector

-Made an ugly scratch on my screen with a? hard disk :|

-Chose to buy 4 x 1GB of RAM instead of 2 x 2GB on my old system, to save money. A year and a ½ later, I had to buy 4 x 2GB anyway

  • Like 3

Nothing overly dramatic, probably my personal least favorite just because it was my hardware.. had a "derp" moment couple years back, made an ugly short in the eletrical. Figures that I can build hundreds of the things for clients over the past couple decades, and wind up nuking my own.

Dual socket motherboard, probably around $400 or so at the time.

Dual CPU's, maybe $500 for the pair.

That look on my face when I first got a whiff of the blue smoke, priceless.

1. Went to fix YLOD on a playstation, thought I could save time by putting it in the oven for a short while, then forgot about it :(

2. Not locking down USB ports on PC's at work - result over 300 PC's and over 100 touchscreens and server farm infected with a virus. 40 hours straight to fix :( (thankfully production boxes were unix)

3. Vista!!! Nuff said

4. Didn't even put a fan on a cpu on a mates PC on Xmas eve. Phooof!

5. Flashed firmware on my Bluetooth unit in the car, and the car went into eco mode and cut power. fried Eeprom

6. Plugging 240volts into the output of my new UPS units, and tripping out my server room - twice!

I really should re-evalute my job

Almost bricking a Linksys WRT54G-TM Tmobile branded router trying to flash DD-WRT. Turns out the customer's laptop battery was just defunct and luckily Windows gave a battery warning or else it was seconds away from going off mid-flash and I forgot about it yet I MYSELF worked on it hah!

when I was new to computers, I was fascinated with the inner workings of the Bios chip and messed it up. :/ it was a 386 processor.

^ I'm not sure if it could be called a mistake, but I 'bricked' my netbook last year, while trying to Update.

I did eventually figure out how to reflash the BIOS chip. :D

^ I'm not sure if it could be called a mistake, but I 'bricked' my netbook last year, while trying to Update.

I did eventually figure out how to reflash the BIOS chip. :D

lessened learned from that? I took it into a shop and got a new bios put in. I wasn't meant to touch things I had no idea about

Was drinking and listening to my iPod (second generation) when it slipped from my hands and felt... unfortunately, instead of landing on the floor it landed, perfectly, inside of my rum & coke glass!

After all these years, it still feels sticky!

xtw3G.jpg

I did the improbable. Before I knew much about building and repairing computers, I had read somewhere you could make your system faster by installing faster memory. I took some memory a friend of mine had just replaced, which was faster than what I had. I cracked open my case, and popped out the old memory just fine.

I installed one stick and it clicked as I pushed it in and the tabs snapped forward. Good so far. I then installed the other stick which was a little harder to get in. But, with a nice forceful push, I snapped it into place. Put the cover back on the case and tried to boot the machine. The lovely, long, single beep issued from the case speaker and then... I smelled smoke. I panicked, pulled the plug on the machine and opened it back up.

Turns out that I somehow managed to put the memory stick in backwards. I know. I know. The slots shouldn't have even allowed this but I did it. The stick was fried as was that particular channel. Amazingly the board was good and the computer booted up and worked fine with the remaining stick and two of the older ones. I also learned not to mix and match memory after this.

So, it only cost me a channel and a stick of memory. But, anybody that I tell that story to always says, "How the hell did you do that? That's near impossible to do." I am Mr. Impossible.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • NASA: This asteroid may not kill us but it probably won't be far off either by Sayan Sen Image by Zelch Csaba via Pexels New observations by NASA's James Webb Space Telescope have eliminated the last remaining impact threat posed by asteroid 2024 YR4, ruling out the possibility that the near-Earth object could strike the Moon in December 2032. NASA said observations collected by Webb on February 18 and 26, 2026, enabled scientists to refine the asteroid's orbit enough to "rule out a chance of lunar impact on Dec. 22, 2032." Instead, asteroid 2024 YR4 is now expected to pass the Moon at a distance of about 13,200 miles (21,200 km). The agency stressed that the update "reflects improved precision in our understanding of where the asteroid is expected to be in 2032 rather than a shift in its orbital path." The announcement closes a remarkable chapter in planetary defence that began in late 2024, when the approximately 60-metre-wide asteroid briefly became the most closely watched near-Earth object in the world. Discovered on December 27, 2024, by the ATLAS telescope in Chile, 2024 YR4 initially appeared to have a small chance of colliding with Earth on December 22, 2032. As astronomers gathered more observations, the impact probability briefly climbed to around 3%—the highest ever recorded for an asteroid of its size—before steadily falling as its orbit became better understood. By early 2025, international observations had ruled out any significant risk to Earth. However, astronomers were left with another possibility: a roughly 4% chance that the asteroid could instead strike the Moon. "The probability that asteroid 2024 YR4 will strike the Moon on 22 December 2032 is now approximately 4%," the European Space Agency (ESA) had said last year, noting that "there is a 96% chance that the asteroid will not impact the Moon." ESA said such an impact, while unlikely, would have presented an extraordinary scientific opportunity. "It is a very rare event for an asteroid this large to impact the Moon – and it is rarer still that we know about it in advance. The impact would likely be visible from Earth, and so scientists will be very excited by the prospect of observing and analysing it," said Richard Moissl, Head of ESA's Planetary Defence Office. "It would certainly leave a new crater on the surface. However, we wouldn't be able to accurately predict in advance how much material would be thrown into space, or whether any would reach Earth," he added. The asteroid also exposed an important blind spot in planetary defence. Because 2024 YR4 approached Earth from the direction of the Sun, it remained hidden from ground-based telescopes until after its closest approach. "We looked into how Neomir would have performed in this situation, and the simulations surprised even us," Moissl said. "Neomir would have detected asteroid 2024 YR4 about a month earlier than ground-based telescopes did. This would have given astronomers more time to study the asteroid's trajectory and allowed them to much sooner rule out any chance of Earth impact in 2032." He added, "As an infrared telescope, like Webb, Neomir would have also immediately given us a much better estimate for the asteroid's size, which is very important for assessing the significance of the hazard." The latest NASA observations underscore the value of space-based infrared telescopes in tracking faint asteroids. According to NASA, Webb made "among the faintest ever observations of an asteroid," extending the object's observational record by nearly eight months at a time when it had become too faint for other telescopes. That additional data allowed scientists to eliminate the remaining uncertainty surrounding its 2032 flyby. Although asteroid 2024 YR4 is now confirmed to pose no threat to either Earth or the Moon, scientists say its discovery remains one of the most significant real-world tests of the international planetary defence system, demonstrating how continued observations can rapidly transform an object once considered hazardous into one whose future path is known with high confidence. Source: NASA, ESA This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • Yup. Google is just scraping the entire internet for their own ad profits without sharing revenue with the sources. It's obviously stealing, but since these sites depend upon Google's search scraps to survive... As for me, I just stopped using Google for anything except Reddit searches. If Reddit's own search wasn't complete crapola, I'd never use Google search again.
    • I had a feeling this was coming. Picked up my first Mac ever last Saturday. Glad I did.
    • In a major surprise there is actually some good deals for the first time in years. At least for me.
  • Recent Achievements

    • Conversation Starter
      Admir earned a badge
      Conversation Starter
    • First Post
      The_Focal_Point earned a badge
      First Post
    • Apprentice
      daryld went up a rank
      Apprentice
    • Contributor
      Carltonbar went up a rank
      Contributor
    • One Month Later
      The_Focal_Point earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      419
    2. 2
      +Edouard
      170
    3. 3
      PsYcHoKiLLa
      130
    4. 4
      Xenon
      69
    5. 5
      neufuse
      69
  • Tell a friend

    Love Neowin? Tell a friend!