How would one acquire a Hwinfo debug file?
Had stuff to do lately so haven't had much time to tinker for hours with cpu stuff. But i noticed on prime95 small FTT test version 26.6 it crashes after like 20 mins, so i'm back again lol.
I tried restarting hwinfo as well as my pc, nothing changed. Cpu-z reports "core voltage" but since my mb is an z87-k, that is most likely just the same "VIN4" reading that HWInfo provides, although they differentiate a bit. Like hwinfo reports 0.832v but cpu-z reports 0.888v. And even tho cpu-z refreshes less often than hwinfo, over a 10 sec period the 0.888v barely changes while hwinfo keeps changing near 0.832v so it's pretty clear there's a difference. I however read that if you disable SVID control, which i had disabled for years, then u won't get a vcore reading from the external voltage regulator. Well I enabled it and i still don't see any vcore reading, so maybe it just doesn't really do anything since the mb has an intertal voltage regulator so the external voltage regulator is useless, making all the bios options about it like SVID Control or Thermal Feedback just dummy options that do nothing. That's my theory anyway, maybe i'm wrong. I could not find much if at all about this in google. so nothing to disprove it so far. So here are some more pics of the differences between readings
I have Spread Spectrum disabled (always have), and my blck multiplier as well as "initial blck frequency" set to 100, cpu strap is set to 100 and ratio is set to 100:100. As such i'm heavily inclined to believe cpu-z over hw info on these reportings, especially since task manager also reports core clocks very close to those of cpu-z. So that means smth with hwinfo is wrong, so i'm waiting for instructions now how to get a debug log.
On another note, is VTT voltage as shown in Hwinfo just cache/uncore voltage? Because i have cache voltage set to 1.1v with 39 multiplier, and vtt voltage is the only one resembling anything near 1.1v
although i cannot understand why it remains static. If vin4 is my vcore, it goes down to like 0.8v when there is no activity, so there is power saving. But why is VTT the same always static? Is it not cache/uncore voltage? I googled about VTT but how could find little info and it was all very confusing, apparently it's a very old reading since most topics are from like 2012 and earlier. Then again my cpu was made 2013 so not old at all in regards to it, but still. Tho, if we are to judge by all the incorrect reportings hwinfo reported, i wouldn't be surprised if this one is off as well. Still doesn't explain why it's static though, unless it's not cache/uncore voltage and that one is just not shown.
After i started prime95 small ftt test, vtt jumped from 1.112 to 1.120 V, so it's not completely static it seems.
During prime 95 test, the core voltage remains at 0.912V in cpu-z, yet increases to 1.304V in hwinfo, i have it set to 1.24V in bios yet i also have very aggressive LLC so that could explain why it goes higher, but still weird that now cpu-z is the one missreporting, since there's no way the core voltage is still at 0.912V under full stress test. This is all very confusing and i can now see why they dumped internal voltage regulators... However judging by the fact that hwinfo has been misreporting other values, i wouldn't be surprised if the Vin4 reading is shown more (or less) than it actually is just because it's being incorrectly reported. Like obviously, the reading itself is not necessarily exactly the same as the vcore reading, but it's clear that it's the cpu voltage, but what i'm saying is, hwinfo is not reporting the same value as the value that the motherboard is giving. Because the mb is giving 4200 mhz as shown by cpu-z and 4.18ghz as shown by task manager, yet hwinfo is reporting 4130 so it's not reporting what the mb is reporting.