Hello all, just wondering if anyone else has noticed this issue on Kaby Lake, or Skylake hardware. HWINFO64 shows my socket designation as LGA2066
↧
Socket designation
↧
Just wanted to register and say thanks for this great tool
Hello Martin developer,
This is a great app and I am so thankful for it.
Thanks a lot again.
This is a great app and I am so thankful for it.
Thanks a lot again.
↧
↧
Incorrect DRAM voltage reading on ASUS Z170 Pro Gaming
I have incorrect DRAM voltage reading on ASUS Z170 Pro Gaming motherboard. It shows 2.688-2.704 instead 1.344-1.352.
![.png]( "PNG Image")
Безымянный.png (Size: 107.85 KB / Downloads: 2)
Безымянный.png (Size: 107.85 KB / Downloads: 2)
↧
HWiNFO32 and HWiNFO64 v5.47-3105 Beta released
HWiNFO32/64 v5.47-3105 Beta available.
Changes:
Changes:
- Added NVIDIA GeForce GTX 1080 Ti.
- Fixed reporting of AMD Ryzen memory timings if first memory controller is not active.
- Fixed occasional erratic sensor readouts on ASUS CROSSHAIR VI HERO.
- Added reporting of SMU Firmware Revision for AMD Ryzen.
↧
Fans speed values - not all fans are displayed.
Hello, friends!
I am using the of HWiNFO64 v5.47-3105, everything is cool. Unexpected, perhaps a small question.
There is the motherboard ASUS SABERTOOTH 990FX R3.0 - has six fan headers.
Program monitoring ASUS AISuite3, BIOS monitor - displays the speed of all six the fans.
HWiNFO64 displays speed of only five fans, the cpu_opt fan is not visible.
(Pictures are attached below.)
Is there a way include of displaying all the fans present on this MB?
Maybe there was an answer to this question, but I did not find it.![Huh]( "Huh")
Thanks for ....
p.s. Also I wanted to attach a HWiNFO64.DBG file, but it has a size of 14939673 bytes, сan not upload file.
![.png]( "PNG Image")
HWiNFO64.PNG (Size: 38.41 KB / Downloads: 4)
![.png]( "PNG Image")
allsuite.PNG (Size: 183.94 KB / Downloads: 5)
![.png]( "PNG Image")
170315204021.png (Size: 345.12 KB / Downloads: 3)
I am using the of HWiNFO64 v5.47-3105, everything is cool. Unexpected, perhaps a small question.
There is the motherboard ASUS SABERTOOTH 990FX R3.0 - has six fan headers.
Program monitoring ASUS AISuite3, BIOS monitor - displays the speed of all six the fans.
HWiNFO64 displays speed of only five fans, the cpu_opt fan is not visible.
(Pictures are attached below.)
Is there a way include of displaying all the fans present on this MB?
Maybe there was an answer to this question, but I did not find it.
Thanks for ....
p.s. Also I wanted to attach a HWiNFO64.DBG file, but it has a size of 14939673 bytes, сan not upload file.
HWiNFO64.PNG (Size: 38.41 KB / Downloads: 4)
allsuite.PNG (Size: 183.94 KB / Downloads: 5)
170315204021.png (Size: 345.12 KB / Downloads: 3)
↧
↧
My thoughtS on this software
Hi
WOW! I've used and am using a lot of this kind of software (like HWMonitor, MSI AfterBurner, CPUID, etc. to name a few), but your software, now your software made me sit up and take note. That being said I am not without suggestions, so I will proceed to supply these suggestions in the hopes that you will consider them. It is my first time in your forum and like most people I did not read much before this post, so please just delete it and accept my apologies if I overstepped the bounds of acceptability in your house.
Note that I downloaded HWiNFO a couple of hours ago so these are first impressions.
I noticed the following changes to my system:
1. CPU usage is up by 5% on average (that is after I disabled most voltage etc. monitoring in the app and it is in the tray) causing my pumps to spin up a bit in idle, but I guess that can be expected. I will tweak some.
2. My mouse is jerky and sometimes jumps from one place to another whilst the application is open.
I noticed the following about the program that makes it less fun to use:
1. OSD: To set up the OSD you need to go into the settings and find the item again when you are looking at the item in the main list. A right-click menu item which only shows the OSD setup portion in a popup will really simplify this.
2. OSD: I noticed that I can add the label of the first item in a row and it will look more like MSI AfterBurner (CPU: 23C, 45%, 1500 RPM), but I do not want that to be the label in the main list. A new field to the OSD setup page called 'OSD Label' where we can specify what to call it in OSD would be great.
[b]3.[/b] OSD: It is impossible to see from the main list information like 'Is this item in OSD and where (row, col)'. Custom columns showing this information would be very helpful. Also a column with the heading (sensor name) so we can reorganize, but still know where the sensor is located.
4. Customize: To customize items (color, label) suffer from the same problems as the OSD mentioned in nr. 1.
5. Interface: If we say could move items around and colorize them and so on and then save that layout so that we can easily switch between layouts, that would be great. Currently you get a warning that sounds pretty ominous when you want to just put something somewhere else. I learned why when I clicked the 'Restore Original Order' button and it disabled 90% of the sensors. I like the original layout, but I would like to be able to switch to a custom layout at times showing only the items I am interested in with my own heading.
6. Interface: If the main headings (sensor names) were tree items that can close items under them and then these items are not monitored until it is opened again it would solve problems I have not thought of yet. I don't know if this will be helpful if nr. 5 was implemented.
7. Interface: I notice your app will list two entries like 'GPU Core Power' & 'GPU Chip Power'. Each of these show a different value to the MSI AfterBurner 'GPU Power' entry. I assume MSI AfterBurner combines the two to get a value. If we could add entries that combine other entries with a math equation we supply it would help a lot. A good example is the fans in your app only shows the RPM for my motherboard & CPU, but I need the speed as a percentage too for OSD. If I could add an entry that calculates this for me based on RPM it would solve the problem.
I also noticed the following that appears to be bugs, but what do I actually know:
1. The temperatures in the main list shows minus values even thought this option is off in the preferences. I assume because they have only received minus values since the start.
2. Some items in the main list the label in black, but the values are gray. Mostly for the items with minus values (but others too), so I assume you did this on purpose, but it is not clear why.
I downloaded your app for the CPU tachometer monitoring that MSI AfterBurner does not supply, but now I am considering replacing the MSI AfterBurner OSD with your app also since there is a vertical gap between the two app entries (GPU & CPU) and your values don't jump all over the place due to the very useful right-padding.
Kind Regards
Jayson
WOW! I've used and am using a lot of this kind of software (like HWMonitor, MSI AfterBurner, CPUID, etc. to name a few), but your software, now your software made me sit up and take note. That being said I am not without suggestions, so I will proceed to supply these suggestions in the hopes that you will consider them. It is my first time in your forum and like most people I did not read much before this post, so please just delete it and accept my apologies if I overstepped the bounds of acceptability in your house.
Note that I downloaded HWiNFO a couple of hours ago so these are first impressions.
I noticed the following changes to my system:
1. CPU usage is up by 5% on average (that is after I disabled most voltage etc. monitoring in the app and it is in the tray) causing my pumps to spin up a bit in idle, but I guess that can be expected. I will tweak some.
2. My mouse is jerky and sometimes jumps from one place to another whilst the application is open.
I noticed the following about the program that makes it less fun to use:
1. OSD: To set up the OSD you need to go into the settings and find the item again when you are looking at the item in the main list. A right-click menu item which only shows the OSD setup portion in a popup will really simplify this.
2. OSD: I noticed that I can add the label of the first item in a row and it will look more like MSI AfterBurner (CPU: 23C, 45%, 1500 RPM), but I do not want that to be the label in the main list. A new field to the OSD setup page called 'OSD Label' where we can specify what to call it in OSD would be great.
[b]3.[/b] OSD: It is impossible to see from the main list information like 'Is this item in OSD and where (row, col)'. Custom columns showing this information would be very helpful. Also a column with the heading (sensor name) so we can reorganize, but still know where the sensor is located.
4. Customize: To customize items (color, label) suffer from the same problems as the OSD mentioned in nr. 1.
5. Interface: If we say could move items around and colorize them and so on and then save that layout so that we can easily switch between layouts, that would be great. Currently you get a warning that sounds pretty ominous when you want to just put something somewhere else. I learned why when I clicked the 'Restore Original Order' button and it disabled 90% of the sensors. I like the original layout, but I would like to be able to switch to a custom layout at times showing only the items I am interested in with my own heading.
6. Interface: If the main headings (sensor names) were tree items that can close items under them and then these items are not monitored until it is opened again it would solve problems I have not thought of yet. I don't know if this will be helpful if nr. 5 was implemented.
7. Interface: I notice your app will list two entries like 'GPU Core Power' & 'GPU Chip Power'. Each of these show a different value to the MSI AfterBurner 'GPU Power' entry. I assume MSI AfterBurner combines the two to get a value. If we could add entries that combine other entries with a math equation we supply it would help a lot. A good example is the fans in your app only shows the RPM for my motherboard & CPU, but I need the speed as a percentage too for OSD. If I could add an entry that calculates this for me based on RPM it would solve the problem.
I also noticed the following that appears to be bugs, but what do I actually know:
1. The temperatures in the main list shows minus values even thought this option is off in the preferences. I assume because they have only received minus values since the start.
2. Some items in the main list the label in black, but the values are gray. Mostly for the items with minus values (but others too), so I assume you did this on purpose, but it is not clear why.
I downloaded your app for the CPU tachometer monitoring that MSI AfterBurner does not supply, but now I am considering replacing the MSI AfterBurner OSD with your app also since there is a vertical gap between the two app entries (GPU & CPU) and your values don't jump all over the place due to the very useful right-padding.
Kind Regards
Jayson
↧
Incorrect DRAM voltage reading on ASUS Z170 Pro Gaming
I have incorrect DRAM voltage reading on ASUS Z170 Pro Gaming motherboard. It shows 2.688-2.704 instead 1.344-1.352.
![.png]( "PNG Image")
Безымянный.png (Size: 107.85 KB / Downloads: 5)
Безымянный.png (Size: 107.85 KB / Downloads: 5)
↧
Smart scan on hdd access
Hi,
First I want to say thanks for this great software!
Just let me describe my problem and what I would need to solve it:
I'm using a software called aquasuite, which came together with a fan controlling device for my watercooling. This software was designed for controlling fan speed in dependence of temperatures. My only problem is the input. Until now I'm using open hardware monitor for reading the relevant temperatures, among these my 3 hdds' temperatures. Actually it works very well but I think the permanent reading of smart values prevents the drives from spinning down and going to standby. That doesn't matter for my primary hdd but I'd like the two others to take a rest for most of the time my pc is running.
I first thought of a solution like reading the values every 30 minutes and keep my primary hdd tracked more often. That would be possible by using a second program like AIDA, which would read all hdds after a long interval and using HWinfo with a short interval but secondary hdds disabled (disabling single devices is a really great feaature that other softwares don't have!!).
But this solution doesn't guarantee that neither the secondary hdds are read when working, so that a rising temperature is detected and the fan starts, nor that the fan is cooling to much/long (which makes noise btw), as the decreasing temperature won't be noticed since the scanning interval is long (for allowing long standby times).
So what I really could use is a hdd-access-dependent trigger that realizes when a hdd goes from standby to working state and tells HWinfo to measure smart values/temperature every x seconds during the next y minutes.
I assume this could be a hard task of programming but I don't know if it's even possible at all so please let me know what your opinion is.
PS: I hope this text doesn't contain too many mistakes.
First I want to say thanks for this great software!
Just let me describe my problem and what I would need to solve it:
I'm using a software called aquasuite, which came together with a fan controlling device for my watercooling. This software was designed for controlling fan speed in dependence of temperatures. My only problem is the input. Until now I'm using open hardware monitor for reading the relevant temperatures, among these my 3 hdds' temperatures. Actually it works very well but I think the permanent reading of smart values prevents the drives from spinning down and going to standby. That doesn't matter for my primary hdd but I'd like the two others to take a rest for most of the time my pc is running.
I first thought of a solution like reading the values every 30 minutes and keep my primary hdd tracked more often. That would be possible by using a second program like AIDA, which would read all hdds after a long interval and using HWinfo with a short interval but secondary hdds disabled (disabling single devices is a really great feaature that other softwares don't have!!).
But this solution doesn't guarantee that neither the secondary hdds are read when working, so that a rising temperature is detected and the fan starts, nor that the fan is cooling to much/long (which makes noise btw), as the decreasing temperature won't be noticed since the scanning interval is long (for allowing long standby times).
So what I really could use is a hdd-access-dependent trigger that realizes when a hdd goes from standby to working state and tells HWinfo to measure smart values/temperature every x seconds during the next y minutes.
I assume this could be a hard task of programming but I don't know if it's even possible at all so please let me know what your opinion is.
PS: I hope this text doesn't contain too many mistakes.
↧
Issue with RTSS OSD
Hi,
I'm using MSI-Afterburner (4.3 final) RTSS (6.6.0) and HWiNFO64(5.47.3105) on w10.
I've been using this combination to get a nice OSD showing FPS(from afterburner) and some stats from HWiNFO (GPU: Temp, Load, Clock, VRam used, CPU: Temp, Load, RAM: Used, Free) through RTSS. All programs automatically startup with windows.
This used to work fine, but the last couple of weeks HWiNFO numbers stopped showing up in the OSD after boot. Every boot I have go in sensors/configure/OSD(RTSS and toggle one item from on to off and back before all of them show again.
I've uninstalled, reinstalled and reconfigured all 3 programs, even did a clean install of w10 but the issue remains.
Did I mess up, missed something or Am I doing something wrong? Or did a bug creep in either with the latest RTSS or HWiNFO versions?
Regards, Darkje
I'm using MSI-Afterburner (4.3 final) RTSS (6.6.0) and HWiNFO64(5.47.3105) on w10.
I've been using this combination to get a nice OSD showing FPS(from afterburner) and some stats from HWiNFO (GPU: Temp, Load, Clock, VRam used, CPU: Temp, Load, RAM: Used, Free) through RTSS. All programs automatically startup with windows.
This used to work fine, but the last couple of weeks HWiNFO numbers stopped showing up in the OSD after boot. Every boot I have go in sensors/configure/OSD(RTSS and toggle one item from on to off and back before all of them show again.
I've uninstalled, reinstalled and reconfigured all 3 programs, even did a clean install of w10 but the issue remains.
Did I mess up, missed something or Am I doing something wrong? Or did a bug creep in either with the latest RTSS or HWiNFO versions?
Regards, Darkje
↧
↧
HWiNFO On Screen Display (desktop)
Ive seen a few threads talking about the rivatuner integration for OSD of HWiNFO sensor information. However, I am trying to find out if there is a way of having a general OSD for the windows desktop. AIDA64 has such a function, which allows you to choose which sensors you would like to display, and provides a method of customizing fonts, colors, OSD transparency, sensor display order, etc. -- and then you are able to freely move the display around on your desktop (i place mine at the top right, where it anchors itself). However, there are many features of HWiNFO that I like, and I would love to make the switch from AIDA if I was able to have a similar OSD panel. (see screenshot below for my current setup)
Is there a way of doing this, either in the vanilla HWiNFO, or with 3rd party plugins?
Thanks!
![[Image: R08L6Yx.jpg]]()
Is there a way of doing this, either in the vanilla HWiNFO, or with 3rd party plugins?
Thanks!
![[Image: R08L6Yx.jpg]](http://i.imgur.com/R08L6Yx.jpg)
↧
HWiNFO32 and HWiNFO64 v5.47-3115 Beta released
HWiNFO32/64 v5.47-3115 Beta available.
Changes:
Changes:
- Added NVIDIA GeForce GTX 1080 Ti.
- Fixed reporting of AMD Ryzen memory timings if first memory controller is not active.
- Fixed occasional erratic sensor readouts on ASUS CROSSHAIR VI HERO.
- Added reporting of SMU Firmware Revision for AMD Ryzen.
- Simplified adjusting of sensor item settings via right-click context menu.
- Added board-level monitoring of CPU current and power on ASUS CROSSHAIR VI and PRIME X370.
- Enhanced sensor monitoring on GIGABYTE X370 series mainboards.
↧
Fans speed values - not all fans are displayed.
Hello, friends!
I am using the of HWiNFO64 v5.47-3105, everything is cool. Unexpected, perhaps a small question.
There is the motherboard ASUS SABERTOOTH 990FX R3.0 - has six fan headers.
Program monitoring ASUS AISuite3, BIOS monitor - displays the speed of all six the fans.
HWiNFO64 displays speed of only five fans, the cpu_opt fan is not visible.
(Pictures are attached below.)
Is there a way include of displaying all the fans present on this MB?
Maybe there was an answer to this question, but I did not find it.![Huh]( "Huh")
Thanks for ....
p.s. Also I wanted to attach a HWiNFO64.DBG file, but it has a size of 14939673 bytes, сan not upload file.
![.png]( "PNG Image")
HWiNFO64.PNG (Size: 38.41 KB / Downloads: 8)
![.png]( "PNG Image")
allsuite.PNG (Size: 183.94 KB / Downloads: 9)
![.png]( "PNG Image")
170315204021.png (Size: 345.12 KB / Downloads: 7)
I am using the of HWiNFO64 v5.47-3105, everything is cool. Unexpected, perhaps a small question.
There is the motherboard ASUS SABERTOOTH 990FX R3.0 - has six fan headers.
Program monitoring ASUS AISuite3, BIOS monitor - displays the speed of all six the fans.
HWiNFO64 displays speed of only five fans, the cpu_opt fan is not visible.
(Pictures are attached below.)
Is there a way include of displaying all the fans present on this MB?
Maybe there was an answer to this question, but I did not find it.
Thanks for ....
p.s. Also I wanted to attach a HWiNFO64.DBG file, but it has a size of 14939673 bytes, сan not upload file.
HWiNFO64.PNG (Size: 38.41 KB / Downloads: 8)
allsuite.PNG (Size: 183.94 KB / Downloads: 9)
170315204021.png (Size: 345.12 KB / Downloads: 7)
↧
Core i7 (Kaby Lake) core clocks
I have been watching the Sensor Status>Core #n Clock display on and off for a while now, and re-check it when a new version of HWiNFO comes out.
Prior to the latest version (5.47-3115) - and possibly one or two BETA releases before, I would see the full range of my CPU (i7-7700) "turbo" clocks: 3.6 GHz (normal) up to 4.2 GHz (occasionally)... and very occasionally, I would see nonsensical readings of 6-7 GHz.![Wink]( "Wink")
I don't know how much of what is displayed for these values is just being directly read from H/W, vs how much of this has to be computed from multiple inputs.
BUT, with this newest version of HWiNFO, I never see anything above 4.0 GHz - is it possible that you are now artificially "clamping" these values, and chose the [incorrect] 4.0 GHz value as the max allowed here? If so, you might check the Intel docs for this CPU, which really can go to 4.2 - if not, ?
While we are on the subject of observed values, the "Bus Clock" reading appears to show a range of readings that may not be "possible" (46.4 MHz - 105.8 MHz)? I thought it was a fixed value - 100 MHz in my case - but I may have this wrong?
Details: Z270-based mobo, NO overclocking, XMP-3200 memory, Win10 x64.
Prior to the latest version (5.47-3115) - and possibly one or two BETA releases before, I would see the full range of my CPU (i7-7700) "turbo" clocks: 3.6 GHz (normal) up to 4.2 GHz (occasionally)... and very occasionally, I would see nonsensical readings of 6-7 GHz.
I don't know how much of what is displayed for these values is just being directly read from H/W, vs how much of this has to be computed from multiple inputs.
BUT, with this newest version of HWiNFO, I never see anything above 4.0 GHz - is it possible that you are now artificially "clamping" these values, and chose the [incorrect] 4.0 GHz value as the max allowed here? If so, you might check the Intel docs for this CPU, which really can go to 4.2 - if not, ?
While we are on the subject of observed values, the "Bus Clock" reading appears to show a range of readings that may not be "possible" (46.4 MHz - 105.8 MHz)? I thought it was a fixed value - 100 MHz in my case - but I may have this wrong?
Details: Z270-based mobo, NO overclocking, XMP-3200 memory, Win10 x64.
↧
↧
fan cable splitter, would it be a problem?
If I use a fan splitter cable for two similar fans connected to one motherboard fan header, would it be a problem for HWInfo? I mean, the fans will be running at the same speed (I guess?), but will HWInfo be confused which of the two fans it will get the fan RPM from? For example, one of the fans start to fail and runs at lower speed, from which fan will HWInfo take the speed from?
I'm starting a new build --- Maximus IX Code, i7 7700K, Cosmos II chassis.
I plan to do the following:
Case Fan 1 header - 1x 140mm - rear
Case Fan 2 header - 2x 120mm - side
Case Fan 3 header - 1x 200mm - front
I'm starting a new build --- Maximus IX Code, i7 7700K, Cosmos II chassis.
I plan to do the following:
Case Fan 1 header - 1x 140mm - rear
Case Fan 2 header - 2x 120mm - side
Case Fan 3 header - 1x 200mm - front
↧
Minor bugs with "Save Report"
It doesn't remember the filename when you hit "Browse".
It doesn't see mapped drives (network drives mapped to drive letters) while in browse.
It doesn't save or use the new network location when you do a later "Save Report", so I have to browse anew each time.
I want to save reports on a server, in a common location. It could be a bit easier to accomplish this.
Thanks.
It doesn't see mapped drives (network drives mapped to drive letters) while in browse.
It doesn't save or use the new network location when you do a later "Save Report", so I have to browse anew each time.
I want to save reports on a server, in a common location. It could be a bit easier to accomplish this.
Thanks.
↧
HWiNFO32 and HWiNFO64 v5.47-3125 Beta released
HWiNFO32/64 v5.47-3125 Beta available.
Changes:
Changes:
- Added NVIDIA GeForce GTX 1080 Ti.
- Fixed reporting of AMD Ryzen memory timings if first memory controller is not active.
- Fixed occasional erratic sensor readouts on ASUS CROSSHAIR VI HERO.
- Added reporting of SMU Firmware Revision for AMD Ryzen.
- Simplified adjusting of sensor item settings via right-click context menu.
- Added board-level monitoring of CPU current and power on ASUS CROSSHAIR VI and PRIME X370.
- Enhanced sensor monitoring on GIGABYTE X370 series mainboards.
- Enhanced sensor monitoring on some ASRock X370 series mainboards.
- Added support of some later Corsair H110i coolers.
- Added reporting of AMD AGESA version.
- Added a new telemetry method to monitor Ryzen CPU+SoC voltage, current and power.
- Improved support of Intel Skylake-SP.
↧
Disk Drives disappearing
When ever i launch HWiNFO64 two of my five drives are missing and they dont come back until i reboot the system.
↧
↧
Feature suggestion
Dear Martin,
I suggest that you can come up with a feature in which the user can see how the OSD(RTSS) would appear when setting up the parameters to monitor when in gaming or 2D rendering.
Now I have to open GPU-Z and open 3D renderer test to see how the monitoring looks when I setup the OSD(RTSS)
And thanks for the great program.
I suggest that you can come up with a feature in which the user can see how the OSD(RTSS) would appear when setting up the parameters to monitor when in gaming or 2D rendering.
Now I have to open GPU-Z and open 3D renderer test to see how the monitoring looks when I setup the OSD(RTSS)
And thanks for the great program.
↧
Corsair PSU disappears
Hello,
in HWiNFO64 5.47 Beta I was until today able to see my Corsair PSU HX750i sensor data. Now all PSU rows are gone, I just see empty rows and there is no PSU data in the "hidden rows" list. I use Corsair Link 4.6.0.86 which by its own shows all PSU sensor data.
Using the 5.46 portable version, the issue remains the same. The PSU does not show up anywhere ..![Huh]( "Huh")
in HWiNFO64 5.47 Beta I was until today able to see my Corsair PSU HX750i sensor data. Now all PSU rows are gone, I just see empty rows and there is no PSU data in the "hidden rows" list. I use Corsair Link 4.6.0.86 which by its own shows all PSU sensor data.
Using the 5.46 portable version, the issue remains the same. The PSU does not show up anywhere ..
↧
2 ITE Chip detected
Perhaps you could help me,
why after i reloaded HWiNFO several times, HWiNFO gives reading of 1 some times 2 ITE chip, but in maiboard manual layout/ spec there's no mention of second ITE chip.
is it mainboard has defect, or just need updating of chipset driver?
thanks again
![.zip]( "ZIP File")
ITE Chip(s) Detected.zip (Size: 1.5 MB / Downloads: 1)
why after i reloaded HWiNFO several times, HWiNFO gives reading of 1 some times 2 ITE chip, but in maiboard manual layout/ spec there's no mention of second ITE chip.
is it mainboard has defect, or just need updating of chipset driver?
thanks again
ITE Chip(s) Detected.zip (Size: 1.5 MB / Downloads: 1)
↧