Share via

Constant BSOD - TPM Error (Event ID 15)

Anonymous
2022-12-11T16:29:47+00:00

Nearly everyday for the past couple of months, I have experienced multiple blue screens. The error code that shows on the BSOD changes every time, some times its IRQL_NOT_LESS_OR_EQUAL, sometimes its SYSTEM_SERVICE_EXCEPTION, etc. However, event viewer shows me a TPM error pretty much every time I blue screen which is as follows: "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 15). I don't know what to do. I have tried updating everything I possible can from common windows updates to updating the BIOS, and have ran many full scans for potential viruses. I don't know what is helpful for you guys, so here is a picture of Event Viewer at the time of a recent Blue Screen. As seen in the picture, I will occasionally get that Critical Error of Kernel-Power (Event ID 41) but this does not happen every time I blue screen. Here are my PC specs (if I missed any info please let me know and I will provide it):

  • Mother Board: GIGABYTE Z390 Aorus Pro LGA 1151
  • CPU: Intel Core i7-9700K 8-Core 3.6 GHz
  • GPU: MSI GeForce RTX 2070 SUPER
  • RAM: CORSAIR Vengeance RGB Pro 32GB (2 x 16GB)
  • PSU: EVGA SuperNOVA 850 G5, 80 Plus Gold 850W
  • SSD: Western Digital WD Black SN750 NVMe M.2 2280 1TB
  • OS: Windows 10 Pro 64-Bit

Also, here are the 5 most recent Minidump files: https://www.mediafire.com/folder/zj8rrle9ehqfc/Minidump_files

I have contacted GIGABYTE but they are taking a while to process so I figured I could look for additional help here. Thanks for your time and any help is really appreciated.

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

13 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-12-27T06:58:52+00:00

    After using just the good ram stick for over a week, I experienced zero blue screens. I now have new ram that I just bought and installed on the 24th. So far so good. I guess my problem is solved for now.

    4 people found this answer helpful.
    0 comments
  2. Anonymous
    2022-12-13T19:47:55+00:00

    Sure, here are all of my plugged in devices that I believe fall into the HIDCLASS category:

    • Keyboard: HyperX Alloy Origins
    • Mouse: Razer DeathAdder V2
    • Xbox Controller
    • Drawing Tablet: Wacom One CTL-472-N

    Not sure if these next ones are HID but they are connected to my computer via USB so here they are anyways:

    • Monitors: #1: ASUS VG248QG #2: DELL S2316M
    • Headphones: HyperX Cloud II
    • Desk Fan: MAINSTAYS FL-804T

    My computer is also connected to a battery back up which does seem to have a USB connection going into my computer. The model is the CyberPOWER 1500va AVR.

    0 comments
  3. Anonymous
    2022-12-13T17:07:47+00:00

    The minidump files indicates "HIDCLASS.SYS". It is a Human Interface Device driver that supports Keyboards, Mouse and other input devices.

    May I know what HID devices are plugged into your PC when you encountered the BSOD?

    Thanks.

    0 comments
  4. Anonymous
    2022-12-13T00:07:51+00:00

    Well, I tried to run Driver Verifier and followed all instructions, but upon reboot to get it started, I almost immediately blue screened, and after that BSOD rebooted my computer, I almost immediately blue screened again. So, I have disabled Driver Verifier and here is a link of both minidump files: https://www.mediafire.com/folder/07p1sb28knzlg/Minidump_after_Verifier_BSOD

    0 comments
  5. Anonymous
    2022-12-11T17:54:15+00:00

    Hi LittleSilverOwl,

    I'm Paul and I'm here to help you with your concern.

    The minidump files only indicated a system kernel driver "ntkrnlmp.exe". Since it's a system file it means something else drove it into a fault. It could be hardware, software, or driver.

    I recommend that you run Driver Verifier to find any misbehaving, corrupted, or outdated driver.

    Follow the instructions from this article.

    https://www.tenforums.com/tutorials/5470-enable...

    Reminders:

    => Disable Driver Verifier after 48 hours or after receiving a BSOD.

    => Create a Restore Point before running Driver Verifier.

    Share the minidump file once you receive a BSOD error.

    Standard Disclaimer: There are links to non-Microsoft websites.

    The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

    0 comments