I am testing a computer system with Intel Core2 Duo and IDT's audio CODEC. I am conducting a 20min test run (i.e. CPU, serial, USB, sound, etc.) using BurnInTest 6.0 Build 1019 and I notice that the Sound Loopback test (5% distortion setting) stops operations just after a couple of minutes. The other tests continue to run normally. Changing the test load dutycycle didn't help:
With 100% dutycycle on all tests
--------------------------------
Cycles Operations Result Errors Last Error
CPU 200 330 Billion PASS 0 No errors
Memory (RAM) 19 55.167 Billion PASS 0 No errors
2D Graphics 1 1673 PASS 0 No errors
Sound 0 349860 FAIL 1 No operations reported in timeout period
USB Plug 1 97 795 Million PASS 0 No errors
Serial Port 4 34 1.977 Million PASS 0 No errors
Disk (C
14 17.521 Billion PASS 0 No errors
With 5% dutycycle on all tests
--------------------------------
Cycles Operations Result Errors Last Error
CPU 190 133 Billion PASS 0 No errors
Memory (RAM) 0 1.051 Billion PASS 0 No errors
2D Graphics 5 5014 PASS 0 No errors
Sound 0 25284 FAIL 1 No operations reported in timeout period
USB Plug 1 0 5.099 Million PASS 0 No errors
Serial Port 4 24 1.412 Million PASS 0 No errors
Disk (C
2 2.770 Billion PASS 0 No errors
If I just run the Sound loopback test by itself, it doesn't stop prematurely and there are no errors.
I switched to the newer build 1019 because when I was using build 1008 there were intermittent sound corruption errors (but note I never saw the sound test stop early). Below is test run from build 1008:
With 100% dutycycle on all tests
--------------------------------
Cycles Operations Result Errors Last Error
CPU 210 452 Billion PASS 0 No errors
Memory (RAM) 33 96.933 Billion PASS 0 No errors
2D Graphics 3 3397 PASS 0 No errors
Sound 235 12.046 Million FAIL 2 Corrupt Audio input
USB Plug 1 89 735 Million PASS 0 No errors
Serial Port 4 37 2.170 Million PASS 0 No errors
Disk (C
16 21.083 Billion PASS 0 No errors
Please provide suggestions regarding this issue that I am seeing with the 1019 build.
With 100% dutycycle on all tests
--------------------------------
Cycles Operations Result Errors Last Error
CPU 200 330 Billion PASS 0 No errors
Memory (RAM) 19 55.167 Billion PASS 0 No errors
2D Graphics 1 1673 PASS 0 No errors
Sound 0 349860 FAIL 1 No operations reported in timeout period
USB Plug 1 97 795 Million PASS 0 No errors
Serial Port 4 34 1.977 Million PASS 0 No errors
Disk (C
![Smile](https://forums.passmark.com/core/images/smilies/smile.png)
With 5% dutycycle on all tests
--------------------------------
Cycles Operations Result Errors Last Error
CPU 190 133 Billion PASS 0 No errors
Memory (RAM) 0 1.051 Billion PASS 0 No errors
2D Graphics 5 5014 PASS 0 No errors
Sound 0 25284 FAIL 1 No operations reported in timeout period
USB Plug 1 0 5.099 Million PASS 0 No errors
Serial Port 4 24 1.412 Million PASS 0 No errors
Disk (C
![Smile](https://forums.passmark.com/core/images/smilies/smile.png)
If I just run the Sound loopback test by itself, it doesn't stop prematurely and there are no errors.
I switched to the newer build 1019 because when I was using build 1008 there were intermittent sound corruption errors (but note I never saw the sound test stop early). Below is test run from build 1008:
With 100% dutycycle on all tests
--------------------------------
Cycles Operations Result Errors Last Error
CPU 210 452 Billion PASS 0 No errors
Memory (RAM) 33 96.933 Billion PASS 0 No errors
2D Graphics 3 3397 PASS 0 No errors
Sound 235 12.046 Million FAIL 2 Corrupt Audio input
USB Plug 1 89 735 Million PASS 0 No errors
Serial Port 4 37 2.170 Million PASS 0 No errors
Disk (C
![Smile](https://forums.passmark.com/core/images/smilies/smile.png)
Please provide suggestions regarding this issue that I am seeing with the 1019 build.
Comment