MemTest86 v8.4 Pre-release (May 8/2020 Update - v8.4 has been officially released)

[keith]

(May 8/2020 Update) MemTest86 v8.4 has been officially released. Thank you for all the bug reports and feedback.


Downloads
(May 8/2020 Update) MemTest86 v8.4 Pro and Site Edition can now be purchased from our sales page. As usual, the Free Edition is available for download on the normal MemTest86 download page. Pre-release builds are no longer available for download.


Fixes/Enhancements

• Added new config file parameter 'CHECKMEMSPDSIZE' for checking consistency of total memory capacity of detected SPDs against system memory size
• Added new config file parameter 'SPDMATCH'. If enabled, will look for SPD.spd file which contains the raw bytes to compare SPD bytes to. This is useful for production line testing of RAM sticks to check that SPD data programming was done correctly.
• Memory is now reserved at the beginning and released at the end of the test session to reduce frequency of memory allocations/release and improve UI responsiveness. Previously memory was allocated and deallocated immediately before and after each individual test. But it was observed that on some systems the UEFI BIOS was zeroing RAM on deallocation. Which was very slow on systems with a large amount of RAM. This change significantly speeds up testing on these systems.
• Added fallback when failing to set the menu screen size to the max supported resolution. This works around a UEFI BIOS bug and avoids a blank screen on a small number of systems.
• Added tftp.remap file for fixing backslash/forward slash issues with uploading XML files when running TFTP server on Linux machines. This is useful for some production line testing scenerios.
• Added warning message when failing to inject ECC errors for Ryzen chipsets (due to being disabled by BIOS in production systems)
• Added specific Mac Pro models to black list to workaround display and multiprocessing bugs in their UEFI BIOS
• Added preliminary ECC support for Ryzen Zen 2 (Ryzen 3000 series chips)
• Added preliminary support for retrieving CPU info for Intel Comet Lake chipsets

How to report problems

Either make a post here in the forum, or send us an email at the address listed on our contact page. When reporting an error please provide as much details as possible. If you are running on a USB drive, there should be a log file that has been generated in the EFI/BOOT directory called MemTest86.log. Sending us this will be of great help. Additionally a photograph of the problem would also be useful if possible/applicable.

[sugob]

Hi

I was having all the hanging 'fun' at app startup with the earlier betas [up to 8.4b1008] - this V8.4 PR1 build now WORKS

From end of attached boot log 'MemTest86.log'

020-05-03 14:14:30 - [CONFIG] This platform has 16 logical processors of which 16 are enabled.
2020-05-03 14:14:30 - Applying configurations complete
2020-05-03 14:14:30 - Console size = 80 x 25
2020-05-03 14:14:31 - Checking for graphics mode support
2020-05-03 14:14:31 - Graphics mode available
2020-05-03 14:14:31 - Enabling graphics mode
2020-05-03 14:14:31 - Get screen size
2020-05-03 14:14:31 - Current screen size: 1920 x 1200
2020-05-03 14:14:31 - Screen size = 1920 x 1200
2020-05-03 14:14:31 - Char width=8 height=19
2020-05-03 14:14:31 - Loading images
2020-05-03 14:14:42 - Enabling graphics mode
2020-05-03 14:14:43 - Get screen size
2020-05-03 14:14:43 - Current screen size: 1920 x 1200
2020-05-03 14:14:43 - Get_AMD_17_CurTmp: NB_SMN_INDEX_0=0x00150D84 NB_SMN_DATA_0=0x00000000
2020-05-03 14:14:43 - Get_AMD_17_CurTmp: Setting NB_SMN_INDEX_0 to 0x00059800
2020-05-03 14:14:43 - Get_AMD_17_CurTmp: NB_SMN_DATA_0=0x36900FEF
2020-05-03 14:14:43 - Get_AMD_17_CurTmp: 0x36900FEF, 0, 436

So I think can tick my issue off the list - cheers

The issue with using mouse [Logitech MX master] still remains - [physically] move mouse 1cm, moves pointer about 1 to 2mm on screen [in approx the correct direction]. I can see that the screen pointer movement seems to lag a small but noticeable amount [about ~1/2 sec] from moving mouse [this would be liveable if the movement issue was fixed]
Works as expected in BIOS menus and in Windows 10 i.e. move mouse 1cm, moves pointer about 5cm [which is like the scaling inverted
i.e. instead of memtest86 multiply mouse movement by 5 to get corresponding screen movement, it's dividing...or is that a co-incidence]

Thanks

M