GeForce 368.39 WHQL driver download

#5286195

Netherwind

2016-06-08 16:48

Not sure if you 1070/1080 users noticed any gains? [youtube]ux7aH7r1KoI[/youtube]

#5286221

-Tj-

2016-06-08 17:50

I'm not sure if this issue is related to the ones I've been getting since installing the 368.xx drivers but I opened up the Event log this morning to see a lot of errors regarding various services terminating unexpectedly and so on, far more than normal, perhaps triggered by this driver since they all started occurring since I reinstalled the v368.22 driver yesterday morning to play Mirror's Edge Catalyst (since you are forced to use this driver otherwise the game will not start; rather annoying to be honest). Anyway, I also opened Device Manager and checked the Show Hidden Devices option. It revealed two entries with caution marks under Network Adaptors; one for Microsoft ISATAP Adapter and another for Microsoft Teredo (I believe this is something to do with IPv6 something my ISP does not yet support). Both failed to start because a previous version was conflicting with them, something like that. So I did a System Checkpoint and uninstalled both then rebooted. Both now show as working without the caution symbol. Need to test further to see if those fix anything... Finally, I also saw this error in the Event log: Faulting application name: svchost.exe_wuauserv, version: 10.0.10586.0, time stamp: 0x5632d7ba Faulting module name: nvwgf2umx.dll, version: 10.18.13.6839, time stamp: 0x5750f3f8 Exception code: 0xc0000005 Fault offset: 0x0000000000759c9d Faulting process ID: 0x3a4 Faulting application start time: 0x01d1c153b519d792 Faulting application path: C:\WINDOWS\system32\svchost.exe Faulting module path: C:\WINDOWS\system32\nvwgf2umx.dll Report ID: 8db06311-02de-4ed1-a4b9-0bc0cef7b043 Faulting package full name: Faulting package-relative application ID: I'm wondering if anyone else who is experiencing the same issues as me is also getting the same error. If I understand it correctly it is some conflict between an NVIDIA driver component and the Windows Update service, which is one of the issues I was having (specifically the Windows Store which stalls when manually checking for updates). I have also disabled the two useless NVIDIA SHIELD streaming services as I have no need for them. Why NVIDIA insist on having one of those set to Automatic and always running is baffling because I would have thought it would have made more sense to set them to Manual and only have the service run when needed? There's already too many background services for NVIDIA as it is! Just to reiterate, I have re-ran sfc /scannow and dism.exe /scanhealth this morning and both returned NO errors. P.S. I am wondering if I should start a separate thread for those of us experiencing the "stub has received bad data" and other issues with these 368 drivers as any discussion regarding it are likely to get lost amongst all the other posts. This thread can go into more detail about what hardware and software we are running in order to try and find some commonality (other than the fact we are using 368 drivers obviously) that might be triggering these issues. Good idea or not?

That nv file is dx11 part of driver so there is something buggy for sure.. What if you reinstall the driver (override), potentially it could be that nvupdatus issue, do you use this feature too? Well I use only driver, phsyx, hdaudio, rested deleted and never saw this bad stub, just checked event viewer yesterday and nothing really special, I had one dcom issue but googled that and fixed again, I remember this permission issue in win8.1 when i upgraded from win 8.0 lol https://answers.microsoft.com/en-us/windows/forum/windows_8-performance/event-id-10016-the-application-specific-permission/9ff8796f-c352-4da2-9322-5fdf8a11c81e?auth=1 That windows update conflict and store bug means something is not right by permissions or conflicts between services. Try to rebuild WMI and reboot https://support.software.dell.com/vworkspace/kb/88861 Now repair windows update, re-register it, you can use this handy tool https://gallery.technet.microsoft.com/scriptcenter/reset-windows-update-agent-d824badc Or Windows10 manager, it has both scripts in repair center and its handier lol, 20day trial In this app there is also a special Windows store fix; its by modern settings >> re-register store apps, clear old cache (wait 1-2min), then it auto opens store app and sign in again http://s6.postimg.org/6bt6s5hp9/image.png http://s6.postimg.org/jvembll25/image.png http://s6.postimg.org/wle9ay3ml/image.png http://s6.postimg.org/gsdw8863h/image.jpg

#5286304

Darren Hodgson

2016-06-08 19:55

Just do an in place upgrade then with the 1511 Iso it takes 15 minutes of your time and maybe it solves the problems

It doesn't though... unfortunately... as I've read two posts from people who've done a clean reinstall of Windows because they thought the stub/bad data error was the result of a corrupted operating system only to find the issue returns as soon as they install the 368 driver. That is the reason I have not done it but I know I can fix the issues on my system simply by reverting to the v365.19 driver. So why don't I then? Because EA in their infinite wisdom decided that I can only play Mirror's Edge Catalyst with the 368 driver!!! That's what makes this issue so aggravating.

#5286306

tsunami231

2016-06-08 19:57

This might help some of you with the task scheduler and bad stub errors, because I think it has something to do with third party antivirus software on windows 10. I had avast installed recently, and it was causing the same errors on my system. I uninstalled it, and non-coincidentally, the errors stopped as well. If those of you that are having these problems are using anything other than windows defender, I recommend uninstalling whatever antivirus you have, unfortunately.

I use Avast and have no such issue

#5286307

Netherwind

2016-06-08 19:59

As a workaround go to "Set up multiple displays" and disable your receiver before switching it off. You can also fiddle with the "Multi-display/mixed-GPU accelleration" options.

I don't really have an option to disable my receiver. I mean, in the display area I have two options, either my Acer monitor or the LG TV (even though the signal has to go through the receiver). Disabling it is like pressing Win+P and selecting "Monitor only". Funny thing now is that if I turn off the TV, my monitor turns itself off 🙂 Previously it didn't do that. I'll try DDU and install 365.19 again, see what happens. Edit - My monitor works during boot and Windows load but turns itself off at the logon screen.

#5286332

Darren Hodgson

2016-06-08 20:35

Just a quick question for those people who have the same stub/bad data error as myself: are you running the NVIDIA SHIELD and/or Stardock WindowFX/WindowBlinds services? I have disabled all four on my system and have not yet seen the error plus Task Manager is still running after a couple of hours and the Windows Store update seems to be working. One or more of those may possibly be conflicting with the 368 driver to cause the issue (but doesn't with 365.19). My money is on one of the Stardock programs as I've had them installed and set to automatically start with Windows for both but don't actually use either. Still too early to know for sure if the issues are fixed but, fingers crossed, it is one them. Really do not want to be in a situation where I am unable to install the latest driver because of stuff like this as I play many of the latest games such as Mirror's Edge Catalyst that require the newest drivers to be installed. *UPDATE* Forget that... got stub error just now and Windows Store Check for Updates has reverted back to being stuck on searching! At least Task Scheduler still works... 🙁 Pah!

#5286388

-Tj-

2016-06-08 22:42

GTA5 MultiPlayer crashed, followed by a TDR..

Description Faulting Application Path: H:\Games Part2\GTA 5\GTA5.exe Problem signature Problem Event Name: APPCRASH Application Name: GTA5.exe Application Version: 1.0.678.1 Application Timestamp: 56e29e89 Fault Module Name: GTA5.exe Fault Module Version: 1.0.678.1 Fault Module Timestamp: 56e29e89 Exception Code: 80000003 Exception Offset: 000000000119ace3 OS Version: 10.0.10586.2.0.0.256.48 Locale ID: 1060 Additional Information 1: f635 Additional Information 2: f63535430a109116b55143a2513b3d05 Additional Information 3: 8a3e Additional Information 4: 8a3e65f6498f1604edf64c1213fc532d

It happened after I changed MSAA 4-5times while using TXAA., plus enhanced MFAA in driver if it matters.. Will see if its better without MFAA enhancement.. Well MFAA seems to be a buggy driver feature.. 🙁

#5286442

dr_rus

2016-06-09 00:26

I always install the normal way and also only have display driver service.

Same. Driver+Audio+PhysX is my typical install.

#5286448

tsunami231

2016-06-09 00:42

I been extracting the installer for 10 +years and manual install them threw the setup file Drivers+physic

#5286461

dr_rus

2016-06-09 01:08

I hope they integrate the Vulkan driver like OpenGL, not sure why it needs it's own installer.

The driver is integrated like OpenGL, VulkanRT is the API itself provided by Khronos as a separate installer.

#5286471

tsunami231

2016-06-09 01:22

I always install the normal way and also only have display driver service.

with 386.22 the display driver service (nvvsvc.exe) was reduce to 1 instance of it, before that it was 2 instance of it, this was something that always annoyed me, one less thing to annoy me now, not sure what the (nvxdsync.exe) does only 1 instance of that, I have no other service from nvidia cause I dont install gfe. Also never seen this "NVidia Backend" probably cause I manual extract drivers and manual install driver by click on the setup, instead click the installer?

#5286475

Nastya

2016-06-09 01:37

Installed without issue, from the limited games I played, everything is golden.

Great to hear. Can you let the thread know if you encounter any TDRs, please. I am hesitating to install these since the newer sets give me trouble even on desktop.

#5286478

tsunami231

2016-06-09 01:46

both nvvsvc and nvxdsync are in my experience, simply a link between the driver and the nvidia control panel. both can be set to manual in services.msc, without any affect on GPU usability. both will start up as soon as you open nvidia cpanel. and yep, backend and nvtray are installed if you use the official driver installer without unpacking and deleting stuff. this is a recent change since 35x or 36x drivers. In the past if you selected only driver+physx in the installer, it would act identical to the manual method we both use.

See back on windows 7 or was it XP disabling NVVSVC resulted in AA not work in any game when forced threw nvcp, I have since just left it on And I dont delete anything from package I just use 7-zip to extract the installer and run setup.exe so I dont think you actual have to delete things from the package. nvtray or nvidia backend files files might be on PC but they have never been set to run on startup, unless this all changed since 368.22

#5286504

pato9

2016-06-09 03:52

Hey guys, i tested the new driver and want to share my work with you, I hope to be of help and you enjoy the video audio is in Portuguese however I put subtitles in English for you, thank you. https://www.youtube.com/watch?v=QyZB0BRC0mA

#5286509

mr1hm

2016-06-09 04:33

the first installation of these drivers gave me TDR error on desktop right after i set up my global settings and manually rebooted my computer. second installation seems to be ok, no TDR.. played Overwatch, CSGO and WoW.. all seems normal. i used DDU before installing these drivers in both instances.

#5286532

endbase

2016-06-09 07:15

yeah something messed up with the services on the nvidia driver. i'm using classic shell & i removed also can't solve the issue so i can ensure is not related to stardock. no choice just wait manuelG release new hotfix.

I'm using startdock BTW start10 and Windowblinds don't have any issues

#5286614

yosef019

2016-06-09 10:40

Hey guys, i tested the new driver and want to share my work with you, I hope to be of help and you enjoy the video audio is in Portuguese however I put subtitles in English for you, thank you. https://www.youtube.com/watch?v=QyZB0BRC0mA

how its takes only 4 gb ram in rotr its usualy take 10-12 gb ram

#5286619

signex

2016-06-09 10:52

Hey guys, i tested the new driver and want to share my work with you, I hope to be of help and you enjoy the video audio is in Portuguese however I put subtitles in English for you, thank you. https://www.youtube.com/watch?v=QyZB0BRC0mA

Like the intro, short and sweet. 😀

#5286764

Cave Waverider

2016-06-09 15:44

the difference between the manual and normal installation of just the driver+phsyx is that the nvidia backend and nvtray gets installed with the normal installation. They're not in services.msc, so I guess calling them a service is incorrect. But they are extra processes. If I had the bad stub issue, i'd definitely try installing the driver without those two to rule it out as a possible cause of the issue.

Alas, I'm always (well, I tried installing them for testing once on one of my clean installations to see if it fixes the bad stub error, but it didn't) installing it without those two and the bad stub error comes up every time I have any 368.xx driver installed.

yeah something messed up with the services on the nvidia driver. i'm using classic shell & i removed also can't solve the issue so i can ensure is not related to stardock. no choice just wait manuelG release new hotfix.

I don't use anything from Stardock either. And since the bad stub error also comes up with a completely clean and fresh install of Windows 10 Pro (no programs installed, I've seen this happen with the vanilla and current 1511 live builds as well as the latest insider builds on respective clean installs on three different computers) and just any 368.xx driver installed for me, it's definitely caused by the driver. Not sure why it doesn't happen on some machines, perhaps the driver has an incompatibility with certain other hardware on Windows 10 or something. Not sure.

#5286899

tsunami231

2016-06-09 19:27

Interesting. that must have been in the past, when you could actually change AA in a game via cpanel, even when alt tabbing out of the game. I remember being sad when they announced the feature is no longer feasible. I personally don't bother setting any nvidia services to manual any more, but I did test, and there were no issues with them set to manual on the numerous games i've tested. Good to know about not having to delete the folders as well. I always did it just because it seemed logical they would get installed unless removed from the installation folder.

Well NVtray is installed its not set to autorun or anything though, and the nvidia backend I cant find anything named that in my nvidia folders. As for applying AA on the fly back then I never new that, I just new back then if the service wasnt runing AA didnt work and I think other settings didnt work either.

Could be something like a conflict between nv's new drivers and realtek drivers or something akin to that.

Ugh Realtek drivers there is reason why I dont update them no more. that 4+ year issue with system locks happen cause there drivers didnt like HW acceleration with the likes of Flash/java/FF HW those type programs running while have any voice chat program up and running come to mind cause that combination was instane lockup all the time. to bad you really cant get away from realtek onboard audio other then the rare creativelabs solution, you can how ever get away from there nic's