02-01-2024 12:34 PM - edited 02-02-2024 11:51 AM
Hello,
Before I begin, here are my specs:
All drivers installed and currently on the latest BIOS 1801 (ME 16.1.30.2307) , chipset / intel me/ serial IO / etc.
Now on to the problem...
I'm experiencing what appears to be a memory stability or training issue where my system becomes unstable after the first reboot. The only time my system runs well and games don't lag or stutter is after a cmos flash or bios flash. After a bios or cmos flash, I'll set XMP 1, boot into Windows and all is well. However, when I reboot or shut down my system and power back up, all my games become overrun w/ input lag and stutter. It's a night and day difference. My first thought was memory instability but it just doesn't make sense that the only way to fix it is by flashing either the bios/cmos to correct the issue. If it works the first time, it should certaintly work the second time unless something is changing behind the scenes. I've attempted lowering my memory frequency all the way down to 6400 from 7200 1 step at a time to see if any of these frequencies will resolve the issue. The confusing part is that I'll still continue to pass memory stress tests such as y-cruncher VST, tm5, linpack, memtest86, etc, even though all of my games now are clearly lagged and inputs delayed. This very fact makes this a very difficult issue to troubleshoot. W/ that said, I've also tried disabling mrc fast boot and fast boot. The only thing that makes sense to me is that the memory is training poorly upon reboot regardless of the mrc fast boot setting. I also tried locking in my memory values right after a bios/cmos flash and enable mrc fast boot, but that doesn't seem to work either. Memory temps are NOT an issue and never break 40 degrees during gaming. I even have a mini fan pointed at them because I dabble in memory overclocking. I'd also like to note I've tested my system at the stock/default memory profile where my memory runs at 4800mhz, same story. Runs just fine after the initial flash, and then performance tanks after the first reboot or power off.
I have been dealing with lag/stutter on this setup for quite a while now, and I'm pretty sure it's related to memory training but I can't be 100% certain. Anyone have any thoughts or suggestions on how to resolve this? I know asus has dozens of memory training algorithms and I wonder if any of these settings can ensure my memory trains properly every single time. Any help will be appreciated.
Solved! Go to Solution.
02-03-2024 01:54 PM - edited 02-03-2024 01:56 PM
MRC Fastboot is enabled by default. The "best way" to train the memory is to use parameters that are stable. Most of the MRC settings do not need to be touched. The easiest method for tuning memory is tuning voltages for VCCSA, IVR TX, etc. If the system is stable at stock (no XMP or overclocking) then there's nothing wrong with the CPU or drivers.
02-01-2024 04:32 PM - edited 02-01-2024 04:32 PM
Hello cthree
What I might do is install HWinfo, with HWinfo running play a game.
When the lag sets in, check all your components are working normally.
Check your gpu clock speeds to make sure your gpu is ramping up, you can also check to see it's drawing the recommended wattage.
Post a screenshot of Hwinfo after your games lag, be sure to include the maximum columns. Maybe this will tell us something.
It can also detect errors as shown on the far right.
Click the pic to make it bigger.
02-02-2024 12:00 AM
Thank you for the response! I have already gone to great lengths troubleshooting this. I've confirmed that my ram, gpu, psu, nvme drive are good, either through extensive stress/stability testing and/or switching them out with a known good piece of hardware. I've already swapped out my cpu/psu/ram/nvme with known good ones just to ensure it wasn't hardware failure of some type.
W/ that said, I'll gladly post all columns of hwinfo64 tomorrow when my system will likely begin to lag after rebooting. My short term fix in the interim is to flash cmos, jump into the bios and enable XMP1. When doing this, my system will be perfectly stable and responsive until I reboot. Maybe you'll catch something I overlooked.
02-03-2024 03:22 PM - edited 02-03-2024 03:25 PM
After starting up my system again today, everything is back to lagging. Here are my system stats during a game.
02-01-2024 10:37 PM
Also, what are you running for storage? What GPU do you have in there? Which drivers?
The input lag, which peripherals are you using, how do they connect? Wired? Wireless?
Across all games equally?
Do some handle it better than others?
What are your UEFI settings, specifically things like ASPM and Virtualization.
Need a lot more info, but we can likely help you get to the bottom of it.
02-02-2024 12:24 AM
Hey man, thank you for taking the time to help me out!
GPU is MSI RTX 4090 Suprim Liquid. Currently the latest drivers. I've tried previous drivers as well resulting in no impact on my issue.
NVME drive is a Samsung 980 Pro 1tb (4th gen) and a Sabrent 3rd generation 1tb nvme
Keyboard: Steelseries Apex Pro TKL. I also have a Corsair K70 RGB TKL which I tested with to see if my keyboard was rhe culprit.
Mouse: Currently using the Lamzu Thorn / Atlantis OG 4k. Both wireless. I've also tested using wired to rule out the mouse along with every polling rate, no impact. I have also tried every USB port.
Sound: I swap between a wireless and wired headset. No difference when using either my wired (connected to sound card via 1/8th stereo connector), or Wireless (usb).
Networking: I currently use the onboard intel NIC with latest drivers. I've also installed a realtek 2.5gb pcie nic to test, no change.
When I experience the clear input lag/stutter, it's across all games. The problem remains until I clear cmos and enable xmp1.
UEFI settings: XMP1, I leave ASPM at defaults currently. What I have learned with the rtx 4090 is that it doesn't seem to like aspm disabled. It's okay to disable native aspm and clock gating, but fully disabling aspm in the bios results in stutter/hitches. This was not the case with my 3080. With that said, I've also tested disabling aspm, yet my problem rears it's ugly head after rebooting or shutting down and powering back up. I've tested virtualization on/off. Fast boot on/off, secure boot and tpm on, csm disabled, rebar and 4g disabled.
As I mentioned earlier, I have a strong suspicion that memory training is good after a clearing cmos and then memory trains poorly after rebooting or shutting down. I've spent a lot of time tuning my memory with the hope of resolving this and despite how stable I get my memory, even with loose timings, my system will become unstable out of no where because I rebooted. I'm curious what else other than poor memory training could cause such behavior.
02-02-2024 02:21 AM
There's a free little program called Latency Monitor that might reveal something useful.
Also, when you are running HWInfo, check out the WHEA errors section.
If you see issues in either, at least it's a start in terms of where the problem might be.
02-02-2024 11:11 AM - edited 02-02-2024 11:34 AM
Hi John,
Appreciate the tip.
I'm already aware of latency monitor and have been using it for years and dpc latency checker pre windows 10. My DPC latency is excellent w/ no spikes. I use this quite a bit to confirm I'm not running faulty driver causing dpc latency issues.
Also, no WHEA errors.
02-01-2024 11:16 PM
As above, best to list all system specs. Storage especially, as there have been some GEN 5 drive teething issues.
02-02-2024 11:18 AM
Hi There,
I've come across many of your replies in the past. You're obviously quite knowledgeable in general but also w/ memory overclocking and configuration. Do you have any suggestions on the best way to train memory on this board and how to immediately lock in those settings? On other boards I simply disable fast boot and/or enable fast boot (slow training) on say an MSI board, and then once I'm happy w/ my memory settings, I immediately go back into the BIOS and enable fast boot to stop my memory from being trained further.
Also, could a faulty intel me or chipset driver be contributing to this? The behavior that I experience screams memory instability issues since performance varies greatly from each reboot. Since my sticks pass every mem test after hours and hours of stress tests, I can't help but think it's a training issue. I've tested and checked virtually everything else.