Been using it for a couple days now with no know issues.

---

Been using it for a couple days now with no know issues.

Just built my new rig with Windows 10 and have that driver, also no issues.

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

I've had two batches of 100 GPU work units garbage out with zero run time since updating a few days ago. But also coincides with the latest Win10 cumulative update (KB4093105). I'm going back to the prior driver after my entire queue clears (will be a couple of days for CPU / iGPU tasks) and see what happens. I'm beginning to think my trusty old 1060 (well, not that old) might be having issues. Though it seems to work fine for everything but SETI crunching.

---

But also coincides with the latest Win10 cumulative update (KB4093105).

Never allow M$ update your Nvidia driver.
DL the latest driver directly only from the NVidia site and install with the clean option.
That solves the problem.

---

If it's not broken...Don't fix it..

or in this case, if the driver runs the apps, don't update them... Most updates are only released to support new games, not scientific computations...

---

I had no choice in the matter. The 2 versions I have on my data drive are for Win7. I had to download the Win10 version. I gotta remember, when downloading stuff, that I have Win10 now and not Win7. ;-o

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

I had no choice in the matter.

Don't worry, Just do what i post and that will fix your problem.

---

I had no choice in the matter.

Don't worry, Just do what i post and that will fix your problem.

Obviously, you did NOT read my complete post or you would see that I have NO problem.

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Obviously, you did NOT read my complete post or you would see that I have NO problem

Sorry, i was talking about Mike Ryan problem and quote your msg by mistake.
The well know M$ Nvidia update crash.

---

I'm still using 372.54 for my 1060's and 365.19 for my 550 Ti's.

I'm definitely one of those who will only upgrade my drivers only when it's absolutely necessary.

Cheers.

I'm still using 372.54 for my 1060's and 365.19 for my 550 Ti's.

I'm definitely one of those who will only upgrade my drivers only when it's absolutely necessary.

Cheers.

That time is approaching for the 550Ti's since both Microsoft and Nvidia are dropping support for Fermi class cards and 32bit drivers. Of course you don't need any new drivers. The current ones work. Just make sure you keep a copy of the Nvidia driver around since it will disappear from the Nvidia site. Only thing you have to worry about are the cards dying. But then you will buy something newer.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Not sure what class my card is but think I saw it as fermi somewhere but have saved last few Nvidia driver updates for a rainy day..

Obviously, you did NOT read my complete post or you would see that I have NO problem

Sorry, i was talking about Mike Ryan problem and quote your msg by mistake.
The well know M$ Nvidia update crash.

Ah, ok. My apologies. :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

If it's not broken...Don't fix it..

or in this case, if the driver runs the apps, don't update them... Most updates are only released to support new games, not scientific computations...

Abolutely correct. I'm still at 352.86, and I have no reason whatsoever to upgrade a fully working driver. The newer ones will not be faster for crunching.
on the contrary perhaps, since they have to support newer hardware too.

I never play games on my computer, so I'll stick with what I know works perfectly.

The latest will be faster for any new hardware generation after the SW was compiled. The software is built to run on existing HW and it is added an option to run on any future HW. So If your GPU is like the latest hot one then you may have a good luck that the latest driver and just in time compilation feature can give you a boost.

The other scenarios you can think ... You can always try.

..
Petri33

---

To overcome Heisenbergs:
"You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones

The other scenarios you can think ... You can always try.

..
Petri33

The last hot hardware was your Titan V

latest driver and just in time compilation feature can give you a boost.

Petri, are you referring to how the current Nvidia drivers work? Or to your latest special app with the embedded CUDA 9.1?

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I've had two batches of 100 GPU work units garbage out with zero run time since updating a few days ago. But also coincides with the latest Win10 cumulative update (KB4093105). I'm going back to the prior driver after my entire queue clears (will be a couple of days for CPU / iGPU tasks) and see what happens. I'm beginning to think my trusty old 1060 (well, not that old) might be having issues. Though it seems to work fine for everything but SETI crunching.

After letting my queue run dry of all tasks and rolling back to the prior driver (391.35) I started a new batch last night (well, early this a.m.) and have successfully processed over 100 GPU tasks without them erroring out. So it looks like pretty strong evidence that the 397.31 driver could have been the issue. (Though, if that is the case I'd expect nearly everyone using that driver on similar hardware to have problems.) For now we'll carry on and see how it goes.

---

I had problems too, rolled back a version of the NVidia driver (391.35) and smooth sailing since.

After letting my queue run dry of all tasks and rolling back to the prior driver (391.35) I started a new batch last night (well, early this a.m.) and have successfully processed over 100 GPU tasks without them erroring out. So it looks like pretty strong evidence that the 397.31 driver could have been the issue. (Though, if that is the case I'd expect nearly everyone using that driver on similar hardware to have problems.) For now we'll carry on and see how it goes.

Mike, I thought that I had PM'd you to ask if you'd found a solution but I may well have screwed up and not sent the message. I think that I've had the same issue as you on two occasions with compute errors with zero run time since installing driver ver. 397.31. I use Windows 7, x64 and I was totally happy about driver version 397.31 as it reportedly fixed a Windows 7 error that resulted in a blank screen from which the computer could not recover when Firefox was running in the background. The new version fixed the blank screen issue but seems to have created this new issue with Seti@Home. I've reverted back to driver version 385.41 of the Nvidia driver as it was the last released driver that did not cause the screen blanking issue. Running ver. 385.41 has since resulted in over 140 tasks successfully processed with no resulting errors.

---

Hi Dave -- I'd sent a reply, but from my old Yahoo email account so you might have to look in a spam filter or similar.

At any rate, I've now processed 255 GPU work units in the past 24 hours without erroring out since rolling back one step to driver #391.35. So my confidence that the issue is with the 397.31 driver grows every hour. The odd thing about this is that once a work unit failed, it seems something on the card "latched" into whatever state causing all other GPU tasks in the queue to also fail. (Only happened twice, so it's hard to say for certain, but that's what it seemed like.) I still find it odd that if the driver is the issue -- it seems like there would be 100's of users with the same/similar hardware having the same issues. Time will tell I guess.

---