Blue screen if pcAnywhere host is started while Windows Driver Verifier is running (or vice versa)
Last Updated April 23, 2014
Enabled the driver verifier, system will crash with your driver aw_host5.sys, the memory dump analysis is as follows:
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1) Special pool has detected memory corruption. Typically the current thread's stack backtrace will reveal the guilty party. Arguments: Arg1: fffff98008406ff0, address trying to free Arg2: fffff98008406ff4, address where bits are corrupted Arg3: 00000000008d0004, (reserved) Arg4: 0000000000000024, caller is freeing an address where bytes after the end of the allocation have been overwritten
Do not use verifier while host is running, this issue is under review. Symantec has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec is committed to product quality and satisfied customers. There are currently no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. This issue may be resolved in a future major revision of the software at a later time. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns. For information on how to contact Symantec Sales, please refer to the following Web site: http://www.symantec.com/business/index.jsp Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
Windows Vista Windows Server 2008 R2 Windows 7
Imported Document ID: TECH213462
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe