Shows error "No operations reported in timeout period" on BurnIn after resume from S4

[Andy Chen]

Hello,

We tested the following configuration:

1. Set “Auto Stop After” as “30 minutes”
2. Tick up “CPU”/”2D Graphics”/”Disks”/”RAM” and set these items as 100(Maximum load)
3. Select the [GO] button to start.
4. Perform S4 manually during BurnInTest running
5. Resume the system from S4

Then error message "No operations reported in timeout period" shows up on BurnInTest after resuming the system from S4.

OS: Win11 22H2 22581.1 and Windows 10 build 22593

Does Passmark have any suggestions? Thank you.

[Richard (PassMark)]

The No Operations reported in Timeout reported by the test means that for at least 8 minutes the test didn't perform any operations. So, it is a warning that the test is not running for a period. This can be caused by the test 'locking' up.

You are using an older version of the software, V9.1 Build 1004 from March 2020. There have been many changes since then including to the 2D Graphics test,

https://www.passmark.com/products/bu...st/history.php

We no longer support older versions of the software as development has moved on to the current release. We'll recommend testing with the current version of the software.

https://www.passmark.com/products/bu...t/download.php

If the issue continues, you change the travel level to activity trace 2 in the logging options there should be more formation logged around the time when the error occurs.

[Andy Chen]

The No Operations reported in Timeout reported by the test means that for at least 8 minutes the test didn't perform any operations. So, it is a warning that the test is not running for a period. This can be caused by the test 'locking' up.
>> Why does only the 2D Graphics item show "No operations reported in timeout period"? Other items like CPU, Disk, and Memory don't show this warning message after 8 minutes the test didn't perform any operations.

[Richard (PassMark)]

Why does only the 2D Graphics item show "No operations reported in timeout period"? Other items like CPU, Disk, and Memory don't show this warning message after 8 minutes the test didn't perform any operations.

Because the other test didn't stop responding. The 2D Graphics test may have stopped responding because of drivers crash, deadlock, bug in code, etc. Without additional information, we do not know and can only speculate. As mentioned previously, try testing with V10 and if it is still an issue, run BurnInTest with level activity trace 2 and there may be more information in the log files as the reason why.

[Andy Chen]

Thank you. We used the current version of the software to verify.
The result is PASS.