Bsod After Copying Over Setup Files

[S0mE0nesMiNd1]

BSOD after copying over setup files

Hello - Im having a BSOD problem after the computer restarts prior to the setup screen, and after it copys over the setup files. Here is the list of things I have done that may contribute to this problem:

1) used nLite's (Latest Beta) "Safe" selection and removed ONLY the "Safe" selections.

2) using nLite, I integrated RyanVM's Update package.

3) Integrated all of Bashrat's LATEST Driver Packages with Method 2

4) Put on a custom Winntbbu.dll

The odd thing is, it worked perfectly in VMWare. Anyways, heres the BSOD Error:

Technical Information:
*** STOP: 0x0000007B(0xF8A80528,0xC0000034,0x00000000,0x00000000)

If anyone has any ideas I would certainly appreciate it. Thank-You.

[ckw2068]

BSOD after copying over setup files

Hello - Im having a BSOD problem after the computer restarts prior to the setup screen, and after it copys over the setup files. Here is the list of things I have done that may contribute to this problem:

1) used nLite's (Latest Beta) "Safe" selection and removed ONLY the "Safe" selections.

2) using nLite, I integrated RyanVM's Update package.

3) Integrated all of Bashrat's LATEST Driver Packages with Method 2

4) Put on a custom Winntbbu.dll

The odd thing is, it worked perfectly in VMWare. Anyways, heres the BSOD Error:

Technical Information:
*** STOP: 0x0000007B(0xF8A80528,0xC0000034,0x00000000,0x00000000)

If anyone has any ideas I would certainly appreciate it. Thank-You.

<{POST_SNAPBACK}>

Here is what MSDN pulled Q324103

[S0mE0nesMiNd1]

So would you say its most likely driver related?

[ckw2068]

So would you say its most likely driver related?

<{POST_SNAPBACK}>

From your initial post, it's all questionable. It looks like MS has quite a few different things that fall under that stop message.

If you have not aleady one so, I'd try and do a fresh install from scratch and see what you find. Do not use any 3rd soft packages or tweaks

let us know.

[DigeratiPrime]

Im getting EXACTLY the same problem as the original poster. Worked in vmware, but not on a real pc. Same stop message, same time, etc.

This is a SATA Hard Drive, the Drivers from the Mass Storage Pack have worked before.

Has this since been resolved?

I'll reply if i figure anything out.

[Bâshrat the Sneaky]

It might help if the both of you would post on what hardware setup you're trying to install

[DigeratiPrime]

Sorry about that. I am doing a Clean Install, New Partitions, Formatted.

Motherboard: Asus K8V SE Deluxe

Hard Drive: Seagate SATA ST3160827AS

RyanVM Update Pack 1.2

Mass_Storage v.5.02.2

XP SP2

Im going to find a Floppy Drive and the original SATA driveres and report back on how that goes. BTW maybe the thread should be moved? I just searched and found this.

Im reading these links btw:

http://support.microsoft.com/default.aspx?...kb;en-us;324103

http://support.microsoft.com/default.aspx?...124120121120120

[Bâshrat the Sneaky]

... and to which controller is that HDD attached? I thought it had 2 controllers: a VIA and a SiI one.

EDIT: try this (probably it will be this):

open your txtsetup.sif and search this line:

PCI\VEN_1106&DEV_3149= "viasraid"

and change it to:

PCI\VEN_1106&DEV_3149= "viamraid"

I'm very curious...

Note that will only make any difference if the HDD is connected to the VIA controller

Edited April 6, 2005 by Bâshrat the Sneaky

[DigeratiPrime]

OK, found this post actually from Google, originally thought the problem was due to MBR.

Have not ruled that out yet though. During Windows Setup after it finishes copying files, and reboots, after the xp boot screen I get the BSOD.

Will update BTS Driver Packs, as according to this thread:

http://www.msfn.org/board/index.php?showtopic=42820

And report how that goes.