What's the most f-cked up computer bug/glitch you've seen?

[beer]

This one WILL be hard to top.

First, some background:

I am running a Slot A Athlon on a K7 Pro Irongate-based board. I am using a VOS32 heatsink. The K7 Pro supports an "Instant On" feature where the first time you plug everything in, and connect the power, it will start itself up automatically. If it detects a processor, it will immediately power down and will need to be turned on manually. If it can't find a processor, it will power on and all the D-LEDs will be red, and the fans will spin and whatnot.

Now, the bug:

When I first tried to get this system working, I had a lot of problems with everything being connected, and the D-LEDs being red and it not posting. Eventually, I noticed that when I had it like this, there was a little bit of smoke coming from the heatsink.

DOHETH.

The bottom of the heatsink touched the voltage regulator and shorted out the path to the processor. I put some electrical tape on and it worked!

But the electrical tape wore down months ago. Now, whenever I turn my system off, I run the risk of the heatsink falling onto the voltage regulator and the computer turning on w/ the LEDs red and the fans spinning. But, I am assuming, the air pressure from the fans keeps the heatsink over the voltage regulator when it is on, as I have nevr had it mysteriously freeze or something on me when I'm in Windows.

Freaky? You bet. Dangerous? Probably...

 

[Mday]

paulson is the most f-cked up computer bug/glitch i've never seen

 

[damocles]

LOL
The most naff bug i get is the one where my PC crashes when web browsing. Thanks Winme

 

[Monel Funkawitz]

How is turning on the bathroom light and having the 'puter power up?

 

[jonnyGURU]

The most f-cked up computer bug/glitch I've seen is Windows ME.

Doesn't work with on board Trident Blade drivers with any existing drivers, doesn't like many AGP cards in VIA MVP3 chipset boards, in doesn't work with the Rockwell/Connexant modems with any existing drivers..... I'm sure I could go on.

 

[beer]

Somehow these weren't the answers I was loookin for...except the light switch thingy...

 

[SuperGroove]

let me guess Elementa007, you decased your Athlon. I decased mine, and my Alpha P7125 comes close to touching some capacitors. I wish I had a new case! Then I wouldn't have wires pushing my processor eveyr which way. I love the K7PRO though....8.5x112 means GREAT fun

Paul

 

[Pretender]

I couldn't overclock my system to 850 (133fsb/33pci) stablely, but 845 (130/33) worked perfectly fine.

Oh, and when I overclocked my cely 300 to 1.2ghz it opened up a rift in time.

 

[NicColt]

The F9 key in Excell v1.0 would not work. But they released it anyway.

 

[Bryan]

I call it Microsoft Windows

 

[JoLLyRoGer]

Wellll. I built a comp for a friend of mine with a mobo/processor he bought off of a guy at work. The guy had a K7V with a Athlon "Classic" 700 oc'd to 800 w/GFD. Also had updated the bios, and put a password on it too. Obviously I couldn't flash the bios w/o upclocking the L2 cache. Since I didn't have the hack to re-clock the cache back (BTW I'm now much of an overclocker anyway) I had to sit for a couple of hours trying to guess the bios password. I couldn't get a hold of the guy because he was overseas for three mo's. Turned out to be his first name...go figure. Well, that's not all of it. Turns out I get the comp built and I try to install the guy's printer and all the machine will do is try to create files to disk when ever I tried to print something. So I checked out the device mgr. Under System. turns out the computer thinks the ports aren't there. Two mo's later the guy who my friend bought the mobo/CPU off of gets back, so I'm trying to ask him what the F*ck is going on. I takes us both about two weeks to figure this one out, and for all of you really quick people out there, you more than likely already know what the problem was. Yep. That @sshole had disabled the ports in setup to free up resources/memory, and then forgot he had done so. Don't ask me why, he was running 384MB ram on the system when it was his. But anyway, we finally figured it out when we were all having a LAN party over at my friend's place. Sheesh, what a fiasco. But ya know, it always seems to be the most obvious things that get overlooked the most.

Sorry if I've been rambling, it's late and I keep losing my train of thought.

 

[PCAddict]

Years ago when I first started working as a tech, I had a weird case where a customer's accounting software package would not run on any PC with a Seagate hard drive. This was back in the days of DOS. It was driving us nuts. The company I worked for at the time used Seagate drives almost exclusively. His s/w wouldn't run on any of our test-bed systems, or on any of our display models. I ended up figuring it out when I took the program home to my own PC. The only thing I can attribute it to was sloppy programming. Apparently one of the subroutines that accessed the hard drive somehow had a conflict with the Seagate firmware. The program would install and run, but when you went to access the data files on the hard drive it couldn't see them.