Burnin show 2D/3D Graphics test error code No operations reported in timeout period.

[willsm_guo]

Hi Sirs,
We have run BurnIn Test V9.2(1025) on our project and occur 2D/3D graphic test error, the error event log is "No operations reported in timeout period."
Could you please help to check this?
3D error
2D/3D error

[Tim (PassMark)]

There is no release called V9.2 build 1025. From the log it looks like you are using release V9.2 build 1007. See,
https://www.passmark.com/products/bu...st/history.php


For the 3D error it looks like the video card became unresponsive during the test and it locked up, causing BurnInTest to log a no operations error. Operations that would normally be reasonably quick were taking far longer, instead of .

Potentially there was a thermal event causing it to throttle or it had memory issues since the system only has 4GB of RAM and was getting pretty low on free RAM around the time the error occurred (it may have started swapping to disk and that's why everything slowed to a crawl). Reducing the number of tests running would likely stop this from happening (particularly the RAM and GPGPU test).

For example a normal run looked like this, taking 20 seconds to start rendering and exiting after the 15 minutes of test time

+5.985s - DEBUG: SceneRenderer: create new Scene
+20.625s - DEBUG: SceneRenderer: resize buffer
+21.485s - DEBUG: Creating DX12 Test Window
+21.797s - DEBUG: Resize called 300 x 200
+21.891s - DEBUG: CreateSwapChainForHwnd()
+22.610s - DEBUG: MakeWindowAssociation()
+22.610s - DEBUG: IDXGISwapChain1->QueryInterface()
+22.610s - DEBUG: Create a wrapped 11On12 resource for each Swap Chain Buffer
+22.625s - DEBUG: Create depth stencil/view
+22.625s - DEBUG: Resize Scene
+926.469s - DEBUG: stop test, send close message
+945.375s - DEBUG: Exited Main Loop
+945.453s - FPS: 48.590527

When the error occurred these were the timestamps, it didn't even make it to start rendering the scene;

+12.641s - DEBUG: SceneRenderer: create new Scene
+67.813s - DEBUG: SceneRenderer: resize buffer
+85.579s - DEBUG: Creating DX12 Test Window
+119.016s - DEBUG: Resize called 300 x 200
+145.110s - DEBUG: CreateSwapChainForHwnd()
+157.032s - DEBUG: MakeWindowAssociation()
+168.266s - DEBUG: Create a wrapped 11On12 resource for each Swap Chain Buffer
+173.625s - DEBUG: Resize Scene
+185.438s - DEBUG: stop test, send close message
+193.485s - DEBUG: Exited Main Loop
+193.485s - FPS: 5066459970594144256.000000

The 2D3D log was a bit more severe with the 3D test locking up (but not crashing) for nearly 12 minutes during one operation. Likely it is a similar situation to the one above.

See also this post, discussing that 4GB isn't enough RAM anymore for Windows 10, when under heavy load (especially with integrated graphics running 3D jobs).
https://forums.passmark.com/burninte...m-test-failure

[willsm_guo]

Hi Tim,
I understand, thanks for your great support.