nVIDIA GeForce Hotfix Driver v398.46

This is GeForce HotFix driver version 398.46 that addresses the following:

- Black Textures in Wolfenstein II: The New Colossus.

It can be accessed here:

http://nvidia.custhelp.com/app/answers/detail/a_id/4684

Make a system image before installing this if you are feeling brave to try them

@Papusan @Mr. Fox

 

No NVIDIA hotfix driver I've ever installed has been digitally signed.

 

I’m on longer vacation bruh And yees, I won’t be first in the row to test it You still have warranty? Then be my guest.

 

For OP https://forums.geforce.com/default/...vers/announcing-geforce-hotfix-driver-398-46/

 

I can confirm that there is a problem with this driver.
When installing normally it says that it has installed, but actually it did not.
When you disable driver signature enforcement it will install, however after rebooting Windows it will eject the display adapter.
Cleaning it with DDU and installing stable driver resolved this issue for me.

 

I don't install any GeFarts drives except for @j95 mods. Period. I haven't found good a reason to use an NVIDIOT driver newer than like 388.XX yet.

 

Try j95's debloated Nvidia Vulkan development driver 397.96. Its better than WHQL driver. I'm enjoying it. I can OC more and also overvolt.
You can OC a little higher with this driver.

 

hmm works fine here thanks for the heads up



This is while Overwatch was on with 240Hz(237fps) G-Sync on.

 

Update: (Date: 07.07.2018) Nvidia has re-released their 398.46 hotfix to resolve a situation where Windows 10 1607 and higher systems with secure boot enabled are rendered unbootable, or blocks the installation with a digital signature error.
http://www.guru3d.com/files-details/geforce-398-46-hotfix-driver-download.html

 

Is it a crime I'm still using j95's debloated Nvidia Vulkan development driver 388.84? For all the games I tested with this driver only assassin blackflag(2013) is showing a problem in game w/c is slight flickering.

 

How in heaven's name do you OVERVOLT pascal?
You are limited to 1.062v. And this is a vbios limitation....

Pics or it didn't happen
Please?
Pretty please?

 

I have maxwell GPU 980M BGA only. My card is worst than avg. ASIC quality from Dell ASIC Quality: 53%
At stock clocks it consumes 1.075V at 1126MHz(Boost) and 1250MHz(Mem). OC to 200/200 with +50mV will take TDp to 118W at max 80C.
Judal57 is waiting for AGA with GTX 1080Ti on 15 R1. Hopefully he can find some mods and share with you.

 

Oh you're on maxwell.
Those are only partially castrated by Ngreedia.

 

No, it is not a problem. It makes sense to continue using an excellent driver. Unless or until a problem occurs, there is no reason to update drivers. If it works great, it doesn't matter even a little bit how old the driver is.

 

I'm using a debloat 398.46 build so none of that GFE and telemetry bs. Just driver, audio, and physx.

Been playing a lot of Ni no Kuni II while streaming and ran solid for hours. I think 3 builds ago I was having problems with it being stable while I streamed. This is with G-Sync enabled borderless getting about 100-200 on average 150fps in game maxed out on 240Hz monitor. Overwatch plays smoothly as well as Realm Royale. Havent played much of any other games yet.

 

no crime at all, im still rocking j95´s 388.13

 

388.71 is very good if you're on older versions of w10 aka before spring update v1803.

 

thx for the headsup, im actually still on W10 1709 but gonna do a fresh install soon, havent decided yet on either 1803 or maybe enterprise LTSB...

 

I was on v1703 then jumped to v1803. I like jumping higher versions.

 

Don't bother with 1803 if you're on 1709. You're only asking for trouble. (Seriously, it's the worst Windows 10 build so far)

 

When I was testing 17025 it was perfect and didn't have these issues like 17134. Dunno what they did to nicely working software.?

 

1803 doesn't even connect my wifi automatically upon a restart, tried different drivers, I have to manually connect each time even though the connection is set to Auto Connect. I posted this on the My Digital Forums and everyone is experiencing this and there is no solution. Such basic stuff not working in an OS seriously make me hate computers, Windows, Microsoft even more. I am this much close to sell all my crap and switch to an Apple Macintosh Turdbook and be done with it.

 

I don't have that issue. But the same issue was present after in-place upgrade to latest version.
Make sure WLAN auto config, WWAN services in services.msc are set to Automatic instead of Manual.

 

That is weird, I've never run into the auto connect issue you mentioned @Phoenix, funny enough I helped someone with a similar issue on MacOS, it had its own WiFi connectivity quirks a year or two ago which took some time to get fixed.

Did you install the INF only or the full ProSet softare. If you use ProSet that takes over from MS WiFi. Never had issues with ProSet at least for me, so it maybe due to Win WLAN config therefore try full ProSet rather than inf only.

With mobile/tablet being more profitable sales wise I expect desktop side to continue to take a backseat development wise when compared to resources in mobile. Server/Cloud->Office->XBox->Windows, I believe that was their profit order from 1st through 4th in 2016 with Windows only generating 10% revenue out of the total. No wonder they reorganized and started pulling resources from Windows.