XP won't boot, hangs up at AGP440.sys

  • Thread starter Thread starter billhickle
  • Start date Start date
B

billhickle

I just built a new computer, with all new parts except the hard drive
and cd drives. More exact specifications are: ABIT UL-8 motherboard,
XFX Geforce 6200 graphics card, AMD Athlon 3200+ processor, 1 1gb stick
of Ultra PC3200 ram, Ultra V-Series 350 Watt power supply, Seagate 20gb
hard drive(with windows XP Pro installed on it), Maxtor 120gb hard
drive(with lots of data on it), Samsung CD-RW drive. The hard drive I
used already had XP pro on it, but wouldn't boot up in the new
computer. So...I did a repair installation, but now, when I boot up,
it shows the XP loading screen for a while, then gives a blue screen
with this error message:
-------------------------------------------------------------------------------------------------------------------------------------
A problem has been detected and Windows has been shut down to prevent
damage to your computer.

If this is the first time you've seen this stop error screen, restart
your computer. If this screen appears again, follow these steps:

Check to be sure you have adequate disk space. If a driver is
identified in the stop message, disable the driver or check with the
manufacturer for updates. Try changing video adapters.

Check with your hardware vendor for any BIOS updates. Disable BIOS
memory options such as caching or shadowing. If you need to use safe
mode to remove or disable components, restart your computer, press F8
to select advance startup options, and then select safe mode.

Technical information:

***STOP: 0x0000007E (0xC0000005, 0xF79BF750, 0xF7C4A454, 0xF7C4A154)
--------------------------------------------------------------------------------------------------------------------------------------

Then, if I try to start it in safe mode, it hangs up on AGP440.sys,
then eventually gives me the same message.
However, this is all just in the new computer. If I put the hard drive
back in the old computer(which has a PCI video card), everything works
fine. Is there something I can do to that file to make it boot right?
Another thought I had was to install Windows on the Maxtor 120 gig hard
drive, then hook up the smaller hard drive as a slave drive and pull
the correct AGP440.sys file from the big drive and stick it in place of
the one on the small drive. Any thoughts?
 
It souds to me like the video card itself is causing the problem. The
first thing I look at with a video card problem is IRQ conflicts. Your
motherboard should have an IRQ map in the manual, check that the video
gard AGP slot is not conflicting with another PCI card. You may also
check the voltage settings on that AGP slot, make sure that they match
the requirements for the card. It looks like the card should be
supported by the mobo, however. You need to make sure that the AGP slot
is on its own IRQ, and doesn't share with other devices, especially
with sound cards and hard drive controllers.

The reason that the system boots fine with a PCI card is that the
AGP440 file is not accessed, but in order to determine that you have a
bad AGP file is to install a different AGP card in the system and see
if they have the same problem.

The next step would be to install the AGP card, but remove all other
cards from the mobo and see if there is a problem then. I am not sure
about nVidia cards, but I know that some of the ATI cards pull off the
power supply, you might check that the connection there, if there is
one, is good, and then also make an estimation of the power draw from
your power supply. I usually try to have at least 100 watts in excess
of estimation, but I run a 400 watt with both AGP and video PCI cards
pulling from the power supply, so you should be fine with a 350.

I hope this helps!
 
Thanks, but, it only boots on the old computer, and the only hardware
that is the same is the hard drive. I tried booting the new computer
up with an AGP graphics card and with a PCI card, with the same results
both times.
 
I had this problem and it came down to the chipset on the motherboard. I
changed from an Intel based system to a Via chipset based m/b with trying to
use the same HD from the old computer. Put the HD back in the old computer
and un-install the IDE controllers and then put it into the new system and
load up your chipset drivers from your m/b disk. Hope this works, it was a
headache for me to figure out.
 
The last file you see on the screen is the last file that loaded
successfully. It is the file after, the one you don't see, that is causing
the system hang. Because the system has been stopped at this point, there is
no mention of the file that is causing the conflict.

Remove ALL hardware from your computer. You will want your video card and
monitor connected. You want only the primary IDE drive connected (jumpered
as a single drive or master without a slave). You will want the mouse and
keyboard connected. You will want the CD drive connected. Nothing else.

Now, run a repair install again. Are you successful. If so, reinstall your
motherboard drivers and video drivers. Reboot as necessary. Still working?
Good. Now install your other hardware and their associated drivers, one
device at a time. Reboot after each install is complete. Keep going till you
find the one that is causing the system to hang.

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!
 
I just built a new computer, with all new parts except the hard drive
and cd drives. More exact specifications are: ABIT UL-8 motherboard,
XFX Geforce 6200 graphics card, AMD Athlon 3200+ processor, 1 1gb stick
of Ultra PC3200 ram, Ultra V-Series 350 Watt power supply, Seagate 20gb
hard drive(with windows XP Pro installed on it), Maxtor 120gb hard
drive(with lots of data on it), Samsung CD-RW drive. The hard drive I
used already had XP pro on it, but wouldn't boot up in the new
computer. So...I did a repair installation, but now, when I boot up,
it shows the XP loading screen for a while, then gives a blue screen
with this error message:
-------------------------------------------------------------------------------------------------------------------------------------
A problem has been detected and Windows has been shut down to prevent
damage to your computer.

If this is the first time you've seen this stop error screen, restart
your computer. If this screen appears again, follow these steps:

Check to be sure you have adequate disk space. If a driver is
identified in the stop message, disable the driver or check with the
manufacturer for updates. Try changing video adapters.

Check with your hardware vendor for any BIOS updates. Disable BIOS
memory options such as caching or shadowing. If you need to use safe
mode to remove or disable components, restart your computer, press F8
to select advance startup options, and then select safe mode.

Technical information:

***STOP: 0x0000007E (0xC0000005, 0xF79BF750, 0xF7C4A454, 0xF7C4A154)
--------------------------------------------------------------------------------------------------------------------------------------

Then, if I try to start it in safe mode, it hangs up on AGP440.sys,
then eventually gives me the same message.
However, this is all just in the new computer. If I put the hard drive
back in the old computer(which has a PCI video card), everything works
fine. Is there something I can do to that file to make it boot right?
Another thought I had was to install Windows on the Maxtor 120 gig hard
drive, then hook up the smaller hard drive as a slave drive and pull
the correct AGP440.sys file from the big drive and stick it in place of
the one on the small drive. Any thoughts?
Click to expand...


I will bet the problem is really the next line after AGP440.sys. The
system crashes and never displays the driver it is trying to load. On
my system the next line after AGP440 is an Intel driver. Bet is a
leftover from the previous install. See if you can explore
c:\windows\system32\drivers and delete any old drivers there. Good
luck.
 
Is mup.sys an old intel driver? If this is the culprit, then what do I
do about it? Can I delete this file without side effects?
 
Back
Top