[QUOTE=kladner;409118]Those cards not only do a lot more work than my two 580s, but at a lazy guess, they use less power between them.[/QUOTE]
Your 580's, however, are fairly good at LL. Those 9X0's aren't.

[QUOTE=frmky;409125]Your 580's, however, are fairly good at LL. Those 9X0's aren't.[/QUOTE]

In the last day or so, I began testing CUDALucas on one of the cards. So far, it will complete the self test, but crashes the driver doing cufftbench or threadbench. I have it quite throttled back both the GPU and memory. I may try the same things on the other card and see if it might be hardware related.

You might try increasing tdrdelay. I had the same issue until I upped that from the default of (I think) 2 seconds to something more like 10 or 20. I still occasionally get a crash, but it greatly increased the reliability. You can also use a looping batch file to have CUDALucas restart automatically when it crashes and stop when there's nothing left in the worktodo file (or stop when a results file is generated).

It's currently summer in SoCal which means I mainly run at night to avoid coming home to a molten pool of computer on the floor :furious: Also admittedly my 980TIs are both heavily overclocked and can put out around 800-850 GHzD/D each sooo yeah once winter starts to roll in I'll really be kicking ass until then it will be slow going.

[QUOTE=wombatman;409131]You might try increasing tdrdelay. I had the same issue until I upped that from the default of (I think) 2 seconds to something more like 10 or 20. I still occasionally get a crash, but it greatly increased the reliability. You can also use a looping batch file to have CUDALucas restart automatically when it crashes and stop when there's nothing left in the worktodo file (or stop when a results file is generated).[/QUOTE]

I am a bit slow tonight. "tdrdelay"? Is this a CuLu setting? Does it apply to cufftbench and threadbench?

I think I have an example of a looping batch file around. I thought that was used to work around random crashes when doing LL work. Would the same apply to the bench functions?

Thanks! I appreciate the reply. I know there are considerable discussions of CuLu stopping while doing LL here on the forum. It has been a while since I read them.

I still haven't tried the same functions on the other card. The cards in question are a 797 MHz EVGA with a Zalman aftermarket cooler, and a 833 MHz MSI "Lightning". The latter is certainly the better of the two. It runs faster and cooler on less voltage than the EVGA. My previous experience with CuLu taught me that memory clocks on consumer GPUs are too high for DP calculations. I have mine set back from over 2 GHz to 1.6 GHz.

The looping file won't work for the benchmarks. You might have to do them in pieces instead.

Here's a link about TdrDelay. The long and short is that Windows will kill the video driver after 2 seconds of non-responsiveness or something like that. But CuLu sometimes does that without actually locking everything up, and Windows restarts the driver as though it crashed.

[url]http://http.developer.nvidia.com/NsightVisualStudio/2.2/Documentation/UserGuide/HTML/Content/Timeout_Detection_Recovery.htm[/url]

And here's a link that shows how to directly edit it in the registry: [url]https://www.reddit.com/r/battlefield_4/comments/1xzzn4/tdrdelay_10_fixed_my_crashes_since_last_patch/[/url]

I believe mine's set to 20 now. Like I said, you will still get an occasional crash, so I would use a looping batch file, but I definitely saw much much fewer crashes and restarts with the increase TdrDelay.

[QUOTE=wombatman;409154]The looping file won't work for the benchmarks. You might have to do them in pieces instead.

Here's a link about TdrDelay. The long and short is that Windows will kill the video driver after 2 seconds of non-responsiveness or something like that. But CuLu sometimes does that without actually locking everything up, and Windows restarts the driver as though it crashed.

[URL]http://http.developer.nvidia.com/NsightVisualStudio/2.2/Documentation/UserGuide/HTML/Content/Timeout_Detection_Recovery.htm[/URL]

And here's a link that shows how to directly edit it in the registry: [URL]https://www.reddit.com/r/battlefield_4/comments/1xzzn4/tdrdelay_10_fixed_my_crashes_since_last_patch/[/URL]

I believe mine's set to 20 now. Like I said, you will still get an occasional crash, so I would use a looping batch file, but I definitely saw much much fewer crashes and restarts with the increase TdrDelay.[/QUOTE]

Thanks very much! I will try this at once. I see Timeout Detection Recovery, above now, which sort of rings a bell. I really appreciate the quick and detailed response.

EDIT: Both FF and IE are balking at the Reddit link, citing certificate problems.

[QUOTE=chalsall;409116]Just to put on the table...

We recently received, unexpectedly, a great deal of DCTF'ing firepower. This is great, of course.

But... We're still right at the edge of properly feeding the LL'ers and P-1'ers. Slowly falling behind, in fact.

So, those who currently aren't sure if they should DCTF or LLTF, please choose LLTF'ing.

We now return you to your regular programming.... :smile:[/QUOTE]


I had to take the system down for 12 hours yesterday for a chiller upgrade, but I can transition some more power to LL. Is there an easy way to see our current pace vs. demand?

[QUOTE=kladner;409155]Thanks very much! I will try this at once. I see Timeout Detection Recovery, above now, which sort of rings a bell. I really appreciate the quick and detailed response.

EDIT: Both FF and IE are balking at the Reddit link, citing certificate problems.[/QUOTE]

Weird...Chrome had no issue with it. Here's the relevant bit:
[QUOTE]Simply go to your registry: Start --> Run --> Type in "Regedit"
Go to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers" and create a key of type "DWORD (32-bit)" and name "TdrDelay" with a value of 10 as Decimal value.[/QUOTE]

[QUOTE=airsquirrels;409173]I had to take the system down for 12 hours yesterday for a chiller upgrade, but I can transition some more power to LL.[/QUOTE]

That would be very much appreciated. Perhaps 50/50, at least for a week or so?

[QUOTE=airsquirrels;409173]Is there an easy way to see our current pace vs. demand?[/QUOTE]

It's a bit tricky (many "waves", etc), but if you look at [URL="https://www.gpu72.com/reports/available/"]this report[/URL] and don't see at least a few hundred candidates available in the "75" column, then we're short feeding the P-1'ers.

[QUOTE=wombatman;409174]Weird...Chrome had no issue with it. Here's the relevant bit:[/QUOTE]

Again, many thanks! I did spend a while this morning running chunks of cufftbench.bat on the MSI card. It runs for a while, stops, I start it again, it zips through what it's already done, and then does some more. No error messages. The EVGA card always quit with an 'unknown error."