To Stem 83
Thanks for the info:
First you might set the
RETESTPIN=50
As we never tested such a long cycle. But we doubt the problem is there.
VMR-MDK was developed against real targets using kali-i386. It has never been tested using AMD or luks encryption.
MTeams tried luks encryption but the encryption process took too long to complete causing other program processes to fail. We remove the encryption feature and programs ran normally again. So if we were to take a guess, the problem is there.
Suggest you make a persistent usb install of kali not using luks and maybe not amd and see what occurs. If you can just turn off luks try that. We gave up on luks a while ago. We know nothing about AMD.
MTeams
