Page Fault In Non-Paged Error during XP Setup

[barnold]

Hi,

I created an XP with SP3 unattended install disk with Nlite that is bluescreening during setup. This disk was working perfectly BEFORE I integrated any hotfixes.

The stop error is:

A problem seems to be caused by the following file: setupdd.sys

PAGE_FAULT_IN_NONPAGED_AREA

Background:

In Nlite:

Base OS: XP (SP2)

Slipstreamed XP SP3

Added Windows Hotfixes

Slipstreamed storage, nic and chipset drivers (previously extracted using DriverPacks BASE 8.12.4)

The stop error occurs during Setup while the system files are being copied to the hard drive. The file copy process lasts probably 2 or 3 times longer than during a functional setup and I may be wrong, but it appears that it is looping (the same files being copied over multiple times). I'd estimate that the stop error occurs about 15-20 minutes into the copy process.

I created the disks in stages and always tested on physical hardware before the next stage. First just the OS with SP3 slipstreamed. Then the OS with the drivers slipstreamed. Those disks worked great, but when I add the updates it fails. The first time this occured I had added all the hotfixes I downloaded (29 in total). Then I rebuilt the disk (using the same lastsession.ini without integrating any hotfixes and it actually failed again, which really surprised me. At that point i suspected that maybe there was something wrong with the system files, so I recopied over the original XP source files to my build folder. Using those files I built a working disk again with drivers and sp3 slipstreamed but without integrating any windows hotfixes. Now I was pleased to be back to square one so I could start from scratch knowing that the OS source files were working. I decided to only integrate 10 hotfixes into the next build but again, it failed with the exact same PAGE FAULT IN NON-PAGED AREA error and referenced setupdd.sys as the possible culprit.

Could one of the hotfixes cause this error?

Is there a proper method to add the hotfixes to nlite (i.e. should I add them in numerical order by release date, or by KB number)?

See attached pic and thanks for your help.

brian

LAST_SESSION.INI

Edited May 8, 2009 by barnold

[Sp0iLedBrAt]

Two different websites I found on Google explain your problem as a problem with RAM or incompatible hardware. See HERE for example.

[barnold]

Thanks for the response.

This Nlite build WAS working fine before I integrated the updates and I am using the same computer and haven't changed the RAM.

I can try to find different hardware to test on to rule that possibility out, but could this have anything to do with the updates?

thanks!

[johnhc]

barnold, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Hot fixes are integrated in the order in which MS released them, oldest at the top of the list. The RyanVM forum offers Update Packs and each should have a list of included updates, so you can see the proper order even if you do not want to use the pack. Enjoy, John.

[barnold]

Thanks for the tips John.

I attached the lastsession.ini file (had to remove the BSOD screenshot due to 200k size limitation).

I'll start from scratch with a fresh set of source files and keep you posted.

Appreciate everyone's support/advice!

Regards,

Brian

[johnhc]

barnold, your first update appears to be out of order by KB number, although it is the release order that counts. I do not know what the update does and it may be fine there. You can attach to any reply, but we are OK without the BSOD. Enjoy, John.

[Sp0iLedBrAt]

barnold, which program are you using to test your nLited CDs and has an error shown up so far about non-sufficient allocation of memory during the process?

I have a crazy theory, but first I would really like the answer to these questions. Meanwhile, please post any test results that you get.

[barnold]

Everyone - thanks so much for your help. I will need to continue this on Monday, ok.?

I will post results then.

Thanks again

brian

[barnold]

barnold, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Hot fixes are integrated in the order in which MS released them, oldest at the top of the list. The RyanVM forum offers Update Packs and each should have a list of included updates, so you can see the proper order even if you do not want to use the pack. Enjoy, John.

Everyone,

Wanted to let you know that I'm not getting the error anymore. I took John's advice (Thanks John!!) regarding always using fresh source files and looked into RyanVM. I decided to use RyanVM to integrate the hotfixes as well as the driverpacks, then used Nlite only for the unattended stuff and .iso creation. That worked like a charm. I suspect that the problem had something to do with the hotfix or driver integration stages in Nlite. I had extracted the driverpack's drivers to a folder and pointed Nlite to it instead of directly slipstreaming the drivers into the source files using the DPs_Base application. I also had manually downloaded the security updates and was integrating them with Nlite. I think using RyansVM to slipstream that drivers and hotfixes directly into the source files was a lot cleaner and is probably what fixed the problem.

Thanks to all for your help!!!

brian