Search results

Oh, I assumed you had GFAPI. BTW their logo has changed and is now red.

I just noted HWiNFO failed to report my GPU Temperature, Voltage, Fan RPM and Fan PWM %, how come?

Thank you, so the inappropriate Product Name has always been there. I wonder if it will get changed.

Press the [ 0:0 01 ] button that is in column zero of [Link Status], it should have a tooltip.

Hi, I just found a SIV save file with the original H1000i (PID 1C07) and it reports HX1000i as the Product Name, what does your old one (the one that reports 230V) report please?

No, but as I said, I already have one, so you would not need to. Sorry you feel you can't WFH and thank you for all the insight you have provided, feel free to email me if you need any further information. I often wondered which OEM made the PSUs and now I know.

That's true when using a program the update firmware, but not when using a flash hardware programmer such as the DediProg SF100. I suspect I have just spotted another firmware bug, the Product Name is CORSAIR when I suspect it should be HX1000i given what my RM850i reports.

Thank you for the clarification, if they had updated the firmware revision I could have done a workaround. Please ensure the fixed firmware does have a updated revision/version. What's the issue with end users not being able to update the firmware? I have a DediProg SF100, could that do it?

Thank you for the information, but this does not make total sense as looking at #post-48602 the both PSUs report the same V0.03.02 firmware version with one reporting 115 and the other 230. My guess is that "Someone" also failed to update the firmware version, did they please? Is/will there be...

OK and given your two report the same V0.3.2 firmware version I suspect the firmware version from the hardware is not correct. I mentioned this issue to the owner in Germany and he said that iPOO also reports 115 Volts for his and has reported the issue to Corsair. I wonder if Corsair will fix...

There are two variants of the HX1000i, the original with a PID of 1C07 (HID\VID_1B1C&PID_1C07) which does report 230 volts when it should and a later model with a PID of 1C1E (HID\VID_1B1C&PID_1C1E). With the later model it looks like Corsair have messed up and and they incorrectly report 115...

I didn't expect the MegaRAID drives to get reported, but the 2 x HITACHI are simple SCSI drives which I though HWiNFO supported. Below you should see that Log Pages, Temperatures, Cycle Counts and Exceptions are reported.

I see the same effect on my ASUS Crosshair X670E Hero, I have also noticed that after I disabled power saving a Windows update re-enabled it :(

I just noted that HWiNFO failed to report my eMMC drive, should it? I also noticed that when I hot-plug USB-SATA or USB-NVMe HWiNFO fails to report the 'till I restart HWiNFO. Note I did not hot-plug the eMMC drive for HWiNFO.

I was lax with my wording, given you can abort HWiNFO then clearly the system is not totally frozen, just some of the sensors. After posting I checked if SIV had code to report EC sensors on your ASUS ProArt Z790 and it didn't so I added it for SIV 5.80 Beta-04. It would be wise to check what...

Depending on exactly which NZXT Kraken you have my SIV utility may be able to control it and as SIV supports the mechanism Martin referred to all should be OK when both HWiNFO and SIV are in use. To check if SIV supports it check/post Menu->Tools->Link Status + Menu->Tools->Link Fans screen...

After pondering this I suspect that when HWiNFO is stuck it's holding the lock for whichever sensor is causing the issue, so if we could find out which lock then that would probably tell us which set of sensors has the issue. The only program I know of that can do this is my SIV utility which...

What state is the HWiNFO service in after you have aborted HWiNFO and can you stop it? From an admin command window use commands such as: sc query type= driver | find "HW" sc query HWiNFO_204 sc stop HWiNFO_204 Attached is what should happen, first when HWiNFO exited normally and then when I...

Interesting, I guess the $64,000 question does the XT use the same protocol as the Pro. If yes it should be almost trivial to add support, if not then all bets are off. If the Input + Output +Feature lengths are the same they I suspect it hay use the same protocol. To find out I would need to...

My testing shows it is fixed in 471.11 :)