Happy 4th everybody!
Well, over a month later and this piece of crap STILL is not fixed. It's taken awhile because I've been in the middle of moving, they sent an empty return box to my former address which got delayed so I wasn't there to pick it up (out of state move) and I just didn't feel like dealing with it until an IBM rep called me a few weeks later. Anyways....
3 times this POS has been sent back to IBM now, and 3 times has been returned not quite in full 100% working order. Just to recap...
- was originally sent new HD, but had no image, and I had no recovery CDs
- was sent recovery CDs, and got the error in the title of this thread
- was sent another recovery CD set, and same deal
- returned laptop, was sent back with new motherboard and BIOS still with no image, would not even boot!
- returned laptop again, was properly imaged, but did nothing but crash and bluescreen
- returned again, now no Windoze BSODs (yet) but apps still crash left and right.
The repair depot manager supposedly oversaw repair of this thing the last time, and they've put about 3 new motherboards in it from what I can tell, but it's still not working. It does work "somewhat" this time and at least you can get into windows for now, but everything just crashes sooner or later. Internet Explorer crashed the first time I loaded it. Firefox crashes all the time. On boot I get a windows service pack has encountered an error message most of the time. I also get corrupt file warnings when extracting zips that work perfectly fine on my other laptop. I could not install the java runtime environment from a known good zip for example, and had to download a new one which also had "corrupt" files. yeah right... My favorite was when I tried to load firefox and it didn't run so I went into the taskmanager to see if it was there and try to end task it. The freakin Task Manager crashed, and then the Dr Watson postmortem crash analyzer or something crashed trying to analyze the Task manager crash! Occasionally apps will hang at 100% CPU utilization and normally an end task in tskmgr will fix that, but not anymore - they just hang and the only way to fix it is to reboot. Last night it hung on shut down also and I had to force a shutdown by holding the power key for 10 secs. LOL
After 3+ new motherboards and still having the same trouble, I'd have to say that obviously the motherboards aren't the problem and that it's something in the chassis itself. I have no clue how these things are constructed internally, but maybe there's some sort of grounding fault, EMI issue, or other electrical issue within the chassis itself that causes this sort of nonsense. The only way to "fix" it is to just give me a whole new laptop!
So anyways, this piece of crap is just completely hosed. IBM can't fix it, their stupid recovery CDs don't work, and I'm demanding a new laptop once again. I'm typing on it now through firefox, but it's only a matter of time before Firefox crashes, again. This laptop has been well cared for, has never been dropped, abused, or had anything spilled on it and this has just been a total let down.
Now here is something I noticed way back, like a year ago. When I first got this thing, the system current while using the laptop in the most conservative energy mode was about 0.68-0.73A. As time went on I noticed that it would never really go down below 1.00A and that's about the time I started having weird crashes. Maybe there's something weird in the chassis causing something to short or at least draw high current that causes a brown out sort of situation and then memory read/write errors and lots of crashing.

Anyways, it's still drawing 1.00+A at all times and never goes down into the low sub-1.0A range even right now. If I knew what a "normal" T42 motherboard was supposed to look like on a thermal imager cam, I could take this piece of crap into work and point our thermal cam at it and see if I could find an abnormally hot part to track down the problem, but since it's under warranty this is IBM's problem and not mine. I'm just tired of dealing with this...
/rant again