clbitcrack has always had issues, still does, and did you change the compute_cap in your makefile,
otherwise compiling the cubitcrack won't succeed. even if succeeded won't work with your hardware.
change it accordingly to your hardware.
I didn't change the compute_cap value and was still able to compile cubitcrack on windows simply by updating the references to CUDA 10.1 to 11.2 and making sure project resources were in the correct locations. I'm not able to actually run it because of the "misaligned address" error, so I am using clbitcrack instead until someone is able to fix cubitcrack and allow it to run again with CUDA 11.2+.
In the meantime, what issues should I expect clbitcrack to have running on Windows? I'm not working with any P2SH addresses. What other issues would cause clbitcrack to not find a private key, as @yoyodapro mentioned?
If you take away the last 8 or 9 characters, does the issue of "misaligned address" go away?
example:
original address 13x7a9384def882923xxxxxxxx
change to 13x7a9384def882923
Also, play with your driver version. I believe I was able to roll back down and use cubitcrack with a 3070. However, no matter which driver or CUDA, it still isn't optimized for 30xx series. The 3070 should be getting close or above a 2080Ti.