Burnin Test]system Hang up when run Burnin v9.0 test.

[PETER TSENG]

We find our system will hang up on DESKTOP when run CPU,RAM ,Video,2D Graphics, 3D Graphics, Disk, Sound, Network
All of duty cycles is 50% , Fail rate 3/12 system, we run 72hrs to test.

I put the fail log in the attacnment.

I see the latest trace log(BIT_log_200511_013502.trace.txt) stop on Disk test item.
Could you help us to debug is that cause by Disk?
Or CPU, Because I think system hang up on DESKTOP maybe relate to CPU Loading to heavy,but we only setting 50%.
So need your help to analyze this log which cause this issue?thanks.

LOG NOTE: 2020-05-11 02:41:26, Disk , WriteFile - write file header: C:\BurnInTest test files\~bittestC00042
LOG NOTE: 2020-05-11 02:41:26, Disk , Mem Tot (W3): 7772MB [1487MB], page: 9692MB [1771MB], virt: 134217727MB [134212665MB], ext virt: [0MB], 80
LOG NOTE: 2020-05-11 02:41:26, Disk , Mem Tot (W4): 7772MB [1487MB], page: 9692MB [1771MB], virt: 134217727MB [134212665MB], ext virt: [0MB], 80
LOG NOTE: 2020-05-11 02:41:26, Disk , WriteFile - write file remainder: C:\BurnInTest test files\~bittestC00042
LOG NOTE: 2020-05-11 02:41:26, Disk , Mem Tot (W5): 7772MB [1487MB], page: 9692MB [1771MB], virt: 134217727MB [134212665MB], ext virt: [0MB], 80

[David (PassMark)]

our system will hang up

Was it a complete lockup? (Any mouse control, did CTRL-ALT-DEL work?)
Was hard drive LED on case still flashing?
Did the system recover after a power cycle?

is that cause by Disk?

While there was certainly disk activity taking place at the time of the hang, this doesn't mean it was the cause of the problems.

If you had 3 machines from 12 that failed, did they all fail is the same way? Did they all fail at roughly the after the same amount of testing time? Were the last few lines in the log similar for each machine? If you repeat the same test on the failed machine, do they fail again at the same point in the test (or is it all purely random?)

[PETER TSENG]

1.we only plug in mouse when test, after hang up, mouse has function but we plug in Keyboard no function.
2. Hard driver LED no flash after hang up.
3.yes, it can be recover after a force power button restart.

4.same even log info(nothing error.), same BIT_log(disk run at latest.)this is fail rate issue, need to run long time to repro(60hrs.)

[David (PassMark)]

I am guessing it is a hardware failure.

If the mouse worked can you right click on the task bar to bring up task manager?
After reboot can you check the Windows event log?

Did all 3 the machines fail after roughly the same amount of testing time?
If you repeat the same test on the failed machine, do they fail again at the same point in the test (or is it all purely random?)

if it was purely random, with a sudden lockup, and no logged errors then it is going to be hard to debug.
Some debugging ideas,

• Swap components for some from a different vendor and re-test. (e.g. different GPU, different RAM, different MB)
• Try MemTest86 as a more in depth test check for RAM errors.
• Setup Inline PSU tester to look for voltage dips / spikes.

[PETER TSENG]

I attach task manager picture.no1 is fail info , if we use mouse to click something, the task manager will change no.2 picture.
event log show nothing.not only this 3 unit fail, other unit will fail. this issue is random. it seem like not KEY part issue.we
change CPU, HDD, RAM , all conition still can repro. BTW, can we use pure OS to run burn in test, because we need to analyze that is driver issue or BIOS & EE issue.

[PETER TSENG]

attach no1, &no2 picture

[David (PassMark)]

So if you can bring up task manger and the system responds to mouse clicks, then the system really hasn't locked up at all.
Maybe it is just insanely slow. This can happen if there is a lot of swapping to disk, if the system runs out of RAM.But in this case the HDD LED should be on / flashing

[PETER TSENG]

re-test again but other unit occur hang up and KB&MS no function,any info about BIT log? or you want to capture another log?

[David (PassMark)]

From the details provided there doesn't appear to be a problem with BurnInTest. Our free support doesn't extend to debugging your hardware or 3rd party device drivers. Especially when we don't have the hardware to test on.

While we are happy to provide general advice on debugging (see my post above), we can't wave a magic wand and make the problem go away. It will very likely require some experimentation, research and trial and error on your part to narrow down the problem.

[PETER TSENG]

we found uncheck 2d/3d graphic test item can't repro on 30 units(all run 72 hrs).and if we uncheck 2d/3d graphic test item + another 3d graphic tool(unigine heaven) burn in tool system will hang up,(@57hrs @23hrs @17hrs @22hrs) but unigine heaven still running.if we close burnin tool from task manager +close unigine heaven app , system become normal. i think that is burnin tool issue.could you suggest unint to run burnin tool on 72 hrs?

[David (PassMark)]

Again, it would help if you were precise in your terminology. If the keyboard works and you can get to task manager, then the system has not "hung up".
It sounds more like either the system was slow or there has been a crash just in BurnInTest. Again, given the long run time before the issue appeared, I think the most likely explanation is a resource leak. RAM leaks are the most common, but other forms of leaks are also possible, system handle, GDI handles & video RAM for example.

You indicated that the problem only happens when 3D graphics are in use (either in BurnInTest or from 3rd party 3D graphics). This surely seems suspicious and should be the first place to look. Is the video card device driver leaking RAM or have some other problem. Maybe try using a different video card?