To fix stuttering, low FPS, and crashing in Days Gone PC, start with a capped frame rate, borderless fullscreen, updated GPU drivers, and a clean shader cache, then tune foliage, draw distance, and clouds before touching texture quality. Days Gone usually feels dramatically better at a stable 60 FPS than at an erratic 80-100 FPS, especially while riding through the Cascade wilderness or fighting a large Freaker horde.
This isn't a game where dropping every option to Low automatically solves the problem. Texture quality mostly depends on VRAM, while foliage, geometry, and view distance put pressure on the CPU and streaming system. The goal is consistent frame pacing, not a pretty benchmark number that collapses whenever Deacon accelerates toward a new camp.
Before changing anything, check the game's listing on the official Steam page and compare your hardware against the published requirements. Also keep the Bend Studio PC launch information nearby if you need to confirm supported features or patch context.
Find the real cause before changing settings
Days Gone's performance problems tend to fall into three different buckets: a low average frame rate, inconsistent frame times, or a genuine crash. They can look identical for a few seconds, but the fixes are different. If the FPS counter says 55 yet the game feels jerky, you're dealing with frame pacing. If the number stays near 25 everywhere, your GPU or CPU is simply overloaded. If the game closes during loading, a new area, or a horde encounter, suspect drivers, corrupted files, overlays, or unstable hardware first.
Run the same test every time. Load a save near a busy settlement, ride from the O'Leary Mountain Safehouse toward Marion Forks, then spend one minute moving through the town. Repeat the route at night and test one Horde location only after the normal route is stable. This gives you a useful baseline instead of guessing from a quiet forest where almost any GPU looks fast.
| Symptom | Likely bottleneck | First move | What success looks like |
|---|---|---|---|
| Low FPS everywhere | GPU load or insufficient hardware | Lower resolution scale, clouds, and shadows | GPU usage remains high but FPS rises |
| Brief hitch while riding | World streaming or shader compilation | Use SSD storage and clear shader cache | Short spikes become less frequent |
| Stutter during hordes | CPU simulation and draw calls | Reduce foliage and geometry quality | Frame time stays steadier near enemies |
| Crash on startup | Driver, file, overlay, or config issue | Verify files and disable overlays | Game reaches the main menu reliably |
| Crash after playing | VRAM, heat, RAM, or unstable overclock | Remove overclocks and monitor temperatures | Long sessions stop ending at random |
Use MSI Afterburner, AMD Adrenalin, NVIDIA Performance Overlay, or another trusted monitor to watch GPU usage, VRAM, system RAM, and frame time. A GPU pinned around 95-99 percent means the graphics card is the limit. Low GPU usage with a busy CPU thread points toward foliage, geometry, NPC simulation, or background software. Don't chase a CPU percentage averaged across every core; one saturated thread can bottleneck the game while the overall CPU reading looks comfortable.
🎮 Days Gone
Looking to experience this game? Grab your digital key directly on our store for $39.99.
View on Steammoz Store →Build a reliable performance baseline
Install Days Gone on an SSD, preferably with at least 70GB of free space beyond the game's listed storage requirement. An SSD won't magically add 30 FPS, but it helps asset streaming and reduces the severity of hitches while crossing the map on Deacon's motorcycle. Leave free space on the Windows drive too, because an almost-full system disk can make shader and paging behavior much worse.
Use the official PC requirements as a floor, not a promise of locked performance. The minimum specification lists an Intel Core i5-2500K or AMD FX-6300, 8GB of RAM, and a GeForce GTX 780 or Radeon R9 290 with 3GB of VRAM. The recommended target is an Intel Core i7-4770K or Ryzen 5 1500X, 16GB of RAM, and a GeForce GTX 1060 6GB or Radeon RX 580 8GB. Modern systems below those GPU or memory targets can still run the game, but a stable 60 FPS at 1080p isn't guaranteed.
| Profile | Hardware target | Resolution target | Practical expectation |
|---|---|---|---|
| Minimum-like | 8GB RAM, GTX 780/R9 290 class GPU | 1080p Low, dynamic scale | 30-45 FPS with dips in towns and hordes |
| Recommended 60 | 16GB RAM, GTX 1060/RX 580 class GPU | 1080p Medium-High | Near 60 FPS with selective reductions |
| 1440p balanced | Modern 8GB GPU, six-core CPU, 16GB RAM | 1440p Medium-High | 60 FPS with clouds and foliage tuned |
| High-refresh | Modern upper-midrange GPU and CPU | 1080p or 1440p High | 80-120 FPS away from heavy hordes |
Update Windows and install the latest stable NVIDIA or AMD driver using a clean installation option. If your trouble started immediately after a driver update, test the previous stable driver rather than assuming newer always means better. Shut down Discord, Steam, Xbox Game Bar, GeForce Experience, Radeon recording, MSI overlays, RGB utilities, and browser hardware acceleration one at a time. Overlay conflicts are a common cause of launch crashes and odd alt-tab freezes.
On laptops, force Days Gone to use the dedicated GPU in Windows Graphics settings or the NVIDIA Control Panel. Set Windows to High performance, connect the charger, and avoid testing on a silent or battery profile. For desktop PCs, remove CPU and GPU overclocks temporarily. A setting stable in a lightweight esports game can fail during a long Days Gone ride when heat and memory use build up.
Best Days Gone PC settings for smoother FPS
Start with the High preset, then make targeted cuts. Keep textures at High if your card has enough VRAM; reducing textures often makes the image muddy without fixing CPU-side stutter. The biggest wins usually come from shadows, foliage draw distance, geometry, and cloud quality. These options influence the dense forests, camps, Freaker groups, and long sightlines that make the game expensive.
| Setting | Recommended value | FPS impact | Visual trade-off |
|---|---|---|---|
| Display mode | Borderless fullscreen | Low | More reliable alt-tab behavior |
| Resolution | Native, then 90-95% scale if needed | High | Lower sharpness at reduced scale |
| Texture quality | High with 6-8GB VRAM; Medium below that | Low to medium | Surface detail becomes softer |
| Shadow quality | Medium | Medium to high | Less definition in foliage and camps |
| Foliage draw distance | Medium | High, especially CPU-side | Vegetation appears later at range |
| Geometry quality | Medium-High | Medium | Less distant world detail |
| Cloud and fog quality | Medium or Low | Medium to high | Weather and skies look flatter |
| Motion blur | Off | Small | Cleaner camera movement |
| Field of view | Default or slightly lower | Medium | Lower peripheral visibility |
For a mainstream 1080p card, try 1080p native, High textures, Medium shadows, Medium foliage, Medium geometry, Low clouds, and motion blur off. Cap the result at 60 FPS through the game's limiter or your driver. If your machine can hold 75 FPS but cannot sustain 90, cap at 72 or 60 instead. A cap gives the CPU and GPU breathing room, reducing the violent frame-time swings that feel worse than a lower but consistent number.
At 1440p, lower resolution scale before textures if you have adequate VRAM. At 4K, use a 30 or 45 FPS target unless your GPU is genuinely high-end. Days Gone's distant terrain and weather effects can punish a card that looks perfectly comfortable indoors or during a quiet conversation at a camp.
Stop stuttering while riding and fighting hordes
Motorcycle travel is the clearest stress test because the game streams terrain, roads, foliage, enemies, and points of interest rapidly. If stutters happen only when accelerating, the issue is probably asset streaming rather than raw GPU power. Confirm the game is on an SSD, close disk-heavy applications, and avoid recording to the same drive. Keep the frame cap conservative while you test; an uncapped GPU can leave no headroom for sudden streaming work.
Horde fights are different. A large Freaker group stresses CPU simulation, animation, shadows, and visibility. Lowering only resolution won't fix this kind of hitch. Reduce foliage draw distance and geometry first, then shadows. Keep textures where your VRAM allows. If your GPU usage falls during a horde but frame time spikes, the CPU is the wall. Windows Game Mode can help background scheduling, but don't expect it to transform a four-core processor into a modern six-core chip.
Clear the DirectX shader cache after a driver change or a major settings reset: open Windows Settings, choose System, Storage, Temporary files, select DirectX Shader Cache, and remove it. The next launch may stutter briefly while shaders rebuild, so don't judge the result in the first minute. Repeated shader compilation every session is not normal; it suggests a cache, permissions, driver, or storage problem.
Disable background capture and test with variable refresh rate configured consistently. If you use G-SYNC or FreeSync, enable it for fullscreen or borderless applications and cap FPS a few frames below the monitor's maximum refresh rate. For a 144Hz display, 141 FPS is sensible when your system can sustain it; if it cannot, a locked 60 FPS is the smarter Days Gone profile.
For more general PC troubleshooting habits, Steamoz's ELEX crash and FPS guide and EscapeVR performance fixes cover the same driver, overlay, and frame-pacing traps in useful detail.
Fix Days Gone PC crashes and failed launches
Start with Steam's file check. In Steam, right-click Days Gone, open Properties, choose Installed Files, and select Verify integrity of game files. This replaces damaged or missing files without deleting your saves. It is especially worth doing after an interrupted update, a disk error, or a crash during shader compilation. If the verification repeatedly finds files, investigate the drive rather than verifying forever.
Next, disable every overlay and launch utility. Turn off Steam Overlay, Discord Overlay, Xbox Game Bar, NVIDIA or AMD recording, ReShade, and performance monitoring overlays for one test launch. A clean boot is useful if the game crashes during startup: temporarily disable non-Microsoft startup services, restart, and test. Re-enable items in batches so you can identify the offender instead of permanently losing useful software.
Check Windows Security and antivirus quarantine history. Security software can block an executable or prevent configuration files from being written. Add the game's installation folder as an exception only if you trust the installation, and never download random replacement DLL files from unofficial sites. Run Steam normally first; administrator mode should be a troubleshooting test, not the default fix.
Delete or rename the Days Gone configuration folder only after backing it up. A damaged graphics configuration can cause a crash before the menu appears. Renaming the folder forces fresh settings, but it may reset keybinds and video options. If the game crashes after changing resolution, launch in borderless mode or reset the display configuration through Steam launch options, then remove the launch option once you reach the menu.
Keep virtual memory enabled and set Windows to manage the paging file, particularly with 8GB or 16GB of RAM. Don't run aggressive memory cleaners. Monitor CPU and GPU temperatures during a long session, and test stock clocks. A crash after 30-60 minutes often points to heat, unstable undervolting, RAM errors, or VRAM pressure rather than a single bad game file.
If these steps fail, use Bend Studio support and include crash timing, hardware, driver version, Windows build, and the exact mission or location. The game's official Days Gone page is also useful for confirming the game's current platform information. Avoid stacking community mods on top of an unstable installation until the vanilla game runs correctly.
Verify the fix with a repeatable test
After each change, restart the game and repeat the same route from your saved position. Check the Cascade roads, a populated camp such as Copeland's camp, and one controlled Freaker encounter. Record average FPS, the worst one-percent lows, and whether the hitch happened during movement, combat, or loading. If one setting raises average FPS but makes frame time uglier, revert it. Smooth 60 FPS beats a flashy counter that dives every few seconds.
Use this order for the cleanest troubleshooting pass: update or roll back the GPU driver, verify files, disable overlays, move the game to an SSD, clear the shader cache, reset the config, apply the balanced settings profile, and finally cap FPS. Change one variable at a time. That sounds slow, but it prevents the classic mistake of lowering ten settings, seeing an improvement, and never learning which change actually solved the problem.
The strongest all-purpose profile is 1080p native, High textures, Medium shadows, Medium foliage, Medium geometry, Low clouds, motion blur off, borderless fullscreen, and a 60 FPS cap. From there, raise foliage or shadows only if frame time remains stable during motorcycle travel and hordes. Days Gone rewards restraint: consistent pacing, clean drivers, and a little GPU headroom will make Oregon feel far smoother than an unstable maxed-out preset.
For related optimization reading, see Steamoz's Far Cry 6 settings guide and Filament FPS tuning guide. The same principle applies here: measure the troublesome scenario, reduce the settings that affect that bottleneck, and protect frame pacing with a sensible cap.