BSOD on first XPx64 startup with slipstreamed install

[arpharazon]

I have gone through this process 5 times, no luck yet.

1st try - Wasn't aware I needed to sort the hotfixes, so had a lot of hitting "yes" to keep newest versions of .dll's

- Didn't copy driver folders to local drive, so drivers were not integrated.

- This was the only time I got into windows at all despite a few "missing .dll messages during installation.

2nd try - Sorted the hotfixes and deleted a bunch that were superseded by SP2 (XPx64), so I didn't get as many "hotfix is not for this version of

Windows" type messages.

- Got a BSOD upon first startup of Windows (after full format and installation process).

3rd try - Same as 2nd try, I started from scratch hoping to prevent any issues. No luck, BSOD again.

4th try - Basically the same as 2 & 3, from scratch again. BSOD again.

5th try - From the top one more time. Went without the drivers at all. Hoped that might be the culprit. No dice, BSOD once again.

Attaching the last 2 presets, 1 with drivers & 1 without drivers. Hope I'm doing this right.

03_29_09_10pm.ini

03_30_09_12am_no_drivers.ini

I'm actually hoping I did something wrong in nLite, otherwise I have some kind of problem burning .ISO's, but I used 3 different programs in this process and the overall installation seems to be going OK, so I'm just not certain.

Any help will be appreciated.

[johnhc]

arpharazon, looks like you were lucky to get this far. I think your hot fixes are in reverse order at least, except maybe for WMP11. You should place IE7 and WMP11 first and then their updates. It also looks like you have about twice as many updates as needed. I suggest you look at Kurt_Aust's great tutorial. He has a complete list of updates needed after SP2. 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. Enjoy, John.

[arpharazon]

That's weird, but I see what you're saying about the order now that I look at the 2 presets I posted. It seemed like the order was wrong the very first try (neither of the 2 posted presets), when it kept asking about keeping the newer version of the .dll's being integrated during that part of the process. So I ordered them by release date (like the nLite tutorial said to do).

If i go in the reverse order, won't I have to hit "yes" a hundred times again?

As far as too many hotfixes, I only get 3 or 4 that say they're "not for this version of Windows", which I thought was about redundant hotfixes coming after the SP2 I integrated earlier in the process.

I'll look at the tutorial you suggested.

Thanks.

[arpharazon]

Got bored and tried this again. This time I did only XP x64 + SP2 + +WMP11 + a few drivers + some tweaks at the end (no hotfixes at all). Same result.

WTF?

I'm glad I don't need to rely on this piece of garbage for anything. Would have been nice to save some time on the next reinstall (and there's always a next reinstall).

Last_Session.ini

[johnhc]

arpharazon, I agree - WHAT? I see nothing in your Last Session that should lead to a BSOD. What is the displayed error code? When everything is lined up properly, you should get NO error messages at all from nLite. If you are getting compatibility messages on your hot fixes, then they are not for XP x64. You should only include hot fixes that MS released after SP2. Kurt_Aust has a great list. Are your sure you are starting with a fresh copy of your source and integrating one SP (SP2?) Are you installing on a RAID and/or SATA connected HDD? You have no text mode drivers. Are you installing on HW or a virtual system? Please check the particulars on your copy of SP2.

Name: AMD64-en-windowsserver2003.windowsxp-kb914961-sp2-x64-enu_7f8e909c52d23ac8b5dbfd73f1f12d3ee0fe794c.exe

Size: 350 MB (367,964,016 bytes)

MD5: 46D05CE174437A224C8A77047D010AE9

The SHA-1 is the hex at the end of the name.

Please let me hear, John.

[arpharazon]

No error messages from nLite, just BSOD after all the installation steps and trying to get into Windows for the first time.

The BSOD is just as Windows would go to a login/welcome screen and since I am unable to get into Windows at all with this, I can't uncheck the automatic restart under "startup & recovery". So I see the blue screen for half a second before it restarts, I can't see what it's problem is.

I was trying to see if the hotfixes from earlier failures were to blame, so I skipped them altogether this time and just integrated SP2.

I uninstalled and reinstalled nLite, deleted all folders and temp folder files.

It's being installed on a 3rd SATA HDD that I had previously been testing Win7 on. It gets partitions removed and put back and formatted.

Initially, I had those compatibility messages with the hotfixes, even though they all had x64 in the filenames, so I don't know what that was about. I think they were pre-SP2?

The last time I did try it with hotfixes I still had a couple of those messages, but again, the KB# was earlier than the KB# on SP2 on the MS website, so I figured that was the issue.

SP2 particulars: WindowsServer2003.WindowsXP-KB914961-SP2-x64-ENU.exe 350MB

Not sure about that AMD reference you made for SP2, I don't have any AMD H/W, if that's what that means.

[johnhc]

arpharazon, I, too, am confused about the AMD reference on my SP2. I'll have to check into that. The SP is the same and you should check the length in bytes against mine and the MD5. I use HashTab, but there are many free hash checkers available. You should also check the MD5 for nLite installer (see web site.) If you have SATA HDD, then you must install text mode drivers and you have not via nLite. Did you use F6 for this? If so, you must disable OEM Preinstall - see help (? in circle) in the Unattended section, General tag next to the OEM Preinstall pull down. Let me hear, John.

[arpharazon]

Are you referring to the F6 to install 3rd party RAID drivers? I have never done this during a normal installation. I do not utilize RAID configuration.

At one time I thought about it, when I first built the system, but decided against it. And then again, later on, I thought about AHCI configuration, but with the new mobo I did not need this use as many SATA drives as I have.

[johnhc]

arpharazon, you need text mode drivers for your SATA controller. Please post a link to your MB driver page. Enjoy, John.

[arpharazon]

OK, now you lost me. MB driver page? What is that and where can I find it?

Why would these text mode drivers be necessary now when I haven't needed them for a normal install?

[johnhc]

arpharazon, perhaps I am wrong about this if you have never had to use text mode drivers. Are you installing on a SATA drive? Have you installed on this machine on a SATA drive before? I guess by your reply, that you did not build this machine, but store bought it? Please let me know. Enjoy, John.

[arpharazon]

I have never used text drivers that I am aware of.

A short history.

I built the machine about a year and a half ago from scratch. Bought all the components from tigerdirect.

The original mobo had 4 + 4 SATA connectors, but only 4 worked without either a RAID or AHCI driver being used during installation of the OS. When first built I only had 4 SATA drives (2 - 500GB HDD's and 2 DVD burners) so I didn't need the extra 4 SATA connectors then. Add to that 1 - IDE drive (ZIP 750_ and 1 - FDD (3.5" w/7 in 1 card reader).

Later on, I upgraded one of the 500GB HDD's to a 1.5TB HDD, but ended up leaving the 500GB internal and tried an IDE to SATA converter card, which eventually went bad and caused a lot of systemwide havoc.

Around this point I thought I would try the AHCI driver but then found that my FDD controller had gone bad (maybe due to attempting to work in a 5.25" FDD at one point or, less likely, due to the crapping out of the IDE-SATA converter). This was the first time I considered the slipstream option, but I had no luck finding what I could ID as the proper AHCI driver, so I just bought a new mobo and did a full reinstall of XP.

This new mobo has 6 standard SATA connectors that do not need any special drivers to be installed, all 5 SATA drives are recognized by both BIOS and XP.

So the only reason I really want to do slipstreaming is to add SP2 and (hopefully) the post-SP2 hotfixes/updates and then drivers and WMP11 & IE7, if only to save time during/after the next reinstallation, and it's only a matter of time before I decide to do another reinstallation (I'm just that way, some problems refuse to be fixed through utilities or by any other means, plus Tune-Up utilities can screw something up during registry defrag that causes an unfixable BSOD after restart, which was the reason behind they very last reinstall of Windows).

Also, I burned memtest.iso to a CD the other day, and ran it. This was to double-check if my ability to burn .ISO's was the culprit after I had failed to do so 3 times with a copy of Windows7 32 bit I had from a few months ago. That file had been on an HDD that was accidentally formatted and recovered, so the file itself might have been corrupted during that process (as many other files had been).

[johnhc]

arpharazon, yours is indeed a puzzling problem. Here is an experiment to try. Remove almost everything from nLite - no SP2, no drivers, not updates, no tweaks, no component removals. Essentially just burn an ISO from your XP x64 CD and see if that works. If you get the BSOD and Automatic Reboot, try hitting F8 and see if you can go into Safe Mode. If you can, then turn off the Automatic Reboot and reboot. Post you BSOD error code. Did you check the MD5 of your SP2? Please let us know what you learn.

I kinda wish you had not told me about your TuneUp Utilities problem. I am using it but not the defragger. Have fun, John.

[arpharazon]

I'll give that a try. In the past though, if something was causing a BSOD during startup, it usually did the same with a safe-mode too.

Yeah, the TU 1-click maint. always works OK, and it does some registry checking and cleaning, but the registry defrag from the main TU utilities did something weird.

Edit to update:

Did the XP install only, and that worked. Only "additionals" were some Unattended Setup things, product key, XP theme with silver, added username, screen resolution, color quality.

Had to go to work, so tomorrow I'll try adding 1 "extra" per attempt and see how far I get before trouble strikes.

Edited April 8, 2009 by arpharazon

[johnhc]

arpharazon, great!, I think it is important to get a running system to work from. I would suggest you put all your drivers back in and see what happens. I suspect this is where the problem is and you will get there sooner. If it does BSOD, please try to get into Safe Mode. Enjoy, John.