I'm afraid it is too harsh of a test
No need to worry about that. MemTest86 is not a "stress" test. There is no need for that to test RAM. MemTest86 simply writes data to every memory address, then reads the data and makes sure the data is the same. This does not wear create wear and tear like it might on a hard drive. It does not attempt to write and read as fast as possible. It is not a speed test. It is an "integrity" test. That may sound simplistic, data integrity is exactly what we want with our RAM.
But for new RAM, I think your two pass test is just fine. I like to test new RAM too but I just use the "Windows Memory Diagnostic" tool built into Windows. I use MemTest86 only if I suspect I might be having RAM issues.
Well, if your rig isn't giving you BSOD, it's fine.
RAM failures can result in a BSOD, but often don't!
For Windows to create a BSOD (blue screen of death indicating a "fatal system error" or "stop error") there has to be enough time left
before the OS "halts" or "crashes" for Windows to actually sense something is wrong. That is not always the case. And then, Windows
still needs to running enough (and be aware enough) to create the error message (with the applicable stop code)
and write the error to the Events log on the boot drive,
and send that message to the graphics solution to display on the monitor. That all takes a good bit of functionality and quite a few clock cycles.
Bad RAM (depending on the fault) can cause Windows and the entire system to halt so suddenly, it shuts down, freezes or reboots
before Windows is able to determine what the event/error is or toss up any error message (BSOD) on the monitor. So you cannot assume you RAM is good just because you don't get any BSODs.