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

Look ever here it maybe is an windows 10 error and not related to NVIDIA http://answers.microsoft.com/en-us/windows/forum/windows_10-start/the-stub-received-bad-data/f4829753-484e-4cf8-b123-6caf2422d17b?tm=1440578826462

I wonder why i never get that error. i always install gfe too.

I hope these fix the uber-annoying issues I've been having with the v368.22 driver, namely "the stub received bad data" error, the Windows Store check for updates stalling and the borked Task Scheduler. I avoided these by reinstalling the older v365.19 and have not seen any of them for over a week but, unfortunately, I was forced to reinstall v368.22 to play Mirror's Edge: Catalyst and, lo and behold, I got a "stub/bad data" error within seconds of rebooting my PC and attempting to open the Event log!!! The weird and ultimately aggravating thing about those errors is that none of them affect games... kind of ironic really how a graphics driver even causes those but I can 100% replicate the issue simply by installing that driver and fix it completely by installing an older one.

The main issue with the most recent Nvidia drivers is the fact that they screw up my desktop icon layout and I have t reconfigure it everytime. This surely is easy for Nvidia to avoid?

Try this http://www.softwareok.com/?seite=Freeware/DesktopOK

Setting power option to max performance causes 1st card in sli memory clock to remain at 405mhz. Optimal is required

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.

And there I was thinking to skip this release as nothing in the notes that looked interesting. Oh well, DDU here I come

luckily, i'm not alone. nothing much we can do now. starting r368 branch the stub appeared. do u enable fast sync at nvinspector?

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:

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 just wondering on what version of windows you guys are ? sound like insider build trouble to me but I could be wrong

I'm just wondering on what version of windows you guys are ? sound like insider build trouble to me but I could be wrong

that is good question

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.

Fixed for me too! Thank god, it was driving me nuts :eyes:

I'm just wondering on what version of windows you guys are ? sound like insider build trouble to me but I could be wrong

Windows 10 Pro v1511, i.e. the officially released version and not an insider build (I have never installed those). These issues do NOT occur with driver v365.19 and earlier by the way on my system, ONLY with the latest v368.xx branch.

I'm just wondering on what version of windows you guys are ? sound like insider build trouble to me but I could be wrong

I dunno, these issues don't sound like something graphics driver related to me at all. And I don't have any of them on my Win10/1511.

P.S. I would love nothing more than to revert back to the 'stable' v365.19 driver on my system but annoyingly EA is forcing the v368.22 or newer driver in order to play Mirror's Edge: Catalyst, which I downloaded this morning. On running the game with the v365.19 driver the game halted with a request to install v368.22. Clicking OK just exits the game. Surely the driver version should be optional not mandatory? Very frustrating to have to use a buggy driver on my system... 🙁

I dunno, these issues don't sound like something graphics driver related to me at all. And I don't have any of them on my Win10/1511.

Me neither I'm on 1511 build version 10586.338

I dunno, these issues don't sound like something graphics driver related to me at all. And I don't have any of them on my Win10/1511.

they dont they sound like OS issues, but apparently are being trigged by the drivers. i dont think there alot people with issue, which why nvidia said nothing about and and googling on the subject points to OS issue in that some thing is corrupted and not playing nice with the newer drivers. Anyway Has Fastsync been enabled in NVCP yet? or is it still inspector only, or is gona be come another feature Nvidia talks about but is only visible in inspector like framelimiter 1511 10586.318

I dunno, these issues don't sound like something graphics driver related to me at all. And I don't have any of them on my Win10/1511.

Well that's what I thought at first because I did not even consider the graphics driver was the cause. However, if I install v365.19 over the top of v368.xx then the issues are all fixed even without rebooting. I reinstalled v368.22 this morning to play ME Catalyst and straight away I got a stub/bad data error on opening the Event log. This is after an error-free week of using v365.19 since I reinstalled it over the top of v368.22. It is absolutely the v368.xx driver that is the problem on my system, whether it is the direct cause or has some conflict with something else installed on my PC. I know how to fix it (reinstall v365.19!!!) but I can't because I have to use a v368.xx driver for ME Catalyst!

Well that's what I thought at first because I did not even consider the graphics driver was the cause. However, if I install v365.19 over the top of v368.xx then the issues are all fixed even without rebooting. I reinstalled v368.22 this morning to play ME Catalyst and straight away I got a stub/bad data error on opening the Event log. This is after an error-free week of using v365.19 since I reinstalled it over the top of v368.22. It is absolutely the v368.xx driver that is the problem on my system, whether it is the direct cause or has some conflict with something else installed on my PC. I know how to fix it (reinstall v365.19!!!) but I can't because I have to use a v368.xx driver for ME Catalyst!

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.

Lazy install over the top of the last WHQL. Just driver, HDAudio, PhysX installed. I'm not seeing any issues with GTA 5 and the new DLC release, seems to be working fine. Will do some more tests with other games later but for now i want my new GTA cars....

Honestly, what is going on here? As with 368.22 I have this strange problem with HDMI. I normally got a cable connected between my card and my receiver (which is connected to my TV). If the receiver is ON then my normal monitor works but if I turn the receiver OFF then it also turns off my monitor. When I disconnect the HDMI cable the monitor works. If I start the computer in safe mode my monitor works even if the receiver is off. This is also OK when I've used DDU for uninstall but the moment the nVidia installer finished installing this driver, my monitor turned itself off. It's inconvenient having to connect/disconnect the HDMI cable every time I want to watch Netflix on my TV.

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