I've been testing my new system for a few days, now. I'm running the Ryzen 3600 processor on an Asus Crosshair 6 Hero (x370) mainboard, BIOS version 7106 and 32 GB RAM (Crucial Ballistix LT Sport Red, 2 x 16 GB Dual Rank, 3200 MHz XMP).
When running MemTest64, my system usually becomes unstable. Programs just dont work correctly anymore and the system does not recover. Screens might become black, too. In contrast to <this thread here>, I've only allocated 8 out of 12 threads and only around 80% RAM. So it can't be the problem that Windows runs out of memory completely. Unless it's a weird fragmentation issue with the Windows scheduler/allocator.
I first thought my RAM is defective, but ruled that out. All other stress tests and memory test tools worked without any problem so far. To be completely honest, I can't exactly remember whether or not I had a freeze/crash/whatever at the beginning where MemTest64 was not involved. However, I'm quite confident now that I only have issues with MemTest64.
<I posted a longer version of this on Reddit>
Initially I Thought it might be a compatibility issue or simply just a BIOS bug since many issues get reported with the new Zen2 BIOS versions.
Now a friend of mine could reproduce the same behaviour with MemTest64 (also running the Asus C6H board but a Ryzen 1800X). His system has been stable for a long time now. So that settles it for me and I have to say that MemTest64 just is not stable.
One thing that I have to add: I've already ran MemTest64 for 8 hours straight, but was not using the computer at that time, mostly. So, MemTest64 only seems to be unstable when other programs are running. Also quite a few times the issues arised when I opened a program and a UAC request was shown to click "yes" or "no". I'd have a black background (instead of the desktop background), and I'd be able to click "yes" but then the system would be in a weird, instable state already.
When running MemTest64, my system usually becomes unstable. Programs just dont work correctly anymore and the system does not recover. Screens might become black, too. In contrast to <this thread here>, I've only allocated 8 out of 12 threads and only around 80% RAM. So it can't be the problem that Windows runs out of memory completely. Unless it's a weird fragmentation issue with the Windows scheduler/allocator.
I first thought my RAM is defective, but ruled that out. All other stress tests and memory test tools worked without any problem so far. To be completely honest, I can't exactly remember whether or not I had a freeze/crash/whatever at the beginning where MemTest64 was not involved. However, I'm quite confident now that I only have issues with MemTest64.
<I posted a longer version of this on Reddit>
Initially I Thought it might be a compatibility issue or simply just a BIOS bug since many issues get reported with the new Zen2 BIOS versions.
Now a friend of mine could reproduce the same behaviour with MemTest64 (also running the Asus C6H board but a Ryzen 1800X). His system has been stable for a long time now. So that settles it for me and I have to say that MemTest64 just is not stable.
One thing that I have to add: I've already ran MemTest64 for 8 hours straight, but was not using the computer at that time, mostly. So, MemTest64 only seems to be unstable when other programs are running. Also quite a few times the issues arised when I opened a program and a UAC request was shown to click "yes" or "no". I'd have a black background (instead of the desktop background), and I'd be able to click "yes" but then the system would be in a weird, instable state already.