Folding Forum

I've had 12 slots fail in the past 2 days, after running uninterrupted for weeks at a time. So it's a problem I haven't been having.

After I remove the failed slot and add a new slot, it will download a new work unit. But if it gets another 13000, it just fails again.

So probably the Maxwells are still unable to do any core 17 project other than 9201.

Which core were the failures with? If Core 17, v0.52 or v0.55 - these are the old ones which are having problems with Maxwell and some WUs.

It's 0.0.52, I thought it updated automatically.

AFAIK Core 17 has not been updated with any Maxwell fixes yet - my guess is that these Core 17 projects were whitelisted by mistake for Maxwells.

Right, it will always say Project 9201 for a Maxwell core 17 or it won't work.

Breach wrote:AFAIK Core 17 has not been updated with any Maxwell fixes yet - my guess is that these Core 17 projects were whitelisted by mistake for Maxwells.

Apparently they work fine if you update your drivers.

bruce wrote:

Breach wrote:AFAIK Core 17 has not been updated with any Maxwell fixes yet - my guess is that these Core 17 projects were whitelisted by mistake for Maxwells.

Apparently they work fine if you update your drivers.

bruce, per the beta thread, for Maxwell compatibility a change in Core 18 was done, but not for Core 17 (he's still using the old version)...?

I've been checking the forums here regularly to see if any driver updates have been released, but the only topics I've seen still say "game ready driver only, no difference in CUDA bugs.

Besides, the last time I updated my drivers "just because", my PPD dropped over 10% so I went back to the previous drivers.

As for versions of Core 17, the client is supposed to update the core automatically.

Like I said, there were sudden multiple failures across all my folding rigs, and I haven't changed anything on my end.

I think what bruce was getting at is that some projects were previously blacklisted for Maxwell cards, but they should now work with CUDA 7 which is present in drivers 347.xx+. However, for Core 18 there were also core fixes apparently, which I guess (?) weren't necessary for Core 17 and just upgrading the driver to 347.xx should work.

Are you running with "beta"?

No, and I'm not doing anything differently than I've been doing for the past few months.

The assignment servers just started giving me work units that aren't compatible with my gpus.

But I'll update drivers on some of them and see if they can do the new projects.

Hey, I just got a core 17 Project 10466, and it's actually made it to 2.54% without failing. I haven't noticed that project yet, so I'll watch and report what happens.

bruce is deleting my posts, so I won't bother coming here to report any more issues with the assignment servers. bruce is accusing me of secretly running beta when I'm not and never have, so have fun with your power-abusing moderators and your half-dead forum. Meanwhile, hundreds of folders are probably experiencing the same work unit failures that I was trying to report, and instead of bringing the problem to light you're just blaming me and trying to keep it quiet. Deleting my posts won't fold any proteins, but helping people solve this issue will.

Chill man. It's clear that you're not running beta - if you're running beta you'd be using core 0.0.55 and not 0.0.52.