Recent content by KuraiShidosha

Easy solution. Rename menu showed a mismatch and it was simple as clicking Set Original. I'm guessing in the code, Ethernet # device gets an initial entry, then if hardware is swapped and the new adapter occupies the same "slot" internally, it maintains the same given name.

I have a Windows install that I've been using for awhile even through hardware swaps, and I just noticed tonight that my latest motherboard's Realtek network adapter is coming up as my old motherboard's Intel I219-V NIC. Pic: Any ideas?

It did, it's back to normal now.

I reverted to v8.26-5730 and the issue is gone. Temperatures on both DIMMs are accurate and rock solid. All this in the same boot cycle.

Thanks for the quick answer Martin. If anyone here knows how to modify that in RTSS I'd appreciate it. Otherwise I'll likely still go ask on their forums. Also instead of making another thread I guess I'll ask here. When I'm running Shared Memory and monitoring it in game, I see random sensors...

This is kind of one part of a two part question, that could be its own thread. I'm using HWinfo64 Pro licensed with Shared Memory enabled so I can export sensor data to Rivatuner Statistics Server for in-game OSD monitoring. I noticed that changing polling rate in HWinfo64 does not affect the...

Bingo, you were 100% right. The AURA LED Controller must have been keeping that USB controller alive because once I disabled the power down option in that USB3.20 controller, disabling the AURA LED Controller does not cause the temperature sensor from disappearing. Great to know! Thanks man glad...

Figured it out! I had apparently disabled the "AURA LED Controller" under Universal Serial Bus devices menu in Device Manager some time ago because I don't use RGB lighting on my setup, I prefer it to be fully dark. Once I noticed the weird behavior of running OpenRGB causing the Chipset 1...

I didn't think I would bump this again, figuring since the problem happened in the Asus AI Suite that it surely is not a software problem but rather a hardware or BIOS one, but here we are again with a truly bizarre discovery. While checking the Chipset 1 probe in HWinfo64 immediately after...

Installing this Asus software gave me an interesting insight into this problem. When I check the sensors immediately after booting up, it shows the Chipset Temperature accurate to what the BIOS reports. Pic proof: However, after a few sensor update cycles have passed, suddenly the Chipset...

Sadly same result with this build.

Yes, it is called Chipset Temperature in this photo.

I'm running the latest version of the BIOS. I recently swapped motherboards, from an ASRock X670 to this Asus B650E-F. The X670 only showed Chipset 2 temps, Chipset 1 was missing. Now on this B650E-F, it shows nothing. I'm not sure what else could be going on here.

Sorry, here it is.

Hi, I need to bump this thread because the same issue is still present with Asus B650E-F on the latest beta of HWinfo64, v7.67-5285 as of 12/8/2023. I double checked, it isn't hidden (I only hid RTSS.) Any ideas?