The Problem For a long time, across multiple games like Warzone and Total War, my system will run fine and then suddenly collapse into 8-13 FPS with insane frametime spikes. GPU usage plummets to like 10%
The Diagnosis After days of logging telemetry, stripping out audio drivers, fixing NVMe pagefaults, and running DDU, I finally found the absolute root cause using ThrottleStop.
When the FPS collapses, the CPU clock speed hard-locks at exactly 398MHz (0.4 GHz). ThrottleStop Limit Reasons shows it’s being triggered by BD PROCHOT and EDP OTHER.
Here’s the catch: the CPU is sitting at a freezing 44°C and only pulling 14.9W when this limit triggers. The CPU is completely fine, but the Dell motherboard VRMs (or the PSU) are sending a false panic signal, choking the processor and completely starving the 3080
Since Dell hard-locks the BIOS, ThrottleStop has the BD PROCHOT box grayed out, so I can't even force the software to ignore the broken sensor
Next Steps I’m done tearing my hair out tomorrow I’m planning to do a hard EC reset (holding power for 60s unplugged), run the Dell pre-boot F12 diagnostics to see if it catches a dead VRM thermistor, and completely reseat the 24-pin and 8-pin cables on the board (I'm not hopeful)
Has anyone else dealt with a false BD PROCHOT on these proprietary Dell boards? Did an EC reset or cable reseat actually fix it for you, or did you have to fully replace the motherboard/PSU?
Holding power button for 60 sec. while unplugged merely drains flee power. On the other hand, holding in the power button for 30 sec. while plugged in resets BIOS. I'm not certain this is the trick, but may be worth a try.
One can always Google those error codes and see what comes up. More likely than not one might end up getting TMI.
bradthetechnut
9 Technologist
•
9712 Posts
•
40924 Points
0
0
Posted April 22nd, 2026 00:03
Holding power button for 60 sec. while unplugged merely drains flee power. On the other hand, holding in the power button for 30 sec. while plugged in resets BIOS. I'm not certain this is the trick, but may be worth a try.
One can always Google those error codes and see what comes up. More likely than not one might end up getting TMI.