Quick Answer
A Gen 5 NVMe SSD does not normally create button-to-screen input lag. It can cause hitches if it overheats, fills up, or runs background tasks, so treat the symptom as storage stutter until frame-time evidence says otherwise. Use NVIDIA Reflex or AMD Anti-Lag, a 1000Hz polling check, CapFrameX and target 70C drive temperature checks, 15% free space, firmware, and asset-streaming hitches.
Build A Clean Baseline
Use one game, one route or benchmark pass, one preset, and one fixed cap. If the setup worked before, compare today's result with one familiar game scene instead of guessing from memory. Close capture overlays, RGB panels, browser video, and extra launchers before the first run.
Settings And Hardware Checks
In Windows 11, confirm Settings > System > Display > Advanced display shows the intended refresh rate. Then review Settings > Gaming > Game Mode and Graphics > Default graphics settings for VRR and Hardware-accelerated GPU Scheduling. In the game profile, check VSync, Reflex, Anti-Lag, raw input, and any manual FPS cap.
For the Gen 5 NVMe SSD, the practical fix is to check SSD temperature, firmware, free space, indexing, game install location, and M.2 lane sharing. Relevant reference hardware includes Crucial T700/T705, Corsair MP700, Samsung 990 Pro class Gen 4 fallback, PCIe 5.0 M.2 slots. Broad SA Gen 5 NVMe pricing is premium versus Gen 4, especially at 2TB and above. a hot M.2 slot under the GPU can create stutter that feels like lag.
Buying Decision
Keep the current part if the clean test passes. If it fails, buy only against the evidence: display timing points to a monitor or cable, USB timing to a device or port, storage spikes to the SSD, and network spikes to router placement or Ethernet.
FAQ
What should I check first for input lag on this setup?
Start with refresh rate, frame cap, and a clean baseline. Then check the driver, firmware, USB, storage, wireless, or cooling item tied to the recent change.
Should I replace the Gen 5 NVMe SSD immediately?
No. Replace it only after CapFrameX, PresentMon, HWiNFO64, a ping test, Ethernet, or direct USB shows the part is the limit.
What numbers show the fix worked?
A good result has steady 1% lows and no repeated jumps above 33ms. For 240Hz play, 4.2ms is the reference; for 60fps play, 16.7ms is the target.
Practical Check
Capture one clean run, note driver version, refresh rate, frame cap, and temperature, then compare Ethernet or direct USB before replacing hardware.
