How to Fix StarCraft II Core Graphics Driver Crashes on Windows
To fix a StarCraft II core graphics driver crash, restart Windows, confirm which GPU the game uses, install a compatible graphics driver, and run Battle.net's Scan and Repair tool. If the crash continues, test with lower graphics settings, Windows' high-performance GPU preference on a dual-GPU PC, and overlays or custom GPU tuning turned off. Change one thing at a time so you can identify what actually helps.
The error message is a symptom, not a diagnosis. A driver update, damaged game files, an overlay conflict, or unstable GPU settings can all be worth checking. Start with the low-risk steps below; save hardware troubleshooting for cases that persist across more than one game or application.
Before troubleshooting: note when the crash happens
Write down whether StarCraft II crashes at launch, when a match loads, during a large battle, or after switching windows with Alt+Tab. Also note whether the problem began after a Windows or graphics-driver update. If other 3D games crash too, focus sooner on the driver, temperature, power, or hardware. If only StarCraft II fails, prioritize its files, settings, and software conflicts.
1. Restart Windows and install regular updates
Choose Restart from the Windows power menu to reload the graphics stack; closing the game or Battle.net alone does not do that. When Windows returns, open Settings > Windows Update, install pending standard updates, and restart again if prompted. A restart is especially useful after a driver installation or sleep-and-wake issue.
Do not move to preview or Insider builds just to troubleshoot one game. Keep the PC on a normal supported Windows installation and test StarCraft II again before making another change.
2. Identify the graphics adapter StarCraft II can use
Right-click Start, open Device Manager, and expand Display adapters. Record the exact names shown. A laptop may list both integrated graphics and a discrete NVIDIA or AMD GPU; that is normal. A warning icon, a missing adapter, or only a generic display adapter can indicate a Windows or driver problem that should be addressed before changing game settings.
You can also press Windows+R, enter dxdiag, and review the Display tabs. Blizzard's DirectX graphics test guide explains how to check the graphics information Windows reports. Keep a DxDiag report if you later contact support.
3. Install a compatible graphics driver
Get the driver for the exact adapter and Windows version. For laptops, check the PC maker's support page first: manufacturers sometimes customize graphics packages for their models. For a desktop graphics card, use the GPU maker's official source:
Install the latest compatible stable package, then restart Windows. Avoid third-party driver download sites and do not assume a driver for the integrated GPU is the right package for a separate graphics card.
4. If the problem began after a driver update, reset or reinstall it
If the crash started immediately after a driver change, first return any per-game control-panel overrides to their defaults. If that does not help, use Device Manager's Roll Back Driver option when available, or install the previous stable package from the PC or GPU manufacturer. The newest release is not always the best troubleshooting choice when the timing points to a recent update.
If updating over the existing package failed, follow the vendor's clean-install instructions instead of deleting driver folders by hand. Intel documents a clean-install option that removes old drivers and resets Intel graphics settings; it also recommends checking with the computer manufacturer for customized laptop packages. See Intel's clean installation guide. AMD provides system stability troubleshooting guidance. Restart after reinstalling, and leave overclocking or undervolting disabled while you test.
5. Repair StarCraft II in the Battle.net app
Open the Battle.net desktop app, select StarCraft II, and open the game menu beside the Play button. Choose Scan and Repair and let the scan finish before launching the game. This checks the installed files and can replace damaged or missing game data. Try this before uninstalling the entire game; a full reinstall takes longer and is not the first step to take.
After the scan, test the same mode or replay that usually causes the crash. If Battle.net reports that it repaired files, avoid changing several graphics options at the same time so the result stays clear.
6. Temporarily reduce graphics load and change display mode
If the game reaches a match but crashes under load, lower the available graphics-quality settings for a diagnostic test. You can also reduce the resolution temporarily. A stable run at lower settings does not prove a specific component is defective, but it helps narrow the cause to graphics load, driver behavior, temperature, or a particular setting.
If the crash follows Alt+Tab or a display change, test windowed or borderless mode instead of fullscreen, or switch back if the crash began after changing modes. Once the game is stable, raise settings gradually and repeat the scenario that used to trigger the failure.
7. Set the preferred GPU on a dual-GPU Windows 11 PC
If Windows lists both integrated and discrete graphics, you can set a per-app graphics preference. In Windows 11, open Settings > System > Display > Graphics. Add or select the StarCraft II desktop app, choose Options, select High performance if that is the discrete adapter you want to test, choose Save, and restart the game. The app's executable may be in the StarCraft II installation folder, so browse to it if it is not already listed.
Microsoft's Windows 11 graphics settings guidance documents this per-app preference. Names and available choices vary by PC. Treat it as a preference, not a guarantee that every display path uses that adapter. Skip this step if the computer has only one GPU.
8. Turn off overlays and custom GPU tuning for a clean test
Temporarily close game overlays, capture tools, frame-rate counters, and hardware-monitoring utilities. Examples include Discord's overlay, Xbox Game Bar capture, NVIDIA or AMD overlays, screen recorders, and monitoring tools. Blizzard notes that some overlay programs can crash Battle.net games in its Overlay Incompatibilities support article. Disable one program at a time when practical, then relaunch StarCraft II.
Also remove custom GPU overclocks, undervolts, forced anti-aliasing, or other per-game driver overrides while testing. Restore the profile to its default settings and close only applications you recognize; do not end Windows processes at random. If the game becomes stable, re-enable tools one by one to identify a conflict.
How to verify the fix
Reproduce the condition that used to cause the crash. If it happened during a large battle, load a replay or play long enough to reach a similar scene. If it happened after Alt+Tab, repeat that transition. Check that the game launches, enters a match, and remains stable through the specific action associated with the error.
- If a driver update fixes it, keep the driver and re-enable background apps one at a time.
- If stability returns only at lower settings, raise them gradually to isolate the setting or load level involved.
- If it works only with overlays disabled, update or leave the conflicting tool off.
- If the issue started with one driver release, stay on the last stable compatible version and check the vendor's release notes before updating again.
If StarCraft II still crashes
Save a DxDiag report and note the crash timing, GPU model, driver version, Windows version, and troubleshooting steps already tried. Use Blizzard's StarCraft II support hub for game-specific help. If several games also crash, or you see visual artifacts, system restarts, or the GPU disappearing from Device Manager, investigate system stability, cooling, power, and hardware rather than reinstalling StarCraft II repeatedly. Stop overclocking while diagnosing and use the PC or GPU maker's diagnostics or support instructions.
In short, the most efficient order is: restart and update Windows, identify the GPU, update or roll back its driver, repair StarCraft II, reduce graphics load, verify the GPU preference on hybrid systems, and test without overlays or custom tuning. That sequence separates common software causes from broader graphics or hardware problems without changing several variables at once.