Computer does not boot after memory installation
Posted 02 December 2005 - 07:05 AM
Posted 20 December 2005 - 12:11 AM
Great forum you have here. I found this thread because I had *exactly* the same problem as pera. Reading this thread helped me out a bit, so I'd thought I'd share my experience:
My computer/XP was working fine, when I decided to upgrade the RAM. I switched it off, replaced the 2 existing RAM with one 512MB module and restarted. BIOS recognised the 512, but XP wouldn't load and kept giving the blue screen with error DRIVER_IRQL_NOT_LESS_OR_EQUAL, STOP code 0xD1, NTFS.SYS.
So I put in the old RAM modules, and got the same error.
Tried safe mode, last known good config etc. and kept getting the same error.
Then I tried booting from XP CD and going into recovery console - this time a blue screen with a different error DRIVER_CORRUPTED_MMPOOL STOP code 0xD0.
Then tried reinstall XP - blue screen with MMPOOL error.
Then found this thread and thought it might be the HDD, so I tried installing XP on an old HDD and it worked! Then I tried putting the new memory and restarted and got blue screen so I realised the memory wasn't compatible with my motherboard. But this time, when I put the old memory back in XP still loaded ok.
So I tried connecting my original disk as a slave on the primary IDE so that I could access my data - blue screen again. At this point I was pretty sure the disk was totally stuffed. So I took the disk down to the local PC store got them to try to access the disk via an external HDD case with USB adapter. As soon as they turned on the USB adapter, it crashed their PC! So they tried to restart XP and it wouldn't load, even though the disk was just connected through USB! Then they disconnected the disk and XP started fine again.
Anyway, I've bought a new HDD and am currently reinstalling XP. I've given up on trying to recover the data from the old one. Thinking back, I suspect that when I first installed the new RAM I unplugged the wrong power cable, so there was still power going through the motherboard, and this is probably what caused the disk to get damaged? Silly mistake, I should have made sure the little LED on the motherboard had gone out before I started pulling boards...
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users