AWCC OC Controls incompatible with Virtual Machine Platform
This is what I see when I am trying to look at my OC/Monitor settings/feature for CPU/GPU/Memory. I've seemingly tried everything. Everything was working fine yesterday, today I open AWCC and ONLY see the GPU monitor/OC feature, so I uninstall AWCC entirely, reinstall it, and this is what I have been running into ever since. I have updated BIOS, uninstalled/reinstalled AWCC, installed the AW OC controls software, etc. Running out of proposed solutions here. Anything helps, thanks!
This actually has to do with Windows Security > Device security > Memory integrity setting. After a Microsoft update, Windows security prompted me to turn Memory integrity on, when I did, I got the error messages in AWCC. So, I went and turned it off, and everything was back to normal. This is the real cause. I haven't messed with anything else as the "Solution" discusses. Hope this helps!
I went and checked and it was enabled, so I disabled it. Unfortunately the problem persists. I did update the bios right before this problem occurred yesterday, so I suspect that might have something to do with it.
@riteoushamma This was not a solution that works for me, as I work with Virtual Machine Platform on a daily basis. AWCC used to work normally with Virtual Machine Platform enabled. This Last update made it impossible.
Can't believe that's the Community accepted solution! ( maybe yes for the original poster).
(NO mention on the awcc version where the problem occurs)
When you update the bios it is wise to update awcc because they are related. The new package does all the install including AW OC controls software nothing more to my knowledge .Most of the awcc install on my r10 are in the windowsapp folder meaning the windows apps store. So may want to check the store and update whatever is needed. Yes, 5.5.8 has glitches . You may want to restart the installation package and do the repair option
What if you really need the virtual machine. what then?
Beside not all the systems are affected by the virtual machine with awcc .
riteoushamma
1 Rookie
•
8 Posts
6324
0
Posted July 22nd, 2022 21:00
Fixed this issue by disabling Virtual Machine Platform.