Re: Fix - NTOSKRNL.EXE stop after Update Rollup 1


sumguyb......YOU ARE DA MAN!!!!!!
You just saved my weekend (and my ***, since my boss had to come in to
help me, found your post just as we were getting started to resotre
backups..)....same problem....same fix...


Eric wrote:
> *Thank-you for this!!!
> We approved an auto-update on our win2000 backup AD controller and
> ended up
> with the bluescreen kmode...stop...ntoskrnl.exe.
> We actually did a parrallel install and were in the process of
> rebuilding
> the server when I found your post. It worked like a charm - this
> update
> rollup is bad news on domain controllers.
>
>
> "sumguyb@xxxxxxxxx" wrote:
>
> > Fix is below. First the situation: I installed update rollup on
> 20
> > PCs. Worked fine. Installed it on the domain controller and it
> blue
> > screened. Pow! Gone.
> >
> > Went to Google and found 6 threads from this evening with the same
> > problem. Worked on PCS and killed the DC. So why does Microsoft
> still
> > have the patch out there?
> >
> > Here is the solution:
> > * Reboot off you floppies with your 2000 CD in the tray.
> > * If you have odd SCSI controllers press F6 when prompted on disk 1
> and
> > after Disk 2 it will ask for the driver disk.
> > * Choose to repair the installtion and then choose recovery
> console.
> > If it tells you there is no drive, you needed the driver disks
> above.
> > * cd to your windows directory
> > * cd $NtUpdateRollupPackUninstall$
> > * cd spuninst
> > * do a dir and make sure there is spuninst.txt file in there
> > * use the command "batch spuninst.txt" It runs and the first 5 or
> so
> > messages may say Access Denied. That was OK for me.
> > * exit the recovery console by typing exit.
> >
> > *



--
cheezeburger50
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message1743217.html

.