UEFI MemTest not loading on Dell OptiPlex 9020

[MJfromtheUK]

Hi!

Not really sure where to start troubleshooting. I created a USB stick using the tool provided, works fine on every machine I've tried it on except a Dell Optiplex 9020. I have tried it on 3 different machines on the same version and it fails in the same way on all of them.

Text scrolls as it gathers information, then the Memtest/Passmark logo appears and the exit icon appears, but the config icon does not and the mouse / keyboard don't accept input.

Any advice on what to do to troubleshoot welcome!

Things I have already tried:
Different USB sticks
Different USB ports
Using VGA out rather than Display Port (seen as it seems to hang on loading images)

EDIT: Found the log file, uploaded to pastebin- http://pastebin.com/DCeUFa8H

[keith]

Thanks for posting the logs.

It appears to be a UEFI BIOS firmware issue as it is giving invalid data for the height and width of a single character (Char width=1765022362 height=377519913). So check to see if there is an updated BIOS.

We have also added checks for such invalid char width/heights and reset to default values accordingly. Please give the following build a try:

http://www.passmark.com/ftp/memtest8...6.0.0.1011.zip

[MJfromtheUK]

So check to see if there is an updated BIOS.

I'm on A09 which is the latest.

We have also added checks for such invalid char width/heights and reset to default values accordingly. Please give the following build a try

Same result.

http://pastebin.com/EYwySn3Y

[keith]

Just an update on this issue.

This appears to be a bug in Dell's UEFI BIOS firmware with rendering text on screen, returning bogus values for text width and height. This causes problems in MemTest86 when calculating screen coordinates for drawing elements on the screen.

We were able to implement a workaround that uses a legacy method for rendering text. This method, however, is limited to outputting English characters. So if your firmware is affected by this issue and the workaround is required, changing the language may not be possible. This workaround shall be included in the next patch release.