Aikouka
Lifer
Link: http://nvidia.custhelp.com/app/answers/detail/a_id/4661/~/geforce-hotfix-driver-version-397.55
I thought it might be helpful to put a bit of a PSA out there about this driver. I recently updated my machines to Windows 10's April Update (1803) and also to the 397.31 WHQL driver. After that, I kept noticing a problem where I'd turn on the TV (the HTPC was already on), attempt to open Plex, and I'd get an error about it being unable to create the GUI. The easiest way to fix it was just to restart. This also happened on my main desktop where I was unable to open a game until I restarted. I looked into the problem a bit, and apparently, Nvidia released a driver that fixes some rather annoying bugs -- even ones that I haven't been experiencing. For example, GTX 1060 users are reporting some nasty reboot loops. In my case, I assume that the following bullet point addresses my problem:
"Windows 10: Driver may get removed after PC has been left idle for an extended period of time."
I'm not 100% sure if this is just an issue with the 397.31 driver or if it requires the Windows 10 1803 update since all of my affected machines have the 1803 update.
I thought it might be helpful to put a bit of a PSA out there about this driver. I recently updated my machines to Windows 10's April Update (1803) and also to the 397.31 WHQL driver. After that, I kept noticing a problem where I'd turn on the TV (the HTPC was already on), attempt to open Plex, and I'd get an error about it being unable to create the GUI. The easiest way to fix it was just to restart. This also happened on my main desktop where I was unable to open a game until I restarted. I looked into the problem a bit, and apparently, Nvidia released a driver that fixes some rather annoying bugs -- even ones that I haven't been experiencing. For example, GTX 1060 users are reporting some nasty reboot loops. In my case, I assume that the following bullet point addresses my problem:
"Windows 10: Driver may get removed after PC has been left idle for an extended period of time."
I'm not 100% sure if this is just an issue with the 397.31 driver or if it requires the Windows 10 1803 update since all of my affected machines have the 1803 update.
