PAGE_FAULT_IN_NONPAGED_AREA when upgrading to Windows XP

[[email protected]]

I have a laptop that has Windows 2000 Pro on it and it works fine.
When I try to upgrade it to Windows XP Professional, I am getting the
error PAGE_FAULT_IN_NONPAGED_AREA and the BSOD. I start the upgrade
process from Windows 2000, It reboots the system and copies the new
files to C: and reboots the system. Right after the Microsoft Logo
appears, I am getting the error. I have checked the memory and this is
ok. I have run Chkdsk and Defrag before upgrading. Luckily, I have a
Ghost image of the system before the upgrade so I can retry.

I have tried booting into Safe Mode, but it says it can not continue as
Windows XP is in setup mode.

Any idea on how to identify and fix the problem?

TIA

[Will Denny]

Hi

Please try the following link to Jim Eshelman's web page - left hand column
(50)

http://aumha.org/win5/kbestop.htm

--


Will Denny
MS-MVP Windows Shell/User
Please reply to the News Groups

> wrote in message
oups.com...
>I have a laptop that has Windows 2000 Pro on it and it works fine.
> When I try to upgrade it to Windows XP Professional, I am getting the
> error PAGE_FAULT_IN_NONPAGED_AREA and the BSOD. I start the upgrade
> process from Windows 2000, It reboots the system and copies the new
> files to C: and reboots the system. Right after the Microsoft Logo
> appears, I am getting the error. I have checked the memory and this is
> ok. I have run Chkdsk and Defrag before upgrading. Luckily, I have a
> Ghost image of the system before the upgrade so I can retry.
>
> I have tried booting into Safe Mode, but it says it can not continue as
> Windows XP is in setup mode.
>
> Any idea on how to identify and fix the problem?
>
> TIA
>

[R. McCarty]

You "may" have an issue with BIOS ACPI (Advanced Configuration &
Power Interface) compliancy. I'd recommend you go to the vendor's
website and locate the BIOS flash update section. You'll probably want
to determine how many revisions down your current BIOS is from the
latest/last released. At install XP determines which HAL (PC Driver) to
use by reading BIOS data. Some computers will inform XP they are
capable of ACPI when in fact they do not. Updating the Flash code to
a later release can resolve that issue. Usually the current BIOS revision
is shown during the POST (Power on Self Test). Naming conventions
vary, but it will usually take the form of major/minor numbering scheme
like 4.09 or in the case of Dell A09, A10.

Also if your notebook supports it, consider turning off any on-board
peripherals you do not use - such as modems, COM & Parallel ports.

> wrote in message
oups.com...
>I have a laptop that has Windows 2000 Pro on it and it works fine.
> When I try to upgrade it to Windows XP Professional, I am getting the
> error PAGE_FAULT_IN_NONPAGED_AREA and the BSOD. I start the upgrade
> process from Windows 2000, It reboots the system and copies the new
> files to C: and reboots the system. Right after the Microsoft Logo
> appears, I am getting the error. I have checked the memory and this is
> ok. I have run Chkdsk and Defrag before upgrading. Luckily, I have a
> Ghost image of the system before the upgrade so I can retry.
>
> I have tried booting into Safe Mode, but it says it can not continue as
> Windows XP is in setup mode.
>
> Any idea on how to identify and fix the problem?
>
> TIA
>

[NoStop]

On Tuesday 15 August 2006 02:47 pm, had this to say in
microsoft.public.windowsxp.general:

> I have a laptop that has Windows 2000 Pro on it and it works fine.
> When I try to upgrade it to Windows XP Professional, I am getting the
> error PAGE_FAULT_IN_NONPAGED_AREA and the BSOD. I start the upgrade
> process from Windows 2000, It reboots the system and copies the new
> files to C: and reboots the system. Right after the Microsoft Logo
> appears, I am getting the error. I have checked the memory and this is
> ok. I have run Chkdsk and Defrag before upgrading. Luckily, I have a
> Ghost image of the system before the upgrade so I can retry.
>
> I have tried booting into Safe Mode, but it says it can not continue as
> Windows XP is in setup mode.
>
> Any idea on how to identify and fix the problem?
>
> TIA

Laptops can be fussy animals. Assuming it's an older laptop since it has W2K
installed on it, have you looked at a possible BIOS upgrade from the
manufacturer that will enable the use of XP on that laptop? Some do require
this.

--
WGA is the best thing that has happened for Linux in a while.

The ULTIMATE Windoze Fanboy:

http://video.google.com/videoplay?docid=-2370205018226686613

Is this a modern day equivalent of a Nazi youth rally?:

http://www.ntk.net/media/developers.mpg

A 3D Linux Desktop (video) ...

http://www.youtube.com/watch?v=DUSn-jBA3CE

View Some Common Linux Desktops ...
http://shots.osdir.com/

[[email protected]]

After reloading my Windows 2000 image, I upgraded the BIOS and followed
the previous suggestions. I reran the Windows XP upgrade but am
getting the same results. Any other thoughts?

[R. McCarty]

Could you post the Vendor/Model # for the PC.

> wrote in message
oups.com...
> After reloading my Windows 2000 image, I upgraded the BIOS and followed
> the previous suggestions. I reran the Windows XP upgrade but am
> getting the same results. Any other thoughts?
>

[[email protected]]

It is a Dell Latitude D810. It has Windows 2000 Pro on it as we put a
standard image on the system. I am trying to upgrade the system to
Windows XP Pro in order to create a new, updated image.

R. McCarty wrote:
> Could you post the Vendor/Model # for the PC.
>
> > wrote in message
> oups.com...
> > After reloading my Windows 2000 image, I upgraded the BIOS and followed
> > the previous suggestions. I reran the Windows XP upgrade but am
> > getting the same results. Any other thoughts?
> >

[R. McCarty]

As a test case, what happens if you try to install Windows XP fresh on
the Latitude ? The notebook specs would certainly indicate the D810
can support/run XP. You made mention of "We" and since this is a
business model are you creating an image for deployment on multiple
units ?

> wrote in message
ps.com...
> It is a Dell Latitude D810. It has Windows 2000 Pro on it as we put a
> standard image on the system. I am trying to upgrade the system to
> Windows XP Pro in order to create a new, updated image.
>
> R. McCarty wrote:
>> Could you post the Vendor/Model # for the PC.
>>
>> > wrote in message
>> oups.com...
>> > After reloading my Windows 2000 image, I upgraded the BIOS and followed
>> > the previous suggestions. I reran the Windows XP upgrade but am
>> > getting the same results. Any other thoughts?
>> >
>

[[email protected]]

I have been able to do a fresh install of Windows XP and that works.

Yes, we do deploy this on multiple units. The original image Windows
2000 came from an HP 4150 laptop. We are standardizing on the Dell
Latitude 800 series. The Windows 2000 image works fine on the Dell.
It is curious that the upgrade to XP fails.

[R. McCarty]

I think I understand now. Have you checked your 2000 image for any
"Phantom" Device entries ? My guess is the overlay from one chipset
to the other has left Phantom entries. When XP tries to upgrade those
entries are causing the BSOD. I would maybe cleanup the 2000 base
image and try again. You'll need to add a System Variable and enable
"View Hidden Devices" in Device Manager to be able to see/remove
all the Phantom entries.


> wrote in message
ups.com...
>I have been able to do a fresh install of Windows XP and that works.
>
> Yes, we do deploy this on multiple units. The original image Windows
> 2000 came from an HP 4150 laptop. We are standardizing on the Dell
> Latitude 800 series. The Windows 2000 image works fine on the Dell.
> It is curious that the upgrade to XP fails.
>

[[email protected]]

I displayed the hidden devices and had 3 that were disabled. I removed
those and tried the upgrade again. Same error.

I am not sure what the System Variable is that you referred to. Are
there other devices I should look for?

R. McCarty wrote:
> I think I understand now. Have you checked your 2000 image for any
> "Phantom" Device entries ? My guess is the overlay from one chipset
> to the other has left Phantom entries. When XP tries to upgrade those
> entries are causing the BSOD. I would maybe cleanup the 2000 base
> image and try again. You'll need to add a System Variable and enable
> "View Hidden Devices" in Device Manager to be able to see/remove
> all the Phantom entries.
>
>
> > wrote in message
> ups.com...
> >I have been able to do a fresh install of Windows XP and that works.
> >
> > Yes, we do deploy this on multiple units. The original image Windows
> > 2000 came from an HP 4150 laptop. We are standardizing on the Dell
> > Latitude 800 series. The Windows 2000 image works fine on the Dell.
> > It is curious that the upgrade to XP fails.
> >

[[email protected]]

Don't know if this has anything to do with it, but when I boot, I get
an error in the system log regarding %HPCI.DeviceDesc% being unable to
start. I can not find what this is.


R. McCarty wrote:
> I think I understand now. Have you checked your 2000 image for any
> "Phantom" Device entries ? My guess is the overlay from one chipset
> to the other has left Phantom entries. When XP tries to upgrade those
> entries are causing the BSOD. I would maybe cleanup the 2000 base
> image and try again. You'll need to add a System Variable and enable
> "View Hidden Devices" in Device Manager to be able to see/remove
> all the Phantom entries.
>
>
> > wrote in message
> ups.com...
> >I have been able to do a fresh install of Windows XP and that works.
> >
> > Yes, we do deploy this on multiple units. The original image Windows
> > 2000 came from an HP 4150 laptop. We are standardizing on the Dell
> > Latitude 800 series. The Windows 2000 image works fine on the Dell.
> > It is curious that the upgrade to XP fails.
> >

[[email protected]]

I did find the HPCI service and removed it so this error is not
occurring. But, I am still unable to do a successful upgrade.

[[email protected]]

I found the problem. There was a network service attached to the NIC
in the Network Properties for the lan connection. I uninstalled this
and was able to get the upgrade to work. This was all by trial and
error. Unfortunately, there is no logging done by Microsoft to show
what it was doing at the time the error occurs.