FatBoyNL Posted October 12 Share Posted October 12 My ASUS B650E-E Gaming WiFi shows a "CPU VDDIO / MC Voltage" of 1.424V in BIOS > Monitoring section. In AIDA64, a single "VDDIO" voltage value of 0.712V is shown under Computer > Sensor - Voltage values. The VDDIO value reported by AIDA64 is exactly half of the VDDIO value in BIOS, which I don't think to be a coincidence (but I could be very wrong though). So my question is: what exactly is "VDDIO" voltage supposed to represent in AIDA64? BTW I was actually searching for a way to display memory and memory controller voltage values in AIDA64. This seems to be my best bet though. Attached both BIOS & AIDA64 pics for reference. EDIT 1: Just confirmed my alleged assumption on this 'VDDIO - halved voltage' issue by disabling EXPO in BIOS: "CPU VDDIO / MC Voltage", which gives 1.100V in BIOS, but which results in a "VDDIO" voltage output of just ~0.560V in AIDA64. EDIT 2: It seems that "VDD Misc" voltage is also being misreported in AIDA64. It shows 0.552-0.560V in AIDA64, but is reported as 1.100V in BIOS (same value for EXPO ON or OFF btw). Quote Link to comment Share on other sites More sharing options...
FatBoyNL Posted October 25 Author Share Posted October 25 As a workaround, I decided to add two Correction Items for VDDIO and VDD Misc by using a 2:1 ratio on both. This shows perfect results (in my book): Notes: - Purely cosmetic: Renamed (default) "VDDIO" to "VDDIO / MC" to be in-line with (ASUS) BIOS voltage monitor tab. - VDD Misc is fluctuating between 1.104~1.120V, which corresponds with (ASUS) BIOS readings for VDD Misc. - EDIT: Also lowered SoC Voltage from 1.22 to 1.20 in between screenshots btw. Quote Link to comment Share on other sites More sharing options...
FatBoyNL Posted October 26 Author Share Posted October 26 Just installed HWinfo64 in order to look into this issue. HWinfo64 seems to confirm my findings and shows the correct voltage values by default: Quote Link to comment Share on other sites More sharing options...
FatBoyNL Posted November 23 Author Share Posted November 23 Unfortunately, the last few (beta) updates didn't solve this issue 😢 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.