While athletes might worry about the kiss of death, for Windows users its the BSOD that strikes fear into your heart. When it happens, you immediately begin to pray – which might be a good thing. You remember all the recent work that you’ve done and how you meant to back it up and, if only given the chance, you promise yourself you’ll turn over a new leaf and backup regularly – if only you can resolve whatever is causing this BSOD!
Of course, it was on my wife’s laptop.
All kinds of jokes come to mind at this point. (“If Momma ain’t happy, …” etc.) But the truth is, I’d be in more of a fix but less concerned if it hit one of my research machines. I just want Becky’s things to work. It’s how she communicates with the family, with a special relative/friend in Arizona, etc. – cutting that off is worse than me losing temporary access to my research data.
The Dell Inspiron 1100 had been giving warnings over the last few weeks, rather like a volcano getting ready to blow. You’ve seen the movies – the ground starts to raise 1/4″ over a 500 mile radius, Old Faithful slows down (or speeds up, depending upon the movie), fissures open in the Marianas Trench. And so Kokochinski (Becky’s laptop) first began to show signs of slowing. Then came the heat – the fan was running all of the time. (Those should be clear clues to any geek.) I kept putting off looking at it because I “just didn’t have the time right now” and then it happened: the first BSOD.
You always hope that the first BSOD is an outlier. And, in fact, it may be a long time between it and then next, but there’s always a next. And the dump info, if there is any on the screen along with the hated blue background, is seldom useful. I mean, it could really be that one of your drivers took a left turn or dropped a bit, but it could also be (as was in this case) that some poor devil of a routine was randomly selected to be the object of ire for the real culprit. A random crime.
I think the first BSOD hit last Wednesday or Thursday. By Friday there were several more and Becky gave up trying to pretend that it wouldn’t hit before she got the next email sent. Have you ever written a long email to a friend, knowing that the next keystroke could be your last? It’s not the kind of environment to produce transparency and scintillating openness, let alone long emails.
Saturday morning I began where every wife’s geek husband begins: return to the scene of the crime. Turn on the machine, wait a few minutes. Sure enough, that’s what a BSOD looks like. And then you reboot the machine. And sure enough, that’s what another BSOD looks like. More prayer.
Well, let’s see what we know. Inspiron’s collect dust in that little copper device connected to the P4 processor that’s supposed to be responsible for keeping the little bugger cool. Take off a bunch of little screws: off comes the keyboard, screen, fan guard, video processor heat sink, video processor, another heat sink and … what are those 200 pins sticking out of the bottom of the heat sink for? Oh yeah, that’s the processor … forgot. Gee, the fins in the copper heat sink look so clear, that can’t be the problem. Put it all back together – oh yeah, and realize that half the stuff you took off could have stayed on in the first place. (But this insight will pay dividends, because you are about to repeat this process about 5 times. Of course, you don’t know that at this point and so the fact that you won’t need to take it all apart again is at this point no consolation.)
This is getting much too long, so let’s cut to the chase.
The second time you take it apart you discover that all the dust on the fins is on the INSIDE of the heat sink – and there is a lot of it. It’s amazing that any heat escaped by way of the fins at all. Melted solids would have been more likely. But when it is all back together there are more BSOD’s. Check the internet – sure enough, heat sink connections some times dry out and need to be reestablished. (Becky ran to town and got the new tube of heat sink paste for me.) You resink the video processor, but the P4 seems tight still. Well, you’ve had 5 hours of fun so far – enough for one weekend.
By the following Wednesday you’ve spent some more time online and discovered that memory problems produce the same kind of random BSOD’s. Download memtest86+ and run it, one memory module at a time. The two original 128M’s seem fine, but the “new” Black Diamond memory (512M) that is a year old throws some errors on the screen. (Did it get “cooked” when system temp was too high?) Run without the 512M module and things seem stable. What do you know about that?!
Becky’s had 3 uninterrupted hours of internet email and browsing. Well, there have been a few phone calls and the call of the current book, but no BSOD interruptions. Even if I thought the 512M memory might be okay, it’s hard to argue with experience. Leave it out and the thing works. I’ll probably run memtest86+ all night on the 512M module, but even if there are no errors, I think I’ll take it out of the laptop for the last time tomorrow morning.
Recent Comments