Nvidia 364.xx drivers returning incorrect results

UBR47K · 2016-06-01, 07:10

Has anyone experienced getting wrong residues with Nvidia 364.xx with CUDALucas?
I recently went investigating for the reason why my Titan Z decided suddenly crapping wrong results out and the timeframe coincides with a driver upgrade (I am using Linux here).

Googling around, I found this thread https://www.primegrid.com/forum_thread.php?id=6769 which describes issues not too different from what I am experiencing right now.
https://forums.geforce.com/default/t...71356/#4871356 shows that Nvidia acknowledges some issues with compute with their driver.

I have no way to rollback drivers currently so I can't be 100% sure if my card could have crapped out.

If the driver turns out to be bad, could it mean that the "recent" CUDALucas and mfaktc results be wrong? The driver is already out for a few months now.

EDIT:
One important note: The results I get some of them were correct but quite a sizable portion were mismatchings which turned out to be wrong.

mognuts · 2016-06-11, 16:58

BOINC/PrimeGrid is reporting this:

PrimeGrid: Please upgrade your Nvidia drivers!
Recently, Nvidia released driver 368.22 which fixes the serious error introduced with their 364.xx driver. Please upgrade to 368.22 or later, unless you are running Windows XP or Windows Vista.

If you are running the 364.xx or 365.xx drivers, it is imperative that you upgrade to 368.22 or later. The 364.xx and 365.xx drivers can produce incorrect calculation results.

However, if you are running Windows XP or Windows Vista, these versions of Windows are no longer supported by Nvidia's drivers as of 368.22. If you're running XP or Vista, you must revert to an earlier version of the driver (363.xx or earlier).

bgbeuning · 2016-06-11, 22:38

When I was running CUDAlucas and got Linux updates to nvidia,
I had to recompile CUDALucas or I would get all 0 residues.

2016-06-01, 07:10	#1
UBR47K Aug 2015 2²·17 Posts	Nvidia 364.xx drivers returning incorrect results Has anyone experienced getting wrong residues with Nvidia 364.xx with CUDALucas? I recently went investigating for the reason why my Titan Z decided suddenly crapping wrong results out and the timeframe coincides with a driver upgrade (I am using Linux here). Googling around, I found this thread https://www.primegrid.com/forum_thread.php?id=6769 which describes issues not too different from what I am experiencing right now. https://forums.geforce.com/default/t...71356/#4871356 shows that Nvidia acknowledges some issues with compute with their driver. I have no way to rollback drivers currently so I can't be 100% sure if my card could have crapped out. If the driver turns out to be bad, could it mean that the "recent" CUDALucas and mfaktc results be wrong? The driver is already out for a few months now. EDIT: One important note: The results I get some of them were correct but quite a sizable portion were mismatchings which turned out to be wrong. Last fiddled with by UBR47K on 2016-06-01 at 07:12

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Nvidia unlocking Titan X (P) through drivers	Karl M Johnson	GPU Computing	3	2017-08-11 08:40
NVIDIA Quadro K4000 speed results benchmark	sixblueboxes	GPU Computing	3	2014-07-17 00:25
Latest Nvidia drivers 331.40 & Titans	nucleon	GPU Computing	11	2013-10-28 21:28
ecm_factor returning the same number as input	Capone	GMP-ECM	17	2007-06-17 09:19
PRP v2.3, incorrect results for k > 2^32	Angular	Math	6	2002-09-26 02:28

2016-06-11, 16:58	#2
mognuts Sep 2008 Bromley, England 62₈ Posts	BOINC/PrimeGrid is reporting this: PrimeGrid: Please upgrade your Nvidia drivers! Recently, Nvidia released driver 368.22 which fixes the serious error introduced with their 364.xx driver. Please upgrade to 368.22 or later, unless you are running Windows XP or Windows Vista. If you are running the 364.xx or 365.xx drivers, it is imperative that you upgrade to 368.22 or later. The 364.xx and 365.xx drivers can produce incorrect calculation results. However, if you are running Windows XP or Windows Vista, these versions of Windows are no longer supported by Nvidia's drivers as of 368.22. If you're running XP or Vista, you must revert to an earlier version of the driver (363.xx or earlier).

2016-06-11, 22:38	#3
bgbeuning Dec 2014 3·5·17 Posts	When I was running CUDAlucas and got Linux updates to nvidia, I had to recompile CUDALucas or I would get all 0 residues.