If Minecraft crashes and its report mentions “Thrown Exception Reported” or “Thread: Render thread,” start by checking the actual exception in the crash report. “Render thread” is the thread where the failure was recorded, not a diagnosis by itself. The underlying cause might be an incompatible mod, a broken resource pack or shader, a graphics driver issue, a Java setting, or a particular world. The reliable fix depends on the lines immediately above the stack trace and any Caused by: entries.
This guide covers Minecraft: Java Edition on Windows, macOS, and Linux, including vanilla installations and common modded setups. It follows a low-risk order: protect your worlds, identify the crash, test a clean installation, and change only the component that fails. You usually do not need to wipe your .minecraft folder or install a random collection of JVM flags.
Minecraft uses the render thread for client-side graphics and many screen-related operations. A crash report may say Description: Rendering screen, Description: Rendering overlay, or simply list Thread: Render thread under its head section. These labels describe where the crash surfaced; they do not prove that the graphics card is defective.
For example, a render-thread exception can originate in a mod's user interface or during resource loading. The exception type and trace provide better clues: NullPointerException suggests a program tried to use a missing object; a named mod package can point to an add-on; a shader compilation message calls for checking graphics resources or drivers. None of these signals guarantees one specific fix.
| What the report shows | First thing to check |
|---|---|
Caused by: followed by a mod's package or class | That mod, its dependencies, and its exact Minecraft/loader version |
Rendering overlay or a crash during resource reload | Resource packs, shader packs, graphics-related mods, and configuration |
| OpenGL, Vulkan, shader compiler, or graphics-device messages | Graphics API choice, GPU drivers, and hardware support |
OutOfMemoryError or memory-allocation failure | Available system RAM and the installation's -Xmx value |
| Only one saved world crashes | A safe copy of that world, its datapacks, and version compatibility |
Before modifying an installation, make a backup. If Minecraft still opens, go to Singleplayer → select world → Edit → Make Backup. Otherwise, close the game and copy your saves folder to another location; preserve options.txt, mods, config, and screenshots if they matter to you. See Minecraft's official Java world-backup instructions.
Open the newest file in crash-reports if one was created, and compare it with logs/latest.log. Default game directories are:
%APPDATA%\.minecraft~/Library/Application Support/minecraft~/.minecraftLaunchers that keep separate instances may use different paths. Open the affected instance's game folder from its launcher instead of assuming the default directory.
Search the report for Caused by:, Exception, Mod File, and Suspected Mods where present. Read the first meaningful cause as well as the named classes. If no crash report exists, inspect the end of latest.log; a hard process termination may not generate a standard Minecraft report.
Open the official Minecraft Launcher, select Minecraft: Java Edition → Installations → New Installation, and create a test installation for the same game version that was failing. Choose a vanilla release, not a Forge, NeoForge, Fabric, or Quilt profile. For more reliable separation, give this test a new, empty Game Directory instead of reusing the modded folder.
Launch the menu, then create a temporary new world. If vanilla works but your normal profile crashes, focus on mods, packs, or settings rather than immediately reinstalling the operating system. Minecraft's new-installation troubleshooting guide recommends comparing clean and existing installation settings.
In the crashing modded instance, close Minecraft and temporarily move mod files to a backup folder outside the active mods directory. Keep your saved worlds intact. Start with the correct mod loader and only the dependencies required for the pack. Reintroduce compatible mods in small groups; if a group causes another crash, split that group until you find the conflict.
Match every mod to the exact Minecraft version and loader. Fabric builds do not automatically work on Forge or NeoForge, and older mod releases may not be compatible with newer versions. Check the mod developer's release notes before updating. Do not assume Sodium, Iris, OptiFine, or any other named mod is responsible without evidence in your log.
If the error began immediately after adding a mod or updating a modpack, revert that change first. For an established pack, follow its maintainer's supported version list instead of upgrading individual core components at random.
For crashes mentioning graphics initialization, OpenGL, Vulkan, or shader compilation, install the current supported graphics driver for your specific GPU from its manufacturer. Windows users can use the official NVIDIA driver page, AMD support, or Intel Driver & Support Assistant. On macOS, graphics-driver updates are generally supplied through macOS updates.
Restart after changes. If your computer has both integrated and dedicated graphics, check which GPU Minecraft is using in the game's debug information or OS graphics settings. A driver change can help a genuine graphics issue, but it will not fix every Java exception on the render thread. Minecraft Support also recommends OS updates and disabling mods when diagnosing Java Edition visual issues: official graphics troubleshooting.
Turn off shader packs and return to the default Minecraft resource pack. Temporarily remove custom packs from the instance if the game crashes before the menu appears. If a particular mod provides shader options, follow that mod's method for turning them off. With Minecraft closed, you can rename options.txt to options.txt.backup to let the game recreate default settings; this also resets unrelated preferences, so retain the backup.
For Java Edition 26.2 and versions with the Graphics API setting: open Options → Video Settings → Graphics API and try Default or Prefer OpenGL if experimental Vulkan is crashing. Mojang documents Vulkan as experimental in the 26.2 release notes. Older 1.21 installations do not have this same Graphics API menu, so do not follow instructions that assume it exists there.
For performance-related crashes, temporarily lower render distance, simulation distance, and demanding visual features. Treat such changes as a diagnostic test, not proof of the root cause.
Open Installations → Edit → More Options for the affected profile. If you previously entered a custom Java Executable path, record it and try the official launcher's default managed runtime. Check the Java version listed in your crash report and confirm that it matches the requirements of your specific Minecraft version and mod loader. The Minecraft 1.21 generation uses Java 21, but that does not mean every historical or future release should be forced onto Java 21.
Also remove any experimental JVM flags you added while troubleshooting, after saving a copy of the original argument string. Avoid copying long “performance” argument lists from unrelated modpacks or enabling obscure software-rendering flags without evidence. If the launcher manages Java correctly, replacing it with a separate JDK is usually not the first repair to try.
Look for OutOfMemoryError, failed allocations, or exceptionally low memory limits in the log. In the installation's More Options → JVM Arguments, -Xmx is the maximum Java heap size: -Xmx4G means up to 4 GB. Adjust only this value when appropriate, and leave enough RAM for the operating system and other applications.
There is no universal “8 GB for every vanilla world” rule. Mojang's memory-allocation guide notes that default allocations changed for newer versions and recommends not exceeding about half of system RAM on 64-bit systems. For example, on a machine with 8 GB total RAM, a 4 GB maximum may be reasonable if the version and other applications allow it; assigning 8 GB to Minecraft would leave no comparable headroom. A heap increase will not repair a broken shader or incompatible mod.
If a clean vanilla test fails too, confirm disk space, operating-system updates, and the required graphics capabilities. Use the launcher to create a fresh installation, and compare its game directory, Java executable, resolution, and JVM settings with the failing profile. If necessary, close Minecraft and rename the original game directory after copying your saves and other important data; allow the launcher to recreate files. Do not permanently delete the folder until the new installation and your backups have been verified.
If only one world crashes, work on a copy. Check for incompatible datapacks or a world opened in the wrong game version, and try an earlier known-good world backup before attempting invasive recovery. Do not use /fill as a generic “chunk regeneration” repair: it changes blocks and is not a substitute for recovering corrupted world data. Minecraft warns that uninstalling can remove locally stored saves, and its uninstall guidance recommends backups first.
OutOfMemoryError: check the -Xmx limit and available physical RAM.No. It is a crash-report thread label. You need the exception message, relevant stack-trace classes, and Caused by: lines to identify a plausible root cause.
Only when your particular game version or mod loader requires Java 21 and is currently using the wrong runtime. For official installations, test the launcher's managed Java first. Installing a newer or different Java package without checking compatibility can create another launch failure.
The affected environment may load a specific resource, modded entity, datapack, or world region that is absent elsewhere. Test with the same client on a new world or another server, then compare crash logs. Never alter your only copy of the affected world.
Include your Minecraft version, operating system, GPU model, mod loader and mod list, the last change made, and the full relevant crash report or latest.log. Remove tokens, usernames, filesystem identifiers, and other sensitive information before sharing publicly. For suspected vanilla bugs, search and report reproducible issues through Mojang's official issue tracker; for modded crashes, use the modpack or mod developer's issue channel.
The most effective fix for the Thrown Exception Reported render thread Minecraft error is to isolate the first failing component, not to change everything at once. Back up your world, use the real exception to choose a branch, verify whether a clean vanilla profile works, and then change mods, graphics settings, Java, or memory only as the evidence warrants. Keep each successful change so a future crash is easier to diagnose.
Fix Fortnite texture pop-in on PC with official steps for GPU drivers, file verification, DirectX 12, high-resolution textures, VRAM, SSDs, and stutter.
Learn what Heroes of the Storm minimap size and position options are verified, improve readability, and choose camera-click controls that suit you.
Set Super Smash Bros. Ultimate Quickplay to prefer hazards-off stages. Follow the Preferred Rules menu steps and learn why matchmaking may not always honor them.
Enable Server Latency and Packet Loss in Warzone to monitor connection quality, read the overlay, and use recurring spikes to guide troubleshooting.
Learn how to carry from mid lane in League of Legends by setting up waves, choosing safe roam windows, reading side lanes, and converting pressure into objectives.
Fix Minecraft Evoker spell problems with a safe vanilla test, version checks, log review, and a step-by-step way to isolate mod or datapack conflicts.
Fix PUBG stuck on Initializing on Steam with a focused checklist for PC service notices, launch options, game files, downloads, and connection issues.
Fix Brawl Stars stuck at 92% loading with an ordered checklist for service notices, network tests, safe updates, Android cache, and account-safe reinstalling.
Best Dead by Daylight visual filter settings start with a small Gamma lift, neutral color and contrast, and a quick check for dark corners, fog, and bright lights.
Find the Steam and EA app fields for Apex Legends launch options, use EA’s documented FPS command, and see why +exec autoexec.cfg remains unverified.
