Blue Screen after W2K Update Rollup?

Discussion in 'Windows Update' started by Axel Voigt, Jul 5, 2005.

  1. Axel Voigt

    Axel Voigt Guest

    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, Jul 5, 2005
    #1
    1. Advertisements

  2. "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/...Windows/XP/all/reskit/en-us/prmd_stp_oweb.asp

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

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

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

    :

    | 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
     
    Carey Frisch [MVP], Jul 5, 2005
    #2
    1. Advertisements

  3. Hi,

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

    Thanks,

    JWC
     
    Blue Screen after W2K Update Rollup?, Jul 6, 2005
    #3
  4. Axel Voigt

    Axel Voigt Guest

    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
     
    Axel Voigt, Jul 6, 2005
    #4
  5. Axel Voigt

    chrism Guest

    Any news on this post? i have the exact same problem with the exact
    same error numbers
     
    chrism, Jul 6, 2005
    #5
  6. 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
     
    Fritz Burnell, Jul 7, 2005
    #6
  7. Axel Voigt

    fookeongc Guest

    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.
     
    fookeongc, Jul 11, 2005
    #7
  8. 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.aspx?scid=kb;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
     
    Fritz Burnell, Jul 11, 2005
    #8
  9. Axel Voigt

    Axel Voigt Guest

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

    Thank you!!!

    Axel
     
    Axel Voigt, Jul 13, 2005
    #9
  10. Axel Voigt

    yanky Guest

    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
     
    yanky, Jul 13, 2005
    #10
  11. Axel Voigt

    sumguyb Guest

    This worked for me. Why do they still have this patch out there?
     
    sumguyb, Jul 20, 2005
    #11
  12. Axel Voigt

    Don Guest

    All,

    The fix described in this Email thread worked for me as well. But, there may
    be a slightly easier and/or more preferable way. See Article ID 891861
    "Update Rollup 1 for Windows 2000 SP4" dated today 7/30/2005 (revison 8.0).
    Apparently it may be sufficient to replace just Scsiport.sys from the
    uninstall backup directory rather than running the 'spuninst.txt' batch file
    as this Email thread recommends. This may apply only to folks with "an older
    non-Plug-and-Play ISA, EISA, or Micro Channel Architecture (MCA) SCSI
    controller" as per the article. I haven't actually tried it, as I saw this
    new posting of KB891861 just after I backed out the whole SVP4 rollup 1 per
    instructions later in this Email thread.

    One other thought. I'm an IT guy, not a Windows sys admin. But, after I got
    my machine back and fully booted up (after running the batch file
    'spuninst.txt' per this Email thread), I went to "Add/Remove" programs to
    uninstall the Update Rollup 1 for Windows 2000 SP4. This performs a bunch of
    file copies (presumably same as 'spuninst.txt'- perhaps actually using the
    same script), but also synchronizes the registry and does some cleanup. This
    may be a useful/important step after performing the manual rollback using
    'spuninst.txt'? Those of you who know are encouraged to advise.

    Thanks to all of you who posted and helped guys like me save our machines.

    One other contribution: In this thread Fritz posted that he might try
    applying the MS05-18 Hotfix (which is part of the rollup in question). While
    my machine was KO'd by the full rollup, it seems to tolerate the KB890859
    hotfix (MS05-18: Vulnerabilities in Windows kernel could allow elevation of
    privilege and denial of Service).

    Don
     
    Don, Jul 30, 2005
    #12
  13.  
    David F. Sage, Aug 4, 2005
    #13
  14. Axel Voigt

    andy Guest

    Hmm... I tried this as described in KB article 875350, but when I try to run
    uninst.txt as a batch, I get an "access is denied" message for EVERY
    operation in the file. this is not the behavior that is described as
    'normal'. any ideas?
     
    andy, May 14, 2006
    #14
  15. Axel Voigt

    Melissa Guest

    I have a similar problem. We updated a Windows 2000 Server SP4 through
    Windows Update as well, which included the Update Rollup 1. After reboot, it
    started windows, started networking connections, and Blue Screens with:

    STOP 0x00000027 RDR_FILE_SYSTEM Error Message

    I enabled bootlogging and I've read the Windows Update log, which said the
    rollup didn't install and to run it again. The rollup didn't install
    properly before the operator booted. (Sometimes automation creates too much
    trust in some people)

    By the way, I couldn't run the rollup again because I can't get on the
    network. I tried to download it separate, and Microsoft's Genuine Product
    Validator came into play and told me three systems weren't valid. (yes, they
    are, they've been been from virgin installs for about 5 years but let's blame
    Dell and Gateway both anyway for non-genuine products). Couldn't download
    it. I think that problem is because the systems are secured following
    industry standards.

    There isn't a $NTrolluppackinstall folder. The rollup appears in the
    Control Panel/Add and Remove Software panel, but when we tried to uninstall,
    it said it really wasn't there and did we want them to remove it from the
    list.

    I've disabled services, drivers, etc. Can only boot into safe mode. I'm
    down to thinking I have to reinstall the operating system and reconfigure a
    production web server. Didn't have problems on two other systems... but I
    haven't checked them indepth yet. At least they boot.

    I found this tonight in an article at Microsoft Watch. Wish I had read the
    article before the update appeared in the Windows Update list!!

    "If the systems are not running current drivers, the systems may blue screen
    and the uninstall process for the rollup will not be available," said Keith
    Colvin, president of Everyday IT, a systems and networking consultancy. "They
    indicated that they best way to get around this was to install the rollup
    update in safe mode."

    So, why didn't they indicate the possible problem in Windows Update? In the
    past, they stop any downloads that conflict. It seems prudent at the Windows
    Update alert for driver checks, safe mode, etc., before any attempt.

    If anyone has a solution for me.. please let me know. In the meantime, I
    will try to piece some files away from another web server, seemingly
    identical..... maybe even try the repair from the CD.
     
    Melissa, Jun 20, 2006
    #15
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.