-Article ID: 2535094 - Last Review: December 9, 2014 - Revision: 8.0
Server stops responding when you lock or unlock files on a network by using the SMB2 protocol in Windows.
Symptoms:
A computer that is running Windows 7, Windows Server 2008 R2, Windows Vista or Windows Server 2008 stops responding when it uses the Server Message Block Version 2 (SMB2) protocol to lock or unlock files on a network.
If you enable the special pool feature on the computer, you receive a Stop error message that resembles the following:
Code:
STOP: 0x000000D5 ( Parameter1 , Parameter2 , Parameter3 , Parameter4 )
DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
Notes
- The parameters in this Stop error message vary, depending on the configuration of the computer.
- Not all "0x000000D5" Stop errors are caused by this issue.
Cause:
This issue occurs because of a race condition between the NTFS file system driver (Ntfs.sys) and the SMB2 server driver (Srv2.sys).
When the race condition occurs, a structure in NTFS file system driver is released prematurely. Therefore, the issue that is described in the "Symptoms" section occurs when the Ntfs.sys driver accesses the released structure.
Review and request hotfix:
Server stops responding when you lock or unlock files on a network by using the SMB2 protocol in Windows
-----------------------------------------------------------------------------------------------------------
-Article ID: 2965917 - Last Review: December 9, 2014 - Revision: 2.0
A computer freezes during startup after filter drivers are installed in Windows 7 or Windows Server 2008 R2.
Symptoms:
Consider the following scenario:
- You have a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
- You install some third-party filter drivers. For example:
- Symantec Endpoint Protection
- McAfee Data Loss Prevention Endpoint
- McAfee Endpoint Encryption for Files and Folders
- McAfee Agent
In this scenario, the computer will freeze when it next tries to startup.
Cause:
This issue occurs because there is a deadlock between Windows NT kernel and the fltmgr.sys file.
Workaround:
To work around this issue, start the computer in safe mode, and then uninstall the filter drivers.
Review and request hotfix:
A computer freezes during startup after filter drivers are installed in Windows 7 or Windows Server 2008 R2
------------------------------------------------------------------------------------------------------------
-Article ID: 3014300 - Last Review: December 9, 2014 - Revision: 1.0
CredUIPromptForWindowsCredentials API does not select the smart card logon certificate from the pvInAuthBuffer parameter.
Symptoms:
Assume that you use a smart card in which multiple smart card logon certificates are stored. Programmatically, you want to preselect one of the stored smart card certificates in the credential information dialog box when you call the CredUIPromptForWindowsCredentials API. To do this, you populate the pvInAuthBuffer input parameter of the CredUIPromptForWindowsCredentials API with the credential of the certificate that you want to preselect. This issue is that the CredUIPromptForWindowsCredentials API does not preselect the certificate that is supplied in the pvInAuthBuffer parameter. Instead, the default certificate that is stored in the registry is preselected.
Cause:
If the credential that is supplied in the pvInAuthBuffer parameter does not match the first certificate that is stored in the smart card, the default certificate that is stored in the registry is used instead. The default certificate is located in the following registry subkey:
Code:
HKLM\Software\Microsoft\Windows\CurrentVersion\Authentication\Credential Providers\{8bf9a910-a8ff-457f-999f-a5ca10b4a885}\SessionData\1\Certificate
Note The default certificate is stored in the registry subkey after a previous successful smart card logon.
Review and request hotfix:
CredUIPromptForWindowsCredentials API does not select the smart card logon certificate from the pvInAuthBuffer parameter
----------------------------------------------------------------------------------------------------------
-Article ID: 3012696 - Last Review: December 9, 2014 - Revision: 1.0
An IPP printer stops responding after you cancel a print job from PowerPoint in Windows 7 or Windows Server 2008 R2.
Symptoms:
Consider the following scenario:
- You have a computer that is running Windows 7 or Windows Server 2008 R2.
- You have Microsoft Office 2010 or one of its individual products, such as Microsoft Word or Microsoft PowerPoint, installed.
- You have an Internet Printing Protocol (IPP) printer installed that is using a PCL 6 Unidrv-based printer driver.
- You print a large file to the IPP printer, and then you cancel the print job within the Microsoft Office application.
In this scenario, you notice that the print job seems to cancel successfully. However, the print job status display in the print queue properties of the IPP printer indicates an error. Although the status changes from
Spooling to
Printing as expected, the display does not change again for a long time. After this delay, a status of
Error is shown. You may also notice that the print device stops responding and is inaccessible for any printing until it times out and returns to
Ready status.
Review and request hotfix:
An IPP printer stops responding after you cancel a print job from PowerPoint in Windows 7 or Windows Server 2008 R2
-----------------------------------------------------------------------------------------------------------
