Reliability Monitor Logging FirmwareTPM.exe APPCRASHs Since 19-Nov-2022

Confirming presence of same issue...

Per reliability monitor, FirmwareTpm.exe (a temporary file, which no longer exists on my drive) stops working every time I run Dell Update, or check for updates via Dell Support Assist.   I have to assume that FirmwareTpm.exe is generated (or downloaded) by Dell Update / Support Assist, and then deleted when the update is done.

Aside from the "nuisance" of seeing this repeatedly flagged in the reliability monitor, there are no overt/obvious signs of malfunction on my system.   My system is "squeaky clean", so this is NOT a virus/malware issue.   I am also fully up-to-date in terms of Windows Updates.

Exact same senario as me. I will leve my system be as is and wait for a dell fix (again...)

I have the same error on mine, I think it started 11/20. Started every 3 days about 3 minutes after boot. Last time it did it was 12/14.

I also see a audit failure in the event viewer sometimes when opening support assist, usually after the pc has been on for awhile. But I've been seeing that since the June update of support assist. 

And after the support assist update before this most recent one, every 7 days there would be a error that the event viewer service stopped working (always at about the same time that I updated Support Assist). I haven't seen it do that since this new version of Support Assist.

I don't have dell update, and I never let it install Support Assist remediation. However all dell services are enabled.

I have a XPS 8930, Win 10 Home, 21H2.

Forgot to mention, I did update bios from 1.1.24 to 1.1.26 thinking that would fix the FirmwareTPM error, but it didn't.

I am confirming my FirmwareTPM.exe errors...In addition to MANY others with this  month old XPS 8950 I have.  Pics are of recent reliability monitor.  I restored to factory using os recovery for support assist.  First day 63 ciitical errors...Only 3 TPMs.  only 30 something critical errors since 9AM today (It's currently 9:30pm here at reply).  

@lmacri thank you for posting, and thank you for taking the time to form a well-written post.  I would think we would at least get some type of response from Dell Support, but ha ha alas nothing yet.  I have "Premium Plus" and there is hardly anything Premium or Plus about it...most definitely Not Premium Plus. 

---

@lmacri wrote:

... Since 19-Nov-2022 I’ve been seeing errors for a FirmwareTPM.exe APPCRASH logged in my Win 10 Reliability Monitor...Event Viewer shows the faulting application path is always C:\WINDOWS\TEMP\invxxxx_tmp\FirmwareTPM\FirmwareTPM.exe (where “xxxx” is a unique string of alphanumerics for each APPCRASH) and the faulting module is VCRUNTIME140.dll v14.32.31332.0, but I am unable to find an executable called FirmwareTPM.exe anywhere on my computer.

---

Further to my original post, MattSpacer recently reminded affected users in the Dell Alienware Laptop thread 17 R4, FirmwareTPM.exe Stopped Working that there was a similar issue reported seven months ago, but the errors were due to UsbUpdate.exe, not FirmwareTPM.exe - see  LittleMaui's 28-May-2022 Inspiron 3891, Event Viewer Error - UsbUpdate.exe Fails.

I also had that UsbUpdate.exe error (Source = Application Error; EventID = 1000; Faulting Application Path = C:\WINDOWS\TEMP\invxxxx_tmp\Executables\UsbUpdate.exe where "xxxx" varies for each error) on my Inspiron 5584 - see my 10-Jun-2022 post <here> in LittleMaui's thread. Dell employee @DELL-Chris M's 13-Jun-2022 post <here> was marked as the solution for that thread and stated that "There will be no notification of any sort. The OTA (over the air) update is going to happen for all Dell remediation services (SupportAssist, Alienware Update, Dell Update)". There was no change to the version numbers of any of my Dell utilities after the OTA update was silently pushed out to my Inspiron 5584 in June 2022 - my UsbUpdate.exe errors simply stopped on their own.

What we need now is for someone from Dell to acknowledge that they are aware of these new Firmware.exe errors and that a similar OTA update is in the works that will fix this problem.
-----------------------
64-bit Win 10 Pro v22H2 build 19045.2364 * Firefox v108.0.1 * Microsoft Defender v4.18.2211.5-1.1.19900.2 * Malwarebytes Premium v4.5.19.229-1.0.1860 * Macrium Reflect Free v8.0.7175 * Dell SupportAssist v3.13.0.236 * Dell Update for Windows Universal v4.7.1 * Dell SupportAssist Remediation v5.5.5.16206 * Inspiron 5583/5584 BIOS v1.21.0
Dell Inspiron 15 5584, Intel i5-8265U CPU, 8 GB RAM, 256 GB Toshiba KBG40ZNS256G NVMe SSD, Intel UHD Graphics 620

I had the same issues with my XPS 8950 (i7 12700, 32GB RAM, Nvidia 1660ti, Windows 11, BIOS 1.9.0) following the same timeline as you have had. I finally uninstalled SupportAssist  and now my reliability monitor is error free. I still have Dell Update installed by the way. This may not shed any light on the issue but is nice to have ended the daily application reconfiguration entries and the frequent random App crashes. I tried to like SupportAssist but as one of the most knowledgeable forum members posted (paraphrasing), SupportAssist may provide more issues than benefits. 

I have the same system and when opening notepad all my screens go blank.

Dell is aware of these FirmwareTPM.exe errors...

I, too, have these FirmwareTPM crashes.  Since around the same date and same conditions.  Alienware R12.  Everything is up to date.  If Dell is aware for 2 months now, where is a resolution?  Even a temp patch?  It doesn't seem to hurt anything.  It's just "ugly".  I don't like to see extraneous errors in Reliability History.  I'm sure others feel the same.

@moha56  First, they have to find and fix the problem. Then they have to fully test the entire app all over again to make sure the "fix" didn't accidentally break something else.

Besides, they may not consider this a "critical" error message, since it has no impact on PC function. So they might not fix it until the next regularly scheduled update of SupportAssist...

Also keep in mind people were off for a week for the holidays...

I'm aware of all that.   Sounds a bit like you are patronizing me.  Thanks for your input.

As of February 3rd.  Still getting the firmware error.   Troublesome.