+1 confirm this issue too.

@echo off
Set COUNTER=0
:loop
start "OCL_Vanitygen" "C:\path_to_vanitygen\oclvanitygen.exe" -k -o results%COUNTER%.txt -f patterns.txt -v
timeout /t 420

taskkill /f /im "oclvanitygen.exe"

timeout /t 7
set /A COUNTER=COUNTER+1
goto loop

This restarts the tool every 7 minutes. I chose a counter because I'm not sure if the previous results would get overwritten otherwise. Might not be needed.

Unfortunately this doesn't seem to be a viable workaround, and I suspect it may be the very process of finding and recording a match which is failing and causing the freezes.

I have tried both the above script in Powershell and an adapted version for Git bash, both of which do not generate any results file, even when running for periods of time that probably should have found many matches.

Running oclvanitygen directly without the file output flag, the program either eventually freezes or eventually passes 100% match probability without delivering any result (from that point the probability calculation disappears from the console output while the number of keys tried continues increasing). I have tried logging both output and errors to text files and no keys are returned, neither is any error information.

@echo off
Set COUNTER=0
:loop
start "OCL_Vanitygen" "C:\path_to_vanitygen\oclvanitygen.exe" -k -o results%COUNTER%.txt -f patterns.txt -v
timeout /t 420

taskkill /f /im "oclvanitygen.exe"

timeout /t 7
set /A COUNTER=COUNTER+1
goto loop

This restarts the tool every 7 minutes. I chose a counter because I'm not sure if the previous results would get overwritten otherwise. Might not be needed.

I just came back to check on this issue and found a nice workaround.

Tested, and it works!

Additionally, you don't need to use the counter since the result will be appended to the existing file.