M mididoc Well-Known Member Nov 30, 2011 #1 hi martin, since one of the last builts hwinfo64 reads wrong voltage og xmp profile of our ram. the voltage right is 1.65 volt and not 1.4 volt. debug attachement
hi martin, since one of the last builts hwinfo64 reads wrong voltage og xmp profile of our ram. the voltage right is 1.65 volt and not 1.4 volt. debug attachement
Martin HWiNFO Author Staff member Nov 30, 2011 #2 Thanks for the report. It reports the Memory Controller desired voltage level instead of DIMM. This bug will be fixed in the next build.
Thanks for the report. It reports the Memory Controller desired voltage level instead of DIMM. This bug will be fixed in the next build.
M mididoc Well-Known Member Nov 30, 2011 #3 Martin said: Thanks for the report. It reports the Memory Controller desired voltage level instead of DIMM. This bug will be fixed in the next build. Click to expand... ok thanks. (reading was right in older versions.) btw the 1.4 volt are for nothing, this is a non supported value. xmp=1.65 all other jedec =1.5
Martin said: Thanks for the report. It reports the Memory Controller desired voltage level instead of DIMM. This bug will be fixed in the next build. Click to expand... ok thanks. (reading was right in older versions.) btw the 1.4 volt are for nothing, this is a non supported value. xmp=1.65 all other jedec =1.5
Martin HWiNFO Author Staff member Dec 1, 2011 #4 Yes, the bug slipped inside when I updated support for XMP for v1.3 1.4 V reported is the Memory Controller voltage - the BIOS is instructed by XMP to request this voltage to the IMC when this profile is used. Next build will have this fixed.
Yes, the bug slipped inside when I updated support for XMP for v1.3 1.4 V reported is the Memory Controller voltage - the BIOS is instructed by XMP to request this voltage to the IMC when this profile is used. Next build will have this fixed.
