Event ID 13 and event ID 516 may be logged every 40 minutes after a computer that is running Windows Server 2008 or Windows Vista Service Pack 1 resumes from sleep


Consider the following scenario:
  • You are using a Trusted Platform Module (TPM) chip on a computer that is running Windows Server 2008 or Windows Vista Service Pack 1 (SP1).
  • You put the computer to sleep, and then you resume it from sleep.
In this scenario, the following errors may be logged in the System log every 40 minutes:
Event ID: 13

Event Source: TPM

Event Type: Error

Event Description: The device driver for the Trusted Platform Module (TPM) encountered a non-recoverable error in the TPM hardware, which prevents TPM services (such as data encryption) from being used. For further help, please contact the computer manufacturer.

Event ID: 516

Event Source: TBS

Event Type: Error

Event Description: An error occurred while communicating with the TPM. The driver returned 0x8007045d.
The TPM driver and the TPM Base Services (TBS) log these errors when they try to obtain a random number from the TPM chip for the Windows operating system. The operating system uses this random number as an additional source of entropy when the operating system’s cryptographic methods generate random numbers.

Additionally, if the TBS sends other commands to the TPM chip after the computer resumes from sleep and if the operating system receives a "TPM_NEEDS_SELFTEST" response from the TPM, the operating system may be unable to use the TPM chip to generate random numbers for additional entropy.


When the TPM chip resumes from sleep, it must receive a command to continue a self-test before it is ready to process other commands. If the TPM chip does not receive the self-test command before the computer sends other commands to the TPM chip, the TPM chip generates an error message that states that the TPM chip needs a self-test. On many computers, the system Basic Input/Output Settings (BIOS) will issue a command to the TPM chip to continue the self-test. Computers that have the symptoms that are mentioned in this article have a system BIOS that does not issue a command to continue the self-test on the TPM chip.

Every 40 minutes, Windows Server 2008 and Windows Vista SP1 try to use the TPM chip to generate a random number. When the TPM chip returns an error for reasons other than the TPM chip being deactivated or disabled, the TPM driver and TBS log these errors in the System log.

When this issue occurs, the operating system cannot use the TPM chip to generate random numbers for entropy. This behavior causes the operating system to use the same mechanisms to generate random numbers for cryptographic methods that are used in versions of Windows Vista that are earlier than Windows Vista SP1 and on systems that do not have a TPM chip.

More Information

You can safely ignore these errors because Windows will fall back to the same mechanisms that are used to generate random numbers on systems that do not have a TPM chip.


For information about the TPM specification, see the Trusted Computing Group (TCG) TPM Specification, Version 1.2 and the TCG PC Client TPM Interface Specification, Version 1.2. To do this, visit the following Trusted Computing Group Web site:Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.