Reduced startup speed when XMP is activated.
Reduced startup speed when XMP is activated.
Since I increased my RAM, I've observed my PC starting up more slowly. I'm curious about why this happened, especially after switching from a Corsair Vengeance LPX 2x8GB 3200 C16 to 2x Patriot Viper Steel 2x8GB (4 sticks) at 3600 C14. It wasn't a big issue before; it was almost immediate. With XMP turned on, boot times are around 2-3 seconds to load the logo, then 3 seconds to enter BIOS, followed by 4-6 seconds for login. When XMP is off, it's similar—2-3 seconds to post, 3 seconds to boot into BIOS, and 1 second to reach the login screen. Can anyone explain what might be affecting this? For context, AIDA64 mentions XMP actually speeds things up: XMP Off: XMP On:
Everything appears normal, matching typical XMP configurations, so the problem likely lies elsewhere. Consider performing a memory stress test using tools like TestMem5 to detect instability that could affect performance. While possible, such issues are uncommon. Viper Steel B die kits are widely used with Ryzen setups, and your configuration isn’t drastically unusual—just note that higher bin kits often require XMP profiles for memory overclocking, which may not be compatible here.
It's a really bad RAM test. Use HCI MemTest86, Tm5 Antiphase, Prime95 Large FFTs, and real RAM checks—not the weak MemTest86 that misses unstable issues. Consider removing some BIOS overclock profiles from the web and see if boot times improve. Stock XMP settings on boards aren't much better than OEM specs. Keep voltages under 1.7V, avoid fan cooling, as heat is a big concern for memory stability.
Alright, thanks. I didn't know that. I just left it on for half an hour to see if it would pick up any errors instantly, but when I closed the program all the log said was: ========= TestMem5 Log File ========= Customize: Extreme1 @anta777 Start testing at 4:26, 1.5Gb x16 I guess I'll leave it on overnight to see if it picks up any errors.
It seems I misunderstood what caused the slow start. What I thought was related to XMP was actually due to a longer boot time when restarting. My mistake.