I am in desperate need of help!!! I have a 2.0 GHz HP Pav 780c, Award BIOS, 80 Gig Seagate HD, running XP Pro. Here's the situation: My computer froze during a defrag. I rebooted. Bam! Endless loop. It hung at the agp440.sys point, which I found out by trying to start in Safe mode. (I realize this file may not be the actual problem, it just happens to freeze there." I have tried running the recovery console from the XP Pro disk and it doesn't work. It gets to the point where it is "Examing..." the HD and it goes into a loop and hangs. I then installed XP Pro on another HD, disconnected the first one, installed the new one, rebooted...everything worked perfectly. (It's what I'm using now...) (I was hoping I could access the old HD from the new HD in order to recover files, make repairs, etc.) If I connect the old HD and the new HD up at the same time, it hangs. I changed the boot.ini file on the new HD to include an option for booting from the old HD. (I was pretty sure that wouldn't work though, considering I couldn't access/make changes to the old HD's files.) When I boot up and select the old HD as the boot option it gives me an error having to do with a HAL dll. If I select the new HD as the boot option, it hangs. Both HD's use the NTFS file system. I've tried booting with a win 9x disk but I still can't access the drive. I've been searching for a solution for a week now. It seems that a "agp440.sys" problem can be caused by a variety of things, and that there is no single solution. Some posts say it's a problem with the BIOS and such, but in my case, how can that be considering everything works fine when I use (only) the new HD? I'm really stumped here. I would greatly appreciate any help!! D.

The LastKnownGood configuration can be used if the default configuration has been damaged by the installation of a device driver for a device that is not digitally signed and/or is not on the Windows Hardware Compatibility List. When you boot into the LastKnownGood configuration, the kernel copies the system information from the CurrentControlSet to the Clone Control Set. Once the system has successfully booted and the administrator has logged on to the system, the information in the Clone Control Set is copied into the LastKnownGood pointer. Using the LastKnownGood configuration to boot the computer Shut down the computer before you log on. This is extremely important, why? If you log on, the system will save this configuration. Remembering that you have started the system and it is damaged, youwill be saving a damaged configuration. Not a good proceedure. Restart the system. When you are prompted by the Boot.ini file to select the operating system that you want to boot into, press the F8 key. On the Windows XP Advanced Options menu, using the down arrow, select Last Known Good Configuration. Press Enter. Select the operating system for which you want to use the LastKnownGood configuration. Press Enter. The LastKnownGood is copied to the default configuration and the default pointer, and your system will start up the next time that you boot the system. When to use the LastKnownGood If you install a new device driver and Windows XP Professional will not start, follow the above procedure. The LastKnownGood configuration doesn’t contain any reference to the errant driver. Another reason you would want to use the LastKnownGood is when you accidentally disable a driver eg a system drive, that is critical to the proper function of you system. If this happens, use the LastKnownGood configuration during the startup of your system. When not to use the LastKnownGood The LastKnownGood will be of help to you only if there has been a change to the configuration of the system and the change has caused a problem. That is it. If the problem has nothing to do with the configuration of the system, then LastKnownGood will be of no help to you. If you have a problem with hardware failure, missing files, or corrupted files, then the LastKnownGood will not correct them.

The LastKnownGood option was the first thing I tried.