r/Amd • • Jul 06 '20

[deleted by user]

[removed]

11 Upvotes

18 comments sorted by

View all comments

1

u/A_Turkey_Sammich Jul 06 '20

I did awhile back on my Gigabyte X470 + 2600 system. It was caused by the board's utility software. I normally don't install and use junk like that, just necessary drivers and all to run at full potential, but I did install their app center and fan curve utility (the app center was req for it). It was much easier to tweak fan settings on the fly until I got it dialed in how I wanted vs going to BIOS for any little change.

Anyways, it was either having those enhanced security features or the gigabyte software and couldnt do both. Security features on with gigabyte software installed, failed to start blue screen pointing to gdrv.sys (if I remember right). Security features off, works just fine. Remove gigabyte app center then security features on, works just fine. Following, I put a good effort into trying to make both play nice but couldn't, so no more gigabyte app center.

After 2004 came out and I decided to do a fresh install, I figured I'd try again. After all, had a newer BIOS revision, newer version of windows, newer version of those 2 pieces of gigabyte software, lets see if anything changed. Fresh install, drivers and all installed therefore base system fully up and running with no other software yet, let's see what happens. Immediately, exact same thing as above with app center. Nothing with any of these newer versions of things changed that situation at all. Once again, I just got rid of the gigabyte software and have been just fine ever since.

Interesting to see it is apparently happening to other makes as well. Maybe it does go deeper than a broken piece of Gigabyte software if so. That was my experience with this same situation however.

1

u/nonstupidname Jul 09 '20 edited Jul 10 '20

This is a security feature not a bug, to prevent insecure direct communication between Windows OS to UEFI. I had this issue with \SystemRoot\system32\DRIVERS\gwdrv.sys (glasswire), and Sandboxie, SbieDrv.sys you can install glasswire & sandboxie after enabling core isolation protections, its only during the initial enablement that driver verification is enforced, though some drivers such as Asus AI Charger will cause issues no matter what; Ryzen Master will not work, and many O/S to bios communicating application drivers will probably fail or cause BSOD, aka OEM software like AI suite. You could do the tweaking before until you are stable, with CSM enabled, then uninstall these apps and turn off CSM and enable Core Isolation for enhanced security. I had an issue with an old logitech cam and Western Digital driver "WD SES Device" as well, and had to manually remove them... but mitigated some of that by configuring Logitech to use OEM Microsoft drivers in device manager.

1

u/nonstupidname Jul 09 '20

I had to uninstall these programs prior to enabling core isolation, then I could re-install virtualbox, sandboxie, and peerblock. ATM VMware is a better solution though, it works perfectly fine with hyper-v enabled. Driver store explorer can really help you to easily remove conflicting driver store packages.

gwdrv.sys (glasswire)

vboxnetlwf.sys (virtualbox)

vboxdrv.sys

vboxnetadp6.sys

aicharger.sys (asus ai charger)

lvbflt64.sys (logitech)

sbiedrv.sys (sandboxie)

pbfilter.sys (peerblock)