WIn XP SP2 auto updated ... BSOD !!!!

Auto update completed successfully, said Bill G, BG, the Bug Geek Meister...
Time to reboot to complete your Win XP SP2 installation ....

Sounded soooooo nice !

Crash ! BOOM ! BSOD 0x50 !!!!

What gives ?

 

Can you give us the rest of the crash boom error please and a little more info...why were you reinstalling to begin with?

 

Thanks !
Well, Bill Gates invited me to auto update XP to SP2.

Did not update for awhile, installed a few programs
to do work I needed to complete first.

Then did the auto update, install success it said at the end,
then reboot ... no boot.

C: drive has Win 2000 Pro SP4 installed much earlier,
running ok, NAV 7.51, firewall Zone Labs Free, Spybot 1.5, SpywareBlaster 4.1, 160 GB no other partitions.

XP SP1 was installed on D:, 400 GB, no other partitions.

boot.ini on c: looks like this:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect

Tried other swithces such as /sos and /bootlog to try to create
a minidump, does not make one.

What gives ?

 

Hi again,

Do you use a BootSkin program from Stardock Corporation? Is it this error?

http://support.microsoft.com/kb/873159

 

Re: WIn XP SP2 auto update ==> BSOD !!!!

No.
Nothing fancy here, plain vanilla XP.

 

Auto update was on.
Decided to auto update using online download after
putting it off for awhile.

Download & installation was successful, or so it said.
Reboot to complete installation was not, it crashed
right away.

C: drive has 2000 Pro SP4, installed earlier, boots ok.
D: drive has XP SP1 going to SP2 installed later, no boot, crash, bsod.

Are there any utilities to check the registry on drive d: while
I boot from c: ?

What gives ?

 

You're a little late on the SP2 and a long list of " what gives" here:

http://www.windowstalk.org/sp2.htm

 

Thanks !
What to do to make d: bootable again ?
Is recovery possible ?

 

There are a lot of things that cause that error, might help if we had the exact error, not sure if you can use the BSOD debugger on a multi boot. Someone will let us know if you can. Did you have your antivirus running during the install, did you check your PC mfg. for updates prior to install?

http://support.microsoft.com/kb/183169/EN-US/

 

Thanks !
BSOD 0x50 that's all it said, I looked for *.dmp files
on d: drive, there's only a user.dmp, I doubt that's the one.

Pretty sure NAV 7 was on, firewall ZA Free on, spybot 1.5 on,
spywareblaster 4.1 on. All current updates.

Did a scan of the d: drive for virus & trojans afterwards,
nothing found, looks clean.

Mobo updates ok, latest prior to install.

Could the ntloader become damaged during the update ?
http://support.microsoft.com/kb/919529#appliesto

Does it hurt re-installing the ntloader as above, ie, loose the c: drive 2000 Pro SP4 as well ?

 

You could try and "rebuild" D: if you want by following something like:

XP's No-Reformat, Nondestructive Total-Rebuild Option

I have used this several times and always successful, but you will have to do all updates. I would leave C: for the moment, in fact I wonder if you could use a restore point in C: and get to an earlier point in D:. Read the above link twice before you undertake it. I have had OS get screwed before and it occurred just after an update but was able to recover.

 

Thanks !
Updates from SP1 ? Can it be started from SP2 ?
I have the SP2 CD now which I did not earlier.

C: is 2000 Pro SP4, running ok, don't want to touch it for now
D: is XP Pro SP1 w/ SP2 updated and BSOD result

Should I be nervous about re-installing on d: and 'accidentally'
c: crash too ?

 

Langa's article is for one drive only, what will happen
if there are multiple, in my case, dual-boot drives, one c:
and another d: ?

One comment says that this won't work, which was
my experience earlier on anothe XP system with
a single drive. 'R' re-installed everything from scratch, period.

Should I be nervous ?

 

Well if you read the article carefully there are 2 Repairs options that will be offered during the method you MUST skip the first option as this will do a complete "reformat". I really can't comment on the other questions as I haven't experienced them yet, so you use this at your own risk, but it has repaired at least 4-5 OS's for me (and friends).

You should use C: to get into your system and back-up whatever important data that you can.

 

You don't want to use the "Recovery Console" to do a repair install...go on past that a couple or few more steps (been a while since I've done it, can't remember the exact steps verbatim) and it will tell you there has been an operating system detected...would you like to attempt to repair it...that is when you tell it yes...or whatever the correct prompt to activate the procedure.

 

So if you look at the link I posted he clearly states on page 2 to "Ignore the first Repair option" but on page 3 he highlights the option that will allow you to repair your damaged Windows "while leaving all data and settings intact", it should allow you to select partitions and I am sure it will only highlight the partition that has the corrupted copy of Windows. After that you should be able to use the SP2 to install al updates. Just try and get as much data of as possible and use this as a last resort (has saved my bacon on 2-3 occasions and friends love me when I have bought their system back from the dead).

 

Thanks.
Yes, I understand that part.
Will it detect both drives c: (win 2000 pro sp4) and
d: (win xp pro sp1 going to sp2) ?

I'm concerned about loosing either one or both drives.
Cheers and ... don't buy gas.

 

Thanks.
That part is clear. What concerns me
is setup being able to detect BOTH drives c: and d:
accurately and not going gung-ho and destroy one
or both drives.

Cheers and ... don't buy gas.

 

Well use it as a last resort but the link seems to imply it will "replace and repair" a damaged OS but it doesn't indicate that it intends to "format" the drive just overwrite the existing files within a damaged Windows OS. Back up your data if you can. It seems like it should work but I certainly are not making "any guarantees" but I have personally used it at least 4-5 times with success (on single partition HDD's).

 

What ever OS Disk you are using (Vista...XP) is the OS it shall detect and be willing to repair.

 

Thanks!
Here's the situation:

C: w/ Win 2000 Pro SP4, working fine, boots fine
D: w/ Win XP Pro SP1, was booting fine, crashed after
an auto update to SP2 which it reported as successful BTW...

Now, if I boot from the Win XP Pro SP2 CD which I have,
XP DOES NOT find my Seagate drives, I have to load the Adaptec ASH-1233 drivers using F6, and after that it says that in either drive C: or D: there is no OS installed (unknown disk)... what a piece of crap software this is !

Look Dear, before you say anything, I have installed literally thousands of OS Unix installations from Solaris to Linux on any machine you can think of and never saw it NOT recognizing an OS or missing a disk type.

What gives ?

 

Thanks!
Here's the situation:

C: w/ Win 2000 Pro SP4, working fine, boots fine
D: w/ Win XP Pro SP1, was booting fine, crashed after
an auto update to SP2 which it reported as successful BTW...

Now, if I boot from the Win XP Pro SP2 CD which I have,
XP DOES NOT find my Seagate drives, I have to load the Adaptec ASH-1233 drivers using F6, and after that it says that in either drive C: or D: there is no OS installed (unknown disk)... what a piece of crap software this is !

Look Dear, before you say anything, I have installed literally thousands of OS Unix installations from Solaris to Linux on any machine you can think of and never saw it NOT recognizing an OS or missing a disk type.

What gives ?

 

Out of date drivers can cause a clash while installing service packs. Make sure you check all your drivers before you install SP2. Personally...I would download and burn to disk the new SP3 and when you reinstall windows tell it to not turn on automatic updates, and then install the SP3 from the disk you made.

 

Thanks !
Drivers are latest, same as used in Win 2000 Pro SP4 and working fine on C:.
I suspect XP cannot find the bridge, it's plain vanilla VIA, but
it may need also those drivers with F6.

Full steam ahead w/ SP3, will keep you posted ....

Cheers,

 

Thanks !
All drivers were latest before D: Win XP Pro SP1 auto update to SP2.

Cheers,

 

So the Adaptec ASH-1233 is for a "Adaptec Ultra ATA Card 1233"?:

http://www.adaptec.com/en-US/support/sata/ata/ASH-1233/

I'm going to suggest that you remove this card and re-seat it and see if this changes anything.

Can you list your Motherboard, HDD, RAM make and models please. We may have to explore another avenue. Also have you been undertaking any OC of the CPU and do you know what your PCI Freq is set to in BIOS?

 

THanks!
Yep, ASH-1233 that's the one. Latest driver was installed prior to the installation. Already re-seated everything, changed cables, etc. Nothing.

Remember, everything was running fine prior to the Win XP SP1 => SP2 auto update on D: that Win XP reported "successful." Remember that D: is in limbo
between SP1 and SP2, the update reboot never completed.

C: boots fine Win 2000 Pro SP4

D: starts to boot, loads NTLDR, then loads the REGISTRY (software.dat),
then loads one page of drivers the last being mup.sys, then flop ... BSOD !!
0x00000050 PAGE_FAULT_IN_NONPAGED_AREA

IMHO Win XP auto update loaded a BAD driver during the auto update
into the driver list or messed up the registry on D: ... or both.

Mobo: Iwill KK-266
C: Seagate 160 GB Win 2000 Pro SP4
D: Seagate 400 MB Win XP SP1/SP2
Both drives are on the ASH-1233
RAM: 1 GB
CPU: Athlon 1.4, no OC

Before you say anything, remember, everything boots fine from C:, and was booting fine from D: before the D: Win XP SP1 ==> SP2 auto update courtesy of BG, the Bug Geek.

Cheers,

 

Have you tried flashing the BIOS just in case there was an issue that could be related to this?

If not...I would give it a shot...you might be surprised. Sounds like there is some kind of conflict with the chipset and the raid controller maybe.

 

THanks!
BIOS was flashed to the latest already.

Remember, this is an auto update Win XP SP1 to SP2,
it crashed at the update completion boot w/ BSOD 0x50.

Cheers,

 

Remember, the SP3 CD is not self boot, cannot boot from the CD.

Read carefully: the SP3 CD requires Win XP to be running to update the system, which in my case is D:
and does not boot.

Remember, Win XP is not running on D:, only Win 2000 Pro on C: and I don't want to
update Win 2000 Pro on C:, I want to leave C: with Win 2000 Pro alone. I can run
the Win XP SP3 CD when Win 2000 Pro is running, but than it will try to update Win 2000
on C: to XP which I don't want to do, instead of trying to update Win XP on D: which is
what I want.

 

So let's be really clear here do you have the OSs' on one HDD with 2 partitions or 2 x OS's on 2 x HDD?

If it is the later then let's unplug C: altogether (remove it from the equation) and DL the XP driver for the Adaptec Ultra ATA Card 1233:

http://www.adaptec.com/en-US/downlo...uctId=ASH-1233&dn=Adaptec+Ultra+ATA+Card+1233

Place that onto a floppy and then try and boot up for the "repair" option, hitting F6 at the appropriate time and see if the driver can be installed and progress to the next step.

I have to agree it probably is a bad driver, file corruption or transcription error in the updating process.

 

Read carefully now:

C: w/ Win 2000 Pro SP4, running fine, nobody touch it, are you crazy !, got my stuff there....

D: w/ Win XP Pro SP1 going to SP2, did not boot after auto-update that BG, the Bug Geek meister urged me to do, and ... did not boot after the auto-update said 'completed successfully.'... Want to preserve if possible, because installed many new programs there that only run on XP, capice ?

Now read carefully: The famous 'repair' Langa option does not exist, on Langa's screen 7 there are only 'D' to delete, 'Enter' to install and 'F3' to exit.
If anyone says it does, please take me to the Twilight Zone with you. :roflmao

Before you say anything be very carefull with your advice: I know 'Enter' will do a complete new install. I did it before many, many, many, many times....

Read more carefully: don't tell me what to do after I told you what I did ...
It's insane. Yes, F6 that's what I did, I explained it to you many times already earlier. :eek