Just to let you know that it's better that you run Prime95 on Blend as it'll also pressure your L2 cache as well as your RAM, and to run it at least 8-9 hours, so overnight. Also, realize that minidumps are absolutely and completely worthless to diagnose 0x101 bugchecks. At least a kernel dump is required. The MEMORY.DMP is always replaced by the latest crashdump generated by your PC.
I fear that I may only have enough expertise to partially diagnose the issue. While the kernel dump did indeed show me that previously Zone Alarm and your network drivers (you did update them, right?) were involved in that particular 0x101 bugcheck, I don't think I'll be able to ascertain exactly why it locked up without being able to manually reconstruct an x64 callstack from scratch, which is quite a nightmare even to more advanced debug analysts. I'm aware what to do afterwards, but that one step just continues to be puzzling to me since it's so radically different than doing the same for x32 callstacks. I can still give it a go again with another kernel dump to try and correlate a pattern between the latest crash and the one I analyzed previously, but I cannot be 100% sure that I'll be able to discover what did it exactly. I'll continue to research on it, but it may be a good while till I get the hang of it.
Anyways, your best bet right now is to just keep using Driver Verifier and let it work its magic on any new crashdumps you may come across. Remember to not select IRP Logging, Low Resource Sim or Force Pending I/O Requests checks, while selecting all others.