Update causing BSoD for some XP users

Update causing BSoD for some XP users

Summary: Reports are coming in that an update released this week by Microsoft for the Windows XP is causing problems for some users.

SHARE:

[UPDATE: Microsoft has withdrawn the update KB977165 from the Windows Update for this week. I've updated my patch removal instructions below to remove this update first.]

Reports are coming in that an update released this week by Microsoft for the Windows XP is causing problems for some users.

The problem is particularly nasty in that it causes a BSoD (Blue Screen of Death) with the error "PAGE_FAULT_IN_NONPAGED_AREA" and then sends the system into an endless cycle of reboots.

So, which patch is causing the problem? At present we don't know, so the best fix it to uninstall all of the updates that were applied during this month's Patch Tuesday.

If you're suffering from this problem then there is a fix, albeit a convoluted one.

  1. Boot your XP system from the CD/DVD and enter the Recovery Console.
  2. At the Command Prompt type: CHDIR $NtUninstallKB977165$\spuninst
  3. At the Command Prompt type: BATCH spuninst.txt
  4. At the Command Prompt type: systemroot
  5. While step 2 removes the most likely culpit, if you continue to experience problems repeat steps 2 to 4 but replacing KB977165 in step 2 with each of the following in turn: KB978706 KB978262 KB978251 KB978037 KB977914 KB975713 KB975560 KB971468
  6. When you've finished, type the following: exit

The above represents the best fix that I've been able to find for this problem.

Any one out there affected?

Topics: Windows, Microsoft, Operating Systems, Software

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

55 comments
Log in or register to join the discussion
  • Update causing BSoD for some XP users

    Is it really Microsoft this time or another case of people wanting to blame Microsoft? I'm going with the latter. Its got to be these obscure hardware configurations people have, not properly tested and not on Microsoft's WHQL. Plus its only a few rare cases anyway, nothing people should be upset about.
    Loverock Davidson
    • Flamebait response

      Ok, I feel like toasting someone today so here goes...
      Are you that totally brainwashed by MS FUD that you cannot see that an MS supplied patch is at fault, not some obscure hardware. If the obscure hardware was working before the patch, it should continu after the patch. Obviously (at least to anyone capable of breathing) the fault here is clearly in Microsoft's camp.
      Then again, someone of your upstanding track record cannot possibly be wrong (do you get this ironie at all?). Face the facts Lovey, MS messed up.
      GrimmReaperSound
      • "MS messed up" ... or did they?

        Shall we NOT proclaim someone as guilty before we assess all the facts?

        WHAT is crashing? A driver? OS Kernel code?

        WHERE is the code crashing?

        WHY is the code crashing? Code bug? Hardware failure? Memory corruption? Buggered motherboard?

        WHO wrote the code? If it's a driver issue, chances are that MS did NOT write the code.

        WHO is affected by this code and WHY (and how many)?

        Adrian: I am somewhat troubled by this post: you don't cite your sources (links to crash reports?), you don't know WHAT is crashing and yet you rush out guidance on how to fix the issue by uninstalling some random set of patches?

        How about you warn us that reports are coming in, link to the sources and wait until someone somewhere is able to isolate what's going on and what the correct remedies are before potentially having users screw up their machines any more than they already are?
        de-void-21165590650301806002836337787023
        • Ignore Adrian's instructions: Here's the solution to KB977165

          http://social.answers.microsoft.com/Forums/en-US/vistawu/thread/73cea559-ebbd-4274-96bc-e292b69f2fd1?prof=required

          Look for responses by Kevin Hau & Pa Bear, e.g.:

          @everyone posting in this thread:

          1. Uninstalling KB977165 will automatically restore the previous versions of ntkrnlpa.exe and ntoskrnl.exe so there's no need to find "a way to replace them."

          2. That being said, the newer versions of ntkrnlpa.exe and ntoskrnl.exe address the very serious & currently-being-exploited security vulnerability described in MS10-015 so you really do not want to avoid this update! Instead, open a free support incident per my previous reply.

          3. Encountering a STOP error (e.g., 0x00000050) after installing this update could mean that your computer's already been compromised by the security vulnerablity addressed by MS10-015, yet another reason to open a free support incident!

          Microsoft can't fix something if you don't tell them about it! Please open a free support incident ASAP so they know there are "dead bodies!"

          For home users, no-charge support is available by calling 1-866-PCSAFETY (and/or 1-866-234-6020 and/or 1-800-936-5700) in the United States and in Canada or by contacting your local Microsoft subsidiary. There is no-charge for support calls that are associated with security updates. When you call, clearly state that your problem is related to a Security Update and cite the update's KB number (e.g., KB999999).

          Or you can...

          Start a free Windows Update support incident request:
          https://support.microsoft.com/oas/default.aspx?gprid=6527

          Consumer Security Support home page & Microsoft Update Solution Center also offer support options
          https://consumersecuritysupport.microsoft.com/
          http://support.microsoft.com/ph/6527#tab3

          For more information about how to contact your local Microsoft subsidiary for security update support issues, visit the International Support Web site: http://support.microsoft.com/common/international.aspx

          For enterprise customers, support for security updates is available through your usual support contacts.
          de-void-21165590650301806002836337787023
        • Microsoft did NOT mess up...

          Call it what it is... This is just the first of many gentle MS nudges to get people off XP and onto Windows 7...

          Those of us who have supported Windows since the early days know this is business as usual for MS... MS doesn't want people using XP... They want users on Windows 7... What better way to accomplish this than help XP become a little less desirable... Windows ME and Vista are the only releases they haven't done this for.... But they might do it for Vista at some point in the future.
          i8thecat
      • Rhetorical question maybe?

        [i]Are you that totally brainwashed by MS FUD that you cannot see that
        an MS supplied patch is at fault...?[/i]

        In the case of LD, and many of the other MS bigots here, YES.

        Having to do the following to FIX a patch:
        [i]Boot ... from the CD/DVD and enter the Recovery Console.
        (that would be the retail copy DVD I have to buy???)
        At the Command Prompt type: CHDIR
        $NtUninstallKB978706$\spuninst
        At the Command Prompt type: BATCH spuninst.txt
        At the Command Prompt type: systemroot
        Now repeat steps 2 to 4 but replacing KB978706 in step 2 with each of
        the following in turn:
        KB978262, KB978251, KB978037, KB977914
        KB977165, KB975713, KB975560, KB971468
        When you?ve finished, type the following: exit[/i]
        is truly scary; so much for LD always raving on about always having to
        use the command line in Linux!

        Funny, I only have to click "Apply" in Ubuntu and it just works.

        Fascinating how MS (and its fanboys) always blame the user when
        something goes wrong - as it inevitably does.
        rahbm
        • No need for the CLI in Windows either.

          Oh...that's right...you're referring to an eight year and two generations old OS.

          [i]Fascinating how MS (and its fanboys) always blame the user when something goes wrong - as it inevitably does.[/i]

          Has anybody done that?
          ye
          • Sigh

            [i]No need for the CLI in Windows either[/i]

            Really? Then Windows Power Shell would be pointless.

            In any case, your heading is just a red herring and simply an attempt
            at deflection. I said nothing about a CLI and Windows, I was
            commenting on how LD relentlessly claims that Linux needs to be
            continually recompiled and that everything must be done at the CLI,
            and that [i]even if that were true,[/i] it would be trivial compared to
            the repair process needed for this MS patch.

            As for the blame game, this Talkback is [i]riddled[/i] with MS fanboys
            either blaming the user or excusing Microsoft. Some are proudly
            exhorting that none of their machines is affected, implying that there
            is no problem. By the same logic, because [i]I[/i] don't have cancer,
            then there is no such thing.

            No software is perfect; so why do the MS fanboys and bigots fly into
            such a frenetic rage whenever anybody dares to suggest that this fact
            of life may apply to Windows, as it so often has over the years?

            Really, it isn't worth getting ulcers about; MS won't thank you for it.
            rahbm
    • What a difference a few hours makes..

      Going with the latter would be a mistake, as would blaming "obscure hardware configurations" and stating that it's "only a few rare cases". 11 of 34 machines on my network (none of which have exotic non-WHQL hardware) were hit this morning on the first boot after the update was applied. It's a widespread problem, enough so that MS stopped offering the MS10-015 KB977165 update some time before 4pm on 11 Feb.

      It's usually best to sit on your hands and refrain from comment until you have data to support your opinion.
      Werecow
      • re: What a difference a few hours makes..

        [i]11 of 34 machines on my network (none of which have exotic non-WHQL hardware) were hit this morning on the first boot after the update was applied.[/i]

        For a counterpoint, none of the 500+ machines that were patched via WSUS on Wednesday and Thursday have had this problem.
        rtk
        • So what?

          Are you trying to imply that the problem is just a figment of some
          people's imagination unless it affect every single XP machine?
          rahbm
          • re: So what?

            No, stop trying to put words in my mouth. I'm saying there's more to this than just the update.

            And looking at the new information available, I'll happily imply that I didn't experience any problems because none of my machines were infected with a rootkit.
            rtk
    • Testing for WHQL?

      Where is the Microsoft program I can run to generate a report of the hardware currently being used?
      pwatson
    • NO it's not the user

      I've had the BSOD; misreads to external drives
      showing empty files; sound comes and goes; slower
      internet; slower program response.
      Are you a troll for Microsoft?
      easysoul
  • 7 reasons? How about 1 NOT to stick with XP...

    LOL! Adrian, you crack me up. First you post a lengthy article on why to keep XP. Then, you show us the main reason to NOT KEEP XP!
    Narg
    • The main one?

      I don't think it's BSOD. We don't know how widespread this one is.
      Lester Young
  • Hush, now

    We all know XP is still better than Windows 7, even if you can't boot it up.

    Edit: Meant for Narg's post above this one.

    Carl Rapson
    rapson
  • RE: Update causing BSoD for some XP users

    Here again customers need not worry about viruses or Trojans on Window based computer because Microsoft does a good job of screwing up your operating system with their lack of intelligence.

    Yes, they posted a fix, but who ever gets a Recovery CD these days, nobody, why, because Microsoft will not allow manufacturer to ship them to customers.

    Who has a CD drive on a Netbook, nobody!

    Dammit, its time for a Class-Action Lawsuit against Microsoft!
    b93950
    • Wow, what have you been smoking? ...

      "but who ever gets a Recovery CD these days, nobody, why, because Microsoft will not allow manufacturer to ship them to customers."

      Nobody gets a recovery CD anymore because the bits are included on the hard drive in a recovery partition. Read the documentation that came with your PC and LEARN HOW TO USE IT.

      If you are too stupid to make a CD or DVD, contact the manufacturer of your PC and request one, they will be happy to mail you one (for a price). After all, the only reason they didn't send you one in the first place was to save money, not because MS wouldn't let them.

      Netbooks are set up the same way. YOU KNEW it didn't have a CD or DVD drive when you bought it, too, so it is YOUR fault, not Microsoft's.

      If you want to bitch to someone, go look in the mirror and scream away, loser. :-(

      Sorry people, some people just get under my skin.
      babyboomer57
      • Crap, I'm almost out of my BP meds ... Grrrrrrr .... (NT)

        nt
        babyboomer57