2D error occurs and persists if a 3D error has occurred at almost the same time.

[DUTtester]

Hi,

I have recently experienced 2D errors (error writing to GPU memory) when a 3D error has occurred almost the same time (known 3D graphics errors, I would say, as I have read elsewhere in the PM forum, Intel driver problems).




However, the 2D errors are new to me. Is there any connection between the 3D error and the subsequent, increasing number of 2D errors?
The 2D errors appear almost the same time when the first 3D graphics error has occurred:
11:12:29 = 2D error
11.12.30 = 3D error





SystemInformation:

graphic drivers update already checked.

Thanks in advance and have a nice weekend
BR, DUTtester =)

[DUTtester]

I just saw the same error on a second machine (very similar system, only the RAM is different).
The screen briefly goes black and then comes back (known 3D graphics error—Intel driver issue). Then a 3D error is reported and the 2D errors start counting up from that point.

[David (PassMark)]

Both the 2D and 3D test use DirectX and thus the video card device driver.
So if the driver crashes, all the DirectX functions also crash. Thus "DEVICE_REMOVED" error.

And yes, likely it is a driver bug.
But you might also like to try V11 of BurnInTest and not the older V10 release.

[DUTtester]

Hi David (PassMark)
I tested the issue on another computer with the same symptoms (After the first 3D error, a large number of 2D errors occur.) and the new BurnIn V11.





the 2D/3D errors remain.

as mentioned most likely intel driver bug.

thanks for the support and BR

[DUTtester]

Hi David (PassMark)


i also tested Ubuntu25.04 (Kernel 6.16), BurnIn V5 (build1020).

i noticed that the 2D Graphics test (Local video memory (GPU, RAM)) does not start, it keeps stating "Starting", im not sure if i should switch to the setting "Monitor Test (lines and bitmaps)" ?


The Monitor Test (lines and bitmaps) does work.

The 3D test is running without issue.

Thanks and BR