Welcome to my defrag-safe mode hell

Pictured above is a partial screen shot of the visual that the Windows' Defragger on my Thinkpad T42 is presenting to me right now. I think this is bad.
Written by David Berlind, Inactive on

Pictured above is a partial screen shot of the visual that the Windows' Defragger on my Thinkpad T42 is presenting to me right now. I think this is bad.  In fact, I hope it's bad because maybe by correcting it, I'll correct my system.

This morning, I woke up to hell that's worse than the blue screen of death: a hung system. You know the type: mouse frozen, unresponsive keyboard --- but a very rapidly blinking WiFi interface (why is it that when these things happen, nothing seems to work but the one single thing you most don't want to be working?). There's so much stuff on this system that there's no telling what caused it to hang.  It's something that's been happening all too frequently as of late.  A scan of what's being loaded at bootup (using RUN msconfig) makes me wonder if conflicting drivers are getting loaded just to make Windows a happy camper on the Thinkpad's hardware.  For example, there are at least  : pwrmonit ("Power Monitor," I'm guessing), BMMLREF (something that has to do with IBM's Battery Maximizer), and BatInfEx & BatLogEx (is "Bat" a visual cue that this also has to do with the battery).  Then, there are a bunch of drivers and software that are called during bootup from directories with the word "Thinkpad" in their path, but it's hard to know what exactly they're for or if I can bypass them in hopes of getting the system working again. This has always been a complaint for me. Why can't I right click on any driver file in Windows to find out what happens if I stop loading it. In laymans terms.

Today, the situation got worse because now, the system won't boot either. It booted fine yesterday.  I get to the Windows splash screen, but after that, something goes terribly wrong and the hard drive, which sounds normal up until a point, starts to make a rythmic grinding noise as though it's trying to get at something it just can't get at. I'm convinced that's the problem (does anybody know how to make use of a Windows bootup log to isolate whatever's gumming up the works?) I've spent all morning trying to get to the bottom of the problem with no luck.  So, in hopes that it might magically make my problems go away, I've booted into safe mode and am defragging my hard drive.  To boot into safe mode (if you want to do this), you have to repeatedly hit the F8 key at just the right time when a system is booting up.  Do it too early and you'll get a keyboard error.  Do it too late and your window of opportunity to boot into safe-mode is missed and you have to start over (just what you want to do: constantly power-cycle an already misbehaving system).

Finally, the screent that comes up for me in safe mode is, if you ask me, evidence of a problem unto itself.  At the top of my screen, it says I'm running:

Windows XP Build 2600.xpsp2.050301-1526: Service Pack 1

The "sp2" part supposedly stands for "Service Pack 2".  So, why does it say "Service Pack 1" at the end?

Editorial standards