Minecraft Black Screen or Freeze on Launch: How to Fix It

A black screen, frozen window, or "Not Responding" title on launch almost always means Java is busy loading assets in the background or failing to hand off rendering to your GPU. It looks like a dead crash, but in most cases Windows is simply waiting for Java threads to finish building model registries or creating an OpenGL context.

Before changing display settings or reinstalling drivers, determine whether the game is frozen or just taking time to start up.

Rules of thumb for launch delays

First launches and heavy modpacks require patient waiting before you declare a hard freeze. I'd give the process a few minutes and check background activity before forcing a restart.

• On a fresh version launch: wait 3 to 5 minutes. SuperLauncher downloads required version binaries, client libraries, and the matching Java runtime (Java 8, 17, 21, or 25) before opening the window.
• On heavily modded profiles with 150 or more mods: wait 3 to 5 minutes on an SSD or up to 8 minutes on a mechanical hard drive. Mod loaders like Fabric, Quilt, and NeoForge stitch thousands of textures and build block models during this window.
• Check Task Manager: press Ctrl + Shift + Esc, open the Details tab, and locate javaw.exe. If CPU usage is active and memory allocation is rising steadily, Java is working. Do not click inside the window, because clicking triggers the Windows "Not Responding" overlay.
• Check game logs: open %APPDATA%\.minecraft\logs\latest.log in Notepad. Scroll to the bottom and press F5 to refresh. If new timestamps appear, the game is actively loading assets.

If CPU and disk activity drop to zero for over two minutes while the screen remains black, work through the causes below in order.

Cause 1: A heavy modpack or shaderpack is still loading

The most common cause of a black or unresponsive launch window is background asset processing on modded profiles. Modern mod packs load hundreds of entity models, custom sound events, and GLSL shaders before rendering the main menu. During this phase, Java blocks the main display thread, causing Windows to mark the window as unresponsive and fill the display buffer with black or white.

How to fix it

1. Open Task Manager with Ctrl + Shift + Esc and monitor javaw.exe. Watch the memory column. If memory rises continuously (such as moving from 2 GB to 4 GB), let the process run without clicking the window.
2. Check if memory allocation is capping out. Open SuperLauncher, go to Settings > 'Game launch', and adjust the 'Memory (RAM)' slider. Move it from a lower setting to a higher preset (available presets: 2, 4, 6, 8, 12 GB). Bumping allocation from 2 GB or 4 GB to 6 GB or 8 GB gives mod loaders space to construct texture atlases without triggering constant garbage collection stalls.
3. Check shader packs. Shader packs placed in .minecraft\shaderpacks run through the Iris mod on Fabric, Quilt, and NeoForge. Compiling complex shaders on startup can hang the display window. Open SuperLauncher, go to your profile, open the Version page, click 'Installed content', and click Disable or Remove on shader mods or Iris to test startup speed.
4. Alternatively, click 'Open version folder' in SuperLauncher to open %APPDATA%\.minecraft\versions\<profile name>, go to the shared .minecraft\shaderpacks folder, and temporarily move shader zip files to another folder on your desktop.

How to confirm it worked

Launch the profile again. The window transitions from a black box directly into the Minecraft title screen. Opening %APPDATA%\.minecraft\logs\latest.log shows the final initialization log lines:

[Client thread/INFO]: Setting user: Player
[Client thread/INFO]: Sound engine started

Cause 2: Laptop running the game on integrated graphics

On laptops equipped with dual graphics (an integrated Intel or AMD processor GPU paired with a dedicated NVIDIA GeForce or AMD Radeon card), Windows often assigns javaw.exe to the low-power integrated graphics chip by default. Integrated chips often lack the dedicated VRAM and OpenGL driver extensions required by modern Minecraft versions and shaders, causing javaw.exe to hang with a black screen when initializing the display buffer.

How to fix it

I'd configure per-app GPU preference directly in Windows settings to force Java onto your dedicated card.

1. Close Minecraft and SuperLauncher completely.
2. Press the Windows key, type Graphics settings, and open the System Settings page.
3. Under "Custom options for apps", ensure "Desktop app" is selected in the dropdown and click "Browse".
4. Locate the exact javaw.exe binary used by your game. You can find the exact path listed in the launcher log at %APPDATA%\SuperLauncher\logs\superlauncher.log under the Java executable field.
5. Add javaw.exe to the list, click "Options", select "High performance" (which explicitly names your dedicated NVIDIA or AMD graphics card), and click Save.
6. If you use an NVIDIA graphics card, open NVIDIA Control Panel, go to Manage 3D Settings > Program Settings, click Add, select javaw.exe, and set "Select the preferred graphics processor for this program" to "High-performance NVIDIA processor". Click Apply.

How to confirm it worked

Launch Minecraft, enter a world or check the F3 debug screen. The top-right corner of the F3 screen displays your dedicated graphics card model instead of Intel UHD Graphics or AMD Radeon Graphics. The initial black display window resolves into the main menu within seconds.

Cause 3: Outdated or corrupted graphics drivers

Outdated, corrupted, or generic Windows Update display drivers frequently fail during OpenGL context creation or frame buffer swapping. When Minecraft attempts to open a full-screen or windowed OpenGL canvas, broken driver DLL files can freeze the render thread while keeping the process alive, producing a permanent black window.

How to fix it

I wouldn't rely on Windows Device Manager to update graphics drivers, as it frequently installs basic display drivers without full OpenGL support.

1. Identify your graphics card manufacturer (NVIDIA, AMD, or Intel).
2. Visit the official manufacturer driver download page and download the latest installer package for your specific GPU model.
3. Run the installer. For NVIDIA cards, select "Custom (Advanced)" installation and check "Perform a clean installation" to clear cached driver profiles.
4. If a standard driver update fails to fix the hang, download Display Driver Uninstaller (DDU) from Wagnardsoft, restart Windows into Safe Mode, run DDU to wipe old display drivers and registry keys, reboot normally, and install the fresh driver package.

If the display driver crashes completely and closes the game window instead of hanging, see our guide to exit code 1 for general crash handling, and our guide to GLFW error 65542 if the log points at OpenGL driver support.

How to confirm it worked

Launch Minecraft. The game window initializes without stalling. Open %APPDATA%\SuperLauncher\logs\superlauncher.log in Notepad and verify that the game console output records clean OpenGL context creation with vendor driver details:

[Client thread/INFO]: LWJGL version 3.3.3
[Client thread/INFO]: GL_RENDERER: NVIDIA GeForce RTX 3060/PCIe/SSE2
[Client thread/INFO]: GL_VERSION: 4.6.0 NVIDIA 551.86

Cause 4: Antivirus software locking game files or native libraries

Antivirus programs (such as Windows Defender, Avast, AVG, or Bitdefender) inspect newly extracted JAR files, DLL native libraries, and asset indexes when Minecraft starts up. When SuperLauncher launches a profile, Java extracts native libraries like lwjgl.dll and OpenAL.dll to temporary folders. If an antivirus real-time scanner locks these native files to scan them while Java attempts to hook into them, the main thread freezes indefinitely.

How to fix it

Add folder exclusions in your security software for the main game and launcher directories.

1. Open your antivirus security suite settings.
2. Locate the Exclusions, Exceptions, or Allowed Apps section.
3. Add a full folder exclusion for %APPDATA%\.minecraft and %APPDATA%\SuperLauncher.
4. In Windows Security: open Start > Settings > Privacy & Security > Windows Security > Virus & threat protection > Manage settings > Add or remove exclusions > Add an exclusion > Folder, then select %APPDATA%\.minecraft.
5. Save settings, restart SuperLauncher, and launch the profile.

How to confirm it worked

Minecraft launches cleanly without hanging on file validation. Opening Task Manager shows javaw.exe loading without background antivirus services consuming high CPU cycles during startup.

Cause 5: Corrupted resource packs or shaderpack settings

High-resolution resource packs (256x or 512x textures) or outdated shader packs in .minecraft\shaderpacks can exhaust VRAM or fail during texture atlas stitching. If a shader pack requests OpenGL functions unsupported by your current setup, the render pipeline drops into an unhandled wait state, leaving the display canvas black.

How to fix it

Reset video options and disable custom pack loading.

1. In SuperLauncher, click 'Open version folder' on your profile page to view %APPDATA%\.minecraft\versions\<profile name>.
2. Shared folders like saves, resourcepacks, shaderpacks, crash-reports, and logs are shared across profiles in %APPDATA%\.minecraft.
3. Open %APPDATA%\.minecraft and rename options.txt to options.txt.old. This resets all video settings, render distances, GUI scales, and active resource packs back to default values.
4. Go to SuperLauncher > Settings > 'Game launch' and ensure 'Resolution' is set to standard windowed mode rather than forced custom resolutions.
5. In SuperLauncher, open the Version page, click 'Installed content', and select Disable or Remove for recently added resource packs or graphics mods.

How to confirm it worked

Minecraft starts up with default vanilla textures and video settings, bypassing the black screen freeze. You can then re-enable resource packs one at a time from Options > Resource Packs to identify which pack caused the stall.

Cause 6: First launch of a version downloading game files

When you launch a Minecraft version or profile for the very first time, SuperLauncher downloads core game JAR binaries, version assets, sound libraries, and the matching Java runtime (Java 8, 17, 21, or 25). On slow internet connections or during network latency spikes, the window may remain blank or fail to appear while files are validated.

How to fix it

1. Keep SuperLauncher open and monitor the download status bar.
2. Do not close the launcher or terminate Java processes while files are downloading.
3. Check the launcher log at %APPDATA%\SuperLauncher\logs\superlauncher.log. Note that this log is overwritten on every launch, so copy it to another location if you want to save it before relaunching. It documents loader steps, Java runtime paths, and file verification.
4. If a download stalls, close SuperLauncher, check your internet connection and firewall settings, then open SuperLauncher again. If a launch fails completely, SuperLauncher displays a red notice pointing directly to superlauncher.log.

How to confirm it worked

The download bar completes, the red notice does not appear, and the game window opens directly into the main menu. Subsequent launches skip asset downloads and start in seconds.

What doesn't help

I wouldn't waste time on these common troubleshooting traps:

• Force-closing the window immediately when Windows displays "Not Responding". Terminating javaw.exe while mod loaders construct texture atlases interrupts file writes and forces Java to start the entire build process over on the next launch.
• Trying to add custom JVM arguments or change Java paths. SuperLauncher automatically selects the correct Java version (Java 8, 17, 21, or 25 depending on your Minecraft version), and users cannot set custom JVM arguments or a custom Java path in SuperLauncher settings.
• Deleting your save worlds in %APPDATA%\.minecraft\saves. Single-player worlds are not accessed during initial game window launch. Deleting save folders destroys your worlds without fixing graphics driver or GPU selection issues.
• Reinstalling Windows. A black screen or launch freeze is an application or driver configuration issue. Adjusting Windows Graphics settings or updating drivers takes minutes and avoids operating system reinstalls.

If the game still hangs

If none of these fixes resolve the black window, copy %APPDATA%\SuperLauncher\logs\superlauncher.log and check .minecraft\logs\latest.log. Look for missing library errors or driver calls near the end of the log. If the window closes abruptly with an error code, see our guides to exit code 1, GLFW error 65543, and exit code -1073741819 for specific exit code fixes.