Did anyone notice that profomance took a dive with these drivers ? I lost around 500 points in Valley with these.

Actually performance went up for me by around 500 in valley.

Well these were the most pointless drivers i ever saw. Still no SLI fix for 1080's

This set was only released for 1080 FE fan spin up fix as far as I know.

I think it has to do with multiple factors you can not only blame it on the drivers from NVIDIA the thing is what is causing the mix of something "missing" or "corrupted" on your system whe don't have on the same build that is for now the question. My suggestion to you is repair with dism the healthy state and after that update everything related to your OS.

Neither sfc /scannow reports nor dism.exe /scanhealth report any errors so I am pretty sure I do not have a corrupted Windows install. My system is 100% stable, no crashes whatsoever and all games run perfectly. Windows itself is fine as long as do not use any v368.xx driver. Blame my system if you want but the fact remains that I am not the only one with this issue and, as far as I know, everyone else with the same issue has been able to resolve it by reinstalling an older pre-v368 driver. If one driver works and the other doesn't then surely it must be the driver itself that is the problem? I already mentioned that a few people have even tried doing a clean Windows install, which DOES fix the issue ("stub has received bad data") but only because they don't have a v368 driver installed at that point. Once they reinstall the v368 driver then the issue returns. That pretty much confirms in my mind that the issue is not the result of a corrupted operating system.

Damn! The v368.39 have the same three issues as the previous v368.22 driver, namely: 1. On opening non-game shortcuts such as the Event log, I will intermittently (perhaps once in every five to ten times) get a "the stub has received bad data" error. Closing the window and reopening the program a second time always work. 2. The Windows Store's Check for Updates gets stuck in a neverending loop and never completes. This has the side-effect of causing Windows to take longer to shutdown because the background process that the Windows Store uses does not finish. 3. The Task Scheduler will eventually give a "Cannot connect to remote server" error because the service will stop despite being set to Automatic. This can be fixed by manually starting the service. Why on earth these issues are happening with a graphics driver is anyone's guess because games actually run fine and I have yet to see the "stub has received bad data" error while opening a game. I know I am not the only one with this issue as I've seen others, like khanmein reporting the same thing here and over on the GeForce.com forum. Clearly, whatever changes NVIDIA have made to these drivers over the v365.xx and earlier branches somehow causes issues with components of Windows which should not be affected by a graphics driver. My big concern is that there are more people with this issue but, like me initially, they may not have even considered that the graphics driver might be the cause. Indeed, I've seen posts from others who have tried reinstalling Windows to fix the issue only to find it comes back once the v368.22 driver was reinstalled! Very worrying really, not just the "stub/bad data" error, but mostly because it currently breaks Task Scheduler, preventing standard tasks from running (unless the service is started manually again) and because it appears to prevent Windows from updating the Store apps! :3eyes:

I'm getting all the above issues plus my PC doesn't power off after shutting down anymore with this driver (and previous v368.xx drivers) and Chrome 64 bit hangs and the taks can't be killed when I go into settings, clear the browser cache and other things. Going back to 365.xx drivers solves all these problems for me and my friends. I've been able to reproduce this on three PCs so far. I don't have GFE nor that Nvidia update service installed.

Neither sfc /scannow reports nor dism.exe /scanhealth report any errors so I am pretty sure I do not have a corrupted Windows install. My system is 100% stable, no crashes whatsoever and all games run perfectly. Windows itself is fine as long as do not use any v368.xx driver. Blame my system if you want but the fact remains that I am not the only one with this issue and, as far as I know, everyone else with the same issue has been able to resolve it by reinstalling an older pre-v368 driver. If one driver works and the other doesn't then surely it must be the driver itself that is the problem? I already mentioned that a few people have even tried doing a clean Windows install, which DOES fix the issue ("stub has received bad data") but only because they don't have a v368 driver installed at that point. Once they reinstall the v368 driver then the issue returns. That pretty much confirms in my mind that the issue is not the result of a corrupted operating system.

No, it isn't. I thought so as well at first as similar errors are related to a corrupted OS, but that wasn't the case. I installed Windows 10 Pro 64 bit clean twice already (once the latest insider preview build as I thought it might fix it, and when it didn't, I did another clean install of the regular v1511 build) and everything was fine until I installed a 368.xx driver, that's when the issues started appearing. Once I went back to 365.xx drivers, everything was fine again. If I do a completely clean install of Windows 10 Pro v1511 and don't update it and install the 368.xx drivers immediately, the issue pops up as well, so it's definitely related to the drivers. There is no corruption anywhere, the problems are related to the drivers, possibly in conjunction with certain hardware. So far I can confirm the problem with a Titan X, 980 Ti and GTX 970.

Neither sfc /scannow reports nor dism.exe /scanhealth report any errors so I am pretty sure I do not have a corrupted Windows install. My system is 100% stable, no crashes whatsoever and all games run perfectly. Windows itself is fine as long as do not use any v368.xx driver. Blame my system if you want but the fact remains that I am not the only one with this issue and, as far as I know, everyone else with the same issue has been able to resolve it by reinstalling an older pre-v368 driver. If one driver works and the other doesn't then surely it must be the driver itself that is the problem? I already mentioned that a few people have even tried doing a clean Windows install, which DOES fix the issue ("stub has received bad data") but only because they don't have a v368 driver installed at that point. Once they reinstall the v368 driver then the issue returns. That pretty much confirms in my mind that the issue is not the result of a corrupted operating system.

Oke man then I must say that is an major bummer for you and all the people who have the same issues !

I can corroborate the issues Darren Hodgson and Khanmein are seeing. I have pretty much the exact same symptoms when trying to use 368.22/39 on multiple fresh installs of 1511 and/or the latest insider builds. Sfc/Dism come back clean, never installed GFE, etc. I don't use inspector or install any of the 3D Vision stuff. Games and programs apparently run fine, but the messages and log spam are annoying. In fact, you guys reporting the issue here is what helped me to narrow the problem down and find the temporary fix (by rolling back to 365.19 for now), so thank you both very much for sharing or I would be still banging my head over these annoying errors. I don't have the technical answer and I'm not blaming this driver as the direct cause of our problems, but 368.22/39 is definitely exposing/triggering the problem for some of us, hopefully we/Nvidia/MS can root out the exact problem by sharing info. Feel free to ask for any other details that might help sort this out, I wanna fix it too!

Hm, lack of vsync in Steam browser issue seems to be fixed in those. At least I don't get any tearing on store view right now.

Wow, I didn't expect that to get fixed as quickly as it did. Good on Nvidia/Google/Valve whoever. Will install these ASAP!

Honestly, what is going on here? As with 368.22 I have this strange problem with HDMI.

Try setting "Power management mode" to "Adaptive" or "Prefer maximum performance".

Try setting "Power management mode" to "Adaptive" or "Prefer maximum performance".

Tried it, didnt help.

Wow, I didn't expect that to get fixed as quickly as it did. Good on Nvidia/Google/Valve whoever. Will install these ASAP!

I can confirm the problem is gone in normal Chrome with Youtube and Netflix now, Steam, and even the strange broken vsync issue I was having in Rocket League is also now gone. Yay!

I've installed this tiny app shortly after to deal with the tedium of rearranging icons every new driver install or resolution change. http://desktop-restore.software.informer.com

This would be the website, and it doesn't mention Windows 10. WhiteLightning recommended DesktopOK which is actively developed.

Tried it, didnt help.

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.

Does this fix the annoying SLI flicker in Overwatch on certain light sources?

Does this fix the annoying SLI flicker in Overwatch on certain light sources?

Does SLI actual work in Overwatch? Owerwatch does not need sli, it works great with an GTX 750ti in 1440p and one gtx titanX @ 1500mhz in 3440x1440 easy 100 fps....

Ok, lets see if API DX11 ST and MT got any improvement, first two 368.xx had lower then older r364 branch, but quite faster in dx12 (RoTR, AoS, Hitman2016, and other dx12 games). [spoiler] 364.51 DX11 Multi-threaded draw calls per second 2 367 127 DX11 Single-threaded draw calls per second 2 586 994 DX12 draw calls per second 19 895 550 http://www.3dmark.com/aot/123188 364.72 DX11 Multi-threaded draw calls per second 2 233 012 DX11 Single-threaded draw calls per second 2 515 034 DX12 draw calls per second 19 736 941 http://www.3dmark.com/aot/129185 368.22 DX11 Multi-threaded draw calls per second 2 189 715 DX11 Single-threaded draw calls per second 2 421 146 DX12 draw calls per second 21 837 567 http://www.3dmark.com/aot/139974 .............. win8.1 & GTX 780 353.49 DX11 Multi-threaded draw calls per second 2 431 530 DX11 Single-threaded draw calls per second 2 549 102 DX12 draw calls per second 0 http://www.3dmark.com/aot/46129 350.05 DX11 Multi-threaded draw calls per second 2 428 128 DX11 Single-threaded draw calls per second 2 324 301 DX12 draw calls per second 0 http://www.3dmark.com/aot/23143 352.86 DX11 Multi-threaded draw calls per second 2 438 687 DX11 Single-threaded draw calls per second 2 484 574 DX12 draw calls per second 0 http://www.3dmark.com/aot/26030 353.38 DX11 Multi-threaded draw calls per second 2 426 594 DX11 Single-threaded draw calls per second 2 499 234 DX12 draw calls per second 0 http://www.3dmark.com/aot/38140 [/spoiler] EDIT: Ok a little compared to first two R368.. 368.38 DX11 Multi-threaded draw calls per second 2 253 217 DX11 Single-threaded draw calls per second 2 442 040 DX12 draw calls per second 21 417 578 http://www.3dmark.com/3dm/12367101? The only driver that came close to current top R353 was 364.51. R368 still needs some tweaks or better yet bring on R370 🤓. I remember old 275.xx was top, hopefully future 37x.xx delivers the same 😛c1:

Yey! No more screen tearing while scrolling down on Steam!

"the stub received bad data" still exist on this branch 368.xx this error related with fast sync??

According to M$ we can see this error when we have too many services.

According to M$ we can see this error when we have too many services.

You get a similar error message for that, but not the same error code. Besides, the number of services isn't any bigger or smaller with these drivers compared to the older ones where the error doesn't pop up. 😛

One interesting observation with these drivers when playing games ... higher CPU OC's on my system are stable where with previous drivers had to lower the clocks to avoid crashes.

Same sluggish performance in Cities Skylines like the .22 and 25 drivers. Back to 365.19.

Installed fine after DDU but has anyone noticed Power Management set to Optimal in Control Panel, "0x00000005" in Inspector, by default under Global Profile? Don't seem to be an issue as I just got my highest score in RE6 Bench 16846 vs the normal 16670 ish.Just wondering if it was normal..haven't run any other bench/games yet.