Oh wow. Read the room guy. Very few hear believe this is all the MB manufacturer’s fault. And there is a reason for why the vast majority of us easily, easily believes Intel shares a lot of blame here.
I have. You can’t buy from them directly as they are pretty much exclusive contract manufacturers that follow the design spec with 0% deviation. If this is who Intel used, its 100% Intel’s product.
Just because Maytag ovens are used to cook food doesn’t mean they are responsible for what’s cooking in them.
That analogy applies here as foxconn would never touch much less change any settings in the shipping default BIOS. That’s all Intel. Same goes for third parties today. None of them would risk shipping a default BIOS without at least checking with Intel. Not for permission mind you but at least approval that it wouldn’t causes issues or void warranties.
What people choose to believe isn't really relevant to me.
There's a spec, it's what the motherboard makers should be using.
They are not (even after their "intel baseline spec" BIOS update).
Pretty clear cut factually.
Intel needs to be firmer with enforcing their spec, and dictating how deviations should be presented. That's the issue.
They at least seem to be taking that stance now.
Intel requests system and motherboard manufacturers to provide end users with a default BIOS profile that matches Intel recommended settings.
Intel strongly recommends customer's default BIOS settings should ensure operation within Intel's recommended settings.
In addition, Intel strongly recommends motherboard manufacturers to implement warnings for end users alerting them to any unlocked or overclocking feature usage.
For the inevitable "but Intel in their own marketing uses off spec numbers" comments.
The only change from spec is PL1=PL2.
Not -
- Disabling Current Excursion Protection (CEP)
- Enabling the IccMax Unlimited bit
- Disabling Thermal Velocity Boost (TVB) and/or Enhanced Thermal Velocity Boost (eTVB)
- Additional settings which may increase the risk of system instability:
- Disabling C-states
- Using Windows Ultimate Performance mode
- Increasing PL1 and PL2 beyond Intel recommended limits
And other "optimized" defaults, often including automatic overclocking of the CPU clock, BCLK, even RAM timings.
Changing the voltage curve is a significant thing. Both going under and over the recommended values.
Setting PL1 to PL2 is not major. The CPU is already validated to that wattage, and protection features put in place will automatically downclock/reduce volts etc, if thermals become an issue.
Unless those protection mechanisms are turned off by the motherboard manufacturers, by default.
There's a big difference between allowing the CPU to run at the PL2 all the time (253 W), with PL3/PL4 still topping out around ~300 W, to having non standard voltage curves and PL=4096 W/unlimited.
The other end of the spectrum is these modified clock tables/curves causing vdroop that goes
below the Intel recommended spec. This is another cause for crashing that Intel mentioned.
