Illegal memory accesses in VanitySearch too? Damn I wish that the names of functions were printed to standard output as a habit. (Bitcrack and Kangaroo are guilty of this non-practice too.) Errors like this make it hard for me to find the source, although according to you the buggy code is somewhere in a RIPEMD160 function.
Yes, like I said, version 17 works with the string function (taking off last 7 or 8 characters) for the 30xx series cards but will not work with full address. Also, I don't think the newest version works with string with the 30xx cards. I think that's why I went back to version 17. (No particular reason, I already had it compiled and tweaked so I just keep on using it, version 17 that is) I'm not 100 percent (because I have ran a lot of programs on different cards, but I don't think the newest version will run full address with latest drivers. It's a mess; I'll have to keep better notes.
So yeah, bitcrack absolutely doesn't work with 30xx, VS does but with string option, Kangaroo works fine but it is not optimized for 30xx cards; it doesn't take full advantage of the horsepower under the hood.
A side note, for those of you who do have a 30xx card, to get the program to actually read the sm cores correctly, add:
{0x86, 128},
to the GPUEngine.cu like this:
sSMtoCores nGpuArchCoresPerSM[] = {
{0x20, 32}, // Fermi Generation (SM 2.0) GF100 class
{0x21, 48}, // Fermi Generation (SM 2.1) GF10x class
{0x30, 192},
{0x32, 192},
{0x35, 192},
{0x37, 192},
{0x50, 128},
{0x52, 128},
{0x53, 128},
{0x60, 64},
{0x61, 128},
{0x62, 128},
{0x70, 64},
{0x72, 64},
{0x75, 64},
{0x86, 128},
{-1, -1} };
