Slashdot Mirror
Lessons In Hardware / OS Troubleshooting
Esther Schindler writes "We like to imagine that every Microsoft OS installation will work just as well as the company promises. When things don't work out, identifying and remedying the case of failure can be time-consuming and frustrating. This lesson in how to determine why Windows 7 didn't install may help you troubleshoot a problem of your own, and save you from a Lost Weekend. Maybe you'll find this account useful all on its own. But the real key here is that the author is Ed Tittel — who's written over 100 books. If this hardware geek spends days solving a CPU-meets-Windows 7 problem, what chance do mere mortals have?"
I'm a little suspicious; how much of an expert can you be writing 100 books on a variety of subjects.
.net development classes, php, etc..... Yeah he couldn't answer any basic questions that strayed from the text book in front of us.
Reminds me of a tech instructor I had who proudly informed the class he teaches oracle classes, mysql classes, sql server classes, cisco classes, juniper classes,
If you have never had a hardware issue when installing Linux on a machine you must be very lucky.
"Most things work fine" people tell me, which is true. The trouble is that the chances of you owning something that doesn't work is relatively high. (There's probably something from my statistics course that explains why that is, but I have so far managed to suppress that memory.)
After having rebuilt a Mac with OS X, and rebuilt a laptop with Ubuntu 9.04, I was surprised at how smooth and the Ubuntu install was. Of course that was until I wanted to use my webcam with Ubuntu. These kinds of problems get very difficult very fast in Linux. When 9.04 first came out there was a dependency problem that meant that you couldn't easily get some webcams working.
To be fair, that problem is most likely sorted out now, and a non-Apple webcam would have needed a (very easy to install) driver on OS X as well. The point is, Windows and hardware generally work very well.
Actually I had the exact same problem a few months ago upgrading a Dell server from Win2003 x86 to Win2008 x64, I suspected the CPU from the beginning, but I spent a few hours before the Dell Tech agreed with me. They sent a replacement and it worked like a champ.
This proves it has happened to a production Intel Core2Duo CPU at least once, I can't believe I was the only one.
iRepairIT - iPhone, Mac, & PC Repair
I temper this approach with the "this is easy as hell and very quick". So even if I think it is something, if there is something else it could be that's really quick to try I'll ignore my "brilliance" and try that. What is amazing is how often there isn't actually one problem, but two. Also helps if you have a similar working system that you can take the components from (so you know that this or that doodah actually works).
Just last night I fixed my parents computer in one of those long fixes that turns out to be the most fundamentally trivial things. This is why this is not my main occupation.
Basicly they had a reccently built custom Windows 7 + Ubuntu PC that had begun randomly shutting down, often minutes after it had been powered up.
Ok first thing, any obvious errors or cicumstances? No, it would just randomly power off. Windows event logs showed kernel power events, no specific driver, service or app crashing anywhere. Linux was the same. Not a thermal issue cpu + gpu temps nominal and stress test din't immediatley cause a crash.
Suspecting a power or a motherboard issue, first checked and re-seated things internally. It still occured.
Removed extraneous cards, connectors and drives. No result. It would even happen sitting in BIOS setup. Have ruled out a number of problems.
Checked for electrical shorts, poor voltage etc.
Dying power supply? Overloading or shorting? Nope, all voltages nominal, and it was brand new.
I was about to try a spare power supply and a thought occured to me..
It's almost as if the reset switch was being hit, but it wasn't even close to being knocked at any point and the switch otherwise worked fine. Then I knocked the case and the system reset. Yep, the reset switch was faulty, jolting it even slightly would reset. Who needs a reset switch since Vista anyway? Unplugged it from mainboard. Solved.
I decided not to even joke about charging my Dad for two hours of my time.
Chances are if he paid someone to do it they wouldn't necessarily have found the fault that quickly, and he'd be hundreds of dollars out of pocket.
The lesson in troubleshooting? Um... I'm not sure.
After logging in slashdot still does not take you back to the page you were on. It's been that way for 20 years.
..a clue about how computers work. Even experienced windows professionals.
I mean this guy has 32 bit OS working and moves to 64 bit OS...am I following this ok. The 32 bit install presumably went well on the hardware and the 64 bit install fails.
So I grok his first attempts which are replacing the install media once. Seems like a reasonable assumption (some bit out of the billions on the DVD image just happened to be flipped the wrong way). From there though he starts to lose me. The motherboard is perhaps plausible but you would have to be assuming some rather significant difference in hardware support between the 64bit and 32bit systems. From there? RAM is 64bit how? Or even my HD?
I think the most significant thing to learn here is twofold.
i) People - even experienced computer professionals - treat computers like they are magic. Like there is no real science behind how they work. Clearly this guy was replacing parts based on some "experiential weighted average" with regard to how likely they are to cause a "weird" problem.
ii) When A. C. Doyle said "When you have excluded the impossible" he neglected to state that the *order* in which one does so is significant. Eliminating things in order of their apparent relation to the problem (i.e. all the things for which 64 bits makes a difference) and (in a business environment) with respect to cost (i.e. Replacing a CPU is often a cheaper test than replacing a motherboard wrt labour) will likely fix your problem sooner than just going for the "usual suspects".
Aside: I've had two cases where I found a CPU issue. One was very similar to this - crashing during a Windows 2000 install - often at the same place. The problem I had was actually thermal - the heatsink was reversed leaving the thermal patch making minimal contact with the heat spreader. Somehow I figured that out without replacing everything else first.