Tesla FSD v14 Lite Triggers HW3 Overheating, Failures
Get the Energy newsletter
Daily energy & climate — solar, EVs, oil, the policy fights and tech bets shaping the transition. Free.
- Tesla began wide release of FSD v14 Lite to HW3 vehicles on July 21 via software version 2026.20.6.11 (FSD v14.3.6), two weeks after first rolling it out in late June.
- FSD v14 Lite is a distilled version of the HW4 v14 model compressed to run on the memory-constrained AI3 computer, which ships with 8GB of RAM — roughly one-eighth of HW4's memory bandwidth.
- HW3 owners are posting service-mode screenshots showing the APP_w141_ECU_Thermal_Issue fault triggering when the board exceeds 90°C, with multiple owners measuring 96°C and forced FSD disengagements until the unit cools.
- Beyond thermal alerts, some Tesla owners report the computer fully shutting down and requiring replacement per Tesla Service — a scenario that has prompted Electrek to be contacted directly by four owners about the same pattern.
- Tesla is already on the hook to replace the self-driving computer in roughly 4 million cars or compensate owners after admitting HW3 cannot deliver the unsupervised self-driving it was sold to run, and has no clear plan for those owners.
- The APP_w141 fault itself is a long-documented HW3 issue usually traced to cooling-loop problems (low coolant, Octovalve air pockets, clogged radiators) and predates v14 Lite by years — Tesla has not confirmed the software is causing hardware to fail.
- Owners are also reporting broader FSD v14 Lite regressions — phantom braking, hesitation, and brake stuttering — that the article attributes to the same compute ceiling constraining the older hardware.
- Electrek's Take frames the stakes: if v14 Lite is shortening the life of an already-stressed computer Tesla admitted is inadequate, it converts a software rollout into a warranty and goodwill liability at massive scale.
Why it matters: Tesla has already admitted HW3 can't deliver unsupervised self-driving and faces replacing or compensating owners of roughly 4 million vehicles; a software update that accelerates failures on that same hardware turns a routine push into a warranty and litigation problem — particularly as those cars age past warranty coverage. The mechanism is plausible if unconfirmed: a heavier distilled model running hot on a thermally and memory-constrained seven-year-old computer.
