A workaround for the Windows Update lockup problem!

Discussion in 'Windows Update' started by OriginalGorrilla, May 30, 2007.

  1. Don't know why it works, but I set my display adapter to the lowest possible
    resolution (640x480 - 16 colors) and Windows Update works again! (The
    adapter is on the Intel motherboard...not a NVidia). Since the machine I was
    having the problem with spent all night downloading and updating all the
    patches it missed, I haven't yet had a chance to reset the display back to
    something useful, but, at least I was able to update!
     
    OriginalGorrilla, May 30, 2007
    #1
    1. Advertisements

  2. Since the processor [CPU] also shares memory with the onboard video
    adapter, the most likely cause of the BSODs is that enormous amounts of
    CPU cycles are being taken up by svchost/wuauclt/wmiprvse

    Suggest you download and save :

    Windows Update Agent 3.0 For XP and Vista (32 bit)
    http://download.windowsupdate.com/v7/windowsupdate/redist/standalone/WindowsUpdateAgent30-x86.exe

    Update for Windows XP (KB927891)
    http://www.microsoft.com/downloads/...CD-A0B9-497E-8A89-404327772E5A&displaylang=en

    Close the browser
    Install WindowsUpdateAgent30-x86.exe first, then install
    WindowsXP-KB927891-v3-x86-ENU.exe
    Restart the system

    Now try Windows Update with the desired screen resolution
    Did that work ?


    MowGreen [MVP 2003-2007]
    ===============
    *-343-* FDNY
    Never Forgotten
    ===============
     
    MowGreen [MVP], May 30, 2007
    #2
    1. Advertisements

  3. I had already installed the new update agent and the KB927891 patch before I
    tried changing screen resolution. I did get a chance to try setting the
    display back to normal last nite...and update hangs again. The only way
    update works is with 640x480 - 256 colors. The onboard video is an Intel
    82810e...both the Intel site and microsoft have drivers dating from 2002 or
    so. Tried them both with no success. Tonights magical trick will be to load
    a standard driver and see where that gets me...

    So, at any rate, it seems like the svchost cycle hog is the real
    problem...maybe I'll try reducing its priority...

     
    OriginalGorrilla, May 31, 2007
    #3
  4. I expect that this video system steals RAM from the system memory to use as
    video RAM. If so, it will steal a different amount of RAM for each
    resolution, thus causing Windows components to load at different absolute
    addresses for the different video resolutions.

    This suggests that you might have faulty RAM hardware, and it is affecting
    Windows differently according to video resolution.

    I suggest that you try running a vigorous RAM test.
     
    Robin Walker [MVP], May 31, 2007
    #4
  5. I appreciate the suggestion...and, in truth, I began having this problem when
    I increased the system's ram from 128meg to 512meg, so I have already run
    some memory diagnostics...no errors reported.

    ....my next magical trick will be to put the old ram back, and see what
    happens...

    but...in light of so many other people having the same problem, I wonder if
    it might not be something in the update agent's code that is using a bad
    pointer....
     
    OriginalGorrilla, May 31, 2007
    #5
  6. OriginalGorrilla

    RDHampton Guest

    I have a similiar problem... my screen resolution will not adjust above
    800x600 after udating to SP2 for XP home ed. and I'm using the same graphics
    card, Intel 82810e, and have 512Megs of Ram (old system). However, my
    troubles has nothing to do with my RAM. I suspect it's the generic Plug&Play
    driver within the SP2 update. Please, be gentle w/ replies, as I am not an
    IT specialist.
     
    RDHampton, Oct 2, 2007
    #6
    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.