major agp440.sys boot up problem...

[Ruairi Glenn]

Hello,

Sorry for the x post but I need help big time...

I installed a new motherboard and cpu in my system as I fried the old ones.

I did not do a clean install of Windows XP as my HP Pavilion system did not
come with any recovery cd's so I hooked my existing hard drive up to the
system and powered up.

Anyway, it powers up ok but the first time I switched it on there was a blue
error screen that flashed on for a second and then the system rebooted
itself.

Now when I power on I can get past the bios screen ok but before the windows
logo appears I get the boot menu offering safe mode , safe mode with
networking, normal mode etc. A message appears on this screen saying that
the options appear as windows xp did not shut down correctly etc etc

If I choose normal mode then a white progress bar at the bottom of the
screen appears, it gets to the end of it and sits there.....for ever. If I
choose safe mode then it shows it loading all the files from the hard drive
and it gets to a file agp440.sys and it sits there...forever. So whatever
this file is it is causing the system to hang,

Various fixes I have seen include getting into Windows and disabling the
agp440.sys service. But I cannot get into xp at all as my system did not
come with boot cd's.

I can boot to a win98 floppy ok but I cannot access drive c: as it is ntfs,
I thought maybe I could rename agp440.sys to something else.

Any ideas on how to get round this agp440.sys problem? I *really* don't
want to do a clean install as I have no win xp cd's. My hp pavilion system
contains it's setup files on some hidden partition on the drive.

Thanks,

td.

 

[Guest]

Any ideas on how to get round this agp440.sys problem? I *really* don't
want to do a clean install as I have no win xp cd's. My hp pavilion system
contains it's setup files on some hidden partition on the drive.

I had this issue so disabled it via recovery console, it's possible to
disable services and drivers thatta way, but to do this you'll need an
XP CD to boot into it.

I'm sure there was soomething else that stopped me booting the machine
as well though, so still ended up flattening it.

XP doesn't like a change of motherboard IME/IMHO, the only way to do
things right it is installing a fresh.

 

[Nathan McNulty]

Two things. First, you are going to need to repair the installation.
If you do not have a CD of any kind, I would contact HP for one. They
should have given you at least a recovery CD if not an OEM copy of XP to
be installed on your computer. Now you run into the problem that OEM
copies of XP like you have are only supposed to be installed on the
original machine it was on, which means it would not be legal to use it
on your new computer. Before everyone flames me, this is how most OEM
EULA's are written and I really don't care what it says because in my
opinion you paid for the OS when you paid for the computer.

Anyways, if you really want to try to hack your way in, you can still
use the recovery console without having the CD. You will need several
floppies though.

For XP Home without any Service Packs:
http://www.microsoft.com/downloads/release.asp?releaseid=33290

For XP Home with Service Pack 1:
http://www.microsoft.com/downloads/release.asp?releaseid=42818

For XP Home with Service Pack 2:
http://www.microsoft.com/downloads/...07-99F7-4A2D-983D-81C2137FF464&displaylang=en

For XP Pro without any Service Packs:
http://www.microsoft.com/downloads/release.asp?releaseid=33291

For XP Pro with Service Pack 1:
http://www.microsoft.com/downloads/release.asp?releaseid=42819

For XP Pro with Service Pack 2:
http://www.microsoft.com/downloads/...8D-5E10-49B5-B80C-0A0205368124&displaylang=en

I really don't think it is possible to repair an installation using
these disks, but you can still try. I would boot into the recovery
console and try fixboot. It is worth a shot, but you probably need the CD.

 

[Guest]

I really don't think it is possible to repair an installation using
these disks, but you can still try. I would boot into the recovery
console and try fixboot. It is worth a shot, but you probably need the CD.

Fixboot will only write a new boot sector to the HDD.

The boot sector is obviously fine if the user can get as far as loading
Windows.

listsvc and disable are the two commands of most use here, but I still
think he'd be better off reinstalling.

 

[Nathan McNulty]

Thanks, I never use the Recovery Console (just image the drive instead).
Thought fixmbr did both of those and fixboot did NTLDR and some other
things. Anyways, he is going to have to repair the installation as I
see no way of making it work.