"ERROR: file ntnbrlist.cpp line 63: Insufficent memory available for pairlists. Set pairlistdist to match the cutoff."

I have 3x GT 240 512MB cards. Looking at the amount of memory reported in each card, the one throwing the error has 100k bytes less showing, where the other two are identical. Any thoughts as to why this error happens?

Also, a reboot allowed a new WU to download and is working fine for close to 6 minutes (whereas all these died within 10 seconds). I did just recently upgrade to the newest Nvidia drivers (to get around the dummy plug issue), but also installed the two extra GT 240's as well. Just wasn't sure if anyone else has experienced this with this card / driver, etc.

Right now, you seem to be running 3 tasks, with one in wait. Let the system run for a while and see how it gets on. I see one card is overclocked.

You do have to restart to make the drivers work preperly. Did you do this and then see the errors, or did you run Boinc before restarting and see errors?

Anyway, give it time to get a balanced view.

http://www.gpugrid.net/forum_thread.php?id=2191

I definitely restarted after upgrading the drivers. I was just surprised to see a memory-related error message as I would think even if BOINC only gets about 450 / 512 MB memory of the card that would still be more than sufficient. I am just about finishing up my 2nd round of WU's since the errors (should have each card completing WU's over the next 3 hours). Hopefully, I'll get new WU's and never see the error again. I'll report back if so. Thanks.

FYI - I do have one card quite a bit overclocked, but it was the GT240 I had in the system for 6 months. The two new ones I'll be slowly increasing the clocks, but not until I don't see this memory error for a while (though it wasn't on the card reporting the memory error).

I see you now have 6 consecutive successes.

I dont want to speculate any further on the source of these memory errors. Either we will be told why or not (more likely).

FYI, I have 4 GT240's in one system, all with shaders OC'd to about 1600MHz and running well. OC'ing can be an issue, but not always.

Yup. I was a little worried after getting this error numerous times. But, apparently whatever the issue was resolved itself (knock on wood). It must have been some gremlins in the case or something.