Gears of War: E-Day PC Performance - CPU Pegging and Stutter
E-Day on PC is CPU-bound: it pegs almost any processor at 80-100% and produces stutters, freezes, and bad frame times even when the GPU is not fully used. Reported on 9800X3D, 7800X3D, 5800X3D, 9950X, and 24-core Intel chips through the beta and into early access.
The core problem: this is not a missing driver toggle. CPU spikes to 100% are what players link to hitches and hard freezes. Capping the frame rate reduces it - one tester still saw ~88% CPU on a 9800X3D at a 90 FPS cap. The Oct 5 patch added stability changes but mid-match freezes remain.
1The Fix Order That Actually Works
-
1
Confirm the install is on an SSD
Mechanical drives cause missing assets, low-poly models that never finish streaming, stutter, and crashes. Necessary but not always sufficient - reinstalling did not reliably clear texture pop.
-
2
Let first-launch shader compile finish, then restart once
Early hitches and the first benchmark run are tied to shader work. Do not judge performance during that pass.
-
3
Cap FPS in-game, then lock externally with RTSS if pacing is still rough
In-game caps: 60, 90, 120, 144, 240, Unlimited. Set at or just under your monitor refresh. A 4070 / 9800X3D player only got a solid ~120 FPS in PvP after a manual RivaTuner frame lock smoothed stutters the in-game cap did not.
-
4
Drop the settings that move the needle, in order
- Leave Ludicrous alone - treated as a future-hardware preset
- Ray tracing geometry, RT shadows, global illumination, reflections to Low
- Effects to Low or Medium; hair strands off; motion blur off
- Textures and geometry only after the RT options - dropping everything to Low barely moves FPS in a CPU-bound game
- Enable an upscaler: native is a large hit. DLSS or FSR on Balanced/Performance is what reached playable Versus rates
-
5
NVIDIA only: force a DLSS model preset if the image is soft or hitchy
NVIDIA App > Graphics > Program Settings > add the game exe > DLSS Override > Model Presets > Custom > Super Resolution > Preset K. A 7600X + 4070 player went from barely playable Ultra Performance / Low to ~100 FPS on Balanced. Try Preset K first, then the newest preset, and keep whichever holds frame time.
-
6
If the game hard-locks, force-close it
Often no error appears; some reports still need a PC reboot to kill the process. Close overlays and capture tools (Xbox Game Bar especially) before relaunching.
2Decision Points by Symptom
| Symptom | Do this |
|---|---|
| Stutter with high CPU, mid GPU usage | Cap FPS in-game, then RTSS a few frames under the cap. Lowering resolution alone will not fix this. |
| Low average FPS, GPU actually busy | DLSS/FSR Performance first, then cut RT/GI/reflections before touching textures. |
| Models stay PS1-level after a checkpoint | Verify SSD install and that the checkpoint load was not abnormally long. DDU + driver reinstall did not fix it for players who tried. |
| Wanting frame generation | Only after the base rate is already steady. Players who enabled it on an unstable base said it looked worse, not smoother. |
Video Walkthroughs
Common Mistakes
- Judging the port on Unlimited FPS. That is what pushes the 90-100% CPU behavior players are posting about.
- Starting on Ludicrous or native resolution. Both are heavy by design; the game's native warning is real.
- Assuming a new GPU driver or full settings wipe fixes CPU pegging. The same load shows up across AMD and Intel, including chips that should have headroom.
- Editing ini files for multiplayer. Players flagged it as a ban risk; nobody posted a confirmed safe, effective change.
- Treating an HDD install as "fine if it loads." Streaming failures are a separate, reported failure mode.