Burnin Sound test show "No operations reported in timeout period" error.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • GUOXING
    Junior Member
    • Dec 2025
    • 8

    #1

    Burnin Sound test show "No operations reported in timeout period" error.

    ​​​​​​Hello
    I'm experiencing a Sound error while running Burnintest. Test conditions are as follows: OS: Windows 11 25H2 26200.6899. Burnintest version BurnInTest 11.0.1018 (64-bit) and Burnintest V11 (100. CPU Performance: 90% GPU Performance: 90% RAM Performance: 100% 2D Performance: 90% 3D Performance: 90% Sound:100% Video playback: 100% Disk:100% ) Attached is the test error log file.This error is really represent Sound driver/device has issue? Could you please help me find root cause?​​​
    Attached Files
  • David (PassMark)
    Administrator
    • Jan 2003
    • 11085

    #2
    Sound card device driver might have crashed?

    Did this happen more than once (or on other machines of the same model)?
    Does this happen if you just run the sound test by itself?

    Comment

    • GUOXING
      Junior Member
      • Dec 2025
      • 8

      #3
      Sound card device driver might have crashed?
      ------From Event log,I do not find driver crash log about sound card device driver.From Burnin test log,can you see issue point to what?

      Did this happen more than once (or on other machines of the same model)?
      -----Currently,two rounds of Burnin 8-hour testing have show this issue on two other machines of the same model.(F/R:2/40units,2/40*8hrs).

      Does this happen if you just run the sound test by itself?
      -----I'll try this action on failed units.

      Comment

      • David (PassMark)
        Administrator
        • Jan 2003
        • 11085

        #4
        These "no operations" type of issues can be hard to debug. Especially remotely without access to the hardware and if they are intermittent.

        No operations is a error of last resort. No actual error was detected, but at the same time, no actual progress is being made with the task.

        In this case (depending on how you configured the sound test) BurnInTest would have asked the operating system to play a sound, the operating system would ask the device driver to do it (or several layered drivers), which would eventually send the request to the sound card hardware. Something broke in this chain and the sound never got played and the "play" task never finished. So a freeze in part of the Window sub-system. The most common cause for this is a device driver bug of some sort. Sometimes this results in a crash or sometimes a freeze / lockup / dead lock.

        Comment

        Working...