PrimeGrid
Please visit donation page to help the project cover running costs for this month

Toggle Menu

Join PrimeGrid

Returning Participants

Community

Leader Boards

Results

Other

drummers-lowrise
1) Message boards : News : Please upgrade your Nvidia drivers! (Message 96678)
Posted 1571 days ago by Jacob Klein
Hopefully none, at least for this project. To my knowledge, this project's servers won't give you NVIDIA tasks if it detects your driver would produce erroneous results.
2) Message boards : News : Please upgrade your Nvidia drivers! (Message 95783)
Posted 1594 days ago by Jacob Klein
Just want to point out that ... NVIDIA is still supporting new drivers like 368.xx, on XP, on some GPUs. You can confirm this by finding 368.xx drivers on NVIDIA's Advanced driver search, for a GPU like a GTX 780. Essentially, NVIDIA has chosen to drop Vista support for drivers going forward, but still keep minimal XP support. I still recommend Windows 10.

Regards,
Jacob
3) Message boards : News : Trouble with Nvidia's 364.xx driver (Message 95291)
Posted 1614 days ago by Jacob Klein
What I've seen so far indicates that 368.22 fixes the problems if it will install properly - but the installation fails on some hardware/Windows combinations in a way that makes the computer unbootable.

It installed properly on my Windows 10 computer and is running without errors.

However, on my Windows Vista computer (Intel Q9650 CPU, GTX 560, 8 GB memory, 64-bit Windows Vista SP1), the screen went black perhaps halfway through the installation, and stayed that way until I turned off the computer about an hour later. Attempting to reinstall 362.00 ended with messages that newer versions of some parts were already present, and were not changed. The computer has gone downhill over another 6 hours and now will not boot, either normally or in safe mode. While I was still able to run the hardware diagnostics, they reported no errors.

I've already reported this to Nvidia, but can any of you suggest what to do to make that computer run properly again?


See my reply here:
http://boinc.fzk.de/poem/forum_thread.php?id=1205&postid=11079

368.22 does not support Vista. 365.19 is the latest Vista driver.
4) Message boards : Generalized Fermat Prime Search : Invalid GFN WUs when validating ATI against OCLcuda (Message 95282)
Posted 1614 days ago by Jacob Klein
You're welcome. Nice community you have here! It was pleasant working with you.
5) Message boards : Generalized Fermat Prime Search : Invalid GFN WUs when validating ATI against OCLcuda (Message 95276)
Posted 1614 days ago by Jacob Klein
I have passed my successful testing results, to NVIDIA. I'm considering the case closed. Woot!
I'm personally happy, because 368.22 also fixes an issue that could result in TDRs while an OpenCL/CUDA app was running.
So ... FINALLY, I can upgrade from 362.00 to 368.22 :)
6) Message boards : Generalized Fermat Prime Search : Invalid GFN WUs when validating ATI against OCLcuda (Message 95257)
Posted 1615 days ago by Jacob Klein
I have concluded my testing of the OpenCL/CUDA test cases.
Essentially, the 368.22 driver appears to SOLVE the OpenCL/CUDA miscalculation issue entirely.

My results are below.

I will do a little more spot checking later in the week, but I'm considering this issue resolved unless something comes up.

PS: I had some "maxErr exceeded" errors crop up during the 368.22 "43322502^131072+1" runs on both of my overclocked GPUs. But when I removed the overclocks, they calculated correctly. So, I think "43322502^131072+1" is somehow a great stress test for testing the overclock of a nearly-stable GPU. :)

Thanks!
Jacob Klein

============================================================================================================================== GTX 980 Ti - OpenCL Genefer testing ============================================================================================================================== q param: 362.00: 365.10: 368.22: Status: 3646782^131072+1 4bd691363f68a759 4bd691363f68a759 4bd691363f68a759 Never broken 3674128^131072+1 5e477f1623e46ba5 5e477f1623e46ba5 5e477f1623e46ba5 Never broken 3681296^131072+1 8655e9221606630b 8655e9221606630b 8655e9221606630b Never broken 3717024^131072+1 fba4548ad43ae8f5 fba4548ad43ae8f5 fba4548ad43ae8f5 Never broken 3793078^131072+1 3ce3a924ec8052ae 3ce3a924ec8052ae 3ce3a924ec8052ae Never broken 3880700^131072+1 e318cf569684adcf e318cf569684adcf e318cf569684adcf Never broken 43322502^32+1 379f0838325714eb 379f0838325714eb 379f0838325714eb Never broken 43322502^64+1 2229de4c20fa0706 2229de4c20fa0706 2229de4c20fa0706 Never broken 43322502^128+1 36df517cdbf6996b 36df517cdbf6996b 36df517cdbf6996b Never broken 43322502^256+1 5f1094b349ac012d 5f1094b349ac012d 5f1094b349ac012d Never broken 43322502^512+1 45c8e1581af84576 45c8e1581af84576 45c8e1581af84576 Never broken 43322502^1024+1 9e0d0b96b2e6a32a 9e0d0b96b2e6a32a 9e0d0b96b2e6a32a Never broken 43322502^2048+1 7985cfe2366bd551 7985cfe2366bd551 7985cfe2366bd551 Never broken 43322502^4096+1 ad89f4525c85170d ad89f4525c85170d ad89f4525c85170d Never broken 43322502^8192+1 b6013fa4fd5f6d78 (maxErr exceeded) b6013fa4fd5f6d78 ***WAS BROKEN; NOW FIXED*** 43322502^16384+1 76f5aa9fff987d29 270979b48088bb4b 76f5aa9fff987d29 ***WAS BROKEN; NOW FIXED*** 43322502^32768+1 7b5269df77fda9bf 88a68b762462bf8f 7b5269df77fda9bf ***WAS BROKEN; NOW FIXED*** 43322502^65536+1 db4779368e7538c9 (MULTIPLE DIFFERING) db4779368e7538c9 ***WAS BROKEN; NOW FIXED*** 43322502^131072+1 71e42cc1499c83c1 (MULTIPLE DIFFERING) 71e42cc1499c83c1 ***WAS BROKEN; NOW FIXED*** 43370168^131072+1 d3e2790fc7d1cee3 0644bd7a3f6a551b d3e2790fc7d1cee3 ***WAS BROKEN; NOW FIXED*** ============================================================================================================================== GTX 980 Ti - CUDA GFNS testing ============================================================================================================================== params: 362.00: 365.10: 368.22: Status: 21 1000 1001 Baseline Matches 362.00 Matches 362.00 Never broken 21 10000 10001 Baseline Matches 362.00 Matches 362.00 Never broken 21 59712 59713 Baseline (RADICALLY DIFFERENT) Matches 362.00 ***WAS BROKEN; NOW FIXED***
7) Message boards : Generalized Fermat Prime Search : Invalid GFN WUs when validating ATI against OCLcuda (Message 95256)
Posted 1615 days ago by Jacob Klein
Final results within the next 2 hours ... so far so good!
8) Message boards : Generalized Fermat Prime Search : Invalid GFN WUs when validating ATI against OCLcuda (Message 95241)
Posted 1615 days ago by Jacob Klein
My preliminary testing results are looking VERY good.
I think this 368.22 driver is the one we've been waiting for!!

I will do more testing later this evening.
9) Message boards : Generalized Fermat Prime Search : Invalid GFN WUs when validating ATI against OCLcuda (Message 95028)
Posted 1625 days ago by Jacob Klein
I have confirmed that the new Doom 365.19 drivers:
- Do NOT fix the OpenCL/CUDA miscalculations (Internal NVIDIA Bug ID: 200197534)
- DO fix the Poem@Home TDR/crashes (NVIDIA Bug ID: 1754468)

So... If you do any distributed computing involving OpenCL/CUDA calculating, I recommend that you **stick with 362.00** for correct calculations, until the next driver release which should have the miscalculation fix.

Thanks,
Jacob
10) Message boards : Generalized Fermat Prime Search : Invalid GFN WUs when validating ATI against OCLcuda (Message 94995)
Posted 1627 days ago by Jacob Klein
3 more updates:

1) The PrimeGrid CUDA GFNS miscalc... has also been fixed in their dev environment. They didn't state whether it was the same bug as the OpenCL Genefer miscalc, but I suspect it was related at the very least.
2) The PrimeGrid fixes (Internal NVIDIA Bug ID: 200197534) ... DID NOT make the cutoff for the upcoming "Doom" R364 driver, which is due any day. They apologize, but timing didn't mesh. They say that it will for sure land on the next driver release, which (good news) is expected to be released later this month.
3) The POEM@Home TDR/crashing fix (NVIDIA Bug ID: 1754468)... DID make the cutoff for the "Doom" R364 driver, so we'll see that fix shortly.

I also passed on the following message to them, in my email reply.

Thanks,
Jacob

Kevin,

Thank you very much for the detailed info. I especially want to pass on a HUGE thank you, to you and your entire team, from the PrimeGrid community, who are quite pleased with your response on this issue, even if we have to wait a bit more for the "next-next" driver release (which is perfectly fine).

Thanks!
Jacob


Next 10 posts
[Return to PrimeGrid main page]
DNS Powered by DNSEXIT.COM
Copyright © 2005 - 2020 Rytis Slatkevičius (contact) and PrimeGrid community. Server load 0.79, 0.67, 0.78
Generated 25 Oct 2020 | 8:55:34 UTC