PassMark Software released version 6.0 build 1008 of BurnInTest on Tuesday. This program puts the various parts of the computer to work in order to test the reliability and stability of the system. The software is available in a standard version and a professional edition, the latter of which is available in both a 32-bit and a 64-bit version. The professional edition is able to test more hardware, including tape drives and the parallel and serial ports and the USB ports. In addition, the memory tests in the Pro version are more extensive. More information about the differences between them is here to find. The changelog of this release shows the following changes and improvements:
Changhes in version 6.0 build 1008:
- Improvements to the GPU load with the 3D test. With high-end GPUs and a high BurnInTest 3D test duty cycle setting (eg 100%), the CPU can become CPU bound which limits the load on the GPU, this has been improved and the GPU load is now higher on these high-end GPUs.
- Improved the simultaneous testing using the 3D test (particularly for multiple simultaneous 3D tests) and the 2D video memory test.
- The 3D test has been changed such that if Hardware Transform and Lighting is not supported by the Graphics card, then the 3D test will only run with 1 test Window, rather than up to 4 test Windows.
- Improvements in the memory management of the standard memory test when run with the 3D test, sound test and/or Video playback tests.
- The “Install BurnInTest to a USB drive” now also copies the help files to the USB drive or for the BartPE installation.
- Corrected a bug where the test duration could be changed to 21 minutes when starting a script.
- Corrected a bug where a Standard Network test of less than 2 seconds will not record the number of network operations.
- Changed the calculation of the number of Standard Sound test cycles to not increase if no sound test files are specified (ie in the case of a configuration error).
- Scripting changes:
- Accumulated results are now always cleared at the start of a test script, but accumulated across all test runs within the script.
- For scripts with multiple REBOOT’s, if the script was manually stopped before completing, the next script run may have continued from the last command in the previous test script (in rare cases), rather than the first command. This has been corrected.
- A bug was introduced in V6.0.1007, where on a scripted LOAD or SETLOG command, a change in the log file name would not result in a change until the next script was run (not during the current script). This has been corrected.
- In V6.0.1007, report information set with a script command (eg SETSERIAL) was not included in the log file. This has been corrected.
|Version number||6.0 build 1008|
|Operating systems||Windows 7, Windows 2000, Windows XP, Windows Server 2003, Windows XP x64, Windows Server 2003 x64, Windows Vista, Windows Vista x64, Windows Server 2008|
|File sizes||5.05MB – 5.61MB|