+ Post New Thread
Page 2 of 2 FirstFirst 12
Results 16 to 19 of 19
Windows Thread, Windows Updates - HELP - KB2393802 in Technical; Ahhh OK... Weird... must be conflicting with some other setup/software/driver on these machines of ours then...
  1. #16

    Join Date
    Aug 2005
    Location
    Shropshire
    Posts
    195
    Thank Post
    9
    Thanked 6 Times in 5 Posts
    Rep Power
    15
    Ahhh OK... Weird... must be conflicting with some other setup/software/driver on these machines of ours then

  2. IDG Tech News

  3. #17
    TechSupp's Avatar
    Join Date
    Mar 2007
    Location
    South Yorkshire
    Posts
    1,351
    Thank Post
    239
    Thanked 82 Times in 65 Posts
    Rep Power
    26
    I may have the BSOD butvdefinately the same update problem as on a machine with the problem, started in safe mode, uninstalled it, rebooted and right as rain. Fujitsu esprimo e3550 xp sp3. Not all have either downloaded it or have been affected. Only had half a dozen so far.

  4. #18
    SSFC's Avatar
    Join Date
    Nov 2007
    Location
    Stockton
    Posts
    52
    Thank Post
    30
    Thanked 7 Times in 6 Posts
    Rep Power
    11
    We had the same issue, we ended up removing the patch on each pc. we had to:

    • Boot XP from CD
    • Press R to enter recovery console
    • Wait for keyboard prompt to timeout
    • Press 1
    • Use local password
    • Once in enter the following to remove each patch
    $NTUninstallKB2393802$\spuninst
    BATCH spuninst.txt
    type exit

  5. #19
    Mel
    Mel is offline

    Join Date
    Feb 2011
    Location
    Montreal
    Posts
    1
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    Excellent explanation of failure

    From Symantec web site:

    Results of the investigation

    Thanks for posting the information above. After reviewing a number of memory dump files, our engineering team has determined the following:

    * Windows XP leaves approximately 12,000 bytes of shared stack space for kernel modules to share.
    * Windows provides no way to identify available stack space; it just BSODs when the stack overruns.
    * PGP WDE 10.0.2 and below use approximately 600 bytes of stack space.
    * In the PGP WDE 10.1, we proactively reduced this to approximately 100 bytes of stack space.
    * KB 2393802 leaves less stack space available in the Windows kernel for other kernel modules to use.
    * PGP WDE (pgpwded.sys) is generally the last driver loaded. As a result, when we try to grab our modest stack space, the blue screen will display our driver name as the responsible driver.
    * In our testing, almost every system suffering from this problem used the Intel graphics driver. This uses about 7,000 bytes(!) of stack space. Without this single driver using over half of this available shared resource, there would be plenty of room for the WDE driver.

    The above explains a number of items:

    * Why the problem occurs on some systems but not others
    * Why it occurs without PGP WDE installed
    * Why it occurs most often on Win XP
    * Why we did not see this in our testing

    Our current recommendation is to upgrade to PGP WDE 10.1.1; the lower stack utilization allows it to fit in the reduced area. Thus far, we have not seen a case where this did not fix the problem; the reduction in available stack space from the MS patch must be less than 500 bytes.

    As said in a message above, there is no need to decrypt your disk before upgrading to 10.1, though we do recommend a backup as a basic best practice.

    Also, we have not been able to duplicate this on Windows 7. If you have seen this issue on Win7, please post here and let us know if we can reach out to you to see what's happening.

    Unfortunately, this is a difficult situation for a software vendor like us. We're doing the right thing in minimizing our use of the stack - in fact, we proactively reduced it further before this issue even occurred. However, a combination of other programs' behavior and our position in the driver loading process (probably because we were installed last) makes Windows crash with the finger pointing at us.

    Please leave a note here if you use the Intel graphics driver and have seen this issue. I'll be reaching out to Intel to see if they can update their video driver to minimize stack usage.

    My apologies to anyone affected by this issue.

    Bryan Gillson

SHARE:
+ Post New Thread
Page 2 of 2 FirstFirst 12

Similar Threads

  1. Windows Updates
    By neilmc in forum Windows
    Replies: 12
    Last Post: 3rd June 2010, 10:08 AM
  2. Not getting Windows 7 Updates?
    By Jon88 in forum Windows 7
    Replies: 9
    Last Post: 5th February 2010, 10:57 AM
  3. Windows updates
    By chrbb in forum Windows
    Replies: 1
    Last Post: 22nd April 2009, 08:33 PM
  4. Windows Updates
    By nawbus in forum Windows
    Replies: 11
    Last Post: 8th November 2005, 01:31 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •