Windows 10: I always get a random BSOD after "The TPM was successfully provisioned and is now ready for...

I often get a random BSOD with different stop codes, such as: SYSTEM_SERVICE_EXCEPTION, IRQL_NOT_LESS_OR_EQUAL, and many more. Most of the time, when I check the errors through Event Viewer, the information that I usually get before the error happened is "The TPM was successfully provisioned and is now ready for use." If the TPM is the problem, how can I fix that?

:)

 

TPM on Creator's Update.

I have recently reinstalled my computer with the Creator's Update an I'm having this issue that it's intermittent.

When I turn of the computer, I doesn't let me log in with a PIN, during these times it shows event 1026 in the system log with the message

The Trusted Platform Module (TPM) hardware on this computer cannot be provisioned for use automatically. To set up the TPM interactively use the TPM management console (Start->tpm.msc) and use the action to make the TPM ready.

Error: The TPM returned an unexpected result.

Additional Information: 0x940000

Also tpm.msc shows as if the computer didn't have a TPM chip, but device manager shows it without any issue.

Then the other half of times, the computer starts without problem, the PIN option appears on login, the system log shows the event 1025

The TPM was successfully provisioned and is now ready for use.

and tpm.msc shows

The TPM is ready for use.

Anybody else is having this issue?

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.

 

Windows 10 21H2 "The TPM is not ready for use"

I cannot get Windows 10 to actually use my PTT 2.0 (TPM equivalent). It continually reports "The TPM is not ready for use".

2 year old Dell G315 Laptop with Intel PTT 2.0 ENABLED in BIOS.

Intel Core i5-8300U CPU.

UEFI Secure Boot is ENABLED. (Legacy ROM boot is DISABLED)

Boot disk is a GPT-partitioned NVMe device.

Device Manager shows Security Devices > Trusted Platform Module 2.0 > "This device is working properly."

Settings > Windows Security > Device Security > Security Processor = Attestation: Not Supported, Storage: Not Ready

Windows runs and boots fine.

All Windows updates are installed.

The Windows 11 update nag message reports the machine is capable of running 11.

Have tried both a local admin user account and a Microsoft Account.

Have tried the following steps NUMEROUS TIMES over and over...

Used BIOS Clear PTT during boot up and Windows will not initialize or take ownership of the PTT.

Used TPM.MSC Prepare and Clear and Reboot.

Used Powershell Cmdlets to Clear and Take Ownership.

System Event Viewer shows me "The TPM was successfully provisioned and is now ready for use". But when I look at the TPM.MSC is continues to display as STATUS: The TPM is not ready for use.

And GET-TPM shows me:





I've spent hours on the web researching and I'm out of ideas and options. Any help would be appreciated. I KNOW I'm going to be told to perform a fresh Windows installation but it's a complicated software dev laptop and I'm resisting all the time required to fix it back up after a fresh install. Thanks!