03-16-2018, 04:44 PM
(This post was last modified: 03-16-2018, 04:46 PM by walterlacka.)
Atom - I'm able to reproduce this issue when running both GPU's every time I run it. Normally it will occur within a day or two.. sometimes it takes another day or so.
Like the other poster, it happens both on a new session and also on a restored session and it also occurs at varying positions within the hcmask file.
As you suggested, I attempted to reproduce the problem using only a single GPU (of the 2 that are in my rig), and it's been running for a longer time than it normally would if I were using multiple GPU's.
I can let it run longer (with a single GPU) if you'd like to be sure it won't occur when using just 1 GPU. Otherwise, if there's other information needed, please let me know.
PS - this is using the latest version of hashcat 4.1.0 (downloaded directly from https://hashcat.net/files/hashcat-4.1.0.7z) on windows 10
Like the other poster, it happens both on a new session and also on a restored session and it also occurs at varying positions within the hcmask file.
As you suggested, I attempted to reproduce the problem using only a single GPU (of the 2 that are in my rig), and it's been running for a longer time than it normally would if I were using multiple GPU's.
I can let it run longer (with a single GPU) if you'd like to be sure it won't occur when using just 1 GPU. Otherwise, if there's other information needed, please let me know.
PS - this is using the latest version of hashcat 4.1.0 (downloaded directly from https://hashcat.net/files/hashcat-4.1.0.7z) on windows 10