3D Graphics test fail: Unexpected error running DirectX 12 Test. 0x8899000C

[GUOXING]

Hello
I'm experiencing a 3D Graphics test fail while running Burnintest. Test conditions are as follows: OS: Windows 11 26H1 28020.2207. Burnintest version BurnInTest 11.0.1025 (64-bit) and(CPU Performance: 90% GPU Performance: 90% RAM Performance: 100% 2D Performance: 90% 3D Performance: 90% Sound:100% Video playback: 100% Disk:100%. Connected to A/C power ) Attached is the test error log file.
-Fail Rate:1/40units,
-Fail Cycles:1/40*8hr
The following prompts appear in the log:
SERIOUS: 2026-07-23 19:38:14, 3D Graphics, An error occured during the DX12 3D test
LOG NOTE: 2026-07-23 19:38:14, 3D Graphics, Unexpected error running DirectX 12 Test. Error Number 0x8899000C (-2003238900)
LOG NOTE: 2026-07-23 19:38:14, 3D Graphics, There has been a presentation error that may be recoverable. The caller needs to recreate, rerender the entire frame, and reattempt present.
LOG NOTE: 2026-07-23 19:38:14, 3D Graphics, Unknown (0x8899000c)

1. We have found many similar error reports like the above from historical posts. What is the root cause of this error?
2. Failed machines can pass the test when retested. What impact will this error have on functions, or in other words, is this error acceptable?

[Simon (PassMark)]

These errors are typically video card device driver bugs, video hardware failure or 3rd party software causing problems (screen sharing, screen overlays, remote desktop software, etc..). Some user actions can also trigger this error, like updating the device driver in the middle of a test, rotating the screen to portrait mode, forcing a monitor resolution change, physically removing the video card, etc..

[GUOXING]

Hi Simon,
Thank you for your reply. So if this problem only occurs on a single unit once, and the failed unit passes the re-test, then this problem can be ignored or is acceptable, right? Because it has little impact on users, and there are no other actual functional abnormalities.

[Simon (PassMark)]

Up to you to decide whether that is acceptable. If its a one off and not reproducible, probably ok to ignore.

Also depends on how the computer will be used.

A gamer might find it acceptable to have a crash or two a week. But if this was for a medical device or critical infrastructure it probably needs more investigation or replacement of the hardware.

Some errors are also "Soft errors"

[GUOXING]

Okay, so is there any tool or pre-embedded setup available to capture more specific pointers and logs when reproducing this issue again?

[David (PassMark)]

The DirectX error 0x8899000C (also known as D2DERR_RECREATE_TARGET) indicates a presentation or rendering target failure. It happens when the system's graphics environment suddenly loses its connection to the display window or runs completely out of resources, causing the app or game to crash.

Unfortunately it is a pretty general error. Can be a hardware failure, device driver bug causing the driver to crash or could be a resource issue (no more video RAM).

Without the source code for the video card driver, you don't have much chance of finding the real root cause of the problem. If however you were nVidia, then you could use a debug build of the driver with logging running in a debugger (e.g. WinDbg, or Visual Studio). Then you can check the function call and video frame that caused the error and inspect the internal state of the driver. Doing this with a few different crashes could determine if it was random (more likely a hardware failure) or pinpoint the software bug. You would also need to be an expert C++ device driver software engineer.

Otherwise without the source code and being an expert C++ programmer, you are more of less back to trial and error (e.g. swap out the video card and see if the error disappears).

[GUOXING]

Okay, thank you very much for your reply. We will contact Nvidia again for confirmation.