The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Windows Update causing XPS 15 to crash (BSOD)

    Discussion in 'Dell XPS and Studio XPS' started by wetcardboard, Jun 17, 2011.

  1. wetcardboard

    wetcardboard Notebook Consultant

    Reputations:
    8
    Messages:
    246
    Likes Received:
    0
    Trophy Points:
    30
    This seems very odd to me, but the latest Windows Update is causing my PC to not boot into Windows. It gets to the "Starting Windows" screen and then flashes to the BSOD and starts doing a memory dump. I can tell WU is the problem because I have had to do System Restore from the Dell recovery options twice, both times going back to the time prior to installing the updates and then Windows booted fine. Here is what Windows Update is wanting to install:

    [​IMG]

    Uploaded with ImageShack.us

    The optional update not shown is Microsoft Security Essentials, and there's no way I'm installing that.

    Any ideas? Anyone else having this problem? Thanks!
     
    wetcardboard, Jun 17, 2011
    #1
  2. J.P.@XoticPC

    J.P.@XoticPC Company Representative

    Reputations:
    237
    Messages:
    595
    Likes Received:
    0
    Trophy Points:
    30
    Sometimes when an update is causing you problems, you can jump over to Microsoft's website and download the stand-alone installer, and that way you can install one after the other until you find the problematic update.

    For instance, a quick google search for the first update on that screen reveals this link:

    Download Details - Microsoft Download Center - Security Update for Windows 7 (KB2476490)

    Try 'em one-by-one and you may be able to deduce which update causes the issue.
     
    J.P.@XoticPC, Jun 17, 2011
    #2