2D graphics [error ] using BIT v 10.2 on Windows 11 24H2 [2DPC] [amd platform]

[Gaurav]

The BIT configuration is as follows for the test setup : CPU, RAM, GPGPU at 80% duty cycle , 2D,3D at 100% duty cycle.
The OS is windows 11 24H2, the issue does not happen when OS is windows 10.
The issue only happens at 2DPC that is when all 4 memory slots are loaded with RAMs
Driver is also latest from amd.
Want to understand why the issue could happen.
In my analysis I see some differences could be due to WDDM on Windows 11, need more input from experts on BIT

[David (PassMark)]

Error from the log is this one
LOG NOTE: 2025-03-26 00:39:26, 2D Graphics, GPU gfx1036, Verifcation failure of GPU buffer contents
LOG NOTE: 2025-03-26 00:39:26, 2D Graphics, GPU gfx1036, Verifcation failure of GPU buffer contents (Offset: 8128, Read: 0x0000000000000000, Expected: 0x5555555555555555)

The data written to the video RAM isn't the same as the data read from the video RAM. So you have data corruption.

This can be either a real hardware failure of the main RAM (for integrated video cards) or the video RAM. But if the video card device driver has bugs then sometimes the same RAM might get allocated twice. So two different processes are writing to the RAM, both thinking they have exclusive access. So they corrupt each others data in a way that resembles a hardware failure.

[Gaurav]

Thanks David,

This error scenario happens when I am using Windows 11 and 2 DPC configuration, that is RAM on all 4 slots.

- Issue does not happen when it is Windows 10 and 2 DPC
- Issue does not happen when it is Windows 11 and 1 DPC (RAM on 2 Slots or Less)

Any suggestions to differentiate between Real Hardware failure or Device Driver Bug, if any other test that can be run.

[David (PassMark)]

If you are using integrated graphic and there is no dedicated video RAM, then swap out the RAM for RAM from a different vendor and see if you still have the problem.

If you are testing many identical machines and you see this problem on many of them it is more likely a driver issue. If it happened, for example, on one machine out of 100, then it is more likely a hardware failure.