Constant crashes on an ASUS TUF Gaming X570-Plus with a Ryzen 9 5900X are often caused by unstable memory profiles, outdated motherboard firmware, or Windows 11 driver conflicts. By updating the BIOS, disabling EXPO/DOCP profiles temporarily, and verifying system file integrity, you can isolate whether the issue stems from hardware instability or software corruption.
Initial Diagnostic Steps
Before diving into complex hardware adjustments, it is crucial to gather concrete data about the nature of the crashes. Are they blue screens (BSOD), black screen freezes, or sudden reboots? Check the Event Viewer in Windows 11 by right-clicking the Start button and selecting Event Viewer. Look under Windows Logs > System for critical errors occurring at the exact time of the crash. Common error codes include PAGE_FAULT_IN_NONPAGED_AREA, which often points to RAM issues, or KMODE_EXCEPTION_NOT_HANDLED, which may indicate driver conflicts.
If you have recently installed new hardware or updated drivers, consider rolling back those changes. The transition to Windows 11 Pro 23H2 Build 22631.3296 can sometimes introduce compatibility layers that struggle with older chipset drivers. Ensure your AMD Chipset Drivers are downloaded directly from AMD’s official website rather than relying on Windows Update, as these provide the necessary communication between the Ryzen 9 5900X and the X570 chipset.
BIOS and Firmware Updates
The ASUS TUF Gaming X570-Plus motherboard has had several BIOS updates specifically targeting Ryzen 5000 series stability and PCIe lane configuration. An outdated BIOS is a frequent culprit for random shutdowns and crashes in this generation of hardware. Visit the ASUS support page for your specific motherboard model and download the latest non-beta BIOS version. Use the EZ Flash utility within the BIOS to update the firmware, ensuring your power supply remains stable during the process.
After updating the BIOS, reset the settings to default by loading the optimized defaults. This clears any corrupted configuration files that might have persisted from previous versions. Once reset, you can proceed to test system stability without overclocks or aggressive memory timings. If the crashes cease after the BIOS update, the issue was likely related to early-stage microcode bugs affecting memory controller stability.
Memory Stability and EXPO Profiles
Your system uses 32GB of DDR4 RAM, which is excellent for multitasking but sensitive to timing configurations. Many users enable EXPO (Extended Profile for Overclocking) or DOCP profiles to achieve rated speeds immediately upon boot. However, not all RAM kits are perfectly compatible with every X570 board, especially when paired with high-core-count CPUs like the Ryzen 9 5900X. If you have EXPO enabled, enter the BIOS and disable it, setting the RAM to run at its JEDEC standard speed (usually 2133MHz or 2400MHz).
Run a stress test such as MemTest86 or the Windows Memory Diagnostic tool while the RAM is running at base speeds. If the system becomes stable, the issue is definitely related to the memory profile being too aggressive for your current voltage or CPU silicon quality. You can then try enabling EXPO again but manually adjust the DRAM Voltage slightly higher (e.g., from 1.35V to 1.38V) if safe, or loosen the primary timings. Always monitor temperatures using HWInfo64 to ensure the RAM is not overheating, which can also cause silent data corruption leading to crashes.
Power Supply and PCIe Configuration
While the RX 6600 is not a power-hungry card, the overall system power delivery must be stable. Check your PSU cables to ensure they are firmly seated. Additionally, verify that your Samsung 860 EVO SSD is connected to a SATA port that is supported by the AMD chipset and not disabled due to conflicting PCIe lanes. In some X570 configurations, enabling certain M.2 slots can disable specific SATA ports. Consult your motherboard manual to ensure your storage drive is on an active port.
For graphics-related crashes, try installing the AMD Adrenalin software using a clean installation option. Select "Factory Reset" during the setup process to remove old registry keys that might conflict with the new Windows 11 build. This is particularly important if you were upgrading from Windows 10, as leftover display drivers can cause kernel-level panics.
If you suspect deeper OS corruption, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in an Administrator Command Prompt. These commands repair protected system files and component stores, which can resolve unexplained application crashes and system hangs. For more insights on general Windows 11 stability, you might find Windows 11 Laptop Crashing Despite Lack of Resource-Intensive Programs: A Troubleshooting Guide helpful, as many diagnostic steps overlap across desktop and laptop environments.
Frequently Asked Questions
Why does my PC crash only when gaming?
This usually indicates a GPU driver conflict or thermal throttling. Ensure your AMD Adrenalin drivers are up to date and perform a clean install. Monitor your GPU and CPU temperatures to rule out overheating as the cause of the shutdowns.
Is it safe to keep EXPO enabled on my Ryzen 5900X?
It depends on the quality of your RAM kit and motherboard. While many users run EXPO stably, it is best practice to test stability first. If you experience crashes, disabling EXPO and running at JEDEC speeds is the most reliable fix until you can tune voltages manually.
How do I check if my Samsung 860 EVO is failing?
Use Samsung Magician software or CrystalDiskInfo to check the health status and SMART attributes of your SSD. If the drive reports bad sectors or imminent failure, replace it immediately, as a failing drive can cause system-wide crashes and data loss.
Should I update my BIOS before or after installing Windows 11?
It is highly recommended to update the BIOS before installing Windows 11. Newer BIOS versions include better UEFI implementations and security features that are required for modern operating systems to run correctly and securely on Ryzen platforms.
What should I do if the blue screen code keeps changing?
Changing BSOD codes often point to different faulty components, suggesting a broader issue like insufficient power delivery or a failing motherboard. Focus on stabilizing your power supply connections and testing individual RAM sticks one by one to isolate the problematic hardware.