alienware17r4

updated

4 years ago

A

alienware17r4

2 Intern

63 Posts

2

9023

December 5th, 2022 04:00

Is Highly Active Topic

17 R4, firmwaretpm.exe stopped working

Shipped April 2018. Warranty expired in February 2021. Windows 10 20h2, all updates current. I've had this error 10 times. it started on 11/19. In the few days prior to this there were no unusual updates, just the regular defender updates. There is no "firmwaretpm.exe" file to be found on my machine. however, device manager reports that trusted platform manager 2.0 is working properly, and the driver version is 10.0.19041.746. I DO NOT wish to reset it in bios unless someone knows 100% that it will be fixed without losing anything on my machine.

APPCRASH
Application Name: FirmwareTPM.exe
Application Version: 1.1.1.1
Application Timestamp: 6368a364
Fault Module Name: VCRUNTIME140.dll

  • alienware17r4

    2 Intern

    63 Posts

    1227

    0

    Posted February 18th, 2023 02:00

    I'm marking it solved! Last tpm error was on 2/8. support assist got updated on 2/8. windows also got updated a few days later.

  • crimsom

    9 Technologist

    6114 Posts

    3405

    0

    Posted December 5th, 2022 05:00

    Hi @alienware17r4 welcome to this free user-to-user Alienware laptop discussion forum. 

    Please run windows Reliability Monitor. How to use Windows Reliability Monitor to identify software issues | Dell US  

    FirmwareTPM.exe may have been infected by malware or virus. Install and run Malwarebytes Free.  

    Install Windows 10 version 22H2 update. How to get the Windows 10 2022 Update | Windows Experience Blog  

    Install the latest Visual C++ packages (x86 and x64). Latest supported Visual C++ Redistributable downloads | Microsoft Learn 


    [This user does not work for Dell and volunteers their free time. Please remember to say thank you by clicking on my thumb up icon.]

  • alienware17r4

    2 Intern

    63 Posts

    3395

    0

    Posted December 5th, 2022 06:00

    Reliability monitor is how I found these errors.

    i'm virus and malware free.

    I'm running 22h2 (sorry, my typo) don't know how to edit the original post.

    Can't find what the actual version number of the latest and greatest vcredist files is but i have 12.0.30501. since I haven't changed anything with TPM or visual C runtimes, and everything else works fine, it makes little sense that VC suddenly started having a problem with just this application. I have no other errors.

  • alienware17r4

    2 Intern

    63 Posts

    3392

    0

    Posted December 5th, 2022 06:00

    can't verify or scan firmwaretpm.exe because it does not exist as an actual file on my computer. It could be there somewhere that i can't see even showing system and hidden files and folders. Anyone know where it is? Anyone actually have a file with that name?

  • Red49

    5 Posts

    3350

    4

    Posted December 9th, 2022 07:00

    Having what appears to be the same issue since 21-NOV-22 whenever SupportAssist or DellUpdate is run.

    Both of these (and other Dell) apps have been updated more than once in the last 4 weeks.

    What is FirmwareTPM.exe? A fresh copy appears in  "C:\Windows\TEMP\inv????_tmp\FirmwareTPM" (where ???? = a changing four digit hex number). I assume that this is downloaded every time but from where and by what?

    I am running Windows 11 (22H2 Build 22621.900) last updated on 30-NOV-22 on an Inspiron 3671.

    I have updated VC++ from 2015-2019 to 2015-2022 version 14.34.31931.

    Running "sfc /scannow" and "dism /online /cleanup-image /restorehealth" finds no errors.

    Apart from this repeated APPCRASH, PC appears to be running OK.

  • ThomasAAT

    2 Intern

    393 Posts

    3341

    3

    Posted December 9th, 2022 08:00

    You are not alone. I have the same issue and it came out of nowhere. I assume it has to do with Dell AupportAssist and/or dell update.

    I have no errors when running "sfc /scannow" and "dism /online /cleanup-image /restorehealth".

    No malware or virus. So my solution is to let this short it self out. To do a hard reset or update TPM will only make things worse in this senario. 

  • crimsom

    9 Technologist

    6114 Posts

    3341

    0

    Posted December 9th, 2022 08:00

    Hi @alienware17r4 

    If the TPM is not seen in the BIOS, a Hard Reset is required to bring it back online. How to Perform a Hard Reset on a Dell Computer | Dell US  Do not remove Battery, disconnect Battery is sufficient. 

    How to Successfully Update the TPM Firmware on your Dell Computer | Dell US 

    Visual C++ Redistributable Runtimes All-in-One Download | TechPowerUp  


    [This user does not work for Dell and volunteers their free time. Please remember to say thank you by clicking on my thumb up icon.]

  • Red49

    5 Posts

    3336

    1

    Posted December 9th, 2022 09:00

    It's nice to know one is not alone. The crash is silent so will not be seen unless looked for using Reliability Monitor (easier than using event viewer!).

    This is not the first time this year that Dell has upset my system via a bug in either DellUpdate or SupportAssist or both! Memory tells me the last problem (during March/April) was related to a .NET Framework incompatibility. Have they done it again?

  • ThomasAAT

    2 Intern

    393 Posts

    3328

    0

    Posted December 9th, 2022 11:00

    Dell SA is known to bring issues with it. Had a memory error during boot related to SA in 2021 that was bugging me. But manage to ignore it when I found out the culprit.

    And the newest update to SA wont even install on my XPS. And the previous version is causing bluescreen so I have disabled Dell TechHub on my XPS. So yeah, a Gremlin from Dell this Christmas. 

  • Martin B

    1 Rookie

    41 Posts

    3271

    2

    Posted December 11th, 2022 08:00

    You are certainly not alone!  I have had exactly the same issue on my XPS 8900, also since 19th November.  I have Dell SupportAssist and Dell Update installed.

    I am not running the very latest BIOS and wondered if I should update it.  However, having read the comments above my inclination is to sit tight and wait for Dell to sort it out...