Fixed : Missing 'units' from Shared Memory Support - or have I just broke something?

MintyMods

Minty
Hi Martin,

I am asking this before I have fully investigated my side as my C# debugging skills are limited...
Basically I don't think my code has changed but I no longer seem to be getting any 'unit' values populated via the shared memory interface.

For example the previous data I was getting was (includes units e.g. V & MHz) :-

JavaScript:
 { 
         "type":2,
         "label":{ 
            "value":"Core #3 VID",
            "description":"Core #3 VID"
         },
         "id":33554435,
         "sensor_index":1,
         "unit":"V",
         "value":1.2203369140625,
         "min":0.6278076171875,
         "max":1.3009033203125,
         "avg":0.742339550143509
      },
      { 
         "type":6,
         "label":{ 
            "value":"Core #0 Clock",
            "description":"Core #0 Clock"
         },
         "id":100663296,
         "sensor_index":1,
         "unit":"MHz",
         "value":4501.08,
         "min":799.024,
         "max":4504.41,
         "avg":1380.460578083666
      },

After both reinstalling Windows and upgrading HWiNFO I no longer seem to be getting any unit values (Blank Units) :-

JavaScript:
{
         "type":2,
         "label":{
            "value":"Core #3 VID",
            "description":"Core #3 VID"
         },
         "id":33554435,
         "sensor_index":1,
         "unit":"",
         "value":1.2451171875,
         "min":0.6552734375,
         "max":1.2930908203125,
         "avg":0.74424442712268235
      },
      {
         "type":6,
         "label":{
            "value":"Core #0 Clock",
            "description":"Core #0 Clock"
         },
         "id":100663296,
         "sensor_index":1,
         "unit":"",
         "value":4500.0,
         "min":799.024,
         "max":4504.41,
         "avg":1357.917695657045
      },

Sorry if the issue is simple something I have broke my end but thought I would ask in case you can help :)

Thanks
 
I have also tried renaming some units and these changes do show within the HWiNFO user interface but remain blank in what I am seeing via the SHM (via my C# code).

I do however see changes to any labels I change e.g.
{"type":2,"label":{"value":"Core #3 VID","description":"Core #3 VID - Renamed via UI"},"id":33554435,"sensor_index":1,"unit":"","value":0.6976318359375,"min":0.6552734375,"max":1.295654296875,"avg":0.771668236954061}[/CODE]
 
Can I also ask about the 'id' attribute which seems to be consistent across both the above readings i.e. Core #3 VID stays with the same id :33554435. How are these id's determined and are they constant/unique to the sensor (within the same build / across different hardware builds)?

Thanks for any info
 
Running my C# side as a standalone and the units are missing from that output:-

Code:
 DEBUG MintyServiceHWiNFO.MsmServiceHWiNFO - [email protected]#SENSOR_TYPE_VOLT
DEBUG MintyServiceHWiNFO.MsmServiceHWiNFO - [email protected]#1
DEBUG MintyServiceHWiNFO.MsmServiceHWiNFO - [email protected]#33554435
DEBUG MintyServiceHWiNFO.MsmServiceHWiNFO - [email protected]#Core #3 VID
DEBUG MintyServiceHWiNFO.MsmServiceHWiNFO - [email protected]#Core #3 VID - Renamed via UI
DEBUG MintyServiceHWiNFO.MsmServiceHWiNFO - [email protected]#
DEBUG MintyServiceHWiNFO.MsmServiceHWiNFO - [email protected]#0.66650390625
DEBUG MintyServiceHWiNFO.MsmServiceHWiNFO - [email protected]#0.66015625
DEBUG MintyServiceHWiNFO.MsmServiceHWiNFO - [email protected]#1.2860107421875
DEBUG MintyServiceHWiNFO.MsmServiceHWiNFO - [email protected]#0.752181424439406
DEBUG MintyServiceHWiNFO.MsmServiceHWiNFO - [email protected]#SENSOR_TYPE_CLOCK
DEBUG MintyServiceHWiNFO.MsmServiceHWiNFO - [email protected]#1
DEBUG MintyServiceHWiNFO.MsmServiceHWiNFO - [email protected]#100663296
DEBUG MintyServiceHWiNFO.MsmServiceHWiNFO - [email protected]#Core #0 Clock
DEBUG MintyServiceHWiNFO.MsmServiceHWiNFO - [email protected]#Core #0 Clock
DEBUG MintyServiceHWiNFO.MsmServiceHWiNFO - [email protected]#
DEBUG MintyServiceHWiNFO.MsmServiceHWiNFO - [email protected]#799.808
DEBUG MintyServiceHWiNFO.MsmServiceHWiNFO - [email protected]#799.024
DEBUG MintyServiceHWiNFO.MsmServiceHWiNFO - [email protected]#4503.285
DEBUG MintyServiceHWiNFO.MsmServiceHWiNFO - [email protected]#1409.10061323155

So I suspect one of the following:-
  • A setting within HWiNFO I previously had enabled and after re-installing this has changed
  • The Shared Memory Interface API has changed (previously confirmed as not changed as far as I know)
  • Issue with Windows 10 (I did reinstall Windows since this has stopped working)
  • Computers just hate me!
I did reinstall a previous version (v6.06-37770) of HWiNFO and this made no difference.

Any pointers for debugging this further are appreciated.

Thanks
 
Fixed it - resetting the preferences resolved the issue!

I would like to know why re-setting resolves this in case it was due to something I had done?

I can see this coming up again when supporting my own software if the units stop reporting like they did for me?

Thanks

Note to Self: Try resetting preferences before reinstalling - seems like preferences survive a reinstall :rolleyes:
 
Last edited:
Have you perhaps renamed the units to an empty string in HWiNFO? That would explain such behavior.
 
Have you perhaps renamed the units to an empty string in HWiNFO? That would explain such behavior.
How so? Certainly not all of them, I would have renamed a few during testing but they all failed to report. Strange, but they are now working after the reset of preferences.
 
Can I also ask about the 'id' attribute which seems to be consistent across both the above readings i.e. Core #3 VID stays with the same id :33554435. How are these id's determined and are they constant/unique to the sensor (within the same build / across different hardware builds)?

Can you give me advice on these id's please as this may effect my database design in terms of history recording?
 
Can you give me advice on these id's please as this may effect my database design in terms of history recording?
This is a unique ID of a value (reading) within a given sensor, not globally. It remains constant on a machine, so it might be useful for tracking a particular value.
 
Strange, I had this same issue again tonight. All the units missing from the shared memory responses although resetting the preferences didn't help. Installing the latest version resolved it and the units are back.

No idea what is triggering the units to disappear so just posting for the sake of recording it really.
 
Back
Top