Enabling SVM caused AMD graphics, browser, and network problems after reboot
Asked by
MellowPine47
After enabling SVM in the BIOS so I could use a game anti-cheat, my Windows 10 PC started behaving strangely. My monitor colors and refresh-rate options reset, AMD Adrenalin would not open because the driver and software versions did not match, and neither Brave nor Opera would launch. Device Manager showed my Radeon 9060 XT with Code 52, saying Windows could not verify the driver's digital signature.
I temporarily fixed the display driver using a Code 52 tutorial, which restored AMD Adrenalin, my color settings, and refresh-rate controls. However, the browsers still failed, the system became noticeably slow, and my network connection began dropping out. After restarting, all of the original display problems returned, including the Code 52 warning.
So far I have reverted the SVM setting, removed the Radeon adapter, installed the Microsoft Basic Display Adapter, uninstalled AMD Adrenalin, and removed and reinstalled Brave. I also tried using DDU to wipe the graphics drivers. The network sometimes returns after Windows troubleshooting, but the display driver works only until the next reboot. Disabling and re-enabling the adapter has the same temporary effect.
What is the best way to permanently repair the driver-signature error and restore the graphics, browser, and network functionality?
Answers
The symptoms point primarily to a corrupted or improperly installed AMD display driver, not SVM itself. Use DDU from Safe Mode, disconnect the internet temporarily so Windows Update cannot install its own driver, then install the latest Radeon driver downloaded directly from AMD. Use the clean-install option if the installer provides it, and reboot before reconnecting to the internet. Also check that Windows is not showing a second display driver under hidden devices.
Reply to this answer
Code 52 means Windows is rejecting the driver’s digital signature. Before reinstalling, check that Secure Boot and other BIOS security settings were not partially changed, and make sure Windows has the correct date and time. If the error returns after a clean official driver install, run `sfc /scannow` and `DISM /Online /Cleanup-Image /RestoreHealth`, then test with a System Restore point from before the BIOS and anti-cheat changes.
Reply to this answer
Because browsers, networking, and graphics all became unstable, I would not keep applying random fixes or driver videos. Back up important files first, remove the anti-cheat temporarily, and test Windows with a clean boot. If the display driver still comes back as Code 52 after DDU and the official AMD package, an in-place Windows repair install is safer than repeatedly disabling signature enforcement. That can repair damaged system components while keeping your files and applications.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Related Discussions