Generally these types of errors are caused by faulty ram chips or bad 
connections in the ram slots. Take the ram modules out and clean the 
connections. Make sure they are firmly seated. If there is more than one ram 
module, try each one separately. It might be a module or a slot that is 
causing the problems.
Terry

"Graham Butcher" <graham.butcher@dsl.pipex.com> wrote in message 
news:I-KdnbCKktBRpC3enZ2dnUVZ8qadnZ2d@pipex.net...
>
> I have just aquired a SP6000 which had a faulty screen at first. After 
> re-installing Windows XP Pro it worked fine all day but after switching 
> off for the night it developed a fault.
>
>
>
> Now when switching on it gives the following report, "File ntkrnlmp.exe 
> could not be loaded, the error code is 7 (sometimes the code is 14 or 4). 
> Setup cannot continue. Press any key to exit.
>
>
>
> Sometimes on trying to boot I get a message that reads, Windows cannot 
> start because the following file is missing or corrupt, 
> "System32\Drivers\PCI.SYS . You can attempt to repair this file by 
> starting window set-up  using the original setup CD-ROM.
>
> Select 'r' at the first screen to start repair.
>
>
>
> Using the windows XP disc and slecting boot from CD, the system starts to 
> run and then fails with the following message, Windows could not start 
> because of an error in the software. Please report this problem as "load 
> needed DLLs for Kernal" Please contact your support person to report this 
> problem.
>
>
>
> On other occasions it will boot up perfectly and on others I get a report 
> about some media failed test, check cable, and it will then go onto boot 
> OK.
>
>
>
> Any help in pin pointing the problem would be greatly appreaciated.
>
>
>
> Thanks, Graham
>
>
>