Tuesday, February 2nd 2016

NVIDIA Outs Hotfix Driver to Address Graphics Card Eject Bug

NVIDIA rolled out a Hotfix driver update for its recently released GeForce 361.75 Game Ready drivers. The new GeForce 361.82 Hotfix driver corrects a bug which makes your installed GPUs appear as removable devices in your system tray (much like removable storage devices). It may have been a bug in the implementation of support for external graphics solutions over Thunderbolt 3, introduced with 361.75 WHQL. The hotfix driver addresses the issue.

If you find a 300-megabyte download worth fixing the bug (i.e. you often accidentally "eject" your graphics cards (unload display driver) while trying to unmount your external storage devices), then grab the driver for your OS from the link below.

DOWNLOAD: NVIDIA GeForce 361.82 Hotfix
Add your own comment

12 Comments on NVIDIA Outs Hotfix Driver to Address Graphics Card Eject Bug

#1
Fierce Guppy
Changing HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesnvlddmkmSurpriseRemovalSupport from 1 to 0 and rebooting also fixes it.
Posted on Reply
#2
Breit
Fierce Guppy said:
Changing HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesnvlddmkmSurpriseRemovalSupport from 1 to 0 and rebooting also fixes it.
...and they need 7 driver versions (.75->.82) and a 300MB download for flipping that bit. o_O
Posted on Reply
#3
Dr_M
How is a registry value a bug?
Posted on Reply
#4
Mathragh
Dr_M said:
How is a registry value a bug?
It is as much a bug as any other software bug. A registry value is just a bug that coincidentally can be fixed by the user as well, something that isn't possible for most bugs hidden from view in the code of a program itself.
Posted on Reply
#5
Mathragh
It is as much a bug as any other software bug. A registry value is just a bug that coincidentally can be fixed by the user as well, something that isn't possible for most bugs hidden from view in the code of a program itself.
Posted on Reply
#6
Dethroy
It is not a bug. It simply is a feature that has been implemented due to external GPUs becoming a thing (even if minor). Leaving the registry value set to enable said feature was probably just an oversight of their part.
Posted on Reply
#7
Fierce Guppy
Breit said:
...and they need 7 driver versions (.75->.82) and a 300MB download for flipping that bit. o_O
Yeah. Supplying a tiny .reg file for download would have sufficed.
Posted on Reply
#8
Rich Riedl
Fierce Guppy said:
Changing HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesnvlddmkmSurpriseRemovalSupport from 1 to 0 and rebooting also fixes it.
Is that for all nVidia GPUs (internal and external) or just the internal fixed GPUs.

If it's for all, and you don't have an external GPU, simply set the flag and be done with it. If you have an external GPU, however, you still need the 'remove device' capability.

That could explain the size, since the discrimination of internal and external GPUs may have had to be re-thought and implemented in a different way.
Posted on Reply
#9
Serpent of Darkness
Dr_M said:
How is a registry value a bug?
Take a look at this as an example:

If NVidia decides to put in this in your registry during a Driver Update:

Changing HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesnvlddmkmEnableNukeComputer.ini, and it's in your registry, it becomes active when you log into Windows 10, originally it was set to 0, and they decide to set it to 1 in a patch update in an attempt to blow up your graphic card because they don't like you, you can look at that as being a very bad bug. The end result is NVidia trying to nuke your graphic card in my twisted, hypothetical scenario. On the more realistic side, it's probably more of a software implementation oversight on their end. They added this feature to the recent updates, but they forgot to set it to zero initially. It's caused some issues for consumers who don't understand it's function, used it, and it caused problems. Thus, you have a registry bug of snafu. This is NVidia's way of saying, well, we made a boo boo. Let's fix it.
Posted on Reply
#10
Caring1
Dethroy said:
It is not a bug. It simply is a feature that has been implemented due to external GPUs becoming a thing (even if minor). Leaving the registry value set to enable said feature was probably just an oversight of their part.
The oversight was not allowing for morons that thought ejecting the GPU should be done.
Posted on Reply
#11
Primey_
Breit said:
...and they need 7 driver versions (.75->.82) and a 300MB download for flipping that bit. o_O
The hotfix being so large is probably because all hotfixes also include the installer for physx, geforce experience, 3d vision etc. Can't explain the huge version jump though lol
Posted on Reply
#12
R-T-B
Caring1 said:
The oversight was not allowing for morons that thought ejecting the GPU should be done.
If you have a high sensitivity mouse and many removable storage devices, misclicking is a legit issue.

Fortunately, it does almost nothing even if you do.
Posted on Reply
Add your own comment