Recent content by mnemonic

Just to chime in, that i too have the problem pop up since a few icue updates ago. Since corsair wants to also be a hardware monitoring program in which monitoring can not be turned off, it interferes with hwinfo (and i assume others) reading out sensors. Another reason never to buy overpriced...

i created a new user, started hwinfo64 there and no more sensor settings that can be found anywhere on the pc. I have to redo the complete sensor setting to my liking again. No sensorinformation to be found anywhere anymore, not in registry, not in the old user files, Bummer.

I have the i7 11700K (Z590 MSI tomahawk wifi) and just now noticed that under processor the DMI version is being reported as V4.0 16GT/s when it is only v3.0 (x8) 8.0GT/s. The "current DMI link speed" is reported correctly as being 8GT/s but the version and max speed is reported as V 4.0 with...

I don't think there is much to assume when it did not occur for a whole year on 23H2, but the very day 24H2 gets installed it happens instantly. Especially when the cpu accelerates to top frequencies, the mobo cpu sensor drops to 0°. This is an entirely different problem then when 11th gen came...

MSI MAG Z590 Tomahawk wifi (i7-11700K), it's the motherboard Temp sensors of CPU and System. Both sensors drop to 0°c on occasion when the cpu load is maximum. Don't think a debug file is going to help anything, clearly microsoft has done something to change this behavior with win 11 24H2. The...

So with the latest win 11 update 24H2 this phenomena started to appear. On heavy cpu load some motherboard sensors report as 0°c intermittently. This will be a microsoft introduced failure for sure cause it did not happen in 23H2.

hmm, it seems to have returned on cold boot, presentmon being stuck, Unless i quit and restart hwinfo sensor status, then it starts working again. So the first startup of hwinfo makes presentmon get stuck, quitting and restarting hwinfo then in turn makes presentmon report dynamic numbers...

Mainly measured Frequencies were/are affected because of virtualization. No big deal anyway.

I have some good news, today there was a new intel wired NIC driver (29.1) , installed it and rebooted. I did reboots before but that didn't fix the stuck presentmon 2.0. Now presentmon 2.0 is showing dynamic numbers again instead of staying stuck. Before this presentmon 2.0 was stuck at 339.8...

As with the new 8.02 presentmon no longer seems to work, it reports static number and no longer changes. I have discrete AMD 7900 XTX and the iGPU enabled as well. iGPU is GPU0 in windows taskmanager and AMD is GPU1, this has been so forever and did not have static numbers reported by presentmon...

I have this one ssd out of 5 that apparently has a different temperature depending on the boot. One time it's reported 5°c colder and the next boot it's running 5°c warmer. Meanwhile that specific drive (a simple data volume) is 99% idle, yet some boots it gets temp reported same as the ssd...

and to return to the same problem again after the first reboot. Another proof of what a joke those big companies really are, they just get lucky their shit even works.

A small update to this issue, By chance i discovered that the clockspeeds remain at idle (350) instead of staying at max (1300). How i got to this is because windows keeps reverting new intel igpu drivers to old versions, the only thing i did different this time instead of running the intel...

oh crap, i guess my eyes worn't wide enough yet, after opening them a bit more i noticed my obvious mistake. Apparently i mixed up some values since there are more than one. MY BAD. No, everything seems to indeed calculate correctly, i must have had a brain seizure or something.:oops:

So what i was wondering here, i have a case of gfx card oddities as for example memory power usage in watts: when gpu memory is at 1.252 Volts and 1.771 Amps then should the Watts not be 2.217 Watts instead of the 0.000Watts that gets reported by hwinfo64 ? odd stuff, and that's not the only...