It is a free upgrade from V5.3 Pro 1004 to V5.3 Pro 1036.
But we would prefer you to test on V6. As we aren't going to update or support V5 in the future.
Announcement
Collapse
No announcement yet.
Burn In test - system time stopped
Collapse
X
-
>V5.3 Pro 1004 is now pretty old.
>Can you upgrade to V6
We only have license for V5.3, so we just can upgrade to its build 1036.
Leave a comment:
-
V5.3 Pro 1004 is now pretty old.
Can you upgrade to V6 and see if the problem can be reproduced.
BurnIntest never sets the time. We only read the time from the operating system (not by direct calls to the hardware, or CMOS)
There are logging options to get more detailed logs. See the preferences window.
Leave a comment:
-
Burn In test - system time stopped
Hi,
We set "burn in test" for 2 hours, and then some systems can't finish the test after 2 hours because during the test, system time has been reset and can't continue, ie. system time will always stop at 1:00 for example.
We'd like to know Passmark BurnInTest read time from Windows XP or CMOS directly?
Since BurnInTest Event Logs only record test start and stop time, we don't have other clue to check when it has been reset.
Any suggestion?
Test items: CPU Math / CPU SIMD / RAM / 3D Graphics / Disk / Sound
BurnInTest Version V5.3 Pro 1004
Operating system Unknown or new O/S Service Pack 3 build 2600
Number of CPUs 1
CPU manufacturer GenuineIntel
CPU type Intel(R) Atom(TM) CPU Z500 @ 800MHz
CPU1 speed 797.8 MHz
CPU L2 Cache:Unknown
CPU features MMX SSE SSE2 SSE3 DEP PAE
RAM502 MB
Video card Intel(R) Graphics Media Accelerator 500 (Resolution: 800x480x32)
Disk drive Model 8GB NANDrive (Size: 7.4GB)Tags: None
Leave a comment: