0X401E000A

STATUS_GRAPHICS_PARTIAL_DATA_POPULATED 0x401E000A Fix

This error shows up when a DirectX app or driver can't fit all the data into a buffer. Usually happens during GPU monitoring or game overlays.

You're playing a game like Cyberpunk 2077 or running a benchmark like 3DMark, and suddenly the app freezes or crashes. If you check Event Viewer or a debug log, you see STATUS_GRAPHICS_PARTIAL_DATA_POPULATED (0x401E000A). This exact error code means the DirectX runtime tried to write data into a buffer, but the buffer was too small. The GPU had more info to send than the buffer could hold. It's not a hardware failure—it's a data mismatch between your app and the display driver.

The most common real-world trigger is a monitoring overlay. Tools like MSI Afterburner, RivaTuner Statistics Server (RTSS), or even Windows' own Game Bar hook into the graphics pipeline to read GPU stats (temperature, usage, frame rate). They request data from the driver via the IDXGIOutput::GetDisplayModeList or IDXGIAdapter::EnumOutputs APIs. If the app (or driver) allocates a buffer that's just a bit smaller than the actual dataset, you get this partial-populated status. The driver fills what it can but returns the error code instead of crashing.

The root cause: a buffer size miscommunication. The app asks 'how big is this data?' and the driver says 'X bytes'. The app allocates X bytes, but between that query and the actual fill, the data size changes (maybe a monitor resolution changed, or an HDR toggle happened). The driver then writes only what fits and returns 0x401E000A. The app is supposed to handle this by retrying with a bigger buffer, but many games and tools just crash instead.

Fix: Stop the Overlay Tools from Interfering

  1. Close all GPU monitoring tools. Right-click the system tray icons for MSI Afterburner, RivaTuner, and any similar tool (like EVGA Precision X1 or ASUS GPU Tweak). Select 'Exit' or 'Close'. After you close them, the error should not appear. Try running your game or benchmark again. If it works, the overlay was the problem.
  2. Disable the Windows Game Bar overlay. Press Win + I to open Settings. Go to Gaming > Game Bar. Toggle 'Game Bar' off. The Game Bar overlay also hooks into DXGI and can cause the same buffer size issue. After turning it off, restart your game and test.
  3. If the error still shows up, update your GPU drivers. Go to your GPU manufacturer's website (Nvidia, AMD, or Intel). Download the latest driver for your exact model. Install it with a clean option: for Nvidia, choose 'Custom installation' and check 'Perform a clean installation'. For AMD, use the Factory Reset option. After the install, restart your PC. Old drivers sometimes miscalculate buffer sizes for newer games.
  4. Switch to borderless windowed mode instead of fullscreen. In the game's video settings, change Display Mode from 'Fullscreen' to 'Borderless Windowed' or 'Windowed Fullscreen'. This changes how the game interacts with the desktop compositor and can avoid the buffer size mismatch. Test after changing.
  5. Disable any HDR or dynamic resolution scaling temporarily. In Windows Settings > System > Display, turn off 'Use HDR'. In the game, turn off any dynamic resolution or scaling options. These features can resize the display data between the query and fill steps. After disabling, test the game again.
  6. As a last resort, reinstall DirectX runtime. Download the DirectX End-User Runtime Web Installer from Microsoft's site. Run it and let it replace any broken DX files. Then reboot. This almost never fixes it, but if nothing else works, it's worth the 2 minutes.

What to Check If It Still Fails

If you've done all the above and the error still appears, you're likely dealing with a bug in the specific game or tool itself. Check the game's official forums or subreddit for a patch. Sometimes a game update fixes the buffer allocation. Also check if you have multiple monitors with different refresh rates—that's a known trigger for buffer size mismatches. Try running the game on a single monitor at the same resolution and refresh rate. If that clears it, the issue is the multi-monitor setup. You can also use Display Driver Uninstaller (DDU) in Safe Mode to completely wipe all GPU drivers, then reinstall the latest. It's a nuclear option, but it works when a standard clean install doesn't.

Related Errors in Windows Errors
0X00002083 Fix ERROR_DS_ATT_VAL_ALREADY_EXISTS (0X00002083) 0X000D104F NS_S_WMG_FORCE_DROP_FRAME (0X000D104F) – Drop This Frame Fix 0x0000001A Windows Stop Code MEMORY_MANAGEMENT Fix That Actually Works 0X00003612 Fix ERROR_IPSEC_IKE_PROCESS_ERR_VENDOR (0x3612) in Windows

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.