mfaktc: a CUDA program for Mersenne prefactoring - Page 221

kladner · 2014-11-23, 02:12

I have a bit of suspicion about GeForce driver '344.75-desktop-win8-win7-winvista-64bit-international-whql'. Since I installed it, I have had a few instances of finding mfaktc not running. When I restart it, I find that the 580 has locked down to 400 MHz, requiring a reboot. It must be a couple of years since I saw such a problem.

I have now rolled back to the next previous 344.65, but haven't been using it long enough to establish stability. I also have earlier versions like 344.48, in which I have confidence.

Has anyone else noticed a change in behavior with 344.75?

Chuck · 2014-11-23, 16:09

Quote:

Originally Posted by kladner

I have a bit of suspicion about GeForce driver '344.75-desktop-win8-win7-winvista-64bit-international-whql'. Since I installed it, I have had a few instances of finding mfaktc not running. When I restart it, I find that the 580 has locked down to 400 MHz, requiring a reboot. It must be a couple of years since I saw such a problem.

I have now rolled back to the next previous 344.65, but haven't been using it long enough to establish stability. I also have earlier versions like 344.48, in which I have confidence.

I moved to 344.65 on Nov 11 and haven't noticed any problems with it. I don't see any performance changes from earlier versions (I don't do any gaming).

kladner · 2014-11-23, 16:55

Quote:

Originally Posted by Chuck

I moved to 344.65 on Nov 11 and haven't noticed any problems with it. I don't see any performance changes from earlier versions (I don't do any gaming).

So far, so good, here, with 344.65. I am thinking that there may be little reason to keep up with the latest drivers for something as old as the 500 series, if the drivers' main purpose is to tune the latest cards to the latest games.

henryzz · 2014-11-23, 17:57

Quote:

Originally Posted by kladner

So far, so good, here, with 344.65. I am thinking that there may be little reason to keep up with the latest drivers for something as old as the 500 series, if the drivers' main purpose is to tune the latest cards to the latest games.

I still update occasionally for a 8000 series

Chuck · 2014-11-24, 00:31

Quote:

Originally Posted by kladner

So far, so good, here, with 344.65. I am thinking that there may be little reason to keep up with the latest drivers for something as old as the 500 series, if the drivers' main purpose is to tune the latest cards to the latest games.

Agreed. I don't think driver updates have ever made any significant difference on mfaktc performance.

kladner · 2014-11-24, 04:56

344.65 has yet to dump on me. My suspicions about 344.75 are solidifying.

Xyzzy · 2014-11-24, 05:29

Our work boxes are not connected to the Internet. We have a USB key setup with a Windows 7 installer and the few files necessary to set up a barebones CUDA environment. Once a particular program or driver has proved itself to be stable we have no intention of ever replacing it. We can replicate our install from scratch in under 30 minutes. (The configuration files are already built on the USB key.) We have every step written down on a piece of paper and we do the absolute minimum "tweaking" possible to ensure a stable system.

Mini-Geek · 2014-11-24, 12:39

Quote:

Originally Posted by kladner

Has anyone else noticed a change in behavior with 344.75?

I upgraded to 344.75 and haven't noticed any problems running mfaktc on my dual GTX 560s.

wombatman · 2014-11-24, 14:14

Quote:

Originally Posted by kladner

I have a bit of suspicion about GeForce driver '344.75-desktop-win8-win7-winvista-64bit-international-whql'. Since I installed it, I have had a few instances of finding mfaktc not running. When I restart it, I find that the 580 has locked down to 400 MHz, requiring a reboot. It must be a couple of years since I saw such a problem.

Just as a heads-up, you can disable/re-enable the video card under device manager and accomplish the same thing most of the time. Saves the headache of having to restart the entire computer when you push the video card a little too far (as I often do...).

kladner · 2014-11-24, 16:24

Quote:

Originally Posted by wombatman

Just as a heads-up, you can disable/re-enable the video card under device manager and accomplish the same thing most of the time. Saves the headache of having to restart the entire computer when you push the video card a little too far (as I often do...).

Thanks for the tip!

Mark Rose · 2015-01-22, 23:54

I found a "bug".

While double checking some trial factoring assignments in another thread, mfaktc picked 75bit_mul32 for Factor=N/A,54820379,63,66 instead of the usual barrett76_mul32_gs. It ran about 1/7th the speed that 64,66 assignments run since it was sieving on the CPU.

I think the default should be to always GPU sieve, or if the CPU sieve is to be used, to split the assignment at the cross over point.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
mfakto: an OpenCL program for Mersenne prefactoring	Bdot	GPU Computing	1676	2021-06-30 21:23
The P-1 factoring CUDA program	firejuggler	GPU Computing	753	2020-12-12 18:07
gr-mfaktc: a CUDA program for generalized repunits prefactoring	MrRepunit	GPU Computing	32	2020-11-11 19:56
mfaktc 0.21 - CUDA runtime wrong	keisentraut	Software	2	2020-08-18 07:03
World's second-dumbest CUDA program	fivemack	Programming	112	2015-02-12 22:51

2014-11-23, 02:12	#2421
kladner "Kieren" Jul 2011 In My Own Galaxy! 2·3·1,693 Posts	I have a bit of suspicion about GeForce driver '344.75-desktop-win8-win7-winvista-64bit-international-whql'. Since I installed it, I have had a few instances of finding mfaktc not running. When I restart it, I find that the 580 has locked down to 400 MHz, requiring a reboot. It must be a couple of years since I saw such a problem. I have now rolled back to the next previous 344.65, but haven't been using it long enough to establish stability. I also have earlier versions like 344.48, in which I have confidence. Has anyone else noticed a change in behavior with 344.75?

2014-11-24, 04:56	#2426
kladner "Kieren" Jul 2011 In My Own Galaxy! 27AE₁₆ Posts	344.65 has yet to dump on me. My suspicions about 344.75 are solidifying.

2014-11-24, 05:29	#2427
Xyzzy "Mike" Aug 2002 5·17·97 Posts	Our work boxes are not connected to the Internet. We have a USB key setup with a Windows 7 installer and the few files necessary to set up a barebones CUDA environment. Once a particular program or driver has proved itself to be stable we have no intention of ever replacing it. We can replicate our install from scratch in under 30 minutes. (The configuration files are already built on the USB key.) We have every step written down on a piece of paper and we do the absolute minimum "tweaking" possible to ensure a stable system.

2015-01-22, 23:54	#2431
Mark Rose "/X\(‘-‘)/X\" Jan 2013 2×5×293 Posts	I found a "bug". While double checking some trial factoring assignments in another thread, mfaktc picked 75bit_mul32 for Factor=N/A,54820379,63,66 instead of the usual barrett76_mul32_gs. It ran about 1/7th the speed that 64,66 assignments run since it was sieving on the CPU. I think the default should be to always GPU sieve, or if the CPU sieve is to be used, to split the assignment at the cross over point.