Sound test show No operations reported in timeout period during over night test. The trace show as below.
Does the error cause by some Windows thread no response when BurnIn tool do some operation?
BurnInTest V8.1 Pro 1024 (64-bit)
Trace detail level: Activity trace 2
System summary:
Windows 10 Professional Edition build 17763 (64-bit),
LOG NOTE: 2019-01-31 03:59:26, Operation watchdog for 1 is 40965919317306 (previous 3904942770968
LOG NOTE: 2019-01-31 03:59:26, Operation watchdog for 3 is 1701488099328 (previous 1620451917824)
LOG NOTE: 2019-01-31 03:59:26, Operation watchdog for 5 is 63558 (previous 6189
LOG NOTE: 2019-01-31 03:59:26, Operation watchdog for 64 is 52148250 (previous 52148250)
WARNING: 2019-01-31 03:59:26, Sound, No operations reported in timeout period
LOG NOTE: 2019-01-31 03:59:26, Operation watchdog triggered for Sound is 52148250 (previous 52148250)
Does the error cause by some Windows thread no response when BurnIn tool do some operation?
BurnInTest V8.1 Pro 1024 (64-bit)
Trace detail level: Activity trace 2
System summary:
Windows 10 Professional Edition build 17763 (64-bit),
LOG NOTE: 2019-01-31 03:59:26, Operation watchdog for 1 is 40965919317306 (previous 3904942770968
LOG NOTE: 2019-01-31 03:59:26, Operation watchdog for 3 is 1701488099328 (previous 1620451917824)
LOG NOTE: 2019-01-31 03:59:26, Operation watchdog for 5 is 63558 (previous 6189
LOG NOTE: 2019-01-31 03:59:26, Operation watchdog for 64 is 52148250 (previous 52148250)
WARNING: 2019-01-31 03:59:26, Sound, No operations reported in timeout period
LOG NOTE: 2019-01-31 03:59:26, Operation watchdog triggered for Sound is 52148250 (previous 52148250)
Comment