Back Then crashing and low FPS on PC usually comes down to four things: outdated GPU drivers, corrupted or shader-related game data, overly ambitious settings for your graphics card, or background software fighting the game for memory and GPU time. Start by verifying the Steam installation, updating your driver with a clean install, switching to a sensible 1080p profile, and disabling overlays. If the game still crashes, use the Windows crash log and Back Then's local files to identify whether the problem is a driver, an Unreal Engine rendering feature, or unstable hardware.
That order matters. Many players jump straight into obscure launch commands, delete random folders, or lower every option to Low. That can hide the symptom without fixing the cause, and it often makes a story-heavy game look needlessly flat. Back Then is built around detailed environments, lighting, and memory-driven visual transitions, so the goal is consistent frame pacing rather than a meaningless peak FPS number.
Check Your PC Against Back Then's Real Requirements
Before changing settings, compare your machine with the requirements shown on the official Back Then Steam page. The minimum specification is aimed at getting the game running, not guaranteeing a locked 60 FPS. A GTX 1060-class card may launch the game comfortably at 1080p, but complex scenes, high-quality shadows, and cinematic effects can still push frame times well above 16.7 milliseconds.
Back Then benefits from a quad-core-or-better processor, at least 16 GB of system memory for a smoother Windows session, and an SSD. If the game is installed on a hard drive, texture streaming can create pauses that look like low FPS even when the average frame rate seems acceptable. An SSD won't magically increase your GPU's rendering power, but it can reduce asset-loading hitching and shorten recovery after a crash.
| Component | Minimum Starting Point | Recommended Target | What It Changes |
|---|---|---|---|
| Operating system | Windows 10 64-bit | Windows 10 or 11 64-bit, fully updated | Driver, DirectX, and shader compatibility |
| Processor | Core i5-8400 or Ryzen 5 2600 class | Core i7-9700 or Ryzen 7 3700X class | Frame-time stability during streaming |
| Memory | 8 GB RAM | 16 GB RAM | Reduces paging and background-app stutter |
| Graphics card | GTX 1060 6 GB or Radeon RX 580 class | RTX 2070 or Radeon RX 5700 XT class | Resolution, lighting, shadows, and effects |
| Storage | Enough free space for the installation | SSD with at least 20 GB free | Faster loading and fewer streaming hitches |
These comparisons are useful, but don't treat them as a promise. Laptop GPUs with the same name as desktop cards can be substantially slower, and an eight-year-old CPU may struggle with minimum-spec graphics hardware. Close browsers, launchers, RGB utilities, and recording tools before testing. If RAM usage is already above 85 percent at the desktop, Back Then has very little headroom.
🎮 Back Then
Looking to experience this game? Grab your digital key directly on our store for $3.24.
View on Steammoz Store →Stop Back Then Crashes Before Touching Advanced Settings
First, verify the installation. In Steam, right-click Back Then, open Properties, select Installed Files, and choose Verify integrity of game files. This replaces missing or damaged packages without deleting your saves. It is particularly worthwhile after a failed update, a power cut, or moving the game between drives.
Next, perform a clean graphics-driver update. Download the current driver directly from NVIDIA's official driver page or AMD's official support page. Choose the clean-install option where available. If the crashes began immediately after a driver update, rolling back one stable release is sensible; newer is not automatically better for every game.
Turn off overlays for the first test run. Disable Steam Overlay under Back Then's Properties, then temporarily disable Discord Overlay, Xbox Game Bar, GeForce Experience or Radeon recording, MSI Afterburner’s on-screen display, and third-party frame counters. Overlays hook into the rendering pipeline. They are normally harmless, but a crash that disappears when they are off gives you a clear culprit.
Also remove compatibility experiments. Right-click the game's executable, open Properties, select Compatibility, and make sure forced compatibility modes are off unless the developer specifically recommends them. Do not enable permanent administrator mode as a first response. It can create permission mismatches with save files and cloud synchronization rather than solving the underlying crash.
For missing DLL messages, repair the official Microsoft Visual C++ Redistributable packages for both x64 and x86, then reboot. Use Microsoft's latest supported Visual C++ downloads, not a random DLL website. If Windows reports damaged system files, run Command Prompt as administrator and use sfc /scannow. Follow that with DISM /Online /Cleanup-Image /RestoreHealth only if SFC reports that it could not repair everything.
When a crash happens during startup
Try launching with every overlay disabled and the monitor disconnected from HDR or unusual refresh-rate modes. If you can reach the title screen but the game crashes while loading a save, test a new game first. A new game loading successfully points toward a damaged save or a bad streamed asset, while a crash before the menu suggests drivers, permissions, or rendering initialization.
Do not delete your saves blindly. Back up the Back Then save folder first. The exact location can vary, but common Unreal Engine save locations include %LOCALAPPDATA%, %APPDATA%, or the game's Steam userdata directory. Search for a folder named Back Then and copy it elsewhere before testing. If Steam Cloud restores a broken file, disable Cloud temporarily, test the local backup, and re-enable synchronization only after confirming which save works.
Use This Back Then FPS Profile at 1080p
For most mid-range PCs, begin at 1920x1080 in fullscreen or borderless mode, whichever produces fewer alt-tab problems on your system. Set a frame-rate cap close to your monitor's refresh rate: 60 FPS for a 60 Hz display, or 58-60 FPS if you want consistent pacing with adaptive sync. A stable 45 FPS is better than a wildly fluctuating 60-35 FPS range, especially during slow exploration where uneven frame delivery is more noticeable than a lower average.
| Setting | Recommended Value | FPS Impact | Visual Trade-Off |
|---|---|---|---|
| Resolution | 1920x1080 | Very high | Keep native resolution before sacrificing clarity |
| Resolution scale | 90-100% | Very high | Lower to 85% only when GPU-limited |
| Shadows | Medium | High | Small objects lose softer shadow detail |
| Global illumination or lighting | Medium | High | Interior mood becomes slightly less rich |
| Post-processing | Medium | Medium | Less bloom, blur, and cinematic softness |
| Effects | Medium | Medium | Subtle reduction in particles and transition effects |
| Textures | High with 6 GB VRAM | Low to medium | Lower only when VRAM usage causes hitching |
| View distance | Medium or High | Medium | Controls distant scene detail and streaming load |
| Motion blur | Off | Low | Sharper camera movement and easier troubleshooting |
| V-Sync | Off with adaptive sync; On if tearing persists | Low | May add input latency when enabled |
Lower settings in this order: shadows, lighting, effects, then resolution scale. Keep textures high if your GPU has enough VRAM because texture quality usually changes image detail more than it changes raw performance. If you see sudden pauses rather than a consistently low frame rate, lower view distance and textures one step and monitor VRAM usage in Task Manager or your driver overlay.
Back Then is not a competitive shooter, so you don't need to chase 144 FPS at the expense of image quality. A 40 or 60 FPS cap can also reduce GPU heat and prevent clocks from constantly bouncing between power states. That matters on laptops, where thermal throttling often masquerades as a game-engine problem after ten or fifteen minutes.
Find Out Whether Your GPU or CPU Is the Bottleneck
Use a repeatable test instead of judging performance from one dramatic scene. Load the same save, walk through the same room for two minutes, and record average FPS plus the 1% low if your overlay provides it. Then change one setting at a time. If GPU usage stays around 95-100 percent and lowering resolution scale increases FPS, the graphics card is the limit. If GPU usage sits below 80 percent while one or two CPU threads are busy, reduce view distance, effects, and background processes instead.
Watch temperatures at the same time. A GPU running near its thermal limit may lower clock speed, while a CPU can throttle even when its average usage looks moderate. Clean dust from vents, raise a laptop's rear edge, and use a balanced or performance power profile while plugged in. Avoid aggressive overclocks during troubleshooting; unstable memory overclocks can cause crashes that look exactly like bad game files.
| Symptom | Likely Limit | First Test | Best Fix |
|---|---|---|---|
| Low FPS everywhere | GPU or resolution | Drop resolution scale to 80-85% | Use 1080p Medium and cap FPS |
| Stutter entering new areas | Storage, VRAM, or shader compilation | Check SSD and VRAM usage | Move to SSD; lower textures and view distance |
| FPS falls after 15 minutes | Thermal throttling | Compare clocks and temperatures | Improve cooling and use a stable power profile |
| GPU below 80%, CPU thread saturated | CPU or background software | Close recording and browser apps | Lower view distance and cap frame rate |
| Crash during transitions | Driver, overlay, or damaged asset | Verify files and disable overlays | Clean-install driver and retest a new save |
For a deeper look at this style of PC troubleshooting, our guides to ELEX crash and FPS fixes and Dragonkin graphics settings cover the same GPU-versus-CPU diagnostic process in different engines.
Advanced Fixes for Persistent Stutter and Crashes
If basic changes fail, test Windows features one by one. Hardware-accelerated GPU scheduling can help some modern systems and hurt others, so switch it, reboot, and compare the same save. Do the same with Windows Game Mode. Keep variable refresh rate enabled if it produces smooth frame delivery, but disable it temporarily if the game flickers or loses focus when switching windows.
Check your page file too. Let Windows manage virtual memory on the SSD instead of disabling it. An 8 GB system running Back Then with a browser, launcher, and voice chat can run out of committed memory even when physical RAM appears nearly full. A page file will not make the game faster, but it can prevent sudden application exits caused by memory pressure.
Clear shader caches only after recording your current settings. NVIDIA Shader Cache, AMD's shader cache, and Windows DirectX shader data can occasionally become corrupted after a driver change. Clearing them forces recompilation, so the first run may stutter more than normal. Let the game sit at the menu for a few minutes, then replay the same area. If stutter steadily improves, shader compilation was likely part of the problem.
Use the Steam launch option -dx11 only as a diagnostic experiment if Back Then's default rendering path repeatedly crashes on your machine. It may improve compatibility on older hardware, but it can also remove features or fail to launch if the build does not support that mode. Remove the command if it changes nothing. Never stack five launch options copied from a forum post; you won't know which one helped or caused the next problem.
Finally, inspect Windows Event Viewer under Windows Logs > Application immediately after a crash. A faulting module naming your GPU driver points toward a driver or hardware stability issue. A Back Then executable fault with no driver module makes file verification, save testing, and overlay removal more useful. Capture the timestamp, error code, GPU model, driver version, and what happened on screen before contacting the developer through the official Steam discussion and support channels.
The clean testing order that saves time
Run one controlled pass after each change: reboot, close overlays, launch Back Then, load the same save, and repeat the same route. Start with file verification, then the driver, then the 1080p Medium profile, then temperatures and memory. This approach is less exciting than downloading a mystery optimizer, but it tells you exactly what worked.
For reference, Steamoz's PC requirements guide explains why listed minimum specifications should be treated as a floor, while our Desperados III performance coverage shows how frame pacing can matter more than headline FPS in slower, cinematic games. Those lessons apply neatly here.
The winning Back Then setup is usually conservative: current stable drivers, verified files, no overlays during testing, an SSD installation, 1080p resolution, Medium shadows and lighting, High textures when VRAM allows, and a firm 60 FPS cap. If your hardware cannot hold that target, cap at 45 or 30 rather than letting the frame rate swing. Once the game runs for a full hour without a crash or hitch, raise one setting at a time. That is how you keep Back Then's visual atmosphere intact without turning every memory transition into a troubleshooting session.