There seems to be a conflict while HWiNFO tries to access the DIMM modules, so it can't read the information.
Are you maybe using some other system monitoring or management tool in parallel ? If yes, please try to disable it before running HWiNFO if that helps.
Please check in the BIOS if there's maybe an option like DIMM Temperature or TSOD polling. If there's something like that, try to disable it and check if that maybe helps. Please let me know the result.
Thanks for the additional information.
I see 2 entries in the Memory Configuration screen: "DRAM RAPL MODE" and "Thermal Throttling". Can you please try to change these and see if it has any effect on this problem in HWiNFO ? I'm not pursuing this as a solution, it's just to prove if my theory is correct.
01-10-2013, 07:13 AM (This post was last modified: 01-10-2013, 07:36 AM by Laugh|nGMan.)
Bingo! Problem solved. Changed Thermal Throttling to DISABLED. Previous state was CLTT (Closed Loop Thermal Throttling)
Thanks a lot Martin!
Pity that i need to sacrifice CLTT. Now four Temperature sensor readings from HWiNFO64 is gone (Intel CPU #0 section - Memory Channel 0, 1, 2, 3 Rank Max ~47.0C)
Info taken from xtremesystems forum:
Quote:TS ON DIMM
TS on DIMM is a closed-loop throttling technique that offers a more advanced approach to system thermal management through the use of a physical thermal sensor to further reduce guardband present in the existing methods. The reduction of guardband has a direct and positive impact on system performance.... Instead of using power prediction to estimate the temperature of the DRAM case, TS on DIMM uses a physical thermal sensor integrated on the DIMM module to monitor the temperature of DIMM...The SMBus master is inside the chipset. The sensor acts as a slave sitting on the SMBus with SPD on a module. Physically, the sensor and SPD  can be either integrated into one package as shown in Figure 3 or separated as two stand-alone parts on a module. However, the thermal sensor and the SPD are two separate logical functions using two different SMBus addresses. At power up, BIOS read data from the SPD and initiate the thermal sensor by programming its registers via SMBus, including setting the critical threshold value. When the initiation is complete, the thermal sensor will begin monitoring the temperatures and assert the Event# signal when the temperature of the sensor exceeds the critical trip point. Once the thermal sensor is initiated the system can also poll the thermal sensor via the SMBus at any time and monitor the temperatures real-time.
Thanks for the feedback. I just wanted to know whether TSOD polling is the cause of this problem and it indeed is.
Now I need to find a solution how to get SPD info working together with active TSOD polling.
Will post an update here shortly when I have s solution that needs testing...
Thanks. It seems all my attempts to temporary disable CLTT (which causes TSOD polling that interfers with DIMM SPD readout) fail and are overriden back by system...
Please try this build: http://www.hwinfo.com/beta/hw64_411_1833.zip
and post a new debug file result.
Thanks for the update.
Here's one more attempt - http://www.hwinfo.com/beta/hw64_411_1834.zip
Note that this build might cause HWiNFO to lockup. If that happens, wait a while, then try to close it via Task Manager.
Please attach a new debug file.
Then I'm sorry, but it seems the system doesn't allow me to switch TSOD polling off. I try that but it seems it's locked into this mode and that doesn't allow to read DIMM information. I'll make some more research, but currently the only workaround for this problem is to disable CLTT in BIOS.
If I find another way, I'll post an update here.
Thanks for all your feedback and testing.
I have just tested a different Supermicro machine (X9DR6-F) which has CLTT enabled in BIOS too. HWiNFO had no problems to read SPD there.
The difference I found is that on the other machine HWiNFO was able to temporary disable TSOD polling (until DIMM SPD is read out), whereas on your machine the TSOD polling mode somehow can't be disabled and it causes HWiNFO to fail to read DIMM SPD information.
My understanding is that there might be a BIOS implementation difference (either somehow locking that mode, or constantly forcing it to be enabled).
Maybe a BIOS update might fix this ?