I upgraded my graphics card from an RX 6400 to an RX 9060 XT 16GB and performed a clean driver installation with DDU. Windows and other games appear to recognize the card, but Minecraft now fails to launch. The standard launcher only shows Exit Code 1, while Modrinth reports "Failed to find Graphics Adapter." This happens across multiple Minecraft versions and launchers.
I have already cleared the shader cache, checked for virtual display drivers, and confirmed that the AMD drivers are supposedly up to date. Another game also reported the driver version as 0.0.0, which makes me think something is wrong with how the driver is being detected. I would prefer not to reinstall the drivers again unless necessary, since I already did a clean installation a few days ago. Would rolling back to an older driver help, and what else should I check?
My system has a Ryzen 5 5600G, an RX 9060 XT 16GB, and an MSI A520M-A Pro motherboard. The relevant Sodium error includes "GetFileVersionInfoSizeW failed, error=0" and "Failed to find graphics adapters."
1 Answer
That stack trace is coming from Sodium’s graphics-adapter detection, not necessarily from Minecraft itself. The `GetFileVersionInfoSizeW failed, error=0` message suggests Sodium cannot read the installed driver module’s version information. First try launching a completely vanilla instance with no Sodium, Fabric, shaders, or other performance mods. If vanilla works, update Sodium to its newest version or temporarily remove it; a recently released GPU or driver may not be handled correctly by the version you have installed.
Also check Device Manager to make sure the RX 9060 XT appears normally with no warning icon, and confirm your monitor cable is connected to the new card rather than the motherboard video output. If other applications still identify the driver as version 0.0.0, then reinstalling the AMD driver is reasonable: use DDU again in Safe Mode, reboot, and install the current recommended driver rather than an optional preview package. If the newest driver is the problem, try the previous WHQL release afterward.
The error is specifically from Sodium, and I had been testing through a modded instance. I’ll try a vanilla profile first and then update or remove Sodium. I’ll also check Device Manager and the display cable before doing another driver cleanup.