If you've noticed some increased fan noise recently, this could be the culprit. That might not sound like a lot, but is enough to likely start some fans spinning more than they should and making a racket in your rig. The error is reported to suck up 10-15% of your CPU resources, sometimes even more. This issue with Nvidia's drivers is less catastrophic, but still an annoyance if your CPU's resources are being unnecessarily taken up by the Nvidia Container software after you've quit a game. A long road to travel because of a mixup between AMD drivers and Windows' determined update process, but one that at least has a resolution.īest CPU for gaming (opens in new tab): The top chips from Intel and AMDīest gaming motherboard (opens in new tab): The right boardsīest graphics card (opens in new tab): Your perfect pixel-pusher awaitsīest SSD for gaming (opens in new tab): Get into the game ahead of the rest Startup repair reportedly made things much worse, but doing a system restore to a previous restore point made things functional again. That's easier said than done, as Chacos had to mash the power button on fifteen different boots before they actually managed to get it recovering. That should encourage an automatic recovery event, which in turn allows you to select from some advanced options to sort out your system. The workaround, which arose from a painstaking back and forth with AMD engineers, is to hit the power switch on your PC in the split second in between the BIOS keypress options screen and the spinning Windows logo appearing.

AMD workaround: Uncheck the Factory Reset box on installation of the new drivers or, if your system has corrupted, spam the power switch on bootup to force an automatic recovery event.Nvidia workaround: Either revert to an earlier driver or use Task Manager to End Task on the Nvidia Container entry.How do I fix the latest GPU driver issues?

Radeon update