[QUOTE=flashjh;394698]Go into the registry and modify the key manually, change it to 128 (dec) see attached picture for the location. Restart the system and try again. Use the batch file I posted to track and see if it's still hanging or not.

Modify the "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers" TdrDelay DWORD[/QUOTE]

Did this last night with TdrDelay set to 20 (since I already had that and was running other things). It restarted 45 times(!) overnight, which is pretty much the opposite of what I was seeing running it under MinGW64. So I'm going to run it under MinGW64 and see how many times it restarts using a bash script.

[QUOTE=wombatman;394831]...which is pretty much the opposite of what I was seeing running it under MinGW64.[/QUOTE]
This is the 1st I've heard of MinGW64. What is it and how did you use it to run CUDALucas?

[QUOTE=owftheevil;394829]Version built for cuda 4.2 - 7.0 and some quick benchmarks for comparisons of the different cuda versions on Linux:[/QUOTE]

Awesome, I'll get several versions tested on Windows, as well. I am hesitant to release CUDA 7 versions until it's out of RC.

Many thanks to owftheevil and flashjh :bow:

Il will wait for the 7.0 and try to recompile under Linux when ready. I assume the source is on SourceForge.

Luigi

[QUOTE=flashjh;394833]Awesome, I'll get several versions tested on Windows, as well. I am hesitant to release CUDA 7 versions until it's out of RC.[/QUOTE]
Agreed. That was a specific offer for Luigi.

[QUOTE=flashjh;394832]This is the 1st I've heard of MinGW64. What is it and how did you use it to run CUDALucas?[/QUOTE]

I'm no expert on it, but it's basically a Windows-based Linux-y environment. I've primarily used it to compile things like GMP, GMP-ECM, MSieve, and the like and then run them. At this point, there are a number of individual toolchain builds, but here's a main website for it: [url]http://mingw-w64.sourceforge.net/[/url]

Here are my timings with 2.05 on a GTX580

CUDA 5.5
[CODE]Using threads: square 256, splice 128.
Starting M57885161 fft length = 3136K
| Date Time | Test Num Iter Residue | FFT Error ms/It Time | ETA Done |
| Feb 07 20:36:39 | M57885161 10000 0x76c27556683cd84d | 3136K 0.24805 4.7168 47.16s | 3:03:49:48 0.01% |
| Feb 07 20:37:26 | M57885161 20000 0xfd8e311d20ffe6ab | 3136K 0.23438 4.7092 47.09s | 3:03:45:21 0.03% |[/CODE]

CUDA 6.0
[CODE]Using threads: square 256, splice 128.
Starting M57885161 fft length = 3136K
| Date Time | Test Num Iter Residue | FFT Error ms/It Time | ETA Done |
| Feb 07 20:32:02 | M57885161 10000 0x76c27556683cd84d | 3136K 0.25000 4.8228 48.22s | 3:05:32:02 0.01% |
| Feb 07 20:32:50 | M57885161 20000 0xfd8e311d20ffe6ab | 3136K 0.25000 4.8281 48.28s | 3:05:33:48 0.03% |[/CODE]

CUDA 6.5
[CODE]Starting M57885161 fft length = 3136K
| Date Time | Test Num Iter Residue | FFT Error ms/It Time | ETA Done |
| Feb 07 20:34:24 | M57885161 10000 0x76c27556683cd84d | 3136K 0.22266 4.8867 48.86s | 3:06:33:43 0.01% |
| Feb 07 20:35:13 | M57885161 20000 0xfd8e311d20ffe6ab | 3136K 0.23682 4.8775 48.77s | 3:06:28:26 0.03% |[/CODE]

Your times are ½ mine, what card are you using?

[QUOTE=wombatman;394831]Did this last night with TdrDelay set to 20 (since I already had that and was running other things). It restarted 45 times(!) overnight, which is pretty much the opposite of what I was seeing running it under MinGW64. So I'm going to run it under MinGW64 and see how many times it restarts using a bash script.[/QUOTE]

@flash, I've been running CUDALucas under MinGW for at least 3 hours (probably more like 5 or 6), and I don't have a single restart. No idea what the difference is between the command prompt and MinGW, but MinGW with TdrDelay=20 is pretty much continuously stable. I'll be running CUDALucas overnight to get a longer term test (and will note exactly when I start and stop).

CUDALucas 2.05 Final Release
 

After many months and a lot of work CUDALucas 2.05 is released. You can find the binaries and the lib files [URL="https://sourceforge.net/projects/cudalucas/files/"]here[/URL] for Windows and Linux.

New features in 2.05:
[CODE] - RCB (round - carry - balance, ~1% decrease in iteration times)
- On-the-fly FFT selection. Keyboard driven or automatic if error level exceeds threshold
- Included GPU memtest and tools to automate FFT finetuning and thread selection
- Bit shift to prevent errors from producing similar results[/CODE]

Because of the time it took to get this to release, most of the code changes have been extensively tested, but before you go production, please allow the following tests to complete (should take a couple hours on a 580):

[CODE] CUDALucas -cufftbench 1024 8192 5
CUDALucas -threadbench 1024 8192 5 0
CUDALucas -r 1
CUDALucas 6972593[/CODE]

If all these tests won't complete, take a look at your card timings and also look at running a memtest on the card (see readme).
(if threadbench won't complete on 2.0 cards due to the driver issue, try changing the 0 to a 1 or skip that test)

You can also follow the instructions [URL="http://www.mersenne.ca/cudalucas.php"]here[/URL] and send updated data to mersenne.ca

If you have contributed to CUDALucas, please contact flashjh and owftheevil
on mersenneforum.org so we can add you to the list of developers. Please
include your contribution to CUDAlucas so it can be added to this README.

To automate CUDALucas on Windows you can use [url]http://mersenneforum.org/misfit/downloads/MISFIT-CULU/[/url]

Thanks to everyone for making this happen! Happy hunting!

Excellent work! Congratulations to all concerned. Is there a CUDA 5.0 version for 64bit windows? I can't see it in the list, although there is a 5.0 version for Linux on sourceforge. A CUDA 5.0 version would be useful because it avoids the crashing problem, when used with the appropriate driver. Also, can you confirm that this is revision r78?

mognuts

[QUOTE=mognuts;394900]Excellent work! Congratulations to all concerned. Is there a CUDA 5.0 version for 64bit windows? I can't see it in the list, although there is a 5.0 version for Linux on sourceforge. A CUDA 5.0 version would be useful because it avoids the crashing problem, when used with the appropriate driver. Also, can you confirm that this is revision r78?

mognuts[/QUOTE]
Thanks...
I uploaded the files. The 5.0 and 4.2 wouldn't compile without a small change.

The current revision is 79 and all is up to date.

If anyone finds anything during a run or you have suggestions for new changes, let us know!