Pci.sys Error - Toshiba Satellite Pro 4600
-
Pci.sys Error - Toshiba Satellite Pro 4600
I have recently experienced a problem with my Toshiba Satellite Pro 4600 running XP. Yes, I know it is getting on abit and is abit slow at only 700mhz, but it is all I have!
Basically, I suddenly got the blue screen of death when I moved my laptop. I rebooted it, and then got a message saying that the pci.sys file might be miising or corrupt. Windows gave me instructions to go into recovery mode and repair this problem. Alas the recovery mode kept coming up with an error.
I eventually diagnosed a faulty ram slot. I removed one of the 256mb of ram from slot b, and the computer works fine. I put the removed ram into slot a, and it worked fine. I put the original 128mb ram in slot b, and it crashed. So I assume that there is nothing wrong with the ram, but there is a fault with the slot. My computer has been running fine for about a year with the two slots full. It also seemed to be intermitent aswell. Sometimes it would boot fine with both slots full, sometimes it would crash when the pc was moved, or if the slot cover was touched.
I have since reformatted the hard drive, and reinstalled windows, but this failed to correct the problem.
Has anyone got an idea what the exact problem is, and how much they would estimate it would cost to repair?
Many thanks
Pacuk01
-
Try cleaning the RAM module contacts with... ethyl... I forget, an electrical cleaner - or a damp cloth -Let em dry though!
I got some dust in mine and it burnt out the connect tracks!
Maybe time for new RAM?
BTW I dream of 700Mhz... I'm sad like that.
-
FORGOT - checl all cards modules leads etc sre fitted snug.
-
I have the same problem although I don't get an error message but the memory in slot B simply doesn't get recognized. I don't think it's to do with the connection as my module had never been out of the slot and the cover had always been safely shut. I've read in another thread elsewhere that this is a fairly common problem that it can only be solved by replacing the motherboard. Is it possible that there is a simpler solution? Can the problem be more closely diagnosed?
Rubie
-