Download: GeForce Hotfix Driver Version 398.18

Published by

Click here to post a comment for Download: GeForce Hotfix Driver Version 398.18 on our message forum
https://forums.guru3d.com/data/avatars/m/260/260048.jpg
"397.93" Hotfix for a previous driver?
https://forums.guru3d.com/data/avatars/m/254/254827.jpg
cryohellinc:

"397.93" Hotfix for a previous driver?
Yeah that's a strange description from nVidia but this driver has a newer branch r397_91-11 (398.11 was r397_91-9) so one would assume that the fix wasn't included in 398.11
https://forums.guru3d.com/data/avatars/m/260/260048.jpg
Vidik:

Yeah that's a strange description from nVidia but this driver has a newer branch r397_91-11 (398.11 was r397_91-9) so one would assume that the fix wasn't included in 398.11
That's odd indeed.
https://forums.guru3d.com/data/avatars/m/242/242471.jpg
And that shitty nvcontainer glitches??
data/avatar/default/avatar22.webp
Maybe drivers 397.93 leave some files/settings behind that cause issues and this fixes.
https://forums.guru3d.com/data/avatars/m/254/254827.jpg
EdKiefer:

Maybe drivers 397.93 leave some files/settings behind that cause issues and this fixes.
Or maybe they had this hotfix ready or in testing for quite some time even before 398.11 was out and they simply forgot to change the release notes. Whatever. It works as good as any other driver so it doesn't really matter IMO:)
data/avatar/default/avatar21.webp
Yeh, we never get the full change list of fixes, does seem weird its only 1-2days from 398.11
https://forums.guru3d.com/data/avatars/m/245/245409.jpg
Installed this one after 398.11 kept causing "CTXFIHLP" conflicts at shutdown/reboot. Never had that issue before. Did the DP firmware update as well and all looks good. This hotfix doesn't give any process hang issues at shutdown, so far. Firestrike and WD2 performance in line with previous 397.64
https://forums.guru3d.com/data/avatars/m/239/239932.jpg
I had that black screen issue :-/ I ended up reinstalling windows because last known good config wouldn't work and safe mode also crashed when I tried to get rid of the driver. I'll be staying on 397.64 for a while.
data/avatar/default/avatar22.webp
Dragondale13:

Installed this one after 398.11 kept causing "CTXFIHLP" conflicts at shutdown/reboot. Never had that issue before. Did the DP firmware update as well and all looks good. This hotfix doesn't give any process hang issues at shutdown, so far. Firestrike and WD2 performance in line with previous 397.64
if i remember right... ctxfihlp are creative file and you can disable this from initialization without problems
https://forums.guru3d.com/data/avatars/m/272/272909.jpg
Is this one WHQL certified? I think it is only a hotfix..
data/avatar/default/avatar30.webp
Dj_ALeX:

Is this one WHQL certified? I think it is only a hotfix..
No, Its listed in GPU-Z as Beta.
data/avatar/default/avatar11.webp
This driver and the last changed something. My nvidia inspector multi-display power saver was working good at 174hz p8 low power state. 398.11 and this hotfix 398.18 looks like the voltage isn't the same value on p8 state it keeps changing every time I look at it. Up and down anywhere from 0.825v to 0.874v
data/avatar/default/avatar32.webp
Voltage is nice an smooth here 0.850v with GTX970.
data/avatar/default/avatar12.webp
EdKiefer:

Voltage is nice an smooth here 0.850v with GTX970.
Voltage aside, have you used really high hz on these past couple drivers in p8 state? -.-
data/avatar/default/avatar02.webp
I'm so confused. Does Windows 10 suffer from this or not? It says it's only for Windows 10 and then says Windows 10 doesn't have this issue.
https://forums.guru3d.com/data/avatars/m/242/242471.jpg
squalles:

if i remember right... ctxfihlp are creative file and you can disable this from initialization without problems
that file is responsible for auto headphone detection, although I never had a issue with it.. Ok except one time when I upgraded from win8.1 to win10? but that turned out to be windows glitch.. It didn't work as intended and never detected when I connected my headphones. Made a thread here once, the only fix was to refresh windows back then.
data/avatar/default/avatar32.webp
jdc2389:

Voltage aside, have you used really high hz on these past couple drivers in p8 state? -.-
no, I am on a 60hz Dell display, so maybe that is it. I remember at one point above 120hz would crank up the clock, not sure now.
https://forums.guru3d.com/data/avatars/m/242/242471.jpg
So far no nvcontainer bug yet, will see how it goes now with this set.. EDIT: ok nvm, spoke too soon., Watched vlc player, closed it then wanted to turn off pc and ....?!! https://s6.postimg.cc/8h34ujim9/-_-.png 😡
data/avatar/default/avatar07.webp
Hotfix stands metaphorically for something like fix, but that was a real hot... fix.. the other day i was trying to open my windows laptop, to work with few other programm and get my work done.. when suddenly i realise that the first inhales of my laptop where like dragon's breath.. Damn hot. Laptop crashed hundreds of times while i was drawing in my deadline and had to figure out what is going on.. getting out my screws to take out, and rescue my hard drive, it was like magma stroke.. hitting the heart of my data.. So while i was preparing for my laptop farewell, or crossing fingers for the least, happened that i try for safe mode and worked.. god bless the fancy packages! Just an experience of that hotfix-like issue