Check if the fan is causing the CPU to freeze at 600mhz.
Check if the fan is causing the CPU to freeze at 600mhz.
I'm facing an unusual issue with my Latitude E6400. The CPU is clocking between 500-600 MHz, which is far below the expected 2.5-3 GHz. This problem occurs consistently across two motherboards and two CPUs (T9900 and P8400), both of which are officially supported by BIOS. I'm unsure why the firmware is limiting CPU speed so low. My initial thoughts are that the RAM might be faulty (I had a similar issue on my server recently) or the fan could be defective. The onboard diagnostics from Dell indicate the fan is connected, yet the system still doesn't function properly. If I supply power to the fan, it works correctly. It seems the fan might be the root cause, causing the CPU to throttle due to a perceived absence.
That's the idea I had too. Clearing CMOS didn't help, so I suspect it was thermal throttling—even though both cores stayed under 60°C.
It's very possible for the motherboard to slow the CPU down to protect itself (things like the chipset or VRM) due to not having a confirmed Fan. On modern Intel systems it's through "BDPROCHOT". Not sure if it was implemented in the Core 2 Era, but even so the motherboard has total control over bus and multiplier.
Additional details suggest a broader problem with these laptops overall. It seems ThrottleStop might resolve the issue. Note: After restarting at 2,200mhz it worked well again, but then crashed once more. Overall improvement noted.
You must use ThrottleStop to resolve the throttling problems these laptops are experiencing. The HWiNFO image displays a Clock Modulation throttling issue. Open the Clock Modulation section in ThrottleStop, adjust it to 100.0, and press the Turn On button. Remove the BD PROCHOT setting. Share additional ThrottleStop screenshots if you require assistance.
Haha, just checked your message from Tom's Guide back in 2007. It really helped a lot. ThrottleStop functions well until the clock multiplier exceeds 9, after which I encounter a WHEA BSOD. It could be related to a chipset driver problem since the laptop was slow out of the box and I haven't installed any drivers yet.