Windows 11 fresh installation may trigger blue screens when XMP is enabled post-installation
Windows 11 fresh installation may trigger blue screens when XMP is enabled post-installation
We created a few PCs the previous day using: Asus Prime B760-Plus i5-13500 Corsair 32 GB (16GB x 2) 7200 MHz DDR5 WD_Black 1TB NVMe EVGA 650W. After assembling and installing Windows 11 Pro on both, we began configuration. When we realized XMP wasn’t enabled, we switched to BIOS and activated it. Initially, they would only display a blue screen unless XMP was turned off. Even after updating the BIOS, the same issue persisted. Since we hadn’t made further adjustments yet, we cleared the partitions and reinstalled Windows 11 Pro with XMP enabled. This resolved the blue screens, and we were able to disable XMP without problems, then re-enable it smoothly. We repeated the process on the other system successfully. It seems the problem lies with Windows itself rather than memory stability, as previous discussions suggested. We’re still curious if others have found alternative solutions beyond a full reinstall or manual memory tweaks. Do you know if Microsoft has acknowledged this as an issue?
The easiest way to confirm if this is a memory stability issue, or some weird bug, would be to do some memory testing and see if they're producing errors. My first thought would be that 7200 on a B760 board with an i5 is fairly optimistic, but I haven't been checking out OC forums to know what speeds they can achieve on average.
This situation points to a potential memory problem with your setup. Running at 7200MT/s isn't consistent across all LGA 1700 CPUs when using XMP profiles, particularly for the higher-end models. The memory controllers on newer generations are much better than those on older ones, so issues here are likely due to hardware limitations. You have two choices: adjust the IMC voltages manually in hopes of fixing it, or accept slower memory speeds until the issue resolves.
One of the two setups matches exactly what I outlined earlier, functioning smoothly with all updates and drivers from the Armory Crate software included with the board. There were no blue screens or other issues. The second setup uses an ASUS PCE-AX58BT Wi-Fi card originally placed in the first PCe x1 port. After installing the Intel chipset driver via Armory Crate, the system would restart with a blue screen again unless the frequency was adjusted. Removing the Wi-Fi card eliminated the blue screen at 7200 MHz. Interestingly, reinstalling the same card in the same slot resolved the problem completely.
It's unlikely there's anything magical going on, what happened either you wrote corrupted data to disk (corrupting the OS) or it wasn't perfectly stable, you only thought it was. You can use y-cruncher VT3 to test memory stability. If you truly believe Windows or Microsoft is at fault here, find a way to reproduce the problem and isolate it to Windows (rather than memory or XMP) then you can blame them.
What you mention could stem from driver or software problems. Personally, I wouldn't rely on motherboard utilities such as Armoury Crate for this situation—they're known to be inconsistent. Still, it's important to note: memory can exist in various conditions, and overclocking often leads to unstable behavior rather than complete failure. Silent instability is a common issue, causing file corruption and occasional crashes without obvious signs. Without thorough stability testing tools designed for memory, it's hard to confirm or rule out the cause just from casual checks. It's possible your overclock runs smoothly, but many users agree it may not be reliable long-term. BSODs usually indicate unstable overclocks, especially in memory, while unusual behavior during Windows installation isn't something I've encountered outside of those specific cases. If you're experiencing strange events with the CPU and Wi-Fi, hardware issues like the memory controller might play a role—but overclocking increases stress on all components, making problems more likely to appear.