- Joined
- Jul 13, 2016
- Messages
- 3,307 (1.08/day)
Processor | Ryzen 7800X3D |
---|---|
Motherboard | ASRock X670E Taichi |
Cooling | Noctua NH-D15 Chromax |
Memory | 32GB DDR5 6000 CL30 |
Video Card(s) | MSI RTX 4090 Trio |
Storage | Too much |
Display(s) | Acer Predator XB3 27" 240 Hz |
Case | Thermaltake Core X9 |
Audio Device(s) | Topping DX5, DCA Aeon II |
Power Supply | Seasonic Prime Titanium 850w |
Mouse | G305 |
Keyboard | Wooting HE60 |
VR HMD | Valve Index |
Software | Win 10 |
There is actually a reason for that. When you let the CPU downclock , so do the voltages , though you might have achieved a stable overclock those P-states might not be fully stable , therefor switching between these states may crash your system.
The P-States baked into the processor are tested by Intel and completely stable. You should only ever keep a fixed voltage / clock when your are figuring out your max overclock. If your processor is crashing from switching from your custom P-state and one of the low power one's made by Intel either your overclock isn't stable, your power supply isn't giving the correct voltage, or your motherboard is doing something wrong. I have been overclocking Intel processors for what seems like forever and since adaptive voltage has introduced I have never had an issue with the system crashing after I'd gotten an overclock stable after an 8 hour stress test that could at all be attributed to low power P-States.