07-10-2018, 09:23 PM
(This post was last modified: 08-12-2018, 12:43 PM by BotPass.
Edit Reason: Update with new information
)
Thank you for the responses.
I will have a look at it.
EDIT:
Just one followup to let you know.
The fix seems to work. Even though I cannot distinguish the returning code between opencl error or another error in a script, it helps as a work around for the OPENCL_OUT_OF_RESSOURCES. I could not find the reason for those.
Additionally it seems that under (unknown) rare circumstances hashcat print the last status before exit, but did not exit even after hour. Strangely it could not be killed by taskmanager and the system has to be rebooted. This happens not only to the one system with CL_OUT_OF_RECCOURCES but also on my second one.
I will have a look at it.
EDIT:
Just one followup to let you know.
The fix seems to work. Even though I cannot distinguish the returning code between opencl error or another error in a script, it helps as a work around for the OPENCL_OUT_OF_RESSOURCES. I could not find the reason for those.
Additionally it seems that under (unknown) rare circumstances hashcat print the last status before exit, but did not exit even after hour. Strangely it could not be killed by taskmanager and the system has to be rebooted. This happens not only to the one system with CL_OUT_OF_RECCOURCES but also on my second one.