AMD OpenGL driver (atio6axx.dll) access violation when enabling rendering on Rembrandt iGPU

Environment

• Minecraft: 1.21.11
• Fabric Loader: 0.19.3
• Fabric API: Latest
• Sodium: 0.8.12
• Voxy: 0.2.16-beta

Also reproduced on:

• Voxy 0.2.15-beta

Hardware

• Laptop: ASUS Vivobook 15 M1502NAQ
• CPU: AMD Ryzen 7 170 with Radeon Graphics
• GPU: AMD Rembrandt integrated graphics (PCI Device ID: 1002:1681)
• Driver Version: 32.0.21032.24 (AMD Adrenalin 25.10.32)

Operating System

• Windows 11 25H2

Description

Enabling Voxy rendering immediately causes the renderer to freeze.

The game itself continues running (audio continues, mobs continue attacking, etc.), but the screen freezes and flickers continuously.

Sometimes the game remains frozen indefinitely.
Sometimes it crashes to desktop.

The issue is fully reproducible.

Reproduction

1. Create a fresh Fabric instance.
2. Install only:
   • Fabric API
   • Sodium 0.8.12
   • Voxy 0.2.16-beta
3. Launch Minecraft.
4. Enable Voxy rendering.

The renderer immediately freezes.

Things already tested

• Fresh Fabric instance
• No other mods installed
• Fresh world
• Latest official AMD driver
• ASUS official graphics driver
• AMD compatibility patch
• Voxy 0.2.15-beta
• Voxy 0.2.16-beta

All produce the same behaviour.

Crash Information

Prism Launcher exit code:

-1073741819

Windows generated a crash dump.

WinDbg reports:

Failure Bucket:
INVALID_POINTER_READ_c0000005_atio6axx.dll

Faulting module:
atio6axx.dll

Exception:
0xC0000005 (Access Violation)

Driver version:
32.0.21032.24

The crash occurs inside the AMD OpenGL driver while Voxy rendering is being initialized.

Btw Im like new to github and all and I stumbled upon this issue just now and I had chatgpt write this out for me cause Idk anything about debugging and whatever so uh dont judge, if you need me to submit a log or something just ask, though I probably wont know what to do so please guide me

Start with the listed minimal reproduction and the Windows crash dump or WinDbg report; the issue names no repository file, test, or entry point. Confirm the failure with Voxy rendering enabled on the specified AMD driver, then gather the logs or diagnostics maintainers request and determine whether the crash is reproducible.