T42p: Expansion Memory burned out on upgrade to 2 GB RAM?

[unitedunited]

T42p: Expansion Memory burned out on upgrade to 2 GB RAM?

A few weeks ago, my T42p had a case of repeated stop errors (blue screen of death). I intially thought the problem was due to Access Connections 4.12, and was back to normal after I removed it. A week or so later I had the same problem. This time I suspected the problem was a bad driver loading at startup so I ran a registry cleaner and the problem seemed to disappear again for about 10 days. It came back in a big way yesterday. This time I can't even get into windows because, the error message tells me, of a corrupted Config.sys file.

Booting in DOS, I ran PCDoctor's full memory test (before I had only run a quick one along with the full battery). It failed my 2nd memory socket (the expansion board) by noting an error in DIMM2. A second run of this test also failed, noting the error in DIMM2 a different location. Chkdsk and a surface read scan of the HD were OK. So it seems as though my expansion memory is toasted.

I have a Crucial 1GB DDR Memory PC2700 333Mhz 200-pin SODIMM (crucial part # 103534) in my underside expansion slot. I bought and installed this back in Feb. after researching the compatibility on lenovo's web site and under the supervision of our IT guru (who had recommended crucial as a good brand). Iit has given me no problems until now.

so my questions are:

-Did I miss something and somehow install less than fully compatible memory? My research indicated I had picked the right module, but I now notice that crucial's web site lists upgrades only for the T42p 2373 and 2378 models (mine is a 2374). Could this mean anything?

-Could physical issues be to blame? Both of my last stop-error-fests occured on booting up at a library following a bus and subway journey. Of course I carry my TP in a padded case and try to keep it unjostled, but the streets of new york are fierce (and the shock absorbers of the buses are not). Or might I have overheated the TP by keeping it in its case on standby?

I am going to be removing the expansion memory and will probably have to roll back to factory settings, I guess, to get working again. I really do use the 2GB of RAM because I tend to run a lot of memory-intensive applications, often simultaneously, so any thoughts on how I might fix/avoid this problem in the future would be greatly appreciated.

Thanks,
uu

[egibbs]

Have you tried just reseating it?

Ed Gibbs

[unitedunited]

I did, and no dice. but since my config.sys file is now screwed, I'm not sure that means anything--I should have tried that from the get go. I think I will have to restore the factory settings without the expansion module, anyway, just to eliminate that as a source of problem, then reinstall when I get a replacement from crucial.

[ballestplaya]

If you have a regular windows xp pro sp2 disk (oem/retail) you can acutally do a repair which should replace the file you missing without deleting any of your files/programs

[unitedunited]

I wish... my TP was bought through my school and didn't come with a WinXP disk. It would be nice if IBM rescue and recovery had a similar utility, or an option to just restore certain files (like config.sys) but it doesn't seem to.

[unitedunited]

egibbs:

I reseated again, still get corrupted config/system file error and can't boot windows, but now it does pass the memory test in PC doctor. Do TP's have a track record of expansion memory coming loose in the socket?

[christopher_wolf]

egibbs:

I reseated again, still get corrupted config/system file error and can't boot windows, but now it does pass the memory test in PC doctor. Do TP's have a track record of expansion memory coming loose in the socket?

Not that I know of; the only counter-example of which was on the early revision T30s and IBM went to the trouble of fixing the hardware problem for the affected users.

[unitedunited]

i guess i'll just have to send the module back to crucial and hope that does it. thanks for the help!