My old ASUS B450M system died, so I replaced the motherboard with an MSI MPG B550M Gaming Plus, moved everything into a new case, improved the cooling, and replaced my old SSDs with a Kingston NV3. The rest of the main hardware is a Ryzen 7 5700X3D, RTX 3080 Ti, and 32GB of Corsair Vengeance DDR4.
I performed a clean Windows installation, updated the BIOS, installed the AMD chipset and NVIDIA drivers, enabled XMP, Resizable BAR, Secure Boot, and TPM, and verified that the GPU is in the top PCIe x16 slot and the memory is in A2/B2. Temperatures, clocks, and utilization all look normal, and I have not applied any registry or command-line tweaks.
The average FPS in Warzone and Hunt: Showdown is roughly similar to before, but frame pacing is much worse. I get noticeable hitching and microstutters, with FPS fluctuating much more aggressively—for example, dropping from around 200 to 160 or 130, or jittering between 116 and 120 even when capped at 120. This did not happen with the old motherboard and SSDs. What hardware, BIOS, Windows, driver, storage, or networking issue should I investigate next?
5 Answers
The Kingston NV3 is a DRAM-less NVMe drive that relies on host memory, while the older Samsung drive has onboard DRAM. Games such as Warzone can stream assets while you play, so storage latency or power-state transitions could show up as hitches even when average FPS is high. Test by installing the game on the old SSD, check the NV3 firmware and SMART health, monitor disk latency and active time, and temporarily disable PCIe Link State Power Management. If necessary, investigate NVMe APST settings as well.
Run a long memory test rather than relying only on the fact that the system boots. XMP can appear stable while producing errors or intermittent frame-time spikes, especially when the memory modules use different memory chips or the new board has different signal behavior. Test both sticks individually, then try JEDEC/default memory settings with XMP disabled. If the stutters disappear, manually tune the memory or replace the mismatched kit.
The same RAM worked in the previous system, but a different motherboard can still react differently to its timings and voltage. An overnight MemTest86 or a thorough OCCT memory test would be worthwhile.
Since the problem began immediately after changing the motherboard, the board itself should be treated as a suspect even if every setting looks correct. The fastest way to confirm that is to test with another compatible motherboard, or temporarily reinstall the old Windows drive if it is still available. Also reseat the GPU, RAM, CPU power connectors, and modular PSU cables. A board, cable, or power-delivery problem can cause inconsistent frame pacing without obvious crashes or abnormal temperatures.
Even experienced builders still have to eliminate the simple physical-contact and cable possibilities. A bad motherboard can be difficult to identify from software checks alone.
Use LatencyMon or Windows Performance Analyzer while reproducing the hitch to look for a driver causing high DPC or interrupt latency. Network drivers are worth testing specifically: disable the unused Wi-Fi or Ethernet adapter in Device Manager, update the active LAN driver from the motherboard manufacturer, and compare results offline. Also test with NVIDIA overlay, HAGS, MPO, FreeSync/G-Sync, and third-party monitoring tools disabled. If software tests remain clean, compare individual CPU, GPU, memory, and SSD benchmarks against expected results and then swap the motherboard or PSU to isolate hardware.
A clean Windows install means the shader caches were rebuilt from scratch. Some games compile shaders during gameplay, which can cause temporary hitching after a reinstall or driver change. Clear and rebuild the NVIDIA and game shader caches, allow the game time to finish compiling assets, and compare 1% and 0.1% lows instead of average FPS. Also verify that Windows and the NVIDIA control panel both use the monitor's 280Hz refresh rate and that G-Sync/V-Sync/ frame caps are configured consistently.
This is less convincing if the stutters remain after many hours of play, but it is still worth ruling out because the issue appeared after reinstalling Windows and changing storage.
If the game runs smoothly from the old drive, that isolates the storage path rather than the GPU or CPU. The lack of dedicated DRAM does not automatically make the NV3 defective, but it makes it a useful variable to test.