Ian&Steve C - hey I did not know there were two different NVIDIA driver types or how to view the driver version when I started.

I am up and running with your and NVIDIA support help. It is a new area for me but I am used to forging ahead.

Many thanks for the help! I explained some of my background in a message.

Mike

Is the Driver problem still a thing? Because I recently installed Windows 10 on my Machine and installed the latest nvidia driver 441.66.

[snip]

For the Game ready driver, no version more recent than 431.60 works well with VHAR workunits yet. I've seen nothing I remember on Studio Driver versions, but I suspect that the same version restriction applies. Some workunits aren't VHAR - newer driver versions work with those. For example, those with .vlar in the name aren't VHAR.

There is no difference in "Game Ready" drivers and "Studio" drivers. They are the same. The only difference is the update frequency. The "Game Ready" drivers update at every new release of every game title. The "Studio" drivers are the "stable-long term release" drivers which only get updates every quarter or half year.

---

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

A proud member of the OFA (Old Farts Association)

Actually I believe the Studio Drivers are a recent innovation/branching optimized for special applications such as Blender, Maya, Premier Pro, DaVinci Resolve, etc.. These are the tool sets of professional media production studios. For years Nvidia has touted the Quadro cards as the graphics engine of choice for these applications citing accuracy over speed but users called BS and saved thousands by using the GeForce cards instead. I worked briefly for the first OEM to break ranks and ship GeForce cards with their high end Hollywood effects machines instead of the Quadro. If you are doing SCIENCE and ENGINEERING yes, the Quadro accuracy is critical, but for images and video GeForce is fine.

---

For this version, they are identical but Studio Driver won't be updated as often and might be on different branch.

Studio Driver will be updated based on professional application updates and Game Ready driver will be updated based on game releases.

As I stated, they have different target audiences. The Studio drivers are targeted at professionals and professional applications that demand stability. They only need to be updated for major new releases of professional compositing and editing applications. There is no game of the week update or hot fixes with the Studio drivers. You get a new point release and hotfix every week with the Game Ready drivers.

---

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

A proud member of the OFA (Old Farts Association)

New realization:
- Installed Windows 10 (fresh install).
- It installed a Windows nvidia driver.
- I installed the nvidia 441.66.
- Found out, that the problem with the SoG WUs is still alive and I wanted to go back to 431.xx
- Deinstalled the 441.66 and deactivated the automatic driver update in Windows
- Downloaded the 431.60 driver and began installing it
- I can not install it because I need a DCH driver. Since Win10 1803 it is necessary installing a DCH driver except you're still on an old version and haven't updated the driver: you're able to use the old one
- Wanted to install the nvidia control panel - can not install it - will be forced to download it from the Microsoft store because this one is DCH compatible (sure to download it I have to be registered...)

Can anyone confirm that?

So now I'm back on 441.66 and waiting for a fix.

EDIT:
Found a 431.60 DCH driver. Will test it later.

---

Back to 431.60 and it seems that my SoG WUs are crunching fine again.

---

If you disconnect the internet, use DDU, and restart ... then you can easily install a driver that is either a Standard one or a DCH one, then reconnect the internet.
Works every time.

If you disconnect the internet, use DDU, and restart ... then you can easily install a driver that is either a Standard one or a DCH one, then reconnect the internet.
Works every time.

Thanks for the tip! Will try it next time ;)
But hopefully nvidia will provide a solution for the problem.

---

But hopefully nvidia will provide a solution for the problem.

I wouldn't hold my breath waiting as it's been 3 months now and they've never fixed the pre-Fermi Win10 driver. ;-)

Cheers.

Pre-Fermi driver support stopped, and even Fermi support stopped, with a public announcement, I thought.

Our issue here is still under support, and devs are looking at it.

It's up to you whether you want to hold your breath. I try to be patient in different ways. :)

[quote]Just saw this happening. I have rebooted to see if GPUs where stuck... Nope.

Have a Geforce GTX 1060 6GB and GeForce GTX 1070 Ti using MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe application. The progress Rate is .720 % /hour.

GeForce Drivers: 436.30 ( updated about a month ago )

WorkUnits being processed: 21jn12ac.5582.19699.15.42.209 and 21jn12ac.24517.23380.3.30.153

I will wait until WU's are complete to see if its going to clear it self....

Any ideas on what may be happening.

Thanks in advance...
BoincSpy

I think I'm having the same problem suddenly. Used to work great but last couple of weeks shows .603%/hr and wu time out before finishing. Actually it never shows any progress after starting wu.

AuthenticAMD
AMD FX(tm)-8350 Eight-Core Processor [Family 21 Model 2 Stepping 0]
(8 processors) NVIDIA GeForce GTX 1050 Ti (4095MB) driver: 441.66 OpenCL: 1.2 Microsoft Windows 10
Professional x64 Edition, (10.00.18363.00)

Yes. You need to revert to the 431.60 drivers.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

On December 9, Microsoft's Windows 10 decided on its own to update my video driver for my NVIDIA GeForce GTX 1070 to version 432.00.
Since that date, every Astropulse I have processed that runs more than a few seconds has been marked as invalid!
That computer (6156281) has previously had a nearly zero invalid Astropulse count its entire life.
I am going to try reinstalling the latest archived NVIDIA driver I have, version 416.34.
Has anyone else experienced this problem?

Also, Windows 10 has never messed with my video drivers before. I sure would like to prevent Microsoft from doing this again.
Does anyone know a way to prevent Windows 10 from arbitrarily updating video drivers via their "Driver Updates" section of "Windows Update"?

Thank you for any help you can provide on this.

Windows 10 Driver Updates can be prevented by:
- Visit here: https://support.microsoft.com/en-us/help/3073930/how-to-temporarily-prevent-a-driver-update-from-reinstalling-in-window
- Scroll to "Choose your automatic updates"
- Download the troubleshooter
- While the new driver is not yet installed (or has been uninstalled)
- Run the troubleshooter
- Use the troubleshooter to tell Windows 10 Windows Update to ignore the particular Windows 10 driver

I recommend storing a copy of that troubleshooter locally, in case Microsoft decides to take the webpage down at some point.

A good Guide(s) to not let MS install drivers

https://www.tenforums.com/tutorials/48277-enable-disable-driver-updates-windows-update-windows-10-a.html
EDIT: A good place with plenty of tips and trix
//Lazy

Hi All,

Because of the anonymous platform issues that occurred last week. I switched to the stock GPU program that seti provided ( setiathome_8.22_windows_intelx86__opencl_nvidia_SoG) and I am having the same issue with the Workunits exceeding there time allocations. I did not expect this, so wondering are these GPU programs supported and if they are would it be possible for SETI as a organization to put some pressure on NVIDIA on getting this fixed?

---

It’s the same app that’s in the lunatics package so yes it has the same issue.

Although it looks like the project is sending out the sah app now. So if you return enough bad SoG tasks the project might decide that sah is best and start sending you those instead.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

Thanks all, noticed that myself.
Reverting to v431.60

---

non-profit org. Play4Life in Zagreb, Croatia, EU

NVIDIA released 441.87 drivers today.
I tested them, and they still have the "SETI OpenCL SoG VHAR on Windows 10" problems:

Maxwell:
> Tasks crash with error.
>ERROR: OpenCL kernel/call 'clEnqueueMapBuffer(gpu_GPUState)' call failed (-36) in file ..\analyzeFuncs.cpp near line 1995.

Pascal/Turing:
> Tasks run indefinitely with no load on the GPU.

431.60 are the last drivers that work correctly for those specific SETI tasks on Windows 10.
NVIDIA is aware, and per NVIDIA, we must continue to be patient for a driver version that includes a fix.