Recent content by falkentyne

This sounds like a hardware techsupport issue. I don't think you're going to get much help here with this as this has nothing to do with HWinfo. Could be any number of causes. I'd blame either video card or motherboard for this. The fastest way you can determine if the videocard is faulty is...

Asus EC has resolution down to 1mv on vcore and 1A reporting, and 1W on POUT. (You can see these values on Asus OCTool "Raw VRM"). I am pretty sure Asus EC Field in HWinfo uses these values also (though I have Asus EC disabled due to latency polling issues, similar issues happen when Raw VRM...

Was WHEA error monitoring removed in this version? Having trouble finding it for my Stockfish testing.

The 69269 VR should be software accessible, as it was on Z490 and Z590 boards, unless MSI is blocking ports again for some reason.

Ok so it looks like just changing all of the values together from "column 1" to "column 2" fixes the default spacing. So something is wrong with "column 1". Basically, setting any value in column 1 seems to be too close to the next one even if you set the next one to column 2. But trying...

Martin, in the newest beta, the RTSS OSD fields are messed up. This only started in 4675 beta. I can't align it anymore without actually skipping vertical rows. Here is it in the previous version.

NVVDD2 input power (sum) is GPU Chip Power + SRAM input power. GPU Chip Power is the very top "GPU Core NVVDD input power sum" right below Total board power. GPU Chip Power, at least on 2x8 pin cards, is Misc0 + Misc2 + NVVDD1 input power (sum) I am unsure what the sum is on 3x8 pin cards.

Pretty sure it was because of MSI's completely broken die sense readings, differing whether you had VCC_Sense or Socket Sense enabled in BIOS--which should, on properly working boards like Asus Maximus, ONLY affect the Super I/O Vcore readings, and not affect the VRM readings at all. But on...

Yes it's working perfectly on 471.11. Now I can monitor my GPU power again without running out of memory slowly!

Try increasing the loadline calibration level, CPU Core voltage slightly, or reduce the cache ratio slightly. Possibly the auto voltages on that board are too lenient for the default loadline settingss. Were you playing Minecraft or RDR2 or Ghostrunner or something?

Hi Martin, I looked at his readings and there's definitely something off. I doubt it's anything to do with hwinfo. Has to be something causing the VRM to report strange readings, because it's impossible for for a 5.3 ghz HT off 10900k to report anywhere near that low of 109 amps at full load...

Hi @Martin Small bug with 4380. Seems like tooltips get automatically enabled when you install it (causing a tooltip over every field). However, when you disable tooltips, you still get nonstop tooltips over the bottom icons, and they won't go away at all. Should be an easy fix :)

I asked bmgjet to get back to you but I don't know how he will contact you.

Oh it's functions that are apparently "disabled" for some reason (i am not the person who took that picture). Thank you Martin. Effective (real) GPU clocks will help show people why they get low scores sometimes.

Thread here: https://forums.guru3d.com/threads/rtss-6-7-0-beta-1.412822/page-141#post-5872225 Code is: "NVENC Clocks (Current Clocks)" string.format("{0} ({1}) MHz", nvapi.clocks.current.nvenc_clock, nvapi.clocks.current.core_clock); You can test effective clocks vs requested clocks for...