I have a Ryzen 5 1600AF (Zen+) and 2x 8 GB DDR4 3600 HyperX. when I select XMP1, it says 1.35V in the profile. however, when I boot Strelec WinPE USB (I’m on Fedora, I really don’t want to install windows just so I can run HWINFO), install all drivers and launch HWINFO64 it says 1.2V. so I enter BIOS again, go to Voltages and enter 1.35 manually instead of auto. no change, still reads 1.2V. the BIOS side screen shows 1.35 after reboot.
I’ve found an unresolved thread somewhere with the same problem for my board. I’m on latest BIOS.
am I missing something, is there some additional setting I need to switch so it registers? the BIOS setup is hella confusing and borderline stupid, e.g. enabling virtualization required turning on SMP (how am I supposed to guess what that is?!) that’s located in the “Frequency” subsection (wtf?!).
Here’s a Toms Hardware thread where someone had a similar issue. It may help point you in the right direction.
deleted by creator
Unless gigabyte changed it in a newer revision, that motherboard has 2 it87 chips, but you need a newer driver to see both in sensors.
deleted by creator
Yeah it does need a sensors config for your motherboard too, if you want the proper names, but I won’t be able to get mine until maybe Sunday.
deleted by creator
Here’s my sensors config: https://github.com/frankcrawford/it87/pull/12/files
- BIOS is set to 1.35
- sensors reports 1.38
- dmidecode reports 1.2
So I believe the motherboard is running my ram at the correct voltage, just the dmi is hard coded.
deleted by creator
No worries!
I believe for the driver you need to install
build-essential@development-tools(forgot about fedora) and then runsudo make dkms.
If it’s running stable at the correct speed, does it matter what voltage it runs on?
deleted by creator
If you open the sensors part of HWINFO there should be a
DIMMvoltage from the motherboard, that’s a live reading, what does that say?I’m on Fedora
Here’s a few alternatives to HWINFO I’ve used:
- CPU-X (has a GUI, and is probably the most like HWINFO but still different)
- lm-sensors (might require a custom profile for your motherboard, but can provide live temp/fan/voltage sensor readings)
- dmidecode (built in, can read the data off the dimm, but doesn’t read sensors directly)
Edit: Just realised I have that motherboard, and it’s probably why XMP stopped being stable. I’ll look into it on Monday.
Edit 2: From memory to use lm-sensors you need to use an updated it87 driver for both chips to appear, I can provide a sensors profile on Monday.
deleted by creator
