Burn 10.2 got 2D/3D/GPGPU Error on Nvdia GN22 GPU

[Jason_Twu]

Dear SIRS:
We Got GN22 (RTX 5050/5060 ) fail on Burin 10.2 , fail item are 3D/2D /GPGPU Test on NV GN22 GPU.
system config: RPL I7-13620H/ DDR4 Memory /GN22 (RTX 5050/5060 ) ,
and we change back to old version V7.1 and V8.1 are Pass on same system ,
do you know the diference betwen V10.2 and V8.1 ?
please kindly provide comment or suggestion for use ,tks.







Jason Twu

[David (PassMark)]

V10 and V11 of BurnInTest have a much more complex 3D (DirectX 12) test compared to earlier versions.
So it makes more use of the DirectX API and places higher load on the video card.

We've had a collection of different recent errors with the 5xxx series video cards. The situation is documented here.
https://forums.passmark.com/burninte...force-rtx-5050
(Some of these cards seem to have real problems).

[Jason_Twu]

Dear David SIR:
But we take Burnin 10.2 Fail system performed many online game with 3D directx 12 enable, and everything ran smoothley without any issue and garbage ,
we also try 3D video tool ,ex: Furmark , 3D Timer SPy and 3Damrk 11 , all result are pass, do you have any idea only got fail on Burnin tool?
please kindly share to us, we must fix this issue soon ,tks.





Jason Twu

[David (PassMark)]

We don't know the root cause of the problem and we don't have access to your failing card. But highly likely it is either a video card device driver bug or an actual hardware failure, which provokes an error in the device driver.

If you swap the failing 5060 for another 5060 does the problem go away? And does the problem return when you switch back to the original card?
Are you running the latest video card drivers?

[Jason_Twu]

Dear David SIr:
We have change to NV latest Driver 577.02 , but still fial , and our system is on board GPU chipset not PCIE card ,so can not swap ,tks.






Jason Twu

[David (PassMark)]

Step 1:
Try V11, as V10 is now a bit old.

Step 2:
If you have several units you are testing determine the fail rate

Step 3:
Try and narrow down the problem to just the smallest number of tests that provoke the problem. (e.g. 3D test by itself, or maybe 3D + CPU, or 3D + RAM + CPU)

Step 4:
Check the Windows event log. Sometimes driver failure result in a log entry with some details.

Step 5:
Post a debug log if you like from BurnInTest
https://www.passmark.com/support/bitdebug.php
But I strongly suspect it will one of the known issues documented in the link above.

[dqa_minisforum]

Hi Jason_Twu,

I encounter the same issue with yours recenlty when test on RTX5060 graphics card, and i change another new card, the issue still happened, how about this issue last, any solution to fix it?

[David (PassMark)]

We would suggest following the suggestions previously suggested.

Once you have collected the logs let us know.