R40 "Bad Pool Header" error upon resume from suspend

I have a Thinkpad R40 that crashes with a "bad pool header" error when it resumes from suspend. I've run advanced diagnostics on the RAM and hard drive and both test as good. I haven't been able to find much on the error online, so I'm hoping someone here can clue me in on what else to look at.

 

how about a little more info on your machin, OS.

i guess your error is the stop 0x19 error.

here is a list of the windows stop errors :
http://msdn.microsoft.com/en-us/library/ms793223.aspx

please post the exact stop error message. maybe we can find something in there.

 

It's got a Pentium-M with an Intel 802.11B card (Centrino) running Windows XP SP2. It has two RAM chips installed, both of which test as good.

The error signature is as follows:

BCCode: 19 BCP1:00000020 BCP2:8253A7B8 BCP3:8253A7D8 BCP4: 1A040002

 

have you tried disabling audio,wifi,lan,bluetooth,cardreader...? see if it is a driver related problem.
since this stop0x19 error is mostly related to badly programmed drivers, you might wanna try this first.

please try disabling the hardware, that you do not necessarily need for running the OS. try suspend again , and see if it works now.

if it does, you might consider finding the culprit by switching on one device, see if the error returns or not. when it comes back after enabling a certain device, you may have found the culprit.

a newer driver for that device may solve your problem.

 

I'm thinking right now that it is a driver, because the machine will go into and resume from suspend properly from the XP logon screen. I'm going to look at the major drivers and see if anything has changed recently.

Update: I have a possible bad RAM slot. If I pull one chip the system boots, but with both chips in the system will not boot. I think I may have found the problem.

 

try wifi,lan and audio first. wifi seems to be making quite a lot problems.

 

WLAN drivers turned out to be the problem. Upgraded them and now no more BSOD.

 

glad you got it sorted.

somehow wlan turns out to be a troublemaker.