Ошибка 15 tpm windows 10

Both my wife and I have Asus ROG Crosshair VIII Hero (X570) motherboards (Asus BIOS 1302) with AMD Ryzen 7 3700X processors (AMD Chipset Software 2.04.28.626) that use the CPU’s fTPM ability set up in the BIOS.  Occasionally, in the Windows 10 Event Viewer, we both get Event ID 12 and 15 events about TPM Device Driver Errors (I’ll include an example, below).  At a guess, they might be happening upon waking from Sleep.  My wife has also run into problems with her Windows 10 PIN when that happens and has to reboot to get it to work — I’m assuming the PIN is using the TPM for validation.  I have no idea where to report this, so I thought I’d try here to see if anyone else is seeing it.

Log Name:      System
Source:        TPM
Date:          6/19/2020 7:48:32 PM
Event ID:      12
Task Category: None
Level:         Error
Keywords:      
User:          N/A
Computer:      WIN10-DAVE-X570
Description:
The device driver for the Trusted Platform Module (TPM) encountered an error in the TPM hardware, which might prevent some applications using TPM services from operating correctly.  Please restart your computer to reset the TPM hardware.  For further assistance on this hardware issue, please contact the computer manufacturer for more information.
Event Xml:
<Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
  <System>
    <Provider Name=»TPM» Guid=»{1b6b0772-251b-4d42-917d-faca166bc059}» />
    <EventID>12</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime=»2020-06-20T02:48:32.2444938Z» />
    <EventRecordID>1962</EventRecordID>
    <Correlation />
    <Execution ProcessID=»4″ ThreadID=»332″ />
    <Channel>System</Channel>
    <Computer>WIN10-DAVE-X570</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name=»locationCode»>0x1c000519</Data>
    <Data Name=»Data»>3221225473</Data>
  </EventData>
</Event>

and

Log Name: System
Source: TPM
Date: 6/19/2020 7:48:32 PM
Event ID: 15
Task Category: None
Level: Error
Keywords:
User: N/A
Computer: WIN10-DAVE-X570
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 Xml:
<Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
<System>
<Provider Name=»TPM» Guid=»{1b6b0772-251b-4d42-917d-faca166bc059}» />
<EventID>15</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime=»2020-06-20T02:48:32.2444899Z» />
<EventRecordID>1961</EventRecordID>
<Correlation />
<Execution ProcessID=»4″ ThreadID=»332″ />
<Channel>System</Channel>
<Computer>WIN10-DAVE-X570</Computer>
<Security />
</System>
<EventData>
<Data Name=»locationCode»>0x220003ac</Data>
<Data Name=»Data»>3221225862</Data>
</EventData>
</Event>

Event ID 15: How Can I Fix This TPM BSOD Error?

The world of computers and technology is often fraught with glitches, bugs, and errors that can lead to frustrating experiences for users. One of these is the dreaded Blue Screen of Death (BSOD), which can leave even the most tech-savvy individuals scratching their heads. Among the many possible causes for a BSOD, one that has gained attention is Event ID 15, specifically related to the Trusted Platform Module (TPM). This article aims to dissect Event ID 15 in detail, exploring its implications, potential causes, and most importantly, how to resolve it.

Understanding Event ID 15

Event ID 15 typically indicates an issue occurring with the TPM on a Windows operating system. The Trusted Platform Module is a specialized chip on your computer’s motherboard that enhances security by managing cryptographic keys, passwords, and other sensitive information. It plays a crucial role in securing hardware, software, and data encryption, particularly in enterprise environments.

When your system encounters a BSOD referencing Event ID 15, it signifies that the TPM has encountered a fault or corruption that is preventing the operating system from functioning correctly. This error can arise during different instances, including system boot, while running applications, or even while installing updates.

Why Is TPM Important?

Before diving deeper into resolving Event ID 15, it is essential to understand the importance of the TPM in modern computing:

1. Hardware Security: TPM chips add a layer of protection beyond software-based security solutions. They store cryptographic keys in hardware, making it extremely difficult for attackers to extract sensitive information.

2. Secure Boot: TPM contributes to the secure boot process, ensuring that only trusted software loads during system startup.

3. Data Protection: TPM offers hardware-based encryption, helping to secure files and sensitive data even if the operating system is compromised.

4. Platform Integrity: It helps verify the integrity of the boot process and the operating system, ensuring that no unauthorized changes have been made.

Given these functions, an error associated with the TPM—like Event ID 15—can have serious implications, impacting system security and performance.

Causes of Event ID 15

Several reasons can trigger Event ID 15 related to the TPM:

1. Corruption of TPM: The TPM can become corrupted due to power failures, improper shutdowns, or malware attacks.

2. Driver Issues: Outdated or incompatible TPM drivers can cause conflicts that lead to a BSOD error.

3. Windows Updates: Sometimes, a Windows update might not play well with a specific hardware configuration, including TPM.

4. Faulty Hardware: The TPM chip itself can fail due to manufacturing defects or physical damage to the motherboard.

5. System Misconfigurations: Changes in system settings, especially related to UEFI and Secure Boot, can lead to conflicts.

Symptoms of Event ID 15

When you encounter Event ID 15, you may experience a range of symptoms, including:

• Occasional blue screens while operating the system.
• Inability to boot into Windows.
• Applications failing to start or crashing unexpectedly.
• Performance issues, such as sluggish response times and application freezes.
• Error messages related to TPM during startup or operation.

Diagnosing Event ID 15

Before taking action to fix the issue, it’s essential to diagnose and confirm that Event ID 15 relates specifically to the TPM. You can do this through the Event Viewer:

1. Open Event Viewer: Type «Event Viewer» in the Windows search box and press Enter.

2. Navigate to Windows Logs: Under the «Windows Logs» section, find «System.»

3. Filter for Event ID: Use the «Actions» panel on the right and select «Filter Current Log.» Enter «15» in the Event IDs field to filter results.

4. Review Details: Click on the relevant events to view details of the error, which can give you further insights into the problem.

Fixing Event ID 15

After identifying that Event ID 15 is indeed related to TPM, the following steps can help diagnose and potentially resolve the issue:

1. Clear the TPM

Clearing the TPM can eliminate corrupted data and reset it to factory defaults. However, note that this action will delete any stored keys and data encrypted by them.

• Open TPM Management:

  • Press Windows + R, type tpm.msc, and hit Enter.

• Clear TPM:

  • In the action panel, choose ‘Clear TPM’. Follow any prompts to restart your system.

2. Update TPM Drivers

Outdated or incompatible TPM drivers can be the source of the problem. You can update these through Device Manager:

• Open Device Manager:

  • Right-click on the Start menu and select Device Manager.

• Locate the TPM:

  • Expand the «Security Devices» section.

• Update Drivers:

  • Right-click the TPM and select «Update driver.» Choose «Search automatically for updated driver software.»

3. Update Windows

Keeping your Windows operating system up-to-date can resolve compatibility issues that may cause Event ID 15:

• Settings:

  • Go to Settings, then «Update & Security.»

• Check for Updates:

  • Click on «Check for updates» to see if any updates are pending.

4. Run a System Scan

Sometimes, corrupted files can contribute to the problem. Running a System File Checker (SFC) scan can restore damaged files.

• Command Prompt:

  • Open Command Prompt as administrator (search for «cmd,» right-click, and select «Run as administrator»).

• Run the SFC Command:

  • Type sfc /scannow and hit Enter. Wait for the scan to complete and restart your computer.

5. Check for Hardware Issues

If problems persist, you may need to check the TPM hardware, which may involve:

• BIOS/UEFI Settings:

  • Access your system BIOS/UEFI settings and ensure TPM is enabled.

• TPM Chip Inspection:

  • If you feel comfortable, physically inspect the motherboard and TPM chip for signs of damage.

6. Restore or Reset Your PC

As a last resort, if none of the above methods work, consider performing a system restore or reset to revert the system back to a previous state before the issue occurred:

• System Restore:

  • Go to «Control Panel» > «System and Security» > «System» > «System Protection» and select «System Restore.»

• Reset Your PC:

  • Go to «Settings» > «Update & Security» > «Recovery» and choose «Reset this PC.»

Conclusion

Event ID 15 represents a significant error linked to the Trusted Platform Module, an essential component for security in modern computing. Although encountering a BSOD related to TPM can be a daunting experience, diagnosing the problem is the first step toward resolution.

By following the outlined steps to diagnose and fix the issue, users can often restore functionality to their systems without resorting to drastic measures. Remember that keeping your operating system, drivers, and firmware updated is the best defense against issues like Event ID 15 in the future.

In the realm of computing, proactive vigilance combined with technical know-how can often prevent frustrating errors from escalating into serious problems. By understanding the role and function of critical components like the TPM, users can maintain a more secure and responsive computing environment.

Make sure you have installed the latest AMD chipset drivers (that is not the ones supplied by windows or the ones on ASUS website and yes they are older) The ones you need are from AMD, here https://www.amd.com/en/support/chipsets/amd-socket-am4/x570

In regards to setup of TPM using BIOS, it is kinda related to the correct setup of your Nvme drive, so I have just given that detail and you can work it out, if you have got it set up correctly. Best way to check is to use HWinfo https://www.hwinfo.com/download/ and If done correctly on the summary page towards bottom right, Operating System UEFI Boot will be in green and Secure Boot will be in green (either in grey means you have done something wrong.)

Here is the procedure for install of windows on nvme drive.

1 — Make sure you unplug all SATA and USB drives, the M.2 drive has to be the only drive installed.
2 — Go into the bios, under the boot tab there is an option for CSM, make sure it is disabled.
3 — Click on secure boot option below and make sure it is set to other OS, Not windows UEFI.
4 — Click on key management and clear secure boot keys.
5 — Insert a USB memory stick with a UEFI bootable ISO of Windows 10 on it.
6 — Press F10 to save, exit and reboot.
7 — Windows will now start installing to your NVME drive as it has its own NVME driver built in.
8 — When the PC reboots hit F2 to go back into the BIOS, you will see under boot priority that Windows boot manager now lists your NVME drive.
9 — Click on secure boot again but now set it to Windows UEFI mode.
10 — Click on key management and install default secure boot keys <- this is the step that sets up BIOS TPM
11 – Press F10 to save and exit and windows will finish the installation.

Generally it is really important to install Nvme exactly as described above. If you ever have windows 10 issues or decide to dual boot your system and for example have skip step 1, you will find just how annoying windows 10 boot loader can be etc and for each point there is reason why you should do it this way.

Hope you find this of help.