nVIDIA Graphics Drivers v361.75 Findings & Fixes

Download

Game Ready
Learn more about how to get the optimal experience for Rise of the Tomb Raider and Tom Clancy’s The Division (Beta)

Gaming Technology
Beta support on GeForce GTX GPUs for external graphics over Thunderbolt 3

There is a bug in these drivers where you would see in the taskbar / safely remove hardware icon, that you can now remove your nVIDIA GPU (LOL).

The 'Eject GPU' item can be completely removed by going to the following reg key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvlddmkm

Then change the value of SurpriseRemovalSupport to 0, then reboot.

Note: You will only find this reg entry IF that bug affects your system, if you don't see it, then good, just forget it.

 

did they fix the boot loops with the modded vbios?

 

will test and see soon enough

 

fingers crossed!

 

My scores in both 3DMark and 3DMark 11 went down by 5% vs the trusty 359.00 Driver.

Going back

 

Heh, so did they fix it or not? I'm still on 359.00

 

fix what?

 

can it be used with prema's v1.1.1 modded vbios?

 

Doesn't seem to work. Personnaly modified vbios by prema => black screen. Have to go back to 359.00

 

grrrr.....no idea why they do this!

 

@Mr. Fox @Ethrem @Prema

Users on other forums reporting that this driver has a bug where it shows you in the safely remove icon in the taskbar that you can eject/safely remove your graphics card while the system is running!

Can someone who has any contact with nVIDIA management tell them to post a notice at the nVIDIA Headquarters saying "Please do not smoke white horse while developing new drivers"

Classical nCRAPIA swiss cheese

 

361.60 was the first I could use with my Lenovo without black-screen. These also work fine.

*This is on a Lenovo Y-50-70 Touch GTX 860m (Maxwell).

 

if you run stock vbios and i don't.

 

i have svl7 on my 880m's and all updates and drivers works good ! i dont know why it does not work with u

 

May have something to do with Thunderbolt 3 EGPU ejection,code seems to recognise internal pcie GFX as external,they did say its beta support maybe thats why

On a side note,this EGPU thing seems to be real after all,and not a hoax

 

Confirmed as being buggy detection for eGPU.

Unfortunately I don't have my spare GPU any more, but can anybody with 2 desktop Nvidia cards (non-matching is fine) see what happens? I'm curious to see if they've implemented all the Optimus logic (ie Optimus GPU selection per app, across screens connected to either GPU etc) between dedicated GPUs as this will directly translate over to those of us with Clevo P700DM series laptops which lack Optimus but have TB3 ports for eGPU.

 

When I get home I'll try this driver on Windows 7 with my eGPU setup on my Macbook Air/Mac Mini.

Setup: 2012 Macbook Air/Mac Mini Ivy Bridge w/Thunderbolt 1. External enclosure is MagmaBox 3T w/ NVIDIA GTX 970.

 

I'll give it a go.

Downloading now...

GeForce Experience made me register before it would download it lol. Thanks nVidia.

Edit: First attempt through GeForce Experience



Amazingly, Windows 10 recovered from it and reported GFE for crashing, let me close it, and I'm grabbing the drivers from nVidia along with the latest DDU. Will report back.

 

https://forums.geforce.com/default/...eedback-thread-1-27-16-/post/4791013/#4791013

Another gem from ManuelG: it's a new beta feature for eGPU support

Wok da fok man, seriously walk the fork. nVidia drivers have truly become just as bad (or arguably, worse) than AMD's

 

Omg !! Next level crazy shizz going on here. Safely eject GPU roflmao !!

Fok these game ready drivers, wtf is going on lately are they too busy with the advertising, shield and that GeForced crap...

 

Marginal difference. No eject GPU on my system.

http://www.3dmark.com/compare/3dm11/10864452/3dm11/10843912

I should have specified that the new driver is on the left, old is on the right.

Don't bother with my physics and combined scores, my CPU does stupid garbage like throttling to 3.29GHz when being benched by a Futuremark product.

Just ran all of 2013 as well. Seems like everything is within margin of error compared to 361.43.

My system settings - stock clock 980M SLI using test version of Prema Mod, CPU - 4GHz all 4 cores, 67W TDP, 67W turbo, 130A current limit

 

kinda bummed they haven't fixed the boot loop issue yet with prema's vbios mod....where's the fix?

 

I asked Prema about a possible release since its now in a Game Ready driver. We will see what he says.

 

I hope they do, would be nice.

Sent from my HTC One using Tapatalk

 

Lol, AMD drivers are now better than nVidia. I can't get them to install on any of my Alienwares without boot loop/black screen

 

GTX760 here and finally can disconnect the eGPU without crash. Can not reconnect btw...

 

If you're using Prema's mod, it doesn't currently work with 361 series drivers.

 

Yes, using custom vBIOS on the 780Ms and 980Ms

Never had issues running custom vBIOS + stock drivers from AMD.

 

lol, you called 359.xx trusty..

 

Unfortunately it looks like there needs to be a mod update for the 361 branch. NVidia changed some code that was causing the throttle on the certain Alienware machines with 980Ms which they fixed but broke the mod in the process. Prema is aware of the issue and may have a fix but it's being tested thoroughly first so please be patient.

 

Will see if I can play the division beta and tomb raider with 359.00 drivers.

Sent from my HTC One using Tapatalk

 

Same. Can eject, but reconnect... Nah.

 

Words wisely said by an nVIDIA GeForce Forums member:

 

I wonder how much better AMD driver is by now.

 

WHA?? Prema's vbios is the problem why the Nvida 361 drivers won't install?? I know I still have my original vbios, JUST-where did I put my original vbios.

 

Stock VBIOS for the Clevo 980 GTX and 980M GTX is below, although I'm not sure it'll work on your Alienware

(Link removed)

 

playing Rise of the tombraider right now. Sooo awesome @!

 

thought i want to run OC so yeah we need prema to tweak, test, and release a new vbios.

on the default high setting it goes between 50-60fps. if i cap it to 30fps and set it to very high then it's fine. for a 3rd person game 30fps is fine.

EDIT: also the game crashed with my GPU at 1280 so i am assuming it was either the OC or just the game crashing it....no idea. leaving it at 1260.

 

Thanks for the post, but lucky for me I kept a backup of my original vbios.

 

Would love to be playing Tomb raider, but can't stop playing Fallout 4. Playing at 150+ hours and a bunch of mods. It's like a drug

 

I hitabout 160 hours in FO4 and Still haven't beaten the game, but I assume I'm close, but I got bored.

I'm really just waiting for XCOM2

 

Rise of the Tomb Raider is really good fun and runs nicely as well. It's pretty demanding but performance seems consistent.

 

I removed that link for the stock vbios - flashing a G-sync BIOS to a non-Gsync card is a big no no.

Prema has stock vbios on his site.

Good to see that Tomb Raider is working fine with the old drivers.

 

Thanks for doing that, I didn't know that, I thought there was a G-SYNC/Non G-SYNC BIOS for the motherboard, that was the only thing to worry about but not the actual VBIOS. I was under the impression that they are the same and the Motherboard BIOS must be flashed according to G-SYNC or non G-SYNC

 

No, you can trash the card if you flash the wrong vbios. Prema has a different version depending on if the machine has G-Sync or not.


Well so far these drivers actually appear to be pretty stable. I was having problems with Hyperdimension Neptunia but when I realized it was OpenGL, I went and forced maximum performance for the game, disabled SLI, and forced vsync. No more TDRs since I did that but Heaven runs in both DirectX 11 and OpenGL mode without issue, 3DMark doesn't crash or do any other stupid behaviors, and I haven't gotten a single desktop TDR yet whereas I was getting them occasionally on 361.43.

 

Do you have the eject GPU bug in the taskbar safe remove icon?

 

Nope.

 

LOL. Does it even do anything when you hit eject, for those who had that ?

 

@hmscott @Ethrem @woodzstack

The 'Eject GPU' item can be completely removed by going to the following reg key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvlddmkm

Then change the value of SurpriseRemovalSupport to 0, then reboot.

Note: You will only find this reg entry IF that bug affects your system, if you don't see it, then good, just forget it.

 

Your keyboard opens and GPU ejects.