Thus, it was recommended to wait a while before switching back to an earlier version of Nvidia’s driver. However, since the problem was quite bothersome, it was probable that Nvidia would release a hotfix sooner rather than later. While Nvidia acknowledged the issue, the company didn’t specify a date for the release of a hotfix or a new version of the driver that fixed the bug. Instead, the simplest solution was to switch back to the previous 528.49 WHQL driver, which may not be compatible with some of the latest games but functioned without significant complications. However, the results of these actions were not clear, and it was not advised. Several solutions were proposed to solve the issue manually, such as blocking or deleting NvGSTPlugin.dll. Schilling tried to recreate the issue on two systems with the latest 531.18 drivers, but he didn’t experience the same problem, as he shared on Twitter. In fact, some users, like Andreas Schilling, attempted to replicate the problem but were unsuccessful. It’s important to note that not all computer systems were impacted by the Nvidia driver bug. The issue was noticed through Windows Task Manager, and a few Reddit users thought it was because of Nvidia’s Game Session Telemetry Plugin version 531.18 (NvGSTPlugin.dll). The issue was caused by the Display Container Service, which led to 10% – 15% higher CPU usage after a game was closed. The Nvidia driver bug was first discovered in version 531.18, which caused high CPU usage after exiting games. The bug’s resolution is good news for gamers and shows Nvidia’s commitment to quickly resolving issues.The hotfix addresses the Nvidia Container process that caused CPU usage to spike after exiting a game.The hotfix has been quickly deployed to users with GeForce graphics cards.Nvidia has now released a hotfix (version 531.26) that resolves the bug and a related random crash issue.Several manual solutions were suggested, but the easiest fix was to revert to the previous driver version.Not all systems were affected by the bug, and some users were unable to replicate it.The bug was caused by the Display Container Service in version 531.18 of the driver. ![]() ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |