BurnIn Test error "Failed play back MIDI via sequencer"

[Kelly]

Hello PassMark,

We got a sound error “Failed play back MIDI via sequencer” after ran BurnInTest with below 7 items together overnight, and all of them are set to value 100.
“CPU, RAM, video, 2D Graphics,3D Graphics, Disk, Sound ".

The OS is Win7 SP1(6.1.7601), and the BurnInTest version is V7.1 Pro.

After the error occurs, we checked that the test MIDI file can be played by WMP and the memory is almost run out (3.64GB of total 4GB).
We found some similar discussions on your forum that this error is due to low memory.

Now we have some questions and need you answer for us:

1. Is our error also caused by memory runs too low?
2. Does running so many items together with such high stress(value set to 100) overnight make a higher chance to encounter errors?
3. Can we prevent this error by disable some items such as RAM or Graphics?
4. We’ve ever had the same error on Win8.1, but never seen it after install a hotfix http://support.microsoft.com/kb/2979265/en-us
   We’d like to know is there any solution on Win7 SP1?

[Ian (PassMark)]

As it seems you noticed there is another forum thread on about this error:
http://www.passmark.com/forum/showth...highlight=midi

It is hard to answer specific to your case without a trace log file.

1. Is our error also caused by memory runs too low?
2. Does running so many items together with such high stress(value set to 100) overnight make a higher chance to encounter errors?
3. Can we prevent this error by disable some items such as RAM or Graphics?

If you reduce the memory usage, it will probably take much longer for the MIDI issue to surface.

We’ve ever had the same error on Win8.1, but never seen it after install a hotfix http://support.microsoft.com/kb/2979265/en-us
We’d like to know is there any solution on Win7 SP1?

Generally speaking, it appears this problem is caused by a couple of software components leaking memory, causing the MIDI device to unload. The problems shown in the above forum thread are related to:
- Conexant audio device drivers.
- The Microsoft process audiodg.exe. Information and a hotfix can be found here.
- A SonicFocus handle resource leak that could cause this problem:
http://www.withinwindows.com/2008/05...audio-drivers/

So you should check you have the latest audio device drivers and the Microsoft Hotfix.