PassMark BurnInTest is a software tool that allows all the
major sub-systems of a computer to be simultaneously
tested for reliability and stability. Tests CPU, hard drives,
CD-ROMs, CD burners, DVDs, sound cards, 2D graphics,
3D graphics, RAM, network connections, printers, and
video playback. Test specialized hardware with
BurnInTest 'plug-in' tests.
- Improvements to the GPU load with the 3D test. With high-end GPUs and a
high BurnInTest 3D test duty cycle setting (e.g. 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 (i.e. in the case of a
- 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
- In V6.0.1007, report information set with a script command (e.g.
SETSERIAL) was not included in the log file. This has been corrected.
Tools and Utilities
6.0 build 1008
Product page: here