Mini-Rant: Worst day of working on computers/working ever, and then some.

GT1999

Diamond Member
Oct 10, 1999
5,261
1
71
(Since this is more of a story of what I went through, and not really a problem anymore since I know what the problems are, I'm posting it here in OT)

A friend asks for a favor from me, to build a computer for a friend of his before he goes off to college. He can't finish the job because he's off at Purdue. No problem I say, since this friend has done a lot for helping me out in the past. Guy (who wants his computer built) rings doorbell of my house 10:30 PM last night, I tell him just bring the computer parts into where I work and I should be able to assemble it there. I had permission from work and things like that happen all the time where I work (ISP technical support). Guy brings computer stuff into my work -- I tell him I'll call him when it's done. Switching between tech support calls and building a computer (usually at the same time) isn't very fun, but I managed to get everything together. I've built many computers before so it was a snap. Turn it on -- the fans spin (CPU, PSU, intake), but that's it. I check the connectors from the case -> motherboard. Everything checks out fine. (1-2 hours of troubleshooting while taking tech calls). *Important part* Eventually I get frustrated and despite my conclusion that it's the motherboard, I decide to test the processor from the tech workstation I sit at into this guy's motherboard to see what the results will be. It still doesn't POST with the working tech machine processor. So, I'm almost positive it was the motherboard, then. Alright, so he got a bad motherboard, problem solved. Now, let's put that tech machine's processor and everything back...

Putting the tech workstation back together, I used a couple more screws onto the mobo since it needed it (only 4 screws were keeping the motherboard on the case!). Power it up, nada. Nothing. Alright, so I unscrewed everything, it's barebones, took off the ATX power connector, reconnected it, etc. It still won't turn in. So, not only does the person's computer I'm supposed to work on NOT post (the fans just spin), but the workstation I normally sit at, our 3rd tech computer, doesn't work anymore at _all_. So, I take a power supply from another computer and hook it up to the workstation hoping it might've just been a power supply/connector problem. Nope. It won't turn on.

I must've checked all the cables and rescrewed everything on the workstation's motherboard/connections in about 10 times before I drove back home with my blood pressure rising and completely stressed out. I have to work tomorrow @ 10AM with another tech and receptionist and still try to get the tech workstation to work, while explaining to this guy that most likely his mobo is shot, even though it's brand spankin' new. I'm sure I must've stressed the motherboard on that tech machine some when screwing stuff in so I know that's most likely what the problem was, I broke the damn motherboard.

Anyway, if you don't have to fix something.. don't touch it. That's the moral of this story. Thankfully I'm sure my boss will understand, and I probably won't even have to pay for the replacement parts, though I will state that in the email I send off tomorrow to her (if I can't fix it).

And yes, I'm a dumbass. Out of the 2-or-so-dozen computers I've built, today (specifically this afternoon/tonight) has to be the worst night working with computers for me.. EVER.

Another moral.. I worked over 45 hours this week at work. For technical support for customers who don't know how to use the Internet, and most of them even use their damn computer, along with this stuff, is enough to drive anyone insane. Working there for 3 years and going this this stuff all that time doesn't help much, either.

Yeah, I think this qualifies as my first rant, eh?

:(
 

wyvrn

Lifer
Feb 15, 2000
10,074
0
0
Been there. Its a relatively thankless job with buttloads of stress. One of my bosses once told me its considered the second highest stress job, behind air traffic controllers. Don't know where he got that statistic, though. Anyway, thats why I don't do tech support anymore :)
 

MrCodeDude

Lifer
Jun 23, 2001
13,674
1
76
That happend to me once. Well, accept the test machine worked, but would not post at 133MHz FSB like before :(
-- mrcodedude