Message boards : News : Please upgrade to DRIVER 334.21 or NEWER [closed]
Author | Message |
---|---|
Hi all, | |
ID: 36505 | Rating: 0 | rate:
![]() ![]() ![]() | |
I have recently upgraded to 332.21. I am a little bit conservative on this issue as everything runs just fin on my computers at the moment. | |
ID: 36508 | Rating: 0 | rate:
![]() ![]() ![]() | |
Or can anybody recomened an other driver version? I have run a GTX 660 and GTX 650 Ti under WinXP using the 335.28 drivers, and they have worked fine for me on the longs. More recently I have used a GTX 750 Ti with the same drivers, and it has worked fine on the shorts. I would not hesitate to upgrade, but I recommend a clean install, especially if you have multiple cards on the same motherboard (i.e., use Driver Cleaner or Driver Fusion). | |
ID: 36509 | Rating: 0 | rate:
![]() ![]() ![]() | |
:) I have 3 generations of GPUs in the same PC. When I update drivers, I do this: | |
ID: 36510 | Rating: 0 | rate:
![]() ![]() ![]() | |
I have the 332.21 driver on my WinXPx64 / GTX 780 Ti host, and it says it has CUDA 6. | |
ID: 36515 | Rating: 0 | rate:
![]() ![]() ![]() | |
I have the 332.21 driver on my WinXPx64 / GTX 780 Ti host, and it says it has CUDA 6. This is even a better solution. I would rather stay with 332.21 driver as well. | |
ID: 36521 | Rating: 0 | rate:
![]() ![]() ![]() | |
Not quite sure what it is you are asking here. If you have driver 332.21 you shouldn't be getting the cuda60 app. | |
ID: 36523 | Rating: 0 | rate:
![]() ![]() ![]() | |
334.21 is the minimum driver version that we are sending cuda60s to. This is the driver revision that accompanied the first pre-prelease version of the CUDA 6 toolkit that worked for us. | |
ID: 36538 | Rating: 0 | rate:
![]() ![]() ![]() | |
I have read that the latest 3 drives are hampering the GTX780Ti and that card is already not super with Win7 due to WDDM. So I would like to stick with the 331.82 drivers for a while. However now I am not getting new work anymore from GPUGRID and a message in BOINC says that I need to upgrade the drivers. Don't worry if you can't: the older applications aren't going away. From now on, though, they will get only maintenance updates. But seeing this: 4/22/2014 5:08:33 PM | GPUGRID | Message from server: NVIDIA GPU: Upgrade to the latest driver to process tasks using your computer's GPU 4/22/2014 5:08:33 PM | GPUGRID | No tasks sent 4/22/2014 5:08:33 PM | GPUGRID | No tasks are available for ACEMD beta version 4/22/2014 5:08:33 PM | GPUGRID | No tasks are available for Long runs (8-12 hours on fastest card) 4/22/2014 5:08:33 PM | GPUGRID | No tasks are available for CPU only app 4/22/2014 5:10:21 PM | GPUGRID | update requested by user 4/22/2014 5:10:24 PM | GPUGRID | Sending scheduler request: Requested by user. 4/22/2014 5:10:24 PM | GPUGRID | Requesting new tasks for NVIDIA and intel_gpu 4/22/2014 5:10:25 PM | GPUGRID | Scheduler request completed: got 0 new tasks 4/22/2014 5:10:25 PM | GPUGRID | Message from server: NVIDIA GPU: Upgrade to the latest driver to process tasks using your computer's GPU 4/22/2014 5:10:25 PM | GPUGRID | No tasks sent 4/22/2014 5:10:25 PM | GPUGRID | No tasks are available for ACEMD beta version 4/22/2014 5:10:25 PM | GPUGRID | No tasks are available for Long runs (8-12 hours on fastest card) 4/22/2014 5:10:25 PM | GPUGRID | No tasks are available for CPU only app it seems that I am forced to upgrade the drivers, but then the mighty GTX780Ti will underperform in Win7. Please advice Matt. ____________ Greetings from TJ | |
ID: 36541 | Rating: 0 | rate:
![]() ![]() ![]() | |
TJ, | |
ID: 36542 | Rating: 0 | rate:
![]() ![]() ![]() | |
TJ, Thank you Matt! ____________ Greetings from TJ | |
ID: 36545 | Rating: 0 | rate:
![]() ![]() ![]() | |
334.21 is the minimum driver version that we are sending cuda60s to. This is the driver revision that accompanied the first pre-prelease version of the CUDA 6 toolkit that worked for us. 334.21 is for Linux and adds support for Maxwell's. However I have successfully returned CUDA6 work using 331.49 on Ubuntu 13.10 64-bit from a Kepler: 234x-SANTI_MAR423cap310-69-84-RND5084_0 6452642 20 Apr 2014 | 10:24:50 UTC 20 Apr 2014 | 12:58:06 UTC Completed and validated 9,100.43 1,596.87 18,300.00 Short runs (2-3 hours on fastest card) v8.21 (cuda60) Presumably that rig will stop getting CUDA6 work now, unless I manage to upgrade to the latest drivers, which I don't really need to do as I don't have a Maxwell (and I should still get CUDA42/55 work). ____________ FAQ's HOW TO: - Opt out of Beta Tests - Ask for Help | |
ID: 36546 | Rating: 0 | rate:
![]() ![]() ![]() | |
I got new work again app 8.40 cuda60 and I have driver 331.82. They error out almost immediately, this are some lines: | |
ID: 36547 | Rating: 0 | rate:
![]() ![]() ![]() | |
Looking into it... | |
ID: 36549 | Rating: 0 | rate:
![]() ![]() ![]() | |
Try cuda60 version 841 | |
ID: 36550 | Rating: 0 | rate:
![]() ![]() ![]() | |
app 8.21 errors out with 331.38 driver which is the default for the latest Ubuntu release 14.04 | |
ID: 36551 | Rating: 0 | rate:
![]() ![]() ![]() | |
How about using the ACEMD beta channel just for the cuda 60 long tasks. | |
ID: 36552 | Rating: 0 | rate:
![]() ![]() ![]() | |
Stoneageman - it's a scheduling issue, unfortunately. ItÅ› affecting all apps equally. | |
ID: 36553 | Rating: 0 | rate:
![]() ![]() ![]() | |
Try cuda60 version 841 It is still not working Matt. App and files are downloaded, then it says running, but nothing happened and then they error out. So it seems driver 331.82 can no longer be used? But you mentioned that cuda42 tasks would still be around. Why does my system not getting those as I have a lesser driver then the one needed for cuda60? Or am I missing something or miss-read? ____________ Greetings from TJ | |
ID: 36554 | Rating: 0 | rate:
![]() ![]() ![]() | |
Yeah - scheduling on the Cuda capability reported by the driver is insufficient - the 331s say they do, but they don't. We've reverted to giving cuda60s out only to 334+ | |
ID: 36555 | Rating: 0 | rate:
![]() ![]() ![]() | |
Yeah - scheduling on the Cuda capability reported by the driver is insufficient - the 331s say they do, but they don't. We've reverted to giving cuda60s out only to 334+ Thanks Matt. Highly appreciated especially as it is late evening.I have now two tasks running again at 90% GPU load at 1150MHz on the 780Ti. ____________ Greetings from TJ | |
ID: 36556 | Rating: 0 | rate:
![]() ![]() ![]() | |
Yeah - scheduling on the Cuda capability reported by the driver is insufficient - the 331s say they do, but they don't. We've reverted to giving cuda60s out only to 334+ Mmmm...it's not working so far with 331.38 driver on Linux | |
ID: 36557 | Rating: 0 | rate:
![]() ![]() ![]() | |
Hi Stoneageman, | |
ID: 36560 | Rating: 0 | rate:
![]() ![]() ![]() | |
PS Stoneage - hope you don't think I'm mucking you but just to get the #1 slot off you! :-) | |
ID: 36561 | Rating: 0 | rate:
![]() ![]() ![]() | |
Ha! On that host I've changed to the 337.12 beta driver (after some hassle) so cuda60 tasks are now running OK on that. Just don't have the time to do the rest of the farm just now. | |
ID: 36563 | Rating: 0 | rate:
![]() ![]() ![]() | |
Okay I have now updated to latest driver (337.50). The 780Ti goes to boast 1158MHz, without any program like AfterBurner running. Problem: temperature goes quickly to 83°C when crunching GPUGRID. I don't like those high values so I started AfterBurner, it is still working in boast speed but temperature is 76°C with 91% fan speed. What I now notice is that the GPU load is 66-67% and that is less then it has been with 331.82 driver. I have no Swan_Sync settings yet. | |
ID: 36617 | Rating: 0 | rate:
![]() ![]() ![]() | |
TJ, | |
ID: 36620 | Rating: 0 | rate:
![]() ![]() ![]() | |
Thank you Jeremy, that give me some relieve. | |
ID: 36623 | Rating: 0 | rate:
![]() ![]() ![]() | |
After some experimenting with the core clock I see that if I set it to 1060MHz with AfterBurner it stays at 1060 and GPU load is 66%. If I set he core clock to 875MHz, the GPU load increases to 71%. I have not seen this before but can imagine that it works like this. | |
ID: 36625 | Rating: 0 | rate:
![]() ![]() ![]() | |
Hello Jeremy, one more question if I may. | |
ID: 36640 | Rating: 0 | rate:
![]() ![]() ![]() | |
Try cuda60 version 841 Since this version has the SWAN_SYNC, I've upgraded my drivers, and this version is working fine. However I had a strange period of getting tasks which led to the decision of upgrading the drivers: My hosts had the 332.21 (and the 326.80) driver, and they received and completed CUDA 5.5 tasks normally (CPU time = RUN time). Then my hosts received a couple of CUDA 6.0 tasks which all have failed. Then my hosts received CUDA 4.2 tasks which all have completed successfully. Then I've upgraded my drivers to 337.50, and now my hosts are receiving and completing CUDA 6.0 tasks normally. After that, I've checked the nvcuda32.dll and the nvcuda64.dll in both drivers (332.21 and 337.50), and all four dll's state that they are "NVIDIA CUDA 6.0.1 drivers" (right click -> properties -> version tab -> Product name field), but they have different file sizes. So the CUDA 6 included in previous drivers than 334.21 is not working (to be polite). Yeah - scheduling on the Cuda capability reported by the driver is insufficient - the 331s say they do, but they don't. We've reverted to giving cuda60s out only to 334+ My experiences assure this. Why haven't they increased at least the last digit of the driver's version number? (You don't have to answer this) | |
ID: 36648 | Rating: 0 | rate:
![]() ![]() ![]() | |
TJ, | |
ID: 36662 | Rating: 0 | rate:
![]() ![]() ![]() | |
Thank you very match Jeremy. | |
ID: 36672 | Rating: 0 | rate:
![]() ![]() ![]() | |
Hello Jeremy, | |
ID: 36693 | Rating: 0 | rate:
![]() ![]() ![]() | |
TJ, So, I set for Max Boost, and it works wonderfully, even when the drivers would otherwise stupidly downclock due to supposed low utilization. Forcing Max Boost works wonders. So I will be going back to 331.82 today since I will not be able to watch the systems close. I think the new app 8.41 is now scheduling WU's correctly so I should be ok. Regards, Jeremy | |
ID: 36696 | Rating: 0 | rate:
![]() ![]() ![]() | |
Indeed Jeremy, with 331.82 drivers you will get app 8.41 and cuda42. I have not had any errors since I revered back to those drivers, but that is only about 30 hours. My 780Ti runs now at 888MHz with 72°C. I am happy with that. | |
ID: 36699 | Rating: 0 | rate:
![]() ![]() ![]() | |
Try cuda60 version 841 I've had a small problem twice with cuda60 v8.41: Task 9763720 Task 9784050 Both times, I noticed that the task had 'stalled' - had counted up an unusually large elapsed time, and was making no progress. No message on screen, no crash. I simply suspended the task for a few seconds, then resumed it, and it started from the last checkpoint without any fuss. Stderr has this error logged: <stderr_txt> (same both times) Note how far the temperature of GPU 1 has fallen - the tasks were probably stalled for several hours before I noticed. Also, that 'SWAN swan_assert 0' on restart is new - I don't have SWAN_SYNC set. | |
ID: 36793 | Rating: 0 | rate:
![]() ![]() ![]() | |
I would predominantly be worried about the message,
Apparent in both failures. | |
ID: 36812 | Rating: 0 | rate:
![]() ![]() ![]() | |
I would predominantly be worried about the message, I had another one yesterday: Task 10212213 Only seems to happen on Gerard's tasks, though this is a slightly different sub-type. Yes, I'm primarily concerned about the SWAN FATAL - that should trigger a boinc_temporary_exit, but doesn't. No, a 20 degree drop in temperature isn't the result of a drop in boost - it's a complete cessation of processing, for several hours. I caught yesterday's much sooner, and it only had time to cool down by 2 degrees. 337.50 is still in Beta - I'll leave that to the rest of you, thanks. | |
ID: 36814 | Rating: 0 | rate:
![]() ![]() ![]() | |
Only seems to happen on Gerard's tasks, though this is a slightly different sub-type. I had a BSOD a few days ago (very unusual), which I put down to performing a Windows update. Something similar happened on another PC, which I thought was connected to the most recent security update to Internet Explorer. However, on looking though BoincTasks, it seems that I was running Gerards on both of the GTX 660s at the time (WinXP, 335.28 driver). There is nothing in the Stderr output to indicate anything other than a shutdown to install the updates, but now I am beginning to wonder. http://www.gpugrid.net/result.php?resultid=9785157 http://www.gpugrid.net/result.php?resultid=9786033 | |
ID: 36817 | Rating: 0 | rate:
![]() ![]() ![]() | |
If the updates are automatic, that would do it! | |
ID: 36818 | Rating: 0 | rate:
![]() ![]() ![]() | |
If the updates are automatic, that would do it! That was on a dedicated PC, and I have automatic updates turned off (it is WinXP after all). I leave it running 24/7, and so don't have to worry if the work unit has some sort of restart problem. But it looks like some of the Gerards do, since the BSOD occurred apparently right after the reboot. I say "apparently", because I don't normally have a monitor connected to it, but manage it over the LAN. As I recall, it was only after a couple of hours that I noticed no progress, and no LAN connection, and then found the BSOD after connecting a monitor. It looks like bad luck, and probably won't happen again on that machine. | |
ID: 36819 | Rating: 0 | rate:
![]() ![]() ![]() | |
These things occasionally happen, for unknown reasons. You could run for several months without issue, get a blue screen, shut down, start up and not get another blue screen for months... It's good to post any concerns, just in case there is a bad batch, but it's best to wait and see if it was a one off before hitting the panic button and rebuilding your system. I also had a Gerard WU fail 6days ago on an otherwise good GPU and good system. | |
ID: 36821 | Rating: 0 | rate:
![]() ![]() ![]() | |
I upgraded my Nvidia drivers using xorg-edgers PPA to version 340.46 and now Boinc doesn't recognize my GPU. | |
ID: 38721 | Rating: 0 | rate:
![]() ![]() ![]() | |
Maybe it is something with the NVIDIA driver, can you try uninstalling the xorg-edgers driver and install the original NVIDIA driver? | |
ID: 38723 | Rating: 0 | rate:
![]() ![]() ![]() | |
I upgraded my Nvidia drivers using xorg-edgers PPA to version 340.46 and now Boinc doesn't recognize my GPU. This has been discussed elsewhere here. I believe this is a BOINC error that causes this issue and it would be best to uninstall all NVIDIA drivers and download the video driver from NVIDIA and re-install them manually (http://www.gpugrid.net/forum_thread.php?id=3736&nowrap=true#38456) | |
ID: 38725 | Rating: 0 | rate:
![]() ![]() ![]() | |
I am using driver 334.89. NVIDIA tells me this is the latest driver for my two GTX 650Ti GPUs. | |
ID: 38896 | Rating: 0 | rate:
![]() ![]() ![]() | |
John: 344.65 driver is available for you're OS with (650ti) Kelper cards. | |
ID: 38899 | Rating: 0 | rate:
![]() ![]() ![]() | |
many thanks: I will try to install that driver. John: 344.65 driver is available for you're OS with (650ti) Kelper cards. | |
ID: 38901 | Rating: 0 | rate:
![]() ![]() ![]() | |
Driver 347.09 installed and I am downloading CUDA 6.5 task. | |
ID: 39510 | Rating: 0 | rate:
![]() ![]() ![]() | |
Message boards : News : Please upgrade to DRIVER 334.21 or NEWER [closed]