Has anyone else noticed mfaktc locked up lately? My instances look like they're running and the CPU usage stays @ 100%, but they are not progressing. I just updated to a newer beta driver to see if the old driver was causing the problem, but I was curious if anyone has seen this?

Jerry

I've experienced this from time to time since I first installed it however many months ago (it was at 0.17 at the time, I think) and I've had it where it just stops. Nothing appears wrong, except that nothing is output. When this happened in version 0.18, pressing ^C did nothing, because the current class never finished.

However, this happens rarely enough that it caused no problems. I [i]think[/i] this only happens in Windows, but that could easily be wrong.

[QUOTE=flashjh;288493]Has anyone else noticed mfaktc locked up lately? My instances look like they're running and the CPU usage stays @ 100%, but they are not progressing. I just updated to a newer beta driver to see if the old driver was causing the problem, but I was curious if anyone has seen this?

Jerry[/QUOTE]

Nvidia 285.62 has been working fine for me since Oct 2011; I updated to the mfaktc compiled with CUDA 4.10 and my two instances of mfaktc have continued to run without incident.

Chuck

[QUOTE=Dubslow;288495]I've experienced this from time to time since I first installed it however many months ago (it was at 0.17 at the time, I think) and I've had it where it just stops. Nothing appears wrong, except that nothing is output. When this happened in version 0.18, pressing ^C did nothing, because the current class never finished.

However, this happens rarely enough that it caused no problems. I [I]think[/I] this only happens in Windows, but that could easily be wrong.[/QUOTE]


Yes, this is exactly what I'm talking about... normally I wouldn't have mentioned it, but it's been happening several times a day lately. Since I have to *work*, I don't get a chance to fix it for several hours, which is a lot of lost TFing.


[QUOTE=Chuck;288496]Nvidia 285.62 has been working fine for me since Oct 2011; I updated to the mfaktc compiled with CUDA 4.10 and my two instances of mfaktc have continued to run without incident.

Chuck[/QUOTE]

I'm on 295.51 since just a bit ago. If the lockup occurs again, I'll revert to 285.62 and see if that fixes it.

Thanks

[QUOTE=Chuck;288496]Nvidia 285.62 has been working fine for me[/QUOTE]Same here.

I'm running 290.53 and mfaktc 0.18 (compiled with CUDA 4.10), and have not noticed any problems.

[QUOTE=flashjh;288493]Has anyone else noticed mfaktc locked up lately? My instances look like they're running and the CPU usage stays @ 100%, but they are not progressing. I just updated to a newer beta driver to see if the old driver was causing the problem, but I was curious if anyone has seen this?

Jerry[/QUOTE]

I had this effect on two systems since about half a year, with different versions of mfaktc and NVidia drivers, but only with overclocked GPU and during some other activity (internet browsing). The GPU is probably overloaded and protects itself by a reset to a very slow clock speed, und mfaktc hangs completely, consuming 0 % of the GPU. Also the CPU consumption of mfaktc goes down to 0 %. This happens because I set AllowSleep=1 in the ini file, which works fine and saves some power and noise.

Rad

Okay, i think them the only reason it crashed only in Windows is because in Windows I do overclock it, however I've never noticed instability except for this problem. While in the testing process for the OC, when it crashed, it crashed hard and Windows would complain about the video driver and that it had been restarted and the clock speed reset to stock (factory OC). no such thing occurred whenever mfaktc hanged. I also did not notice my cpu usage drop, although I don't have allow sleep enabled.

Did you test the stability of OC with, say, EVGA OC Scanner? (absense of artifacts in Furry and Tessy tests)

Thanks for all the replies. I downgraded to 285.62 and all seems to be fine now. Been running for a couple of days non-stop. :smile:

I've just updated my box from openSUSE 11.1 (gcc 4.3.x) to openSUSE 12.1 (gcc 4.6.x).
The reason why I didn't update my machine earlier was the fact that CUDA officiall supports only gcc up to 4.4. :sad:
I did the upgrade now because openSUSE 11.1 doesn't support AVX (e.g. Sandy Bridge).
So I've installed openSUSE 12.1 with gcc 4.6 and gcc 4.3 (packages from openSUSE 11.2 repo), setting gcc 4.3 to the default compiler (using the alternatives framework).
Now I can compile and run mfaktc on openSUSE 12.1.

Now the interesting part: I've compiled all mfaktc source files with gcc 4.3 expect the sieve code (sieve.c). [B]For sieve.c I've used gcc 4.6. Result: 20% faster sieving (SievePrimes=5000).[/B] This needs further testing but it looks promising. :smile:
Yes, no code changes, just an updated compiler!

Oliver