HWiNFO32 and HWiNFO64 v4.16 released

Printable View

04-09-2013, 01:05 AM
Mumak

HWiNFO32 and HWiNFO64 v4.16 released
HWiNFO32 v4.16 and HWiNFO64 v4.16 available.
Changes:
- Added support of additional CHiL/IR VRs on GPU.
- Fixed enumeration of GPUs disabled by nVidia Optimus.
- Fixed freezing of Synaptics SMBus touchpads on Intel chipsets.
- Merged and rearranged nVidia Internal GPU sensor with NVAPI.
- Added AMD Radeon HD 7790.
- Added nVidia GeForce GTX 650 Ti Boost.
- Added monitoring of D3D Usage on AMD, nVidia and Intel GPUs (covers Direct3D only).
- Improved enumeration of RAID arrays, added RAID status reporting.
- Enhanced sensor monitoring on nVidia nForce 790i reference mainboards (Zotac, EVGA, XFX, etc).
- Enhanced support of AMD GCN2 family GPUs.
- Added monitoring support for On Semi NCP81022 on GPU.
- Added nVidia GF119 models: GeForce 705M.
- Added nVidia GK104 models: Quadro K2 USM, Tesla K2 USM, GRID K520, GeForce K2 USM, NVS K2 USM.
- Added nVidia GK106 models: GeForce GTX 760M, 765M, 770M.
- Added nVidia GK107 models: Tesla K1 USM, Quadro K1 USM, GeForce GT 740M, 745M, 750M, GeForce K340 USM, NVS K1 USM, GRID K340, NVS 1000.
- Added nVidia GK110 models: GeForce GTX Titan LE, Tesla K20, Tesla K20X.
- Added nVidia GK208 models: GeForce GT 730M, 735M, 740M.
04-09-2013, 06:59 AM
NEOAethyr

You work pretty hard on this... :).

I can confirm it's working on the 104gl, vgx k2.

Can I ask a favor?
I got one mine the same stuff the msi 680 lightning has, the extra voltage monitoring chip thing (gpu, mem and aux).
Is there anyway you can check for that sub maker/device id's on both main device's 1180, and 11bf?
Msi afterburner ignore's the sub id's when the main device id is not 1180.
I can't remmeber now if you had implemented those sensor's or not ont he 680 lightning.
I'm just saying I've got a lightning that's a grid k2, and I'de like to at least see the extra sensor's even though I can't play with the voltages in software anymore, at the moment anyways.
If you could do that, that would be great :D.
If not, not a biggy :).
04-09-2013, 07:06 AM
Mumak

Sure, I can try to implement support of those additional sensors, but it's often quite hard, since the vendors don't release required documents.
Do you know what's exactly that additional sensor (Manuf & model) ?
Also, I'll need the HWiNFO Debug File (with sensor data) to analyze it...
04-09-2013, 08:13 AM
NEOAethyr

How do I make the debug file?, is it the same as the report file option?

http://www.techpowerup.com/reviews/M...front_full.jpg
http://cdn.overclock.net/e/eb/eba754...577d9a217.jpeg
http://elchapuzasinformatico.com/wp-...ighting-23.jpg
http://www.techpowerup.com/reviews/M.../back_full.jpg

I think it's the chil chip.
There's another one on the board too but I think that other one is the one needed on the ref board's.
I don't know the model's or anything, I'de have to take the card out and take it apart again, I can do that a bit later maybe.
The sensor part of hwinfo32 it says chil chl8266, nuvoton nct7717u/nct7718w.

I'm not actually sure now that what was talking about before, were sensor's, maybe they were just set value's in msi afterburner (vmem, aux).
I never checked to see if it's changed, restart the app and recheck to see if it was the correct value, I don't know if I said that right...

Do you think it's possible that there's 2 more sensor's on the chl8266 chip?
04-09-2013, 08:33 AM
Mumak

Check this about how to create a HWiNFO Debug File: http://www.hwinfo.com/forum/Thread-I...tting-a-report
So HWiNFO does already report a CHL8266? That should be then the Digital PWM with sensor. Theoretically it's possible that there are multiple such chips (GPU core, GPU memory, etc).
The NCT7717 is an additional sensor.
Can you also post a screenshot of the Sensors screen so that the GPU sensors are visible?
04-09-2013, 08:54 AM
NEOAethyr

http://img28.imageshack.us/img28/5782/65460520.jpg

I think the aux voltage means the vrm voltage.
I should double check with the dmm though.
But on hwinfo32, compared to aida64, aida has the chl8266. chip gpu voltage named vrm voltage.
While hwinfo32 has 2 gpu voltages, the one under chl8266 is offset to the same value that aida has named vrm voltage.

The only one missing then is the mem voltage reading.
And that's only accessible so far in msi afterburner.
I can still use the osd but I can't use that sensor anymore in that program because of the device id of my card.
It's osd is useful, I see that hwinfo supposedly supports it too these days :).

Debug file:
http://hidemyass.com/files/sxtB1/

Edit:

Also noticed these:

nct7717u/x:
gpu temp (gpu temp in aida64)

nvidia internal:
gpu temp (gpu diode temp in aida64)

And gpu ambient is the same sensor for both programs.

There's one more sensor in hwinfo32, gpu temp (hw) on nv internal.
The doesn't match up with any in aida64.
I almost wonder if it's a digital, but it would have to be verified it is one 1st to be labled as such.
04-09-2013, 09:07 AM
Mumak

Since the CHL8266 is the PWM/VR then all values belong to the VR :) So the "GPU Voltage" under CHL8266 in HWiNFO is identical to "GPU VRM" voltage in AIDA64. It's just a matter of naming ;)
I'm going to check the DBG file now to see if there's maybe anything more...
04-09-2013, 09:33 AM
Mumak

The DBG file you attached doesn't contain sensor data - you probably didn't open the Sensors window in debug mode.

The GPU temp (HW) comes straight from the chip's internal HW registers, unlike the other values from nVidia NVAPI interface. Some users have reported that these values vary sometimes, but I don't know which one is more accurate. I report both of them...
04-09-2013, 09:40 AM
NEOAethyr

I see thanks for the info :).

Here's another debug file ran in sensor mode:
http://hidemyass.com/files/e8R6v/
04-09-2013, 10:34 AM
Mumak

I don't see any other sensor there. It would be highly unlikely to contain multiple CHL chips, this is more common on mainboards.
You might try to create the GPU I2C dump in AIDA64 (right-click on the bottom window bar), that could maybe contain more information...
04-12-2013, 05:07 AM
DefStar

I have found what I believe to be a bug that I can reproduce consistently...

When running your latest HWinfo64 on my Win7x64 SP1, my FPS erratically dip in the physics test of 3Dmark 2013.

Running HWinfo64, minimum fps is 21.
Not running HWinfo64, minimum fps is 27.

I'm pretty sure that's a bug since it results in a loss of over 200 points (comparable to lowering my CPU core speeds 200MHz) in my physics score, and a hardware monitoring program should not degrade performance that severely. Also, I wasted about 2 hours adjusting my memory timings and cpu voltage believing my system was unstable...what a relief it is to now know I was just beta testing HWinfo.

Just a heads up, thanks for the program and keep up the good work.:clap:
04-12-2013, 06:56 AM
Mumak

That might be caused by reading values from some sensors, especially of the EC-type (like ASUS EC, DELL EC), or certain SATA/RAID drivers when asking them for drive temperature (SMART).
HWiNFO itself doesn't cause such high system load, it's just the design/implementation of some sensors.
Try to disable those sensors (right-click + Disable Monitoring) and it should be OK..
Let me know if that won't help.
04-12-2013, 04:35 PM
DefStar

Quote:

Originally Posted by Mumak

That might be caused by reading values from some sensors, especially of the EC-type (like ASUS EC, DELL EC), or certain SATA/RAID drivers when asking them for drive temperature (SMART).
HWiNFO itself doesn't cause such high system load, it's just the design/implementation of some sensors.
Try to disable those sensors (right-click + Disable Monitoring) and it should be OK..
Let me know if that won't help.

You are absolutely correct. Enableing the inbedded Asus (EC) controller on my Maximus v Gene motherboard was the root of the problem...HWinfo even warns that the sensor may cause instability...is this because of the sensor itself (its a buggy/junky sensor), or just because of lack of documentation on this sensor (its Asus proprietary part you have no data on)? I love how all the data is right there, I love its simplicity, but a sleek/flashy look will make it cooler.

Thanks, sorry to waste your time if its just a cheap-o sensor Asus uses that you cannot do anything about.

P.S. Really nice program, I have a BS in computer science and program myself. A nice clean "modern" looking GUI would do a-lot marketing wise...you know make it look cool so newbies will want to install it (similar to the revamped riva-tuner aka. Afterburner). I noticed most programs get a GUI overhaul when some mo-bo or video card manufacturer picks up the software, and then all the sudden everyone want to use it.
04-12-2013, 10:07 PM
Mumak

ECs are very common, especially in notebooks, only few desktops use them. The problem is not the EC itself (it's a general microcontroller running custom firmware), but the way how to access its values from CPU - the interface.
You're absolutely right about the GUI, I'm thinking about a revamp for very long time, however couldn't allocate enough time yet. I'm also not much experienced with GUI and still lacking the right ideas how to redesign the app, especially sensors.

Quote:

Originally Posted by DefStar

You are absolutely correct. Enableing the inbedded Asus (EC) controller on my Maximus v Gene motherboard was the root of the problem...HWinfo even warns that the sensor may cause instability...is this because of the sensor itself (its a buggy/junky sensor), or just because of lack of documentation on this sensor (its Asus proprietary part you have no data on)? I love how all the data is right there, I love its simplicity, but a sleek/flashy look will make it cooler.

Thanks, sorry to waste your time if its just a cheap-o sensor Asus uses that you cannot do anything about.

P.S. Really nice program, I have a BS in computer science and program myself. A nice clean "modern" looking GUI would do a-lot marketing wise...you know make it look cool so newbies will want to install it (similar to the revamped riva-tuner aka. Afterburner). I noticed most programs get a GUI overhaul when some mo-bo or video card manufacturer picks up the software, and then all the sudden everyone want to use it.
04-13-2013, 03:18 PM
DefStar

Quote:

Originally Posted by Mumak

ECs are very common, especially in notebooks, only few desktops use them. The problem is not the EC itself (it's a general microcontroller running custom firmware), but the way how to access its values from CPU - the interface.
You're absolutely right about the GUI, I'm thinking about a revamp for very long time, however couldn't allocate enough time yet. I'm also not much experienced with GUI and still lacking the right ideas how to redesign the app, especially sensors.

Yeah, I only know how to do GUI programming in java (super easy)...but java compiles on any platform with java installed. Is the .net framework related to C#...cause I bet C# GUI programming is just as easy as java's. Seriously, using java and photoshop CS5 you can make a spectacular looking GUI really fast...you basically just make a jpg or gif image of rectangles in photoshop... that look like they reflect light, and then you tell java to use/repeats that image in the background where ever you want it. I made a really good looking scrabble game using java.

<---- I made that girl in my avatar in 3D studio max.... just as a summer project thing.
04-14-2013, 06:37 AM
NEOAethyr

@Mumak.
Please don't go re-writting this program in .net or java...
I can't tell you what to do, whatever floats your boat.
But .net and java blows monkey balls.
04-14-2013, 06:51 AM
Mumak

lol, don't worry, I don't intend to switch to Java or .NET. Though it's easier there, everything you can do with higher-level languages can be done in C (or even ASM), it's just a bit more work :D And I still do care about performance and size ;)
04-14-2013, 12:12 PM
DefStar

Quote:

Originally Posted by NEOAethyr

@Mumak.
Please don't go re-writting this program in .net or java...
I can't tell you what to do, whatever floats your boat.
But .net and java blows monkey balls.

Nobody was implying he should write it in java or .net, someone simply stated what they had used for GUI programming in the past... . I was implying that it will be more difficult without java or .net as I know (e.g. I then took the same scrabble game and rewrote it for the Iphone in C, used some embedded ASM (to do a jump) and then opengl 2.0 for the graphics."Blows Monkey balls"?, fine choice of words, and I respect your opinion...but java does have it's benefits.

Actually, I had totally forgot I wrote that scrabble game for Iphone using opengl....thanks for jarring my memory.
04-14-2013, 12:23 PM
DefStar

Yes, actually opengl was really easy to use as well. I'm sorry, its just that the state your gui is in right now reminded me of java. Yeah opengl is way better. Same principal, make some rectangles in photoshop....but I had a lot more control and could do a whole lot more effects and it ran so smoooooth. opengl is super easy to use.