Windows memory diagnostic tool - auto runs?

Hello Davidk,

The Memtest86+ tool will test the two Crucial modules not the SSD. You are quite right that the SSD is essentially the same but these drives are tested by other means. Zbook suggested some checks which mainly looked at the SSD, my post was about the Crucial modules.

The Windows memory diagnostic tool was checking the Crucial memory modules not the SSD.

Do let us know if you have any further questions and let us know the results of running Memtest86.

That (link to) doco on memtest v5.01 (27/9/2013) suggest to me that something is out of date:
- the code and related date items indicates it's for windows 7 or earlier --> a bit inconguous for a windows 10 machine.
Is there a more recent version??

The explanations in the doco suggest that a bootable usb is being created and the test is run from that. Correct??
If that is the case, what is the advantage of doing it from usb (which as memory is a lot slower than the RAM it supposed to test, and potentially bottle-necked thru the usb host/controller) compared to running it from a local store? Supposedly it's using the same cpu in either case?

The Memtest86 I suggested you run is the best version for your older DDR3 memory modules. There is a newer test for DDR4 memory but we prefer to stick with the older one which has proved to be very useful.

The test runs from a bootable USB and does not involve the Windows operating system. It can be safely run overnight if you wish.

I confirm that MemTest86 Free (Version 8.4) works fine with my DDR3.
I have not tried version 9.0, the latest version.

OK.
Just confirming that the recommended test runs from a bootable usb, created by that memtest86+ download, v 5.13.

What size of usb will I require?

Haven't booted from a usb before, but many times from a DVD (as in a bootable recovery disk for Acronis backup software). Can that memtest86+ also be created on DVD?

Yes, you can use a DVD as the bootable media. It's not a large file so will easily fit on 1GB or less I believe.

prepping to do this . .
Matthew,
That method looks to save a lot of the prep effort in the memtest86+ doco. But (queries) . .
- size. The file you posted is a lot smaller than the size indicated by Philc. is there a specific reason?
- EFI file running on a FAT32 windows partition, when the tool nominally runs a linux core. Contradiction there, can you clarify? also, EFI has connotations for the type of BIOS. or do I have that wrong?
- running that EFI file from a FAT32 usb: explain how that works???

Davidk said:

- size. The file you posted is a lot smaller than the size indicated by Philc. is there a specific reason?

Last year, I downloaded "MemTest86 Free (Version 8.4)" and extracted all the files into a folder. The folder size was 504 MB. The folder contained a number of files, two of which were:

imageUSB.exe (1.88 MB)
memtest86-usb.img (500 MB)

I ran "imageUSB.exe", which created a bootable MemTest86 SD card from "memtest86-usb.img". The SD card contained a 4.65-MB "EFI" folder. I copied the folder and pasted it onto two USB devices. I could boot my PC from both of them.

Davidk said:

- running that EFI file from a FAT32 usb: explain how that works???

Note: the following operations will erase everything from your USB device.
Right-click on the Start button --> Windows PowerShell（Admin）.
Run the following commands shown in red:

DiskPart
List disk
Select disk X （where X is your USB device's number shown on the list.）
Detail disk （Make sure you have selected the correct disk.）
Clean （Erase everything from the USB device.）
Convert MBR
Create partition primary size=2000 （Create the first partition, which will contain MemTest86.）
Format FS=FAT32 quick （Format the partition as FAT32.）
Assign
Active
Create partition primary （Create the second partition, which can be used for your personal files.）
Format FS=NTFS quick （Format the partition as NTFS, which allows files larger than 4 GB.）
Assign
Exit

Then, extract all from "EFI.zip". You will have an "EFI" folder. Copy the whole folder into the root directory of the first, FAT32 partition on your USB device. Boot your PC from that device. It works on my GIGABYTE H81M. I suppose it will work on your GIGABYTE H97M, but no guarantee. Anyway, even if it does not work, you will lose nothing.

Davidk said:

- EFI file running on a FAT32 windows partition, when the tool nominally runs a linux core. Contradiction there, can you clarify?

I cannot clarify. I found nothing about Linux in the "EFI" folder. The folder still works. I just tried it minutes ago. See below:

Davidk said:

EFI has connotations for the type of BIOS. or do I have that wrong?

I booted my PC from the MemTest86 USB device in UEFI mode.

Matthew,
I know I asked, but . . too much information, and as I read it, not enuff to get going: meant as copy the file to usb, plug it in and boot.
As to my remark about linux, it's not unusual to use a linux core to do recovery or other operations on a windows PC. And in the tutorial about creating a bootable usb, the installation complete image shows executed lines about syslinux, which I saw creating the usb stick - next comment.

And philc . .
Tried the bootable usb method per the tutorial. Download and extract memtest86+-5.01.usb.installer.zip Ok, create the bootable disk OK. Everything looked good per the tutorial up to the completed usb stick and the boot from it.

In this BIOS (F6) setting boot priority from usb (UEFI) is only possible when a bootable usb is detected at BIOS stage. Meaning, it's only displayed as an option then - if there is no bootable usb in a connector, that priority option is simply not available in the boot options of the peripherals page. When it is displayed, it seems to be the automatic selection for #1 boot option, and all the others are shunted down one place (what was #1 becomes #2 etc).

So, with the usb stick plugged in, start, BIOS, set the boot priority with uefi as #1, save and exit . . and windows boots normally: nothing remotely like the memtest DOS-style display that's in the tutorial. Tried this several times, same result. So I'm not doing something right, or that boot from usb is simply non working. I've attached an explorer screenshot of the contents of the usb stick: after the installation - and the overall size suggests that the installation albeit finished Ok is missing something. But what?? suggestions??