PUBG Crash Troubleshooting
PUBG Crashing Mid Game: TslGame.exe, LowLevelFatalError, BattlEye, and CrashDump Fix
Fix PUBG closing to desktop during a match, TslGame.exe Application Error, Crash Reporter, LowLevelFatalError, DXGI errors, BattlEye corrupted data, memory crashes, overlays, and unstable GPU or RAM settings.
Last updated: July 18, 2026
When PUBG crashes mid game, closes to the desktop after entering the lobby, crashes during fights, or shows TslGame.exe Application Error, the correct fix depends on the crash timing and the exact message.
Do not begin with a full reinstall. First separate a launch failure from a true in-game crash, remove old Steam launch options, verify the PUBG files, close overlays, check memory and temperatures, and only repair BattlEye when the error specifically mentions BattlEye.
Fastest safe troubleshooting order
Record the exact error and time → restart Windows and Steam → remove all Steam launch options → verify PUBG files → close overlays and recording tools → check RAM, virtual memory, drivers, temperature, and power → return GPU undervolting, CPU overclocking, and XMP or EXPO to default → repair BattlEye only for BattlEye errors → clean reinstall only as the final step → collect CrashDump and DxDiag for support.
Do not confuse crashes with FPS drops
This guide is for PUBG closing, showing a crash reporter, or returning to the desktop. If the game stays open but stutters, has bad 1% lows, or feels choppy, use the PUBG FPS drops guide instead.
Contents
- Identify the crash type first
- Run the five-minute common check
- Remove Steam launch options
- Verify PUBG game files
- Fix TslGame.exe and error-message cases
- Check RAM, virtual memory, and background apps
- Close overlays and conflicting tools
- Check drivers, overclocking, heat, and power
- Repair BattlEye only when the error names it
- Compare fullscreen optimization
- Clean reinstall PUBG as the final step
- Collect CrashDump, DxDiag, and support details
- Frequently asked questions
Identify the PUBG Crash Type First
The first clue is whether PUBG fails before the lobby, closes after entering the lobby, crashes after several minutes, or shows an error such as LowLevelFatalError, DXGI, BattlEye, or TslGame.exe Application Error.
| Symptom | Likely area | Check first |
|---|---|---|
| Small loading window appears, then disappears | Launch failure, BattlEye, runtime, or file issue | Use the PUBG launch-error guide |
| Lobby opens, then PUBG closes | Launch options, overlay, local config, or damaged files | Clear launch options and verify files |
| Crashes after 5 to 30 minutes | Memory, heat, driver, power, or overclock instability | Monitor RAM, temperatures, clocks, and power |
| Crashes during gunfights, smoke, cities, or vehicle movement | GPU load, VRAM, driver, or system instability | Limit FPS, close overlays, compare drivers |
| TslGame.exe Application Error | Memory pressure, damaged files, runtime, or permission issue | Close apps, verify files, check memory |
| LowLevelFatalError or DXGI error | Graphics driver, GPU stability, DirectX path, or damaged files | Driver, default clocks, temperature, file verification |
| BattlEye: Corrupted Data | Anti-cheat or PUBG file corruption | Rebuild BattlEye folder and verify files |
| PC restarts or monitor loses signal | Hardware, power, heat, GPU driver, or memory instability | Stop repeated testing and check system stability |
If the whole PC restarts, treat it differently
A game window closing is not the same as a full PC reboot, No Signal display, or black screen under load. Those symptoms require power, GPU, RAM, and temperature checks before more game launches.
Five-Minute Common Check
- Take a screenshot of the exact error message.
- Write down whether the crash happens in the lobby, during match loading, during fights, or after a fixed amount of time.
- Press Ctrl + Shift + Esc and close remaining PUBG, TslGame, BattlEye, and Steam processes.
- Restart Windows.
- Open only Steam and PUBG for the first test.
- Do not launch Discord, OBS, browser tabs, overlays, game filters, or monitoring tools yet.
- Test Training Mode or a normal match and compare whether the crash still happens.
Recent changes matter
A PUBG patch, graphics-driver update, BIOS update, XMP/EXPO change, undervolt profile, overlay install, or Windows update just before the crash began is often more useful than another random tweak.
1. Remove All Steam Launch Options
Old PUBG optimization commands can conflict with current builds. Test the game with an empty launch-options field before changing drivers or reinstalling.
- Open Steam Library.
- Right-click PUBG: BATTLEGROUNDS.
- Select Properties.
- Open the General section.
- Copy any launch options into a text file as a backup.
- Delete every launch option so the field is blank.
- Restart Steam and test PUBG again.
Avoid outdated launch commands
Commands such as -malloc, -USEALLAVAILABLECORES, forced DirectX modes, custom resolutions, and old window-mode commands can make crash troubleshooting harder.
2. Verify PUBG Game Files
A damaged, missing, or incomplete file can crash PUBG after a patch or during asset loading. Steam can compare local files with the official installation and replace damaged content.
- Restart the computer before starting verification.
- Open Steam.
- Run file verification from the Installed Files section.
- Wait for the scan and any replacement downloads to finish.
- Restart Steam.
- Launch PUBG without overlays or custom launch options.
Verification should come before reinstalling
A full reinstall is slower and may leave local configuration behind. Verify files first unless PUBG or support guidance specifically requires a clean reinstall.
3. Fix TslGame.exe and Error-Message Cases
| Error message | Most useful first direction | Avoid |
|---|---|---|
| TslGame.exe Application Error | Close heavy apps, check memory, verify files, compare permissions only once | Assuming RAM is broken immediately |
| Error at hooking API LoadStringA | Repair official Microsoft Visual C++ Redistributables | Downloading individual DLLs from random sites |
| Crash Reporter or Unknown Crash | Save CrashDump, remove launch options, verify files, close overlays | Changing several settings at once |
| LowLevelFatalError, DXGI, or D3D error | Driver, GPU stability, temperature, default clocks, file verification | Only lowering graphics settings without checking stability |
| BattlEye: Corrupted Data | Rebuild PUBG BattlEye folder and verify files | Deleting anti-cheat files when no BattlEye error is shown |
TslGame.exe Application Error
Close browsers, launchers, recording tools, and other memory-heavy apps. Open Task Manager and check whether memory usage remains close to full while PUBG is running. Then verify the game files.
Error at hooking API LoadStringA
Repair or reinstall the official Microsoft Visual C++ Redistributable packages. Install both the current x64 and x86 packages when the official page provides both. Do not download a single DLL from third-party websites.
Crash Reporter, LowLevelFatalError, DXGI, or D3D errors
- Remove all Steam launch options.
- Verify PUBG files.
- Close NVIDIA, AMD, Discord, Steam Overlay, Xbox Game Bar, OBS, RTSS, and game filters.
- Compare the latest graphics driver with the last stable version if the crash began right after an update.
- Return GPU undervolting, CPU overclocking, and RAM XMP or EXPO to default for one test.
- Check CPU and GPU temperature and clock speed after 20 minutes.
4. Check RAM, Virtual Memory, and Background Apps
| Check | Warning sign | First action |
|---|---|---|
| RAM usage | Stays near 90% or higher before the crash | Close browsers, Discord streams, launchers, and recording tools |
| Commit memory | Reaches the limit before the crash | Restore virtual memory to system-managed size |
| XMP or EXPO | Random crashes started after enabling a memory profile | Test default memory speed |
| Disk activity | 100% disk usage or background installs during matches | Pause downloads, cloud sync, and scans |
- Open Advanced system settings in Windows Search.
- Go to Performance → Settings → Advanced.
- Open Virtual memory.
- Turn on Automatically manage paging file size for all drives.
- Restart Windows and test PUBG again.
Do not disable the paging file while diagnosing crashes
The paging file can help when memory pressure rises and can also be involved in crash-dump creation. Use system-managed size unless you have a specific tested reason not to.
5. Close Overlays and Conflicting Tools
Programs that record, inject overlays, show performance data, apply filters, or hook input can conflict with PUBG or its anti-cheat. Test PUBG in a clean environment before deciding the game files are broken.
- Discord Overlay and screen sharing
- Steam Overlay
- NVIDIA Overlay, Instant Replay, and game filters
- AMD Overlay and recording tools
- Xbox Game Bar background recording
- OBS and other capture tools
- MSI Afterburner and RivaTuner Statistics Server
- RGB, mouse, keyboard, and macro software
- ReShade, filter tools, and unofficial helper programs
Re-enable tools one at a time
If PUBG becomes stable after closing everything, re-enable one program at a time. That method is slower but it identifies the real conflict.
6. Check Drivers, Overclocking, Heat, and Power
- Install pending Windows updates and restart.
- Check the graphics driver from NVIDIA, AMD, Intel, or the PC manufacturer.
- If crashes began right after a new driver, compare the previous stable version.
- Return GPU overclocking or undervolting to default.
- Return CPU overclocking, curve optimizer settings, and tuning profiles to default for testing.
- Disable RAM XMP or EXPO for one comparison test.
- Compare CPU and GPU temperatures immediately after launch and after 20 minutes.
- Check whether clock speed drops as temperature rises.
- For laptops, connect the power adapter and use the manufacturer’s performance or balanced mode for comparison.
| Observed result | Likely direction | First comparison |
|---|---|---|
| Crashes only with uncapped FPS | GPU load, heat, or power stability | Set a stable FPS cap |
| Crashes after 20 minutes | Thermal or memory buildup | Record temperature and clock speed |
| Random crashes after XMP/EXPO | Memory-profile instability | Test default RAM speed |
| PC restarts instead of only PUBG closing | Power, GPU, RAM, or thermal issue | Stop repeated launches and check hardware stability |
7. Repair BattlEye Only When the Error Names BattlEye
Use this step when the message specifically mentions BattlEye, such as BattlEye: Corrupted Data, Failed to initialize BattlEye, or a BattlEye service error. For silent mid-game crashes, start with launch options, file verification, overlays, memory, and drivers first.
- Close PUBG and Steam completely.
- Back up the BattlEye folder to another location.
- Delete the BattlEye folder from the PUBG installation.
- Run Steam file verification.
- Restart Windows.
- Launch PUBG again.
Do not modify anti-cheat files without a related error
Changing BattlEye files too early can hide the real cause and make troubleshooting harder.
8. Compare Fullscreen Optimization
After basic checks, compare disabling fullscreen optimizations for TslGame.exe. This is a comparison test, not a universal fix. Restore the original setting if it makes no difference.
- Right-click TslGame.exe.
- Open Properties.
- Open the Compatibility tab.
- Check Disable fullscreen optimizations.
- Apply and test PUBG.
- Remove the check mark if stability does not improve.
9. Clean Reinstall PUBG as the Final Step
Use a clean reinstall after simpler checks fail. Back up local settings, keybinds, graphics settings, screenshots, or replay-related files before deleting local folders.
- Uninstall PUBG from Steam.
- Press Windows + R.
- Type %localappdata%.
- Back up and then delete the TslGame folder.
- Delete the remaining PUBG folder under Steam\steamapps\common.
- Open Steam Settings → Downloads → Clear Download Cache.
- Restart Steam and Windows.
- Install PUBG again.
- Launch the game with no overlays and no custom launch options.
Clean reinstall can reset settings
Deleting local PUBG folders may remove graphics, control, and local configuration data. Back up first, then restore only what you truly need.
10. Collect CrashDump, DxDiag, and Support Details
If the same crash continues, stop changing random settings and collect useful information for PUBG Support.
- Date and time the crash started
- Whether it happens in lobby, match loading, mid-game, fights, smoke, cities, or after a fixed number of minutes
- Full error message and screenshot
- CPU, GPU, RAM, Windows version, and laptop/desktop model when relevant
- Graphics-driver version
- Whether XMP, EXPO, CPU overclocking, GPU undervolting, or GPU overclocking is active
- Overlays, antivirus, macro tools, capture tools, and monitoring programs
- DxDiag system-information file
- The latest CrashDump folder that matches the crash time
- Already attempted fixes
Submit crash data only to official support
Crash folders and DxDiag can include system information. Share them only through official support channels.
Key takeaway
For PUBG mid-game crashes, start with launch options, Steam file verification, overlays, memory, drivers, default clocks, and temperature checks. Repair BattlEye only when the message names BattlEye. Use a clean reinstall and CrashDump submission only after the safer checks fail.
Frequently Asked Questions
Why does PUBG crash to desktop without an error?
Start with empty Steam launch options, file verification, overlay closure, and memory checks. If it happens after several minutes, also check temperatures, clock speed, and power stability.
What should I do after a PUBG update starts causing crashes?
Restart Steam, remove old launch options, verify game files, close overlays, and compare any recent graphics-driver or tuning changes.
Is TslGame.exe Application Error always a RAM failure?
No. Memory pressure, damaged files, runtime issues, or program conflicts can also trigger it. Check memory usage and verify files before assuming hardware failure.
Should I delete BattlEye folders?
Only when the error clearly mentions BattlEye. For silent crashes, begin with file verification, overlays, memory, driver, and clock stability checks.
Why does PUBG crash after 20 minutes?
Thermal buildup, memory pressure, power limits, or unstable overclocking are more likely when a crash appears only after time passes. Compare temperature, clock speed, RAM use, and default tuning settings.
Should I update the graphics driver?
Yes, compare current official drivers, but if the crash began right after an update, test the previous stable version instead of assuming the newest driver is always best.
Will reinstalling PUBG fix every crash?
No. Reinstalling cannot fix unstable RAM, heat, driver crashes, power problems, overlays, or an unstable undervolt. Reinstall after basic checks fail.
What should I send to PUBG Support?
Send the error time, crash stage, full message, system specs, driver version, overclock status, steps already tried, DxDiag, and the newest CrashDump folder.
Related guides
Official references
- PUBG Support: General Crashing and Performance Guide
- PUBG Support: How to Verify the Integrity of Game Files
- PUBG Support: Game Keeps Crashing
- Steam Support: Verify Integrity of Game Files
- Microsoft Learn: Latest Supported Visual C++ Redistributable Downloads
- Microsoft Support: How to Perform a Clean Boot in Windows
