An error occurred during the DX12 3D test

[Gary Mitchell]

Hello Passmark,

I have an error after running Burin-in Test (V10). The error report says 'An error occurred during the DX12 3D test'. Can you tell me what triggers this message to appear? In order to debug this further. Attached shows my config settings, most are 50%.

I have confirmed there are no issues with DX9 setting.

Can you point me in the right direction for debugging this further?

Best Regards,
Gary

[David (PassMark)]

V10 is an old release now. So you might like to try V11.

If you turn on logging, there might be some additional information.

The majority of 3D problems are device driver bugs, device driver crashes and hardware failures.

[Gary Mitchell]

Thanks David, I will check the result with V11.

There is not much debug to go on, if I want to find the root cause. I am aiming to prove no hardware issues on a board, and this error is a niggle. Is there a separate DX12 3D graphics test I can do to prove the error is not related to hardware?

I will check on the V11 result. Also I can test with Win11. (Above error was testing with Win10 1809). Or maybe just run the DX12, 3D test by itself.

Best Regards, Gary

[David (PassMark)]

You haven't provided any hardware details nor any logs. So yes, there isn't much to go on.

Again, most 3D issues are video card device driver bugs, device driver crashes and hardware failures.
So collecting logs, checking device drivers, checking for reproducibility & narrowing down the problem are the first steps.

[Gary Mitchell]

Hi David,

I found entries in the Event Log page. 3D error occurred at 2025-04-08 23:40:28.

I can see in the Windows System event logs, at 23:40 'Display driver igfxn stopped responding and has successfully recovered.'

Also in the Windows Application event logs there is an entry for 23:40 from source 'Windows Error Reporting'. I'm not sure exactly what this is telling me. Can you tell from the event log entries what has caused the 3D error?

I have x2 separate PC Cores that have a similar entry in the Windows logs. Same graphics driver and OS image on both. I can see an error after 24 hours test.

Best Regards,
Gary

[Gary Mitchell]

Hi David,

Sending Windows Applications log error info for error at 23:40

Best Regards,
Gary

[Gary Mitchell]

HI David,

Sorry I also meant to ask, what constitutes as an error in the 3D Graphics test?

I'm not sure what the error criteria is exactly for that test.

Best Regards,
Gray

[David (PassMark)]

Display driver igfxn stopped responding and has successfully recovered.'

Video cards use a piece of software called a device driver. It standardizes the interface to the video card hardware. So for example, a game only needs to be coded once and works with all video cards (this didn't use to be the case 35 years ago). The standard interface implemented by the device driver is DirectX. The current version of BurnInTest uses DirectX12 by default, but there is an option for DirectX 9.

Ever since video card device drivers were first implemented, they have been buggy. Arguably the most buggy piece of software ever created (but browsers would come close).
nVidia for example is up to version 572.82 of their driver. So more than 500 releases, without even counting minor releases. But even after so many releases it is possible to make videos about all the bugs.

So drivers are hard to get right, and hard to debug.

Anyway, that error in your log means the Intel driver, igfxn, disappeared, crashed or froze up.
Once the driver is gone, DirectX starts reporting errors to BurnInTest and we report them to you.

[Gary Mitchell]

Hi David,

Thanks for the check. Agreed this is a software driver issue. FYI - I have Burn In Test V10 running with Win11 on another unit and this has not failed, so I can conclude this is SW related.

Thanks again for the help. Issue can be closed.

Best Regards,
Gary