TechPowerUp Announces MemTest64 - Test Memory from Within Windows

[Mussels]

just bumping this because it works - was having strange issues with chrome closing tabs randomly, this memtest found one error per pass.

ram came up clean in another system, just simply hated my mobo.

 

[Solaris17]

just bumping this because it works - was having strange issues with chrome closing tabs randomly, this memtest found one error per pass.

ram came up clean in another system, just simply hated my mobo.

Same I use this a lot at work and it’s found or passed hundreds of systems now

 

[Mussels]

only complaint is the system lag while its testing - programs like IBT dont mind stress testing while i watch a video at the same time, but this is rather aggressive

 

[Solaris17]

only complaint is the system lag while its testing - programs like IBT dont mind stress testing while i watch a video at the same time, but this is rather aggressive

I imagine its 100% dependent on the fact that its paging everything to disk. And unlike some stress test programs it probably does not yeild to other software that needs CPU time.

 

[DeathtoGnomes]

just bumping this because it works - was having strange issues with chrome closing tabs randomly, this memtest found one error per pass.

ram came up clean in another system, just simply hated my mobo.

reported for illegal bumping of useful tools.

 

[Fifth Element]

I'm having a strange bug error. When I run my 16GB of DDR4 memory at 2400MHz it runs fine for 24 hours no errors.

But when I change the speed to 2600Mhz it errors out with the following message:

"Memory locking failed (might be reserved by other apps/kernel)
"Test finished with no errors detected"

But it never actually ran the test as it gives this message almost immediately after starting the test with Run Indefinitely enabled.

My system is an Intel 6600K with a Z270 chipset running Windows 10.

Would love to keep testing my memory high but anything over 2400MHz just gives me this error every time.

Additionally, if I run prime95 at 2600Mhz it will do 24 hours with zero errors.

Any advice?

 

[W1zzard]

Try setting a smaller size. I've encountered this bug a few times but couldn't figure out yet what causes it

 

[Mussels]

seen it myself a few times, could never figure it out.

One thing that seemed to help was waiting longer after a boot, before trying the test - but it was odd behaviour.

 

[MikeRoz]

Good tool. Here are some of my suggestions.

1. Only used ~30GB RAM for my 128GB RAM. I hoped it can test close to the limit at least.

1) No idea what's going on there. Add me on Skype for a debugging session

Did you ever figure this one out? First time it ran, it only allocated around 36 GB for me, subsequent runs would be around 16 GB. Manually setting high values like 120 GB fails.

 

[Fifth Element]

Try setting a smaller size. I've encountered this bug a few times but couldn't figure out yet what causes it

I tried various limited tested memory sizes but even dropping to half it would fail. Also it was random. For example half memory would work once but next reboot days later it would fail.

Just an update for you.

 

[ZPERO]

I built a pc using the 2200G on an MSI B350M Gaming Pro and 2x4GB ram. I was having BSODs non stop, I couldn't even install windows without getting a Bsod. I ran Memtest64 and Aida64 free trial as well as mentest86. AIDA64 and Memtest64 both freeze my system, but I was able to run memtest86 and I got a bunch of errors so I sent it back and got a new kit of ram. The blue screens stopped and I managed to run the 3200MHz preset for a while. Then i downloaded my steam games and started freezing up (hard system hang) while playing certain (but not all) games. I ran memtest64 again, unfortunately my Aida64 trial has expired. I cannot run memtest64 at all even at low memory speeds. My entire system hangs while "Detecting usable memory" about three quarters of the way done.

I downloaded memtest64 on a school computer to see if maybe I have a bad mobo or cpu, and lo and behold, it still hangs the system three quarters of the way done through detecting usable memory. Does this program just suck?