Interacting with CPU clock adjustments disrupts RAID array operations on the 7800X3D + Gigabyte motherboard.
Interacting with CPU clock adjustments disrupts RAID array operations on the 7800X3D + Gigabyte motherboard.
Details: Motherboard model Gigabyte B650e Aorus Master Rev 1.0 BIOS version F24c CPU AMD Ryzen 7 7800X3D RAM 2x48GB Corsair RAID setup GPU Radeon RX 7900XT Storage 4x Crucial T700 NVMe M.2 SSD in RAID10 using AMD RaidXpert2 utility Overclocking newbie here. I suspect a voltage issue might be causing the problem when adjusting CPU Clock Control settings. Raising the value beyond default can trigger RAID failures, but lowering it restores normal operation. Possibly the required voltage isn't set high enough. Your current adjustments are: VCORE_SOC 1.2 CPU_VDDIO_MEM 1.4 DDR_VDD Voltage 1.4 DDR_VDDQ Voltage 1.4 DDR_VPP Voltage 1.8 VPU VDD MISC 1.1 VDDP Voltage 1.1. Need guidance, thank you!
Do you have the Asynch CPU/PCIe Clock activated? This adjustment is generally needed to prevent unusual chipset problems when increasing the BCLK on AM5 boards. Additionally, it seems there are some BIOS updates where Gigabyte discontinued ECLK support across their products, so you might be using a version that requires a different BIOS revision to resolve this issue.
Async CPU/PCIe Clock is activated. Additional configurations from a Buildzoid tutorial video are applied: Async CPU/PCIe Clock - ENABLED, FCH Spread Spectrum - ENABLED, DISABLED Precision Boost Overdrive, ADVANCED Precision Boost Overdrive Scalar Ctrl, AUTO CPU Boost Clock Override - DISABLED, and Curve Optimizer - DISABLED. I can enter all these settings, restart the system, and RAID10 along with Windows functions work properly. However, when I adjust the CPU Clock Control, the RAID fails until I revert those changes. It's quite annoying.
It seems like a BIOS problem on your end. I’d check for updates to various versions and see if that helps. Based on the current settings, it should function properly.
New testing results show I can push BCLK beyond 100, but only by a very small margin. At 100.01 it still works, then at 100.25 it fails, and at 100.30 it causes RAID failure. It’s puzzling why the maximum is so low and why it consistently hits one drive in my RAID setup. I might revert the BIOS to F13 just to double-check.
Can we boost the speed using the multiplier? Because the base clock is linked to components like PCIe, this kind of problem is normal, but it looks like a lower limit I've noticed elsewhere. Manual overclocking usually doesn't help much for gaming tasks, and adjusting PBO might be more effective. A complete core overclock could likely reduce gaming performance with today's chips.
It seems the ECLK configuration is likely faulty, which is common in certain BIOS versions. If this is the issue, it probably also impacts the PCIe clock settings, especially affecting NVMe drives that are highly sensitive to timing. On the 7800X3D chip, the multiplier value is fixed. However, on AM5 platforms or boards with external clock generation (like the B650E Master), the CPU base clock is decoupled from the PCIe base clock, reducing the chance of interference with the chipset or other PCIe components—unless the BIOS has altered this setting.
This appears to be a well-considered theory, but it seems inconsistent with other information I’ve seen. The F13 BIOS version mentioned for the last working ECL model doesn’t seem to appear on the support page for the B650e Aorus Master. It’s unclear whether mixing BIOS entries from different board pages is permissible or not.
Great! I'll try F8 tomorrow and observe the results. Since I've already reset my settings, I'm safe to proceed. Thanks for the support and guidance!