Archived from groups: comp.sys.laptops (
More info?)
On 28 Jan 2005 14:03:48 -0800, mike_ferenduros@hotmail.com (Mike
Ferenduros) wrote:
>My thinkpad a31p has started freezing regularly, usually within 10
>minutes of booting windows2000 / linux. It also occasionally fails to
>get to the POST screen; it powers on but the screen stays blank and
>there's no HDD activity. I dropped it around a year ago, cracking the
>case a little, but it still worked 100% until a week or so ago.
>
>Things I've tried:
> - Removing the ethernet, wifi and bluetooth cards (no change)
> - Removing the DVD drive (no change)
> - memtest86 (no errors found)
> - PC doctor (no errors found)
> - Moving the memory to the other slot (no change)
> - Taking it apart and looking for damage (none found)
> - Turning graphcs acceleration to minimum in windows (no change)
> - Switching off HDD DMA and write-buffering in windows (no change)
> - Fiddling with the BIOS (no change)
> - Monitoring the CPU temperature (45c when it hangs)
> - Shaking it to see if that triggers a hang (it doesn't)
>
>The laptop is perfectly functional until it hangs. Oddly, neither PC
>Doctor nor memtest86 hang however long I let them run.
>
>Can anyone suggest anything else I can try? I'm tearing my hair out
>here.
Same thing happen to me for 3 weeks now, with my more than 4 years old
A20P running Win2000. I thought it was the heat build up, now all the
bottom covers are removed. The memory chip don't seem to sit to well
I thought, swop them, use just one, try the other. Swop with
different harddisks, including the one in the ultrabay. Still did not
start. Did all sorts of things to coax the bugger to start, that
work, but only for a few times. Took out the cmos battery, make it
forget what the last boot config was, the bloody thing seems to know I
was trying to trick it. I did realise that when I manage to boot up
sometimes, the ultrabay drive gave more info, like the registry was
not there, must have got wipe out when it went down.
Well, it is working now, but don't know for how long. What I did was
use PartitionMagic to copy the a working Win2000 partition from one
disk to another and boot it up from there. I find using the recovery
CD does not work too well when there are multiple partitions on the
harddisk. It does not install full because the process creates a
temporary drive and the poor guy got confuse with the drive letters
and and not know what to do properly on reboot. When the system
finally startup I send it into config mode, change the quick boot
option into diagnostics. I think I might have found the problem,
fingers crossed for now. This time it showed the 2 memory dimm did
not verify correctly, quick boot shows nothing of this sort. My guess
is when it did run, the memory checksum failed after some time,
hanging the system. Very trickly, because you can never tell what the
system was doing when it died and on one occasion, it wipe out some of
the files and some files did not close properly.
So I will be sending it to the workshop next month when I return from
my break, maybe the thermal rubber is wearing out and retaining heat,
and also seriously looking at a Dell, eg. the Inspiron 6000.