Does an increase in the "polite" setting equal a longer delay?

Edit: Well, looks like regardless of the answer, everything is much more stable. Thanks for the help!

QuickStart for Win version of CUDALucas/CUDA MP1 ??
 

I've downloaded several versions of CUDA MP1 and a couple of versions of CUDALucas -- Debug_CUDALucas_205Beta_CUDA4.2-Win32_r68.exe and Release_CUDALucas_205Beta_CUDA4.2-Win32_r68 -- but when I try to run any of these I just get the console window for a split second and no output, either files or text in the console. Earlier, I was getting a message that a .dll file was missing, but I downloaded the .dll's and that seemed to fix that. But now I can't get the programs to run for more than a split second.

Almost all of the posts about CUDA programs I see are for running under UNIX/LINUX. I happen to have a Wintel box in my office with a GeForce 7300 LE GPU which appears underutilized ... can anyone give me a "GPU computing under Win7 for Dummies"-style instruction sheet for getting LL, P-1, or trial factoring started on this machine ? (Windows 7 64-bit, Core2 6320) Please keep in mind you're talking to a non-programmer (OK, I studied a little C, I use Linux at home, but *not* a blooded programmer).

GPU-Z gives me some info about this card, but doesn't indicate it's CUDA-capable. I tried installing the drivers from nVidia but this didn't seem to change anything. :(

thanks,

MF

Open a command prompt first in the location of your executable and then run it from the command-line, that way you'll see what error message is spit out without the window disappearing.

Your 7300 LE won't be any use unfortunately, if I recall correctly nothing lower than GeForce 8600 supports any form of CUDA (and some things won't play nice before the 200-series).

Still not stable
 

I've been trying to get CUDALucas running on my GTX 570 on and off for a while now. mfaktc works perfectly (and even with a slight overclock). I've tried various settings for -polite (from 0 to 1000). I got a new power supply to ensure that it wasn't a power draw issue. Temperatures while running CUDALucas aren't any higher than those for mfaktc, so I don't think it's that.

I've also compiled CUDALucas myself (under Windows 7 with VS2012) using CUDA 7.0. Neither it, nor the binary that uses CUDA 5.0 (the most recent release 2.05) works consistently. After a variable amount of time (sometimes < 10,000 iterations, sometimes >200,000 iterations), CUDALucas errors with:
[CODE]D:/CUDA/CUDALucas/SourceForge/CUDALucas.cu(1878) : cudaSafeCall() Runtime API error 6: the launch timed out and was terminated.
Resetting device and restarting from last checkpoint.

Using threads: square 512, splice 1024.
D:/CUDA/CUDALucas/SourceForge/CUDALucas.cu(1049) : cudaSafeCall() Runtime API error 46: all CUDA-capable devices are busy or unavailable.[/CODE]

I don't think it's the card itself having issues either--I used the EVGA Overclock Testing Utility and ran both the GPU core burner and the GPU memory (1024 MB) burner. Only ran them for a few minutes, but there were no artifacts and no driver crashes.

Any ideas on what I could look at?

What are your core and RAM clocks?

Brand and model?

The latter questions are less important, but the speed the memory is running at can make all the difference. If I am repeating myself, sorry.

Can I assume that CuLu can complete -st2?

[QUOTE=kladner;392732]What are your core and RAM clocks?

Brand and model?

The latter questions are less important, but the speed the memory is running at can make all the difference. If I am repeating myself, sorry.[/QUOTE]

That would be my guess, too. mfaktc doesn't use the memory at all really. I might try clocking down the memory and see what happens.

Core and RAM are at stock values (797 Mhz and 975 Mhz, respectively, according to GPU-Z). It's an EVGA 570 GTX base model (so no factory overclocking or anything like that).

I'm not sure what -st2 is, but I usually (though not always) am unable to complete a full -threadbench or -cufftbench. Full being from 1 to 8192 with 2-5 repetitions.

I'll try downclocking the memory by 50 and see if that helps.

Sounds a lot like the driver bug that showed up shortly after the 300.?? driver and affects 570s, 580s, and I presume, 590s. I don't think Nvidia has any inclination to fix it. The only solution is to use old drivers and thus old cuda libraries. If it is worth your effort, I know the 295 dirvers with Cuda 4.2 work. flashjh knows a more precise cutoff point.

That seems like it might be it. Dropping the memory by 50 didn't help. It's a shame, really.

[QUOTE=wombatman;392742]Core and RAM are at stock values (797 Mhz and 975 Mhz, respectively, according to GPU-Z). It's an EVGA 570 GTX base model (so no factory overclocking or anything like that).

I'm not sure what -st2 is, but I usually (though not always) am unable to complete a full -threadbench or -cufftbench. Full being from 1 to 8192 with 2-5 repetitions.

I'll try downclocking the memory by 50 and see if that helps.[/QUOTE]

This class of video card is built for gaming, where a few graphical errors are negligible. When I experimented first with CuLu, it was probably on the 460 I'm running now. The RAM defaults to 1800 (900) MHz (remembering DDR memory). I am fairly sure that I only got the Self Test, and Extended Self Test, (-st, -st2) to complete successfully at 1700 (850). 50 MHz reduction in base clock sounds like a good start for testing.

(It's been a while since I ran CuLu. I'm sure I'll here about it from the local deities if I misstated anything above.) :ermm:

I'll try the self-tests as well (pretty sure it's -r 0 and -r 1). I also tried increasing the TdrDelay in the registry from 0 to 8. That just made the screen freeze for ~8 seconds when the driver stopped.