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. 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.Īs 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.Īlso, we have not been able to duplicate this on Windows 7. Our current recommendation is to upgrade to PGP WDE 10.1.1 the lower stack utilization allows it to fit in the reduced area. Why it occurs without PGP WDE installed.Why the problem occurs on some systems but not others.Without this single driver using over half of this available shared resource, there would be plenty of room for the WDE driver. This uses about 7,000 bytes(!) of stack space. In our testing, almost every system suffering from this problem used the Intel graphics driver.As a result, when we try to grab our modest stack space, the blue screen will display our driver name as the responsible driver. PGP WDE (pgpwded.sys) is generally the last driver loaded.KB 2393802 leaves less stack space available in the Windows kernel for other kernel modules to use.In the PGP WDE 10.1, we proactively reduced this to approximately 100 bytes of stack space.PGP WDE 10.0.2 and below use approximately 600 bytes of stack space.Windows provides no way to identify available stack space it just BSODs when the stack overruns.Windows XP leaves approximately 12,000 bytes of shared stack space for kernel modules to share.After reviewing a number of memory dump files, our engineering team has determined the following: Thanks for posting the information above. Once that's done, everything works again. The only solution we've found so far is to log in by whatever means necessary and uninstall the patch. If the original user attempted to log in, the computer would blue screen. The new user could log in at the BootGuard screen with no problems. The original user could no longer successfully log into the computer however, a user who had never logged into that computer before could log in (after using a WDRT) successfully with no ill effects. A WDRT was provided which allowed the user to boot to a Windows GINA where they logged in with their network ID and password, then the computer would blue screen and reboot again. The user would log in at the BootGuard screen and into Windows (XP sp3) as per normal however, after the first reboot after that, the user's network password no longer worked at the BootGuard screen. Some of our users inadvertently applied the patch KB2393802 and after doing so, started having very strange behavior with their encrypted drives.
0 Comments
Leave a Reply. |