Initially one has no idea of how MemTest86 should run ... it would be helpful if you could describe what should appear on the screen, i.e. normal behavior.
My hardware: ASUS G73JW notebook (purchased Dec 2010) with new Samsung 850 Evo SSD. Latest UEFI BIOS for Windows 7, reportedly Win 8 compatible. 8 GB RAM. Intel Core i7 Q 740 @ 1.73GHz
Symptoms: strange errors in Windows 10 after upgrade from Windows 7, e.g. "The instruction at 0x00000000DB4E75FF referenced memory at 0x00000000DB4E7FF" (same address); occasional hangs during boot; unexpected errors; unexpected behavior.
With UEFI boot initially disabled, I ran v4.3.7 and saw it stepping through each test with a rotating State character. No errors.
With UEFI boot enabled, I see two lines in the boot options, both "UEFI: LG USB Drive 1100". Why two? It takes ages to reach the initial splash screen. Then it freezes almost immediately on Pass 0% Test 36% on Test 0 Pass 1/4 and neither ESC nor (c)onfiguration react... even after waiting 5+ minutes.
I'm puzzled why v4.3.7 runs happily with no errors (beyond the first iteration) and v6.2.0 Free hangs almost immediately. Could this be a sign of faulty RAM; a bug in v6.2.0; or have some other cause?
My hardware: ASUS G73JW notebook (purchased Dec 2010) with new Samsung 850 Evo SSD. Latest UEFI BIOS for Windows 7, reportedly Win 8 compatible. 8 GB RAM. Intel Core i7 Q 740 @ 1.73GHz
Symptoms: strange errors in Windows 10 after upgrade from Windows 7, e.g. "The instruction at 0x00000000DB4E75FF referenced memory at 0x00000000DB4E7FF" (same address); occasional hangs during boot; unexpected errors; unexpected behavior.
With UEFI boot initially disabled, I ran v4.3.7 and saw it stepping through each test with a rotating State character. No errors.
With UEFI boot enabled, I see two lines in the boot options, both "UEFI: LG USB Drive 1100". Why two? It takes ages to reach the initial splash screen. Then it freezes almost immediately on Pass 0% Test 36% on Test 0 Pass 1/4 and neither ESC nor (c)onfiguration react... even after waiting 5+ minutes.
I'm puzzled why v4.3.7 runs happily with no errors (beyond the first iteration) and v6.2.0 Free hangs almost immediately. Could this be a sign of faulty RAM; a bug in v6.2.0; or have some other cause?
Comment