If PUBG: BATTLEGROUNDS crashes on startup, drops you back to the desktop, sits on a black screen after the logo, or won't launch at all, it's tempting to throw every fix you find at it at once.
But PUBG runs more than one security check at launch, and its official support center has separate pages for BattlEye errors and for Xenuine errors, so the exact message on screen decides where to start.
We went back through PUBG's official troubleshooting pages on November 10, 2026 and organized them by symptom: what the error points to, what to try first, and what to collect before you open a ticket.
This covers the Steam version on Windows PC, and it skips registry edits and files from unofficial sites on purpose. If the game only crashes while a recorder or overlay is running, start with our guide to games crashing while recording, because the fix there is usually on the recording side.
Otherwise, find your symptom in the table, then work through the steps below one change at a time and relaunch after each, so you know which step actually solved it.
PUBG crash and launch errors by symptom (as of November 10, 2026)
| Symptom or error message | Cause PUBG Support points to | What to try first |
|---|---|---|
| Closes right after launch, or crashes after the PUBG logo | PC below minimum specs, damaged game files, or permission problems | Check specs, restart Steam, verify game files, update Windows and your GPU driver, then run Steam and TslGame.exe as administrator |
| Stuck on 'Starting BattlEye Service...' or a BattlEye launcher error | A temporary BattlEye service fault or damaged game files | End BEService in Task Manager, or start BattlEye Service in services.msc; if it keeps happening, delete the BattlEye folder and verify game files |
| Failed to initialize BattlEye Service: Driver Load Error (577) | Missing Windows security updates | Install every pending Windows update and reboot; if it persists, contact support with a screenshot of the error |
| BattlEye: Corrupted Data (error 25) | Corrupted game files; PUBG's Korean support page adds that it also appears when illegal programs or modified PAK files are detected | Close the game fully, delete the BattlEye folder, verify game files, and do a clean reinstall if that fails |
| Xenuine 'Application is interrupted by external software', or anti cheat codes starting with 0x | Programs running alongside the game (helper, graphics enhancement or system monitoring tools), GPU overclocking, missing system files, or failed memory allocation | Close or uninstall unrelated programs, add PUBG to your antivirus exclusions, run System File Checker for 0x200 and 0x220 codes, reboot for 0x420 and 0x430 codes |
| Black screen, or 'Frequency Out of Range' | A monitor refresh rate or graphics driver setting that doesn't match your display | Set the refresh rate to your monitor's spec (60Hz, 144Hz and so on), roll back a driver update that started it, and disable fullscreen optimization |
| TslGame.exe Application Error, or Error at hooking API 'LoadStringA' | Low memory, or a Visual C++ Redistributable that didn't install properly | Reboot, close everything else and verify game files; for LoadStringA, install the latest supported Visual C++ Redistributable |
| Crashes in the middle of a match | Many possible causes: server or network conditions, PC specs, heat, overclocking | Remove overclocks, check fans, dust and temperatures, avoid running two games at once, and send the crash dump to support if it repeats |
The short answer: PUBG's official order starts with specs, launch options and file verification
PUBG's General Crashing and Performance Guide gives one shared order for problems that come with no error message: check minimum hardware, restart your PC and router, remove Steam launch options, verify the integrity of game files, update Windows, update graphics drivers, do a clean reinstall, disable hardware overclocking, and disable fullscreen optimization for TslGame.exe.
Only after that does it send you to PUBG Support. If you do see an error message, jump to that row in the table first.
The minimum specs listed on PUBG's support page and the Steam store, as of November 10, 2026, are 64 bit Windows 10, an Intel Core i5-4430 or AMD FX-6300, 8 GB of RAM, an NVIDIA GeForce GTX 960 2GB or AMD Radeon R7 370 2GB, DirectX 11 and 40 GB of storage. Not sure what's in your PC?
You can check your PC specs on Windows 11 in about a minute. The launch options step is the one people skip. PUBG's guide says players passed around all kinds of Steam launch commands during early access to squeeze out performance, and it recommends deleting every one of them so they can't be the cause.
Even if you don't remember adding any, open the box and look. And change one thing at a time. If you verify files, update drivers and add an antivirus exclusion all at once, you won't know which one worked the next time this happens.
How to fix PUBG crashing or not launching, step by step
- 1Clear launch options and verify game filesRestart your PC, then open Steam. In your Library, right click PUBG: BATTLEGROUNDS, open Properties, and delete everything in the Launch Options box on the General tab. Then go to Installed Files (Local Files in older Steam versions) and click Verify integrity of game files. Steam checks every file and downloads again anything missing or damaged. For 'Failed to initialize STEAM', PUBG's page says to run both Steam and PUBG as administrator first, and if that fails, to try the launch option -autoconfig or -windowed. Once you've seen the result, clear the option again.
- 2Get the BattlEye service running againIf the launcher hangs on 'Starting BattlEye Service...', open Task Manager (Ctrl+Shift+Esc), find BEService under background processes, click End task, and relaunch. PUBG also documents a second route: press Windows+R, type services.msc, find BattlEye Service in the list and start it manually. If it keeps stalling, close the game completely, delete the BattlEye folder inside Steam\steamapps\common\PUBG\TslGame\Binaries\Win64, and verify game files again so Steam restores a fresh copy. If the error reads 'Failed to install BattlEye Service', reinstall from an account with administrator rights and add the BattlEye executable to your security software's exclusions.
- 3Clear out antivirus conflicts, helper tools and overclocksWhen you see a Xenuine error or a code starting with 0x, look at what's running next to the game. PUBG's advice is to turn off or uninstall helper programs, graphics enhancement tools, system monitoring apps and GPU overclocking utilities, and to add PUBG as an exception in your antivirus, whether that's Windows Security, Norton, McAfee or something else. If ReShade was ever installed, its dxgi.dll in the Win64 folder can stop the game from starting, so delete it and reinstall. For 0x200 and 0x220 range codes, run sfc /scannow from an administrator Command Prompt to repair system files; for 0xA00, reinstall DirectX and the Visual C++ Redistributable. For a code that isn't on PUBG's list, save your running programs with tasklist /v > "%USERPROFILE%\Desktop\Process.txt" and attach that file to your ticket.
- 4Update Windows and your graphics driverPress Windows+R, type ms-settings:windowsupdate, click Check for updates, install everything and reboot. PUBG's support page says Driver Load Error (577) can appear when Windows security updates are out of date, so for that error this is the first step to take. Update your GPU driver from NVIDIA or AMD, and if problems continue, PUBG's guide suggests removing the driver cleanly with Display Driver Uninstaller before installing it again. Your GPU model and DirectX version both show up in dxdiag; here's where to find your DirectX version. It works the other way too: if a black screen or 'Frequency Out of Range' started right after a driver update, PUBG's advice is to roll back to the previous stable driver.
- 5Do a clean reinstallIf nothing above works, reinstall cleanly. Uninstall PUBG from your Steam Library, press Windows+R, type %localappdata% and delete the TslGame folder, then delete BEService_pubg.exe from Program Files (x86)\Common Files\BattlEye and the PUBG folder from Steam\steamapps\common (or the steamapps\common folder on whichever library drive you used). Clear the download cache under Steam Settings > Downloads, restart Steam and download the game fresh. As of November 10, 2026, PUBG: BATTLEGROUNDS is free to play on Steam, so the fresh download costs nothing, but plan for the 40 GB of free space the official minimum specs call for and the download time. PUBG's logo crash article also suggests keeping the game on the same drive as Windows, ideally an SSD for better performance. Your settings, sensitivity included, are commonly reported to live in GameUserSettings.ini under TslGame\Saved\Config, so copy that Config folder somewhere safe first. If your aim feels off afterward, our PUBG sensitivity reset fix walks you through restoring it.
- 6Collect crash data and contact PUBG SupportStill crashing after all of that? Open a ticket on PUBG's support site. The official template asks for the date the problem started, a detailed description, the exact error message, your dxdiag report and the crash dump. Create the dxdiag report with Windows+R, dxdiag, then Save All Information. The dump is the newest folder in %localappdata%\TslGame\Saved\Crashes: zip it and attach it. For large files, PUBG suggests uploading to a cloud drive such as Google Drive and pasting the link. Its page on crashes after the logo also asks for a screenshot or video of the issue, so if you have a recording of the match that crashed, trim that part and include it.
Check before you relaunch or open a ticket
- Your PC meets the official minimum: 64 bit Windows 10, i5-4430 or FX-6300, 8 GB RAM, GTX 960 or R7 370, 40 GB free.
- The Launch Options box is empty, and you verified game files again after a fresh restart.
- PUBG is excluded in your antivirus, and helper, graphics enhancement, monitoring and overclocking tools are closed.
- Only PUBG is running; PUBG Support notes that two games running at once can collide and close the game.
- Your CPU fan spins, the vents are clear and the case has been dusted.
- Your dxdiag report, the newest crash dump and a screenshot of the error sit together in one folder.
Before you relaunch, check the footage of the match that crashed
DOR is a free Windows game recorder. When you launch PUBG it detects the game and records the whole match automatically, saves kills, knocks and deaths as separate automatic clips, and can run an automatic highlight analysis once the match ends. Everything lands in My Clips in the app.
If PUBG crashed mid match, open My Clips before you relaunch and look at the last match. If it caught the stutter or freeze right before the crash, trim just that part in the app and give it a like.
Storage cleanup only kicks in when full match recordings go over their share (5 GB by default), it removes the oldest videos first, and recent recordings and liked videos stay. The original recordings saved on your PC carry no watermark, so you can attach them to a support ticket as they are.
Once PUBG is stable again, let it record every match as usual: our PUBG recording guide covers the full flow, and how to share PUBG gameplay with friends covers sending your chicken dinners.
