Search results

Yup, works!

I'm dabbling in sub-zero liquid cooling. I noticed that my 2 GTX 980s won't report negative temperatures in hwinfo but will report them correctly in MSI Afterburner. Let me know if you need any special files from me. Here is html report, debug file, and hwinfo.ini...

Thanks for the followup post. I see it in the 5.04 changelog, well done :) Fingers crossed to see if the polling doesn't return invalid values after a long period of time again. Hopefully not, due to optimized EC reading or later AMDA00 driver revision.

Bumping this thread from the dead. I have reason to believe that the AMDA00 Interface Driver is responsible for pulling information from the ASUS EC sensor. I found a minor revision update for this driver (1.0.0.0 -> 1.0.1.0). I can now poll the sensor very quickly with minimal CPU usage. It's...

I can probably look forward to this in a future version then I suppose. Also, I never did figure out the issue with that ASUS EC sensor if it was specificly HWInfo breaking it or not. Guess it's just junky.

I noticed there is a new "Thousands seperator". Is it possible to turn this off across all sensors instead of individually?

hwinfo doesn't need to be installed. just run the exe, bam it works.

I closed AI Suite as soon as I restarted and just had hwinfo64 probing the sensor. After 2 days, it returned to a -115C value. I'll have to see if AI Suite by itself causes this problem too.

I will close AI Suite for now and see what happens.

On my Asus Rampage V, I use the ASUS EC chip to report temperature value on my liquid coolant (its a wired temperature sensor that you can place anywhere. I simply taped it to the outside of the tubing and insulated it, works well). I'm not concerned about lag or CPU usage as I put it on a...

I meant that running WITHOUT debug still makes it scan the sensors slowly. Like it checks a TON of other sensors, MULTIPLE times. I'll upload a video because it just checks them too fast. Also I know the EC sensor is slow. I usually disable it unless I need to confirm something like cache...

Hi, sorry about forgetting about this thread. Sensor scan seems to take longer than normal and scans a LOT of sensors. Debug: https://dl.dropboxusercontent.com/u/9768004/temp/HWiNFO64.DBG Report: https://dl.dropboxusercontent.com/u/9768004/temp/SSATENETH-PC.HTM

Hopefully you're still monitoring this thread. Yeah I've checked it out. It's nice, though there is a bug with it. "Added Drag and Drop support in sensors window as a more convenient way to change order of items or hide (drop outside)." When it switches to non-fixed position mode, lots of...

Just creating this thread for now. Have not seen any queries about this motherboard on the forums yet. Will be receiving this board today though and will have some information about it later, including debugs, reports, missing/inaccurate sensors, etc.

fat32face, I had to do trial and error to get the voltages correct within hwinfo for my MSI X99 motherboard earlier. All you can really do is take note of all the voltages, change the ring voltage, and note if any of them changed significantly. Sometimes there might be an offset number...

I spent the last 15 minutes moving/sorting sensors to being 'nicer'. Man, moving sensors is really cumbersome. Hope that's on your 'todo' lost. Would be nice to be able to drag and drop the sensors to the place you want it to go instead of clicking the sensor, clicking the up arrow, clicking the...

Looks good to me. Just need to figure out what the mystery sensors are now.. "Memory Ambient" "AVCC" "VTT" "VIN14" "3VSB" But will leave that for another day. 4AM over here, time for a nap I think.

Ok, I will do that. I opened HWInfo in debug mode, opened the sensors window and let it finish scanning, closed it, then created the report and saved it, then closed out hwinfo entirely. New debug and report files have been uploaded, just click the links again for new versions I sure like...

Nice to see you are still here monitoring the thread :P I'm still working on hotswapping voltages with MSI's "Command Center" program. Got a few voltages left. BTW, that NCT7511Y does have a motherboard temperature sensor, which does seem to have a valid value. edit: I've finished changing all...

+5, +3.3, and +12 are presumably correct VCCIN (CPU Input voltage): Value is correct. VCore (CPU Core voltage): Value is correct on NCT6792D sensor. VCore on NCT7511Y is unknown. Does not respond to actual changes to VCore. Ring Voltage: No sensors change in response to changing Ring voltage...