Article ID: 2679102 - View products that this article applies to.
1) TPM Event Error 13 is logged in the Windows System Event Log occurs during boot.
2) Device Manager still shows the TPM Security Device as present.
Example Scenarios where this might be reproduced:
NOTE: The TPM event 13 will occur regardless of whether the TPM is Enabled/Disabled or Activated/Deactivated and only at boot.
1) Enable Physical Presence via BIOS or Jumper (TPM Assert) within server chassis.
2) Perform combination of Enable & Activate or Disabled & Deactivate within the UEFI BIOS Security configuration and install Windows.
3) Boot into Windows.
4) View Device Manager and verify if TPM Security Device instance is present.
5) Go to Windows Event Viewer and note if TPM Event 13 was logged after Disabling & Deactivating or Enabling & Activating the TPM Device from within UEFI setup.
You may also encounter a .NET Framework exception when loading a snap-in or other component from the MMC console.
This is a known issue with Windows Server 2008 SP2 and Windows Server 2012 on some IBM servers that cause a response code from the TPM which triggers the event error during boot.
NOTE: Certain TPM commands are designed to be un-usable when the TPM is disabled or deactivated.
This has been known to occur on the following family of IBM xSeries of Servers: 366, 460, 3850, 3950 and possibly other models.
With Windows Server 2008 R2, when the TPM is Disabled & Deactivated or Enabled & Activated, Windows will not log an TPM Event 13 error.
In both versions of Windows i.e. Windows Server 2008 and Server 2008 R2, TPM presence will be shown in device manager even though it may be Disabled & Deactivated, this is by design.
It is not recommended to disable and prepare the TPM in succession.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2679102 - Last Review: April 16, 2013 - Revision: 9.0