P4 3.0 Ghz 512k and P4 3.0E Ghz 1024k CPU hang on agp440.sys

[Andy]

Can anyone explain this one. I orignally installed XP
with the P4 3.0Ghz 512k cache CPU and everything worked
great. Got a hold of a P4 3.0E Ghz 1024 cache CPU swapped
them out and on boot (normal and safe) XP hangs on
agp440.sys. Can't get any farther. BIOS for Motherboard
is the latest. So are video card drivers.

I swap back CPUs to original and XP boots up perfect. The
work arounds seem outright silly for such a simple
hardware change. Why would one work but not the other?
The 3.0E is not defective and am using it right now in a
Win ME machine to type this message.

Any ideas?

Andy

 

[V Green]

This sounds like the "SP2 incompatibility with Prescott
CPU's" issue.

Been discussed rather thoroughly here, but not
in the last few days, and I don't have any current
links to the fix.

It's a processor microcode update issue of some kind.

Google will probably turn it up.

 

[Eric Wang]

Maybe you should reinstall the OS.

 

[V Green]

More info:

http://support.microsoft.com/default.aspx?scid=kb;en-us;885626&Product=winxp
http://support.microsoft.com/default.aspx?scid=kb;en-us;324764&Product=winxp
http://cquirke.mvps.org/sp2intel.htm

 

[Guest]

Windows will detect changes in CPU or Motherboard and 'see' this as it being
relocated or cloned. Anti Piracy features in XP will prevent the system from
working.

You need to perform a repair installation to set the system to the new CPU.
Insert your XP installation CD into the PC and boot off the CD [you may need
to change BIOS settings to get this to function].

When you see the "Welcome To Setup" screen, you will see the options below
This portion of the Setup program prepares Microsoft
Windows XP to run on your computer:

To setup Windows XP now, press ENTER.

To repair a Windows XP installation using Recovery Console, press R.

To quit Setup without installing Windows XP, press F3.
Press Enter to start the Windows Setup.
Accept the License Agreement and Windows will search for existing Windows
installations.
Select the XP installation you want to repair from the list and press R to
start the repair.
Setup will copy the necessary files to the hard drive and reboot. Do not
press any key to boot from CD when the message appears. Setup will continue
as if it were doing a clean install, but your applications and settings will
remain intact.
Blaster worm warning: Do not immediately activate over the internet when
asked, enable the XP firewall before connecting to the internet. You can
activate after the firewall is enabled. Control Panel - Network Connections.
Right click the connection you use, Properties, and there is a check box on
the advanced page.

 

[Vince]

Andy:
It is not a "simple hardware change" in your case. the P4 3.0 and 3.0E
differs significantly: the former one is Northwood and the latter is
Prescott, they use different instruction sets. To make xp realize the
change, an in-place upgrade of XP is needed. There is a detailed
instruction http://support.microsoft.com/default.aspx?kbid=315341. But that
reverse all service pack.
If you want keep your current SP, you have to make splipstreaming install CD
which integrates XP installation with the SP of your choice. The article
here http://www6.tomshardware.com/howto/20040908/index.html is detailed
enough even for a beginner. It takes XP sp2 as example, but applies to all
NT, 2k, XP Spn.

Good luck.

Vince

 

[Cari \(MS MVP\)]

http://forum.aumha.org/viewtopic.php?t=7447

 

[Guest]

We had a similar problem with the agp440. The first problem we noticed on
the upgrade from Windows 2K to XP Pro was that every time we logged in the
system took forever to boot and we kept getting the paging file to small
error. No matter what we tried we could not get the paging file fixed.
Things went from bad to worse – the boot process would lock up, when we
finally did get in things were so slow. We tried to log in under safe mode
and it hung up at the agp440.sys. The first several times it just sat there
finally we just let it sit there while we researched the problem. After
several minutes it got past that (15) and finally loaded Windows. We had
logically worked out that the AGP had loaded and what ever came next that you
could not see was the problem. We looked at the winnt\nbtlog.txt and saw
that the AGP440.sys had loaded but the next line and almost everything after
failed to load. The next line was ACPI Uniprocessor. We figured out that
the Intel Applications Accelerator was the culprit. We went into Control
Panel/Add/Remove Programs located Intel Applications Accelerator and removed
it. SO FAR that seems to have fixed our problems. The system loads quickly,
no more paging file problem, and it doesn’t freeze at startup or shut down.
wrote: