Sorry for the vague or erroneous parts. The point is to get the lesser and greater self-tests to complete. At the time that I was experimenting with CUDALucas, one of the heavy hitters around here said he was running his cards at 1600, which might have meant from 200-400 MHz below the stock RAM clock, depending on the particular card. It seemed at the time that CuLu might be a definitive test of VRAM precision in a mathematical setting.

LaurV has experience with Tesla cards. They tend to run both GPU and RAM slower than consumer cards, besides having ECC memory. They are also scary expensive.

It's funny. It passed the short self-test (-r 0), and has had only one hiccup on the longer self-test (-r 1) so far. The one hiccup (a mismatched residue) passed fine when it repeated the test immediately after. The long test hasn't finished yet, but we'll see what it does.

The crazy thing is that this is all at stock clock.

Edit: Update--got through the self-test with only the one hiccup. Tried to rerun threadbench. Failed at FFT of 3780K. Dropped memory speed by 100 Mhz and ran threadbench again. Failed again at about the same FFT. No idea what's going on.

CUDA 6.5 compile
 

Hiya.

I've compiled a CUDALucas binary for my GTX970. If anyone wants to try it out, i've uploaded it to [url]http://monsted.dk/CUDALucas2.05Beta-6.5-x64.zip[/url]

From what i can see, it works as intended, but i'd be interested to hear if the rest of you agree.

[QUOTE=monsted;394095]Hiya.

I've compiled a CUDALucas binary for my GTX970. If anyone wants to try it out, i've uploaded it to [url]http://monsted.dk/CUDALucas2.05Beta-6.5-x64.zip[/url]

From what i can see, it works as intended, but i'd be interested to hear if the rest of you agree.[/QUOTE]

Guess not. It reported no residue on a "doublecheck" work unit and marked it as a prime. Anyone able to make a functioning CUDA 6.5 compile? :)

I can make one, give me a bit, I'll post it when it's done.

Here's a 64-bit CUDA 7.0 version for Windows if you'd like to try it. You'll need the cufft dll (it's waaaay too big to attach here). The cudart dll is included.

[QUOTE=monsted;394411]Guess not. It reported no residue on a "doublecheck" work unit and marked it as a prime. Anyone able to make a functioning CUDA 6.5 compile? :)[/QUOTE]

2.05 Beta CUDA 6.5 x64 is [URL="https://sourceforge.net/projects/cudalucas/files/2.05%20Beta/"]here[/URL] (passed self test)

I can also build the CUDA 7.0 binaries, but 7.0 is still Release Candidate, so if you experience bugs...

CUDA Libs are [URL="https://sourceforge.net/projects/cudalucas/files/CUDA%20Libs/"]here[/URL]. I'll upload the 7.0 libs when 7.0 is final.

Flash, is that a windows build, and if so, what card and driver version are you using? I've never been able to continuously run CUDALucas on Windows--always run into that "Driver stopped responding and restarted" TdrDelay error that nobody can pin down.

[QUOTE=wombatman;394431]Flash, is that a windows build, and if so, what card and driver version are you using? I've never been able to continuously run CUDALucas on Windows--always run into that "Driver stopped responding and restarted" TdrDelay error that nobody can pin down.[/QUOTE]

IIRC, people were working around that problem with a looping batch file which restarts CuLu.

Yes, the batch file works well. It's been a while but the driver issue popped up a while ago. Someone reported the problem to nVidia but they haven't done anything about it.

I tested this on GTX 580 with driver 347.12. I don't have it running full time right now but when I did a batch file always keeps it going.

Something simple:

[CODE]:Beginning
CUDALucas.exe
Goto Beginning[/CODE]

Yeah, I had used the batch file method too. Just wondered if there was a way to just have it run without crashing. Thanks!