GeForce Game Ready Driver 368.22 WHQL Download & Discussion

not related with DDU but 368.22 driver

 

Except I'm running the .22 driver and haven't had one stub error, nor has WL (I assume is also running .22)


--
I've disabled NVIDIA Backend from startup too

 

as always my nvidia backend is disable too. the error can't always reproduce so easily. everything happened randomly. i submitted a file report to nvidia. i tweeted manuel & pelly also no feedback from them.

6th june got new driver for x70 but not sure maxwell will get or not.

 

368.22 here, installed right on top of 365.19, custom+clean, as usual. NVBackend is active probably, see no reason why I would want to remove it.

My Windows 10 is rather fresh though, I've re-installed it afresh back in February, running 1511/.318.

 

maybe b'cos u still got some left over 365.19 files.

 

What's stopping you from checking it?

 

I have just installed the previous v365.19 driver over the top of the 'dodgy' v368.22 ones and immediately all the issues are fixed, specifically:

1. Task Scheduler opens without an error. With the v368.22 driver, the service seems to stop for some reason despite being set to Automatic. This causes a "cannnot connect to remote server" error when opening Task Scheduler. I got around this by manually starting the service.

2. The "stub has received bad data" error appears to have gone. Although this error was fairly infrequent with the v368.22 it would always occur at least once or twice per day. In every case the application would run without the error on the second attempt. As mentioned earlier, this issue did not affect games, only applications ran from a shortcut, whether it be a desktop, quickbar or Programs one (I actually got the error when running the installer for the v365.19 driver while using v368.22!!!).

3. The Windows Store's Check for Updates would get stuck in a neverending loop and not stop until I either rebooted or shutdown. This was 100% replicable; basically it did not work while the v368.22 driver was installed. I have just checked for updates manually from the Windows Store post-v365.19 and it worked first time (four programs had updates and I was able to download and update them).

I have reported this issue to NVIDIA because even now with all the evidence I find it unbelievable that a graphics card driver could cause those issues.

 

Not necessarily related to this driver, but I've gotten two CTDs in Doom ever since installing this driver (clean DDU install ofc).
Didn't get a single one before, will roll back to .19 and see.

 

Yup, that's exactly what I observed as well (although I used DDU to get rid of 368.22 drivers before re-installing the 365.19 ones clean). In addition, I had various connection/timeout errors in Chrome (especially when accessing Chrome settings, extensions store, chrome update, etc.) and problems accessing the localhost in general with the 368.xx drivers. Plus my computer often didn't shut itself off anymore at the end of the Windows shut down procedure. With 365.19 drivers everything is fine.

It has nothing to do with DDU. I did two clean installs of windows without ever using DDU and whenever I installed 368.xx drivers I started getting the errors and problems mentioned above. It's definitely an issue with the 368.xx drivers, although it might not happen with all hardware configurations.

 

basically, what u mean is by installing v365.19 as a based on top of 368.22 that the stub received bad data will gone?

 

I always run DDU before installing, and no stub error here

im on 386.22 and I have no such issue with windows store getting stuck or taskmanager open up with error or this stub error, gotta love those random bugs.

 

i don't have windows store stuck but the stub received bad data is exist & legit. maybe this issue is for maxwell users only???

 

possible are all the people that have this using maxwell? as I still using kepler series

then again some people with same series dont have this happen, like said gona love random bugs

 

What is this "stub" you all are talking about? I never heard or seen this before..

 

https://support.microsoft.com/en-us/kb/2028588

It's the GFE service ;p

I'm not sure what buffer they are talking about and how to determine how much you are using.

 

Yes, I've not had the error since installing the v365.19 driver over the top of the v368.22 earlier on this evening. Also, Task Scheduler and Windows Store updates are both working fine. It's absolutely the driver that is causing the issue on my system.

 

Maxwell and no stub error

Opened task scheduler and WS updates, no errors

Maybe a driver conflict with something else not installed here

 

Possible, I don't install GFE as I don't like it and see no benefit in it.

 

Yea no GFE here either

 

I dont use GFE