Win 10 pushed 388.13 driver

Driver issues associated with the Windows 10 roll-out

Moderators: Site Moderators, PandeGroup

Win 10 pushed 388.13 driver

Postby JonasTheMovie » Sat Jan 20, 2018 3:01 pm

Noticed that my rig had not delivered any points the last 18 hours, opened the VNC, lo and behold, fah_21 had crashed and a reboot splash was covering the screen.
After the reboot the rest of the WU shows a quarter of the normal ppd, but I guess that has to do with the slow return time due to the crash.

But, whats up with Win 10 pushing a driver update even thou I have turned all auto updates off? Why even push a Nvidia update?
Anyone know anything if 388.13 is worth to keep or should I revert back to an older?
Image
JonasTheMovie
 
Posts: 88
Joined: Wed Jan 06, 2016 4:16 am
Location: Northern Sweden

Re: Win 10 pushed 388.13 driver

Postby JimboPalmer » Sat Jan 20, 2018 5:27 pm

Nvidia has 390.65 out, I would always use the Nvidia version. (or AMD for an AMD card)

https://www.geforce.com/drivers/results/129081
Tsar of all the Rushers
I tried to remain childlike, all I achieved was childish.
A friend to those who want no friends
JimboPalmer
 
Posts: 956
Joined: Mon Feb 16, 2009 4:12 am
Location: Greenwood MS USA

Re: Win 10 pushed 388.13 driver

Postby bruce » Sat Jan 20, 2018 8:26 pm

When you run WIn10, you really can't revert to an older driver. They seem to push NV drivers soon after NV releases them. In many cases, they have REMOVED the OpenCL drivers, which crashes FAHCore_21.

I have conflicting information about whether they're now updating the OpenCL drivers at the same time or not. Personally, I'd appreciate reports about whether they did or not.

I try to update my drivers from NV before Win10 pushes the new ones so that OpenCL gets updated, while Core_21 isn't running.
bruce
 
Posts: 22853
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Win 10 pushed 388.13 driver

Postby JimboPalmer » Thu Jan 25, 2018 4:28 am

I would 'finish' the current work Unit then; I would uninstall every nvidia 'feature' but the driver, then do a clean install of just the driver, if it was me.
JimboPalmer
 
Posts: 956
Joined: Mon Feb 16, 2009 4:12 am
Location: Greenwood MS USA

Re: Win 10 pushed 388.13 driver

Postby foldy » Thu Jan 25, 2018 10:33 am

@TAMUmpower: The first problem with crashed work unit is because you need to pause folding before nvidia driver update and resume folding after.

The second problem with lower PPD I guess is because you got a new work unit and there are big work units with higher PPD and small work units with lower PPD.

Did you try to reboot your PC? Is the GPU clock at ~1900 Mhz again?
foldy
 
Posts: 1531
Joined: Sat Dec 01, 2012 3:43 pm

Re: Win 10 pushed 388.13 driver

Postby TAMUmpower » Thu Jan 25, 2018 2:59 pm

Ah thanks. Yea I've been pausing it now and it saves the WO. I've rebooted a ton of times trying different drivers and settings. The clock has remained the same its just the utilization that seems low. It's just odd because I saw it able to pull 92-96% on the GPU already so I know there isnt a hardware issue. Realistically it should be able to just sit at 100% like all the other systems I've folded on.
TAMUmpower
 
Posts: 12
Joined: Mon Jan 08, 2018 9:02 pm

Re: Win 10 pushed 388.13 driver

Postby foldy » Thu Jan 25, 2018 3:30 pm

It is still a bug in FAH or Windows 10 that is push installs a GPU driver while GPU application is running. Maybe Windows 10 only has a check for DirectX games and not for OpenCL apps. Or FAH needs to set a magic Windows flag to signal GPU is used.
foldy
 
Posts: 1531
Joined: Sat Dec 01, 2012 3:43 pm

Re: Win 10 pushed 388.13 driver

Postby bruce » Thu Jan 25, 2018 7:15 pm

I have WindowsUpdate configured to ask me what I want to install. (On Win10-home, that doesn't prevent them from forcing the driver update, but it does delay it). I saw the planned update to 388.13 but I was already on a later version from NV. WindowsUpdate still wanted to install 388.13 :( :!: Anyway, it took several manual changes including pausing/resuming the active WU, but it's happy now.
JimboPalmer wrote:I would 'finish' the current work Unit then; I would uninstall every nvidia 'feature' but the driver, then do a clean install of just the driver, if it was me.
That's what I do, too, unless my sound is using the speakers on the monitor.
bruce
 
Posts: 22853
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Win 10 pushed 388.13 driver

Postby JonasTheMovie » Thu Jan 25, 2018 9:37 pm

So far the 388.13 has proved to be more productive than the earlier "best" driver I used. PPM has been increased 7-9% .
JonasTheMovie
 
Posts: 88
Joined: Wed Jan 06, 2016 4:16 am
Location: Northern Sweden

Re: Win 10 pushed 388.13 driver

Postby bruce » Thu Jan 25, 2018 9:40 pm

A project=to-project variation of +-10% is not uncommon. Unless you're seeing +7-9% ON THE SAME PROJECT, you really don't know what you think you know.
bruce
 
Posts: 22853
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Win 10 pushed 388.13 driver

Postby JonasTheMovie » Tue Jan 30, 2018 6:13 pm

So, after months of steady levels of project returns the available projects just happened to changed at the same time as the drivers updated...
Looking at multiple GPU users an increase of ppd can been seen a couple of days before my win10 pushed the update to my computer.
Since the stat server was down just those days it´s hard to tell anything more from the overall user stats.

Never the less, ppd´s have increased at the same time as my driver updated, not at the same time as it increased for other people.
JonasTheMovie
 
Posts: 88
Joined: Wed Jan 06, 2016 4:16 am
Location: Northern Sweden

Re: Win 10 pushed 388.13 driver

Postby JimboPalmer » Tue Jan 30, 2018 9:21 pm

It does happen, when I first got my GTX 1050ti last April, I was getting about 150,000. Now I average 170,000. so new has been faster for me.
JimboPalmer
 
Posts: 956
Joined: Mon Feb 16, 2009 4:12 am
Location: Greenwood MS USA


Return to Windows 10 + NVidia

Who is online

Users browsing this forum: No registered users and 1 guest

cron