For some context of how hashcat works with GPUs: https://hashcat.net/wiki/doku.php?id=frequently_asked_questions#how_to_create_more_work_for_full_speed https:/

For some context of how hashcat works with GPUs: https://hashcat.net/wiki/doku.php?id=frequently_asked_questions#how_to_create_more_work_for_full_speed https://hashcat.net/wiki/doku.php?id=frequently_asked_questi... Then: https://hashcat.net/wiki/doku.php?id=frequently_asked_questions#why_does_hashcat_sometimes_get_very_slow_at_the_end_of_an_attack https://hashcat.net/wiki/doku.php?id=frequently_asked_questi... It isn’t running a single thread at 100% GPU use until the end, it has to partition up the search space and balance how it creates possible passwords on the CPU, on the GPU, and based on the kind of attack patterns you asked for - and when it’s getting to the end of the search space, some of the search space partitions are done and the remaining ones aren’t enough to load the GPU fully, so hash throughout drops.