This fix is VERY model, mainboard, and hard drive specific. You are taking great risks on several different models of the same manufacturer of ACER, ASUS, Gateway, Lenovo Thinkpad, and Alienware... perhaps several others... If your drive is larger than 80 GB (and with certain BIOS installs), you might be at risk...so do your research.

The post by TWEEKYD with the fix in didn't imply that it was anything other than simple. No posts since then have intimated that it should be done with caution either - or that it should not be done on similar ACER models.

That's why I felt compelled to register and post - in the hope I can stop someone else following that advice and ending up in the same mess as I am now in.

We agree that you did the right thing. It is not simple, and on certain systems it is indeed very risky... as you have learned. In our experience, the problems seem to revolve around very large mobile 2.5" drives 80 GB and over from Seagate and Hitachi, when combined with certain runs of motherboards.
There are only 7 laptop manufacturers in the world nowadays... but they are sold under 87 different brand names. This makes it very difficult for users to get accurate information.
Strangely, the problems only occur on certain models. For instance, IBM Thinkpads, which are superb, will have the errors on some and not others.
The Gateway problems are also spotty. Alienware problems, Acer, and ASUS units seem to be more severe across more models.

I'm having the same problem with a friends Gateway MX 6930....endless reboots. Disabled automatic restart to read the BSOD and got stop error
0x24. Cant even get to a C: prompt to run checkdisk.
Will not start Normally, Safe Mode w/Comand prompt, Safe Mode w/network, last known good configuration..etc. In safe mode it hangs at AGPCPQ.SYS and then reboots.
Used the recovery disc and nothing happened. Used the Operating System Disc to try to get to the recovery console , selected "R", begins recovery and hangs at "please wait". I left it for a few hours and all it did was start the rebooting process all over again.
I trieid putting a WinXP disc in from another computer to try and repair from that and had no success. The hard drive is recognized in the BIOS.
I tried the other applicable suggestions above and had no success with them.
I'm suspecting a bad hard drive sector (boot?)
Any ideas or other suggestions would be greatly appreciated

my windows does not start. i found about 20 minites before it loads. I ran the safe mode and it halts at agpcpq. tried reloading all software from factory settings still no improvement.

However, when i start in safe mode and the get out of the mode and restart the computer, windows starts properly. The moment i power down (not restart) and start in normal mode, windows halts and does not start for about 20 minutes. Going to safe mode and then restarting is the only thing I can do.

Any body, please help

Matthew

my windows does not start. i found about 20 minites before it loads. I ran the safe mode and it halts at agpcpq. tried reloading all software from factory settings still no improvement.

However, when i start in safe mode and the get out of the mode and restart the computer, windows starts properly. The moment i power down (not restart) and start in normal mode, windows halts and does not start for about 20 minutes. Going to safe mode and then restarting is the only thing I can do.

Any body, please help

Matthew

I had a Gateway desktop winodws xp with sp2. Some windows automatic update ran on March10, 2008 and when the computer rebooted it would get about 10 seconds into the windows startup and reboot. Safemode would hang on the agpcpq.sys file and then reboot. I used an XP install cd to bootand chose the R option to get to a command prompt. I could change to C: but when I typed DIR it said the directory couldn't be shown. So I type chckdsk /r from the C: prompt and it ran for about 3 hours, fixed one error and rebooted and was back up and running again with one error at the login about a windows restore file being corrupted and to run chkdsk. I'm going to make a complete Ghost backup before I do anything at this point then maybe run chkdsk again.

Try setting your SATA operation to 'ATA' in the BIOS.

I had all the same problems with my Dell Precision 390 after cloning the original disk. I tried everything listed in this thread to no avail.

I finally fixed it by changing the BIOS setting, SATA Operation from AHCI to ATI

Now works a treat.

Hi guys I've been following this problem since yesterday. I've read all the posts and I think I have something worth while to add here.

I have been given a computer by a friend at work to fix and I have been encountering the same problem (XP locks up after loading AGPCPQ.SYS).

Initially the system would not load windows. It went through to the windows loading screen only briefly before entering an infinte reboot cycle. The first thing I did was load the recovery console and run chkdsk. Having read the forum and seeing all the trouble everyone has been having I was amazed to find that the machine started normally after chkdsk reported some errors and repaired them. I restarted several times and everything seemed to be working but the machine was very slow. I decided to install some anti virus and spyware removal tools and did some scans and they turned up minimal results. By then it was late so I shut the machine down and I went to bed.

However, that was last night and today I turned on the machine only to be greated with a slightly different problem. The machine began to start normally and went through to the windows loading screen but this time after about 10 or or 20 seconds the screen went blank and my monitor showed it was receiving no signal from the computer. The machine itself was still on and showing the HDD light however. After a couple of minutes the machine restarts on its own and takes me to the boot options prompt.

I decided to run chkdsk again from the recovery console and it returned the message that it found errors that were unrecoverable. Much to my distaste. So I decided to use the commands FIXBOOT and FIXMBR (master boot record) and see if that might aid me. When I ran FIXMBR I recieved the warning "*caution* it appears the master boot record is invalid or non-standard...etc" I decided to continue with the process.

I tried safe mode with command prompt and that worked so I decided to try full safe mode. When it restarted this time it decided that it was going to run the disk scan before it started windows so I let it carry on with it. To my horror it began returning "File record segment XXXX is unreadable" errors. Litterally hundreds of them.

It's still scanning now and I decided to do some resarch on what causes this error while I wait and it appears that it could very well be that the HDD has had it's chips. DskChk showed that the machine is only 4 years old (Disk partition created 2004) which surprised me. I don't know the full spec of the system as I can't get in to windows to look. All I know is that it is a Pacard Bell approximately 4 years old and uses an NTFS file system.

Hopefully when/if it completes the scan I will be able to get into windows and back up my friends files. If even in safe mode at least but I am seriously beginning to think that the machine is on its last legs. If all else fails I have another system in which I can install the HDD and take the files that way, using my friends HDD as a slave.

I am begining to think that not everyone here has been experiancing exactly the same problem. Especially since there are those who could not get their system to boot even after installing a fresh copy of windows and then there are also some who can use the CD to use the recovery console, enter safe mode or start windows normally. In this case it means that anyone else encountering this problem may find that some of the fixes posted here are not going to help you at all and could actually be counter productive. I would strongly suggest that before you try the most simple, least intrusive fixes like chkdsk in the recovery tool before you attempt anything serious like a reinstall or a repair.

Sorry for the long post last time guys the scan just finished and it failed to boot normally. Just trying safe mode now and we have lift off so at least I can get at his files.

I am thinking that AGPCPQ.SYS is the final one it loads anyway, which is why you are all apparently encountering the same error. It's pretty misleading because as it has already been said, AGPCPQ.SYS is displayed, meaning it has loaded successfully.

I'm going to save some files and make a note of what he has installed and then I'll have a mess about and see if I can fix it at all. I'll keep you posted.

Oh and thanks for everyones input in the thread as you helped point me in the right direction! Much appreciated ^^

Hi all,

ive just been searching why there was a kind of bug in that damn acer aspire 5100
Well, im just repairing a friend's computer
Never had the time to read all those pages

Anyway, just thougt maybe there's a solution if the problem are persistent,
even, when you reinstall...

just try to format your mbr (in your favorite dos mode)
That might format your Master Boot Record
A tiny place where some data could be hidden...
But never been used under windows

Well, ive just done my subsciption earlier to maybe help someone .. someday

I am now getting this exact same problem with my Gateway desktop, and I was wondering if anyone ever had an answer to this? Thanks.

I'm quite sure this is a HAL-issue. I was able to solve this exactly the same problem by changing HALs.

1) Boot with WinPE 2.0, 1.5 or BartPE

2) Copy or expand Multiprocessor HAL.dll (halmacpi.dl_) and proper ntoskrn.exe + ntkrpamp.exe to your Hard drive -> %WINDIR%\System32 and replace existing files

ACPI Multiprocessor PC
- halmacpi.dll (renamed to hal.dll)
- ntkrpamp.exe (renamed to ntkrnlpa.exe)
- ntkrnlmp.exe (renamed to ntoskrnl.exe)

Edit: You can find these files from your XP installation CD (i386-folder)

3) Reboot

Nvidia graphics driver updated, problem gone.

I'm trying to build an image in VMWare, sysprepping it and taking an image of the sysprepped image. Then pushing the image to another computer. But it fails every single time.
I'm pretty sure what is causing it to fail is the SATA controller. Because using cretney's solution, works for me.

This is not an option I'm afraid since forcing the system to run ATA makes it run slower.

I have tried to add the drivers to the sysprep.inf file like this:

[Sysprep]
BuildMassStorageSection=Yes

[SysprepMassStorage]
PCI\VEN_8086&DEV_27C1&CC_0106 = %systemdrive%\drivers\sata\iaahci.inf ; Intel(R) 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH)
PCI\VEN_8086&DEV_27C5&CC_0106 = %systemdrive%\drivers\sata\iaahci.inf ; Intel(R) 82801GBM SATA AHCI Controller (Mobile ICH7M)
PCI\VEN_8086&DEV_2652&CC_0106 = %systemdrive%\drivers\sata\iaahci.inf ; Intel(R) 82801FR SATA AHCI Controller (Desktop ICH6R)
PCI\VEN_8086&DEV_2653&CC_0106 = %systemdrive%\drivers\sata\iaahci.inf ; Intel(R) 82801FBM SATA AHCI Controller (Mobile ICH6M)
PCI\VEN_8086&DEV_27C3&CC_0104 = %systemdrive%\drivers\sata\iastor.inf ; Intel(R) 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH)
PCI\VEN_8086&DEV_24DF&CC_0104 = %systemdrive%\drivers\sata\iastor.inf ; Intel(R) 82801ER SATA RAID Controller (Desktop ICH5R)
PCI\VEN_8086&DEV_25B0&CC_0104 = %systemdrive%\drivers\sata\iastor.inf ; Intel(R) 6300ESB SATA RAID Controller
PCI\VEN_8086&DEV_2652&CC_0104 = %systemdrive%\drivers\sata\iastor.inf ; Intel(R) 82801FR SATA RAID Controller (Desktop ICH6R)

But this does not work either.

I have tried the HAL.dll solution and this does not helt either. I have tried both at the time.

Anyone have any experience with this? Help would be highly appreciated.

Guys, this problem seems to be pretty hard-lived and mysterious.
I had it on my acer aspire one 150 and managed to fix it, although I don't know how and why.
AA1 150 with windows XP SP3 preinstalled, bought in december 2008 in Hong Kong.

So it all started when I right-clicked on "My Music" and said "play in VLC". I'd done that before, I think, but this time, there was a lock, a freeze and then a blue screen. and on reboot, the "agpcpq.sys" problem (in normal mode windows loading screen would appear for a while, then blue screen).
My problem : I could not find any "recovery" option for my netbook. I was surprised by how empty the aspire one's BIOS is, btw. Luckily i could change the boot order.
Then I had to, first, find a usb stick, then spend hours figuring out how to get my brother's vista-empowered laptop to recognise the usb drive - a whole mess in itself, but my bad, i suppose.
This got me quite tired, so I don't really know which of the actions I performed next was responsible for fixing the problem.
First, I updated the BIOS to latest version (3114 as of now) with the help of Unetbootin and Freedos. Didn't fix the problem.
I then wanted to fiddle around while in DOS, try that fix by TECHMAN, converting disk to NTFS - but it was already NTFS, so I could not access the HDD under Freedos. I went on to search tools for accessing NTFS drives in a DOS environment (figuring out along the way that techman's fix wouldn't save me).
I am very chaotic, so I tried several tools one after the other.
The one did the trick appears to be NTFS4DOS. I ran some disk scans (or checks).
Then I located AGPCPQ.SYS and wanted to delete it. First, i tried to copy it to system32, whereupon my netbook froze. I unplugged it and took out the battery, tried to boot into safe mode and lo! it worked! I rebooted in normal mode and it worked and still does (the day after).
Still don't know what is really the matter and how it was fixed. I hope this "success story" can help a techier person shed light on this error.

Had the same issue on a Dell Lat D610 this morning. Running checkdisk on C with a /r switch worked perfectly. [ran chkdsk from BartPE in case you're wondering]