ForceWare 368.xx drivers causing "The stub received bad data" errors

[RejZoR]

I was getting this crap randomly on like 1/4 of executed apps, just randomly. And after error appeared, if you tried to execute the app or game, it then launched without a problem. I just clean installed Windows 10 and I couldn't figure it out what the hell is causing this, especially since SFC and DISM that I managed to finally figure out check all out clean. I also downclocked entire system because I thought OC is causing this. Most often when trying to launch Task Scheduler, but also happened on paint.NET, MusicBee and tons of other common apps I use.

I'm also suspecting it was ForceWare 368.xx that was causing my Task Scheduler service to be just stopped for no reason and I had to manually start it here and there.

Event Viewer was also getting filled with "Faulting application name: svchost.exe_wuauserv" in connection to NVIDIA's "nvwgf2umx.dll". Which gave me a rough idea. Because I wasn't getting the stub error 2 months ago, that's for sure.

Uninstalled EVERYTHING from NVIDIA, force deleted driver via Device Manager and waited for Windows 10 to automatically re-install ForceWare 358.91 from May 2016.

While it has only been a night in between after I've done this, so far no "The stub received bad data" nonsense on anything and I also have ZERO above mentioned errors in Event Viewer after 6 hours. Before, I could have over 200 errors in just an hour.

Can anyone else confirm this? If you're getting the stub error, check Event Viewer for red errors with mention of "nvwgf2umx.dll". Also downgrade to drivers before 368.xx and observe if you're still getting the stub errors or Event Viewer errors. There aren't tons of complaints over it because I think people just couldn't figure it out what's causing it since the stub error doesn't really tell what caused it. Maybe with some help from TPU staff we can figure out if my findings are indeed correct and get NVIDIA's attention to fix this nonsense. I want to use latest drivers, not some old stuff from months ago...

 

[okidna]

I don't have this issue as far as I remember, but maybe because I'm still using Windows 7 when I still use my 970. Let me try to install my 970 to my Windows 10 PC and try to replicate the issue later.

Meanwhile, there's a similar thread regarding this same issue at Guru3D, even ManuelG from NVIDIA forum already popped up to gather some meaningful data to replicate and investigate the issue : http://forums.guru3d.com/showthread.php?t=408232

Oh and also this possible quick fix : https://forums.geforce.com/default/...68-51-released-6-17-16-/post/4909512/#4909512

 

[RejZoR]

Interesting. I found tons of results via Google, but were mostly for Windows 8.1, 7 and even XP so I was kinda left in the dark. Interesting I didn't get Guru3D results hm... And I was going mad how the hell can a clean system have so many problems, it never even crossed my mind graphic drivers could be causing all of it (even the dying of Task Scheduler service!). Absolutely crazy how NVIDIA manage to f**k this up so badly.

I also have to change settings because I want transparency filtering, forced highest refres rate and Adaptive V-Sync. Not changing settings means I'll have to use my all powerful GTX 980 without essential things I've been using for basically a decade.

I'd appreciate if @W1zzard or someone influential could get NVIDIA in touch. Because I know they don't care at all when casual users report issues on their forums. Been there, done that, seen that. And this thing is driving me insane. I've never ever had such stupid enormous problems because of graphic card in 17 years. I kid you not.

EDIT:
Interesting, they say DSR causes this, but I haven't even enabled this thing in current clean install so that can't be it.

EDIT2:
I see ManuelG actually joined Guru3D. Ok then. I have to try without MFAA. I do use that globally all the time.

 

[R-T-B]

I use DSR and the latest drivers without this issue for whatever it's worth. Unsure as to your cause, but you should be open to the possibility it's not the driver, as always.

 

[RejZoR]

It IS the driver. We just don't know what part of it exactly is causing this. Reverting back to 1 older generation and problems were gone.

It just sucks Windows 10 keeps force installing drivers from Windows Update if you revert drivers past WU driver. That's why I was so against this stupid forced updating driver nonsense in Win10. Because when such issues appear, OS itself is preventing you from using older problem free drivers. I was lucky here that I didn't have to go so far back...

Anyway, I'll try latest 368 again without changing any settings if problems are gone and if they are, then I'll systematically go one setting after another to see what's what.

 

[Mussels]

new nvidia user here with a 970, not seeing these issues.

368.39, W10 x64

 

[RejZoR]

Try enabling these under global settings:
- 16x anisotropic filter
- MFAA
- Transparency AA -> Multisampling or 8x Supersampling
. Single screen performance
- Refresh rate: Highest available
- Adaptive V-Sync

This is what I use enabled all the time.

 

[erocker]

Try enabling these under global settings:
- 16x anisotropic filter
- MFAA
- Transparency AA -> Multisampling or 8x Supersampling
. Single screen performance
- Refresh rate: Highest available
- Adaptive V-Sync

This is what I use enabled all the time.

Turn them off one by one and see what's causing it. Then: http://www.nvidia.com/object/driverqualityassurance.html

 

[Mussels]

after seeing that you run 144Hz, methinks thats the problem. check the Vsync related options first.

 

[RejZoR]

Looks like it's really MFAA setting. I've enabled everything I use except MFAA. No errors in Event Viewer and no stub errors either. Ok...

 

[Mussels]

sounds like a bug worth reporting to green team HQ.

 

[TheHunter]

Yeah its MFAA issue if set in global profile. Nv is already working on it.

 

[Mussels]

i was thinking about testing that feature... guess not!

 

[TheHunter]

i was thinking about testing that feature... guess not!

You can still test/enhance it per game profile, its ok like that..

Speaking of per game profile, batman arkham origins had it bugged too (hbao burned in the image), I reported it @368.22? and its been fixed with 368.39.. so they do fix them fast.

 

[Laurijan]

There is a ton of Nvidia related driver issues going on after 362.00 from what i read in the nvidia forum and google.
For the 970 some guys on reddit 3 month ago said that 362.00 is the last stable driver.

 

[rtwjunkie]

There is a ton of Nvidia related driver issues going on after 362.00 from what i read in the nvidia forum and google.
For the 970 some guys on reddit 3 month ago said that 362.00 is the last stable driver.

I've found the 365.19 is extremely stable, including for 970, so that's more current for those that need it.

 

[Caring1]

I reported it @368.22? and its been fixed with 368.39.. so they do fix them fast.

What is the latest driver and what improvements does 368.49 bring?

 

[TheHunter]

the latest is a HF 368.51 driver, it fixes flickering by high Hz displays (mostly gsync)


Im keeping these older just in case, they were the best..

Atm at latest HF 368.51, seems ok.. I didn't notice any negative fps, although I usually play DSR'd and vsync'd.