Edited Jan 31, 2026 Most crashes require getting the details from the log file. The error dialog code is not always helpful. LINUX solutions not provided in this document. Consult a Linux User Group. Program crash logs are primarily located in the /var/log/ directory "Not Responding": DO NOT END PROGRAM or needed crash information will be excluded from the log. IMPORTANT: See examples of what crash reports look like near the MIDDLE of this document. THESE ARE DIAGNOSTICS. TO GET THE SOLUTIONS REPORT THE CRASH ERROR AS DESCRIBED sent to the helpdesk or support. Pagefile (out_of_sysmem) page two: https://robertsspaceindustries.com/spectrum/community/SC/forum/51473/thread/diagnosing-game-crashes-page-two 3221225477 Exception EXCEPTION_ACCESS_VIOLATION(0xC0000005): https://robertsspaceindustries.com/spectrum/community/SC/forum/51473/thread/exception-access-violation-0xc0000005-known-causes OS Crash, reset, blue screen: Use Windows Event Viewer Windows logs->System and look for RED ERROR at the time of the crash. There are dozens if not hundreds of reasons for game crashes ("stopped running", "stopped responding", "encountered an error", etc) all the way from Windows updates, Mainboard drivers, malware, protection software, system configurations, C++ Preview, Network Optimizers to only name a few. Crash reports which are not able to be solved by the player may require a system builder or IT specialist to find and correct. --> Crashes which do not get logged are usually caused by a hardware/driver/software/Protection or OS failure or configuration which closes the game before it can write the crash report. CRASHES which blue screen or reboot the computer are Windows, driver or hardware failures:<-- Use Windows Event Viewer WINDOWS LOGS->Programs or System and look for RED ERROR near the time of the crash. Another reason for lack of report is the launcher is running from the wrong location so old/wrong reports are being viewed. Intel Bluetooth and Wifi accelerators are examples of frequent crash culprits. Nvidia dynamic vibrance known recent crash cause. Vulkan can cause problems on SOME SPECIFIC cards and drivers on both Nvidia and AMD. EasyAntiCheat: https://support.robertsspaceindustries.com/hc/en-us/articles/4412276152343-Easy-Anti-Cheat-Troubleshooting 15000 16000 and EAC: Your Firewall/Antivirus may block connection. Avast, Acronis, BitDefender, WebRoot, Bullguard, ESET, RAV?, Avira? Trendmicro and Comodo are the worst for this. If those don't work, check the web site support for your MB. Download and install all the latest MB drivers (especially chipset and LAN.) If game resets/reboots the computer or blue screen this is an indication of a severe hardware failure. - Do NOT disable Windows pagefile no matter how much sysram you have. - 16GB sysmem players will need a custom pagefile. See helpdesk-volunteers. Many 32GB players now also need one. - Some crashes will be specific to game play or location in the 'verse. - Some crashes can be caused by corrupted bindings file. Back up: <drive>:\Roberts Space Industries\StarCitizen\LIVE\USER\Client\0\Profiles\default\ folder and delete. ---> In 3.23 many crashes are caused by Vulkan, Radeon Image Sharpening or Game Upscaling. See how to disable Vulkan below... - Possible cause Valorant or League of Legends installed: Riot Vanguard. The surest way to identify the cause of the crash and specifically address the cause with the least amount of guessing is the game log file as follows: SC GAME CRASH LOG (game.log file): If you have filename extensions disabled in Explorer you only see the text file named "GAME". In 2.0x Launcher SETTINGS GET LOGS Manual Steps: 1) Look in the Star Citizen Launcher SETTINGS GAMES. This is where the game is installed. 2.0 Launcher: Press the Gear Icon next to "Live", "PTU" etc. 2) Use Windows File Explorer to find that location on your computer. 3) Double click on the "game" or "game.log" file in \Live\ or PTU folder. 4) In VIEW menu set Notepad to WORDWRAP ON. 5) Scroll ALL the way to the bottom. Copy/Paste ONLY the text between: "Cloud Imperium Games public crash handler taking over..." and... "Run from internal:" -->NOTE: Older logs from past crashes are in \logbackups\ ============================================================== EXAMPLE CRASH MESSAGE looks like this but may have different errors: EXCEPTION_ACCESS_VIOLATION_0xC0000005_ (or diff ALL_CAPS_WORDS separated by underscores.) OR this: STATUS_CRYENGINE_WATCH_DOG(0x2BADFF60) OR this: Star Citizen process exited abnormally (code: nnnnnnnnnn) ============================================================== No other text is useful. ->IGNORE<- BELOW the crash report (is useless info for Reference not needed): Run from internal: Is fatal error: Is reported bug: Is GPU crash: Is Timeout: Is out of system memory: Is out of video memory: -->>HINT: Search for text: "Crash Hander Taking Over" Crash message is immediately BELOW that.<<-- LAST STEP in DIAGNOSIS: Years of experience has proven the last 20 lines containing the needed information will fit in the helpdesk chat. Paste the information there to get further assistance and diagnosis. GPU CRASHES: DXGI_ERROR_DEVICE_REMOVED DXGI_ERROR_DEVICE_HUNG STATUS_CRYENGINE_GPU_CRASH(0x2BADFF59) AFTERMATH https://robertsspaceindustries.com/spectrum/community/SC/forum/51473/thread/solutions-solve-gpu-crashes-in-the-game-log-file DISABLE VULKAN: Currently many problems are upscaling (disable). %localappdata%\Star Citizen\sc-alpha-3.23 ...\GraphicsSettings\GraphicSettings.json edit "GraphicsRenderer" to value 0 and save OR... Delete the file. AMD cards = Driver rollback Courtesy Elundil 3221225477 Exception EXCEPTION_ACCESS_VIOLATION(0xC0000005) in ESC OPTIONS GRAPHICS