Blue Screen after W2K Update Rollup?

Hi,

I just attempted to update a Windows 2000 Server SP4 through Windows Update
including the Update Rollup. After reboot it shows a Blue Screen.

Stop: 0x0000001E (0x0000005,0x804A6467,0x00000000,0x00000000)
KMode_Exception_not_handled
Adress 804A6467 base at 80400000, DateStamp 427b58bb - ntoskrnl.exe


All F8 options don't work. There have never been any problems with the
server which is a file and DHCP Server in an W2K domain.

Does anybody know a solution? Should I run a repair installation from CD? Is
there a known problem with the update rollup?

Thanks a lot,
Axel

--
Axel Voigt
www.schul-support-service.de

"Stop: 0x0000001E" Error Message During Setup
http://support.microsoft.com/kb/161703/EN-US/

Stop 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED
http://www.microsoft.com/resources/d...d_stp_oweb.asp

Windows 2000 Error Codes
http://labmice.techtarget.com/troubl...errorcodes.htm

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User
Microsoft Newsgroups

-------------------------------------------------------------------------------------------

"Axel Voigt" wrote:

| Hi,
|
| I just attempted to update a Windows 2000 Server SP4 through Windows Update
| including the Update Rollup. After reboot it shows a Blue Screen.
|
| Stop: 0x0000001E (0x0000005,0x804A6467,0x00000000,0x00000000)
| KMode_Exception_not_handled
| Adress 804A6467 base at 80400000, DateStamp 427b58bb - ntoskrnl.exe
|
|
| All F8 options don't work. There have never been any problems with the
| server which is a file and DHCP Server in an W2K domain.
|
| Does anybody know a solution? Should I run a repair installation from CD? Is
| there a known problem with the update rollup?
|
| Thanks a lot,
| Axel

Hi,

I encounter exactly the same problem. I wonder if you have found some
solution?

Thanks,

JWC

"Axel Voigt" wrote:

> Hi,
>
> I just attempted to update a Windows 2000 Server SP4 through Windows Update
> including the Update Rollup. After reboot it shows a Blue Screen.
>
> Stop: 0x0000001E (0x0000005,0x804A6467,0x00000000,0x00000000)
> KMode_Exception_not_handled
> Adress 804A6467 base at 80400000, DateStamp 427b58bb - ntoskrnl.exe
>
>
> All F8 options don't work. There have never been any problems with the
> server which is a file and DHCP Server in an W2K domain.
>
> Does anybody know a solution? Should I run a repair installation from CD? Is
> there a known problem with the update rollup?
>
> Thanks a lot,
> Axel
>
> --
> Axel Voigt
> www.schul-support-service.de

nothing yet :-(

some more people seem to have the same problem
http://www.broadbandreports.com/forum/remark,13766832
from there: maybe this is a hint. maybe one could replace ntoskrnl.exe by
recovery console:
"After analysis, I discovered that the Ntoskrnl.exe version is 5.0.2195.1
instead of 5.0.2195.7045 (version installed by the rollup). This apply also
to other system files."

If I find a solution I'll post it here.

Axel



"Blue Screen after W2K Update Rollup?" schrieb:

> Hi,
>
> I encounter exactly the same problem. I wonder if you have found some
> solution?
>
> Thanks,
>
> JWC
>
> "Axel Voigt" wrote:
>
> > Hi,
> >
> > I just attempted to update a Windows 2000 Server SP4 through Windows Update
> > including the Update Rollup. After reboot it shows a Blue Screen.
> >
> > Stop: 0x0000001E (0x0000005,0x804A6467,0x00000000,0x00000000)
> > KMode_Exception_not_handled
> > Adress 804A6467 base at 80400000, DateStamp 427b58bb - ntoskrnl.exe
> >
> >
> > All F8 options don't work. There have never been any problems with the
> > server which is a file and DHCP Server in an W2K domain.
> >
> > Does anybody know a solution? Should I run a repair installation from CD? Is
> > there a known problem with the update rollup?
> >
> > Thanks a lot,
> > Axel
> >
> > --
> > Axel Voigt
> > www.schul-support-service.de

Any news on this post? i have the exact same problem with the exact
same error numbers

Try uninstalling the Rollup Pack

reboot in recovery console
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"
exit the recovery console

Let us know if this works,

Fritz



"chrism" wrote:

> Any news on this post? i have the exact same problem with the exact
> same error numbers
>
>

Hi Fritz,
I have the same problem, I have followed your intruction and its work.
I was wondering, will the server install the Rollup Pack back after
restart. Thanks.

Fritz Burnell wrote:
> Try uninstalling the Rollup Pack
>
> reboot in recovery console
> 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"
> exit the recovery console
>
> Let us know if this works,
>
> Fritz
>
>
>
> "chrism" wrote:
>
> > Any news on this post? i have the exact same problem with the exact
> > same error numbers
> >
> >

Glad to hear that this got you up and running. When I get time I am going
to try the to apply the MS05-18 Hotfix
http://support.microsoft.com/default...b;en-us;898114 to see if it
solves my problem. MS05-18 is part of the rollup.

I have Automatic Updates turned off, so I manually decide which updates to
apply. Make sure you have automatic updates turned off on the system in
question.

Fritz

"" wrote:

> Hi Fritz,
> I have the same problem, I have followed your intruction and its work.
> I was wondering, will the server install the Rollup Pack back after
> restart. Thanks.
>
> Fritz Burnell wrote:
> > Try uninstalling the Rollup Pack
> >
> > reboot in recovery console
> > 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"
> > exit the recovery console
> >
> > Let us know if this works,
> >
> > Fritz
> >
> >
> >
> > "chrism" wrote:
> >
> > > Any news on this post? i have the exact same problem with the exact
> > > same error numbers
> > >
> > >
>
>

yep, it worked for me as well. server is up and healthy again :-)

Thank you!!!

Axel

--
Axel Voigt
www.schul-support-service.de


"Fritz Burnell" schrieb:

> Try uninstalling the Rollup Pack
>
> reboot in recovery console
> 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"
> exit the recovery console
>
> Let us know if this works,
>
> Fritz
>
>
>
> "chrism" wrote:
>
> > Any news on this post? i have the exact same problem with the exact
> > same error numbers
> >
> >

Fritz,

We had the same issues after the latest Windows updates yesterday AM.
We followed you 'uninstalling the Rollup Pack' instrustions and got our
server back up.(I had minor issues with getting my required scsi/raid
drivers to diskette and a minor Admin password issue-we installed AD
about one month ago.....)
Thank you for your posting!!!!!
yanky