XPS 14 9440, yet another update that broke my system
<The Basic warranty on this XPS 14 9440 expired 26 months/8 days ago on August 2, 2024. DELL-Admin>
At one point, I ran into some trouble: my laptop shut down, and an overheating error appeared. I took it to a service center to have the thermal interface replaced, but that didn’t help. Based on the error, I decided not to overcomplicate things and simply bought new cooling fans—yet that didn’t solve the issue either. Frustrated, I decided to install a different operating system (Linux) for testing; I checked all the sensors and analyzed the system logs, but still found no solution. At this point, I was so fed up that I started looking for a new laptop.
However, being the kind of person who likes to get to the bottom of things, I kept digging.
I discovered a bug in BIOS version 1.22.0: by switching the operating mode, I was able to stop the shutdowns. To be precise, after resetting the BIOS to its default settings, I simply toggled a specific mode, and the problem vanished immediately. This only worked after a full reset to the initial factory settings!
Thinking everything was finally sorted, I set up a new OS—but I forgot to uncheck a box during a BIOS update. It updated to version 1.28.0, and the problem returned.
I honestly don’t understand how this is even possible. How can such a major company justify releasing such unpolished, buggy updates? I bought this device, and I just want to be able to use it. Please help me resolve this issue.
I have just experienced a very similar problem the same machine an XPS14 9440 with the NVidia GeForce 4050 gpu. After installing bios 1.28.0, the machine registered that it had been installed and requested a reboot. The requested reboot hung with a black screen and illuminated top row. It remained in that state for more than ten minutes. After trying a forced shut down with the power button multiple times (holding down for 30 sec at least), I managed to get a shutdown. Powering up with the power button resulted in the fan running at maximum speed, the machine getting hot and all the top row illuminated at maximum brightness. I disconnected the WD19s dock and left the battery to discharge over night. After reattaching the dock and the battery getting sufficient charge the machine rebooted and appears to be functioning normally. ChatGPT advised that I should have charged via the power adaptor instead of the dock. I connect the power adaptor and did a shut down and cold restart which completed normally as has a restart via the alt-F4 menu. System info is reporting the bios as 1.28.0. Needless to say it was a disconcerting event. The last bios update created a problem as well. A hung reboot that required a hard shutdown via the power button and on restart the system required the bit locker key. My memory is a bit sketchy on the exact sequence of events for that one. I keep my systems up-to-date with Dell and M/soft updates but not sure I want to chance bricking my machine with the Dell updates given these experiences. System info below.
It's not good enough Dell.
Item Value
OS Name Microsoft Windows 11 Home
Version 10.0.26300 Build 26300
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name SOLUM
System Manufacturer Dell Inc.
System Model XPS 14 9440
System Type x64-based PC
System SKU 0C6B
Processor Intel(R) Core(TM) Ultra 7 155H, 1400 Mhz, 16 Core(s), 22 Logical Processor(s)
BIOS Version/Date Dell Inc. 1.28.0, 27/08/2026
SMBIOS Version 3.8
Embedded Controller Version 1.38
BIOS Mode UEFI
BaseBoard Manufacturer Dell Inc.
BaseBoard Product 0H14N3
BaseBoard Version A00
Platform Role Mobile
Secure Boot State On
PCR7 Configuration Elevation Required to View
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "10.0.26100.1"
After a factory reset, it was absolutely necessary to switch between modes; otherwise, the device would shut down while still in the BIOS. The next time I entered the BIOS, it had reverted to the default mode, even though I had changed it previously. This completely resolved the issue for me on firmware version 1.22.
Why am I the one who has to test this?
I’m not getting paid for it(
@N0vak If the heatsink assembly and fans have already been replaced, then you possibly have a particularly hotter CPU. The dell heatsink assembly already comes with the needed thermal pads applied to them. Thermal paste should still be needed. Even if the BIOS thermal setting is set to Ultra Performance, which forces the CPU to run hotter for longer, you should expect thermal throttling and not shut downs. By changing the setting to Optimized and resolving the issue, that should be the indication that the CPU is thermal tripping causing the shut down. So its possibly the silicon lottery at play here, meaning that the motherboard may need to be replaced if all else fails. If still under warranty, contact support for next steps. If out of warranty, heres what I would check out before calling it the motherboard:
Ensure the thermal paste was properly applied or that new paste is applied, maybe even use a better paste
Ensure the heatsink is torqued correctly as it is sequenced
Ensure the thermal chipset drivers are up to date - tuning and framework
Run the onboard diagnostic to see if there are any thermal errors in particular
restart the unit
tap the F12 key on the keyboard as the dell logo appears
Select Diagnostics - make note of any error and validation codes
Use the Dell Optimizer app to help manage thermals
If you need the absolute best performance, then right you'll want to use the Ultra Performance option in the BIOS. However, if it remains unstable afterwards then the board sounds likely. If we just need stability on the system, then sticking with the Optimized setting should suffice and honestly you might not even see a large difference in performance. You'd really have to run synthetic benchmarks to see how the 2 settings compare.
DELL-Daniel V #IWork4Dell Digital Support Forum Liaison
Do you realize that this is a systemic issue?
The solutions you’re suggesting are meant for an average user—but I’ve already tried all of those steps first. I’ve even replaced the thermal interface twice. My device is no longer under warranty, and I cannot visit in person to have it inspected. I appreciate that you acknowledge your mistakes, but why should the customers have to suffer?
I’ve run synthetic benchmarks and performed system diagnostics; no errors were found. The device shuts down randomly, regardless of the workload. I can provide the service tag or grant remote access to the laptop. I don’t need advice; I need a resolution. Please allow me to downgrade the firmware—I will take full responsibility for it.
I am prepared to provide any information required by a technical specialist. I want to resolve this issue so I can continue using the device, as I genuinely like it.
Subject: Addendum with evidence - false critical thermal shutdowns: trip point _CRT = 47.85 C on IPF zone SEN3 (BIOS 1.28.0)
I captured hard evidence that this is NOT a real overheating problem:
1) One shutdown is fully recorded by Windows as Kernel-Power Event ID 86 ("The system was shut down due to a critical thermal event"):
- Thermal zone: "Intel(R) Innovation Platform Framework: SEN3"
- _CRT (critical trip point) = 321 K = 47.85 C
A critical trip at 47.85 C is ~50 C below any sane silicon limit (95-105 C).
2) Timeline proof that the trip cannot be real: on 2026-10-31 the system booted at 10:22:38 and performed the critical thermal shutdown at 10:23:08 - 30 SECONDS after a cold boot. Nothing can physically overheat that fast.
3) I caught the moment of a power loss on a sensor log (AIDA64, 2 s interval, attached):
- last samples before the cut: CPU 58 C, PCH 49-51 C, SSD 40 C - no overheating at all
- "IA: Thermal Event" was asserted 39 times in 31 minutes while the CPU was at 46-81 C
- "Package/Ring thermal throttling" 37 times; PROCHOT never
- the flags appear exactly when a board sensor crosses ~47-48 C - right at that 47.85 C trip
- a PCH sensor is ABOVE the 47.85 C trip in 531 of 925 samples (its normal range: 38-56 C)
- the NVIDIA dGPU was disabled during the test - the machine still shut down
4) Physical confirmation: with the bottom cover removed the notebook runs stably. With the cover installed the PCH/GPU-area sensors routinely exceed 47.85 C and the machine performs "critical thermal" power-offs. Same hardware, only airflow differs - this is only possible if the trip threshold sits in the middle of the sensor's normal operating range.
5) All unclean shutdowns have BugcheckCode=0 and PowerButtonTimestamp=0: instant power cuts, not BSODs, not button presses.
6) The IPF thermal stack is visibly broken: "Intel SoC Thermal IPF Extension Provider", "PerfMon IPF Extension Provider" and "PMT IPF Extension Provider" all report DEGRADED, and the participant ACPI\INTC1062\SEN3 itself reports ERROR.
7) Version dependence: on BIOS 1.22 the shutdowns could be stopped by switching Thermal Management to another mode. After updating to 1.28.0 the problem returned and the mode workaround no longer reliably helps.
Conclusion: either the critical trip point for IPF zone SEN3 is wrong (47.85 C), or SEN3 is mapped to the wrong sensor (a PCH / GPU-hotspot-class sensor that normally runs 38-56 C instead of a chassis skin sensor). Paste, fans and cooling cannot fix this.
Dell team: could you please check the SEN3 trip point / thermal policy in BIOS 1.28.0 (this looks like a regression versus 1.22), or advise a safe downgrade path to 1.22 for affected units?
You're grasping for any solution short of the only one that will solve the problem. The bottom line is that the system you have seems (by your past notes) to run fine OTHER than when it is pushed to higher performance levels. That model system just is not designed for heavy workloads, and certainly not for workloads over extended periods. You can't buy a 3 cylinder turbocharged economy car and expect to tow a 5,000 pound trailer with it.
If the system runs OK in balanced performance trim under moderate workloads, the issue is not the system - it's the workloads you're asking it to do.
Perhaps you misunderstood the issue. This is idle mode, without a load. The shutdowns occur randomly; there is no pattern to the load. This happens not even in the system, but in the BIOS. I have a fair amount of experience working with laptops.
DELL-Daniel V
Community Manager
•
922 Posts
•
5303 Points
12
0
Posted October 29th, 2026 19:12
What option did you change in the BIOS? The SATA Operation or another option?
DELL-Daniel V
#IWork4Dell
Digital Support Forum Liaison
New to Community? Check our FAQ!