m17 R4, AWCC fusion CPU/RAM monitors broken

Question

Ok so here's the issue I'm dealing with. About 2 weeks I opened a support ticket looking for a solution to fix my m17 R4 that wasn't showing the CPU nor RAM monitors in the AWCC fusion tab. I know AWCC has had some issues in the past that may be solved by uninstalling with revo Uninstaller and reinstalling, but I've done that many times, even with frequent restarts, and it did not work this time. The chat support lady was very nice and tried to help, uninstalling and reinstalling various things, to no avail. Eventually she had me do a hardware self-test on it through the BIOS iirc, and all components passed. Well, after that the CPU and RAM monitors were still not showing up, so they decided to send a technician out to my place to replace the motherboard, thinking that it was a hidden hardware issue. Well, after the motherboard replacement, the CPU and RAM monitors were still not showing up, it had the same issue as before. So, before opening another support ticket, I decided to try uninstalling the latest version of OC controls with revo uninstaller and reinstalling the previous version. This actually worked... about halfwAWCC RAM monitor locked at 13818MHZ.ay. The CPU/RAM monitors  did come back, and the CPU is showing normal, but now the RAM seems normal for about a minute then it spikes and locks at 13818 MHZ. If i close the laptop and reopen it it will show normal at 2300ish MHZ for maybe a minute before re-locking to 13818MHZ.  Also, updating to the latest version of OC controls makes the CPU and RAM monitors go away again. I'd open another support ticket to report the bugs there but the support chat has been too busy to take any new chats for the past few days, so I decided to post here.

RPT943 · Accepted Answer

I managed to fix the CPU and RAM monitors not showing up on the latest updates for AWCC and OC controls. a Dell-cares mod asked me to verify the windows version using win+r and typing "msinfo32". while i was here I just so happened to notice that virtualization-based security was turned on and running. so I thought that was odd because i thought i already disabled VBS through core isolation

i turned off virtualization/virtualization-based security by

hitting the windows key and the search bar,

typing "turn windows features on or off",

unchecking "virtual machine platform" and "windows Hypervisor platform" and pressing OK

after a restart everything was fixed and back to normal!

Alienware

Was this post helpful?