Quantcast
Channel: HWiNFO Forum - All Forums
Viewing all 2655 articles
Browse latest View live

HWiNFO v5.83-3420 Beta released

$
0
0
HWiNFO v5.83-3420 Beta available.

Changes:
  • Enhanced sensor monitoring on ASRock Z270M-ITX.
  • Fixed a possible crash on some systems with larger VBIOSes.
  • Fixed enumeration of multiple VBIOSes in VFCT.
  • Enhanced sensor monitoring on MSI X470 series mainboards.
  • Enhanced sensor monitoring on ASUS X470 series mainboards.
  • Updated monitoring of stopped fan on Sapphire Radeon RX Vega GPUs.

S.M.A.R.T Item just noticed

$
0
0

.jpg   Screenshot 2018-04-18 11.31.36.jpg (Size: 278.35 KB / Downloads: 2)
Can anyone help me and maybe tell me what this is?
First time I noticed it in the review info page.
[05] Reallocated Sector Count:                                                  100/5, Worst: 100 (Data = 50,0)



Thanks

[Request] Longer Temperature-Fan Lookup Table?

$
0
0
I'm not sure about anyone else, but I like to keep the lowest fan setting (1) just below audible, and the highest fan setting (6) at maximum. The problem is that, with 6 points, there are only 5 steps from inaudible to very loud. It's very common that i find myself in a situation where the fan goes back and forth between two settings every second, and the jump is necessarily somewhat large and therefore distracting. 

So I guess my question is this: Would you kindly consider adding more points to this table? That would allow us to make smoother transitions between levels. Of course, this wouldn't inconvenience anyone who doesn't want it because you don't have to use the entire table.

I think Ideally we would have a smooth function linking temperature to fan speed like they have in speedfan, but I'm not going to ask you to reinvent the wheel here. I'm not an expert on coding, but I hope that adding points would be relatively easy.

ASUS EC voltages on x99M-WSSE

$
0
0
Hello,
I come across some voltages which I am not certain about. Does someone know what these voltages are? (surrounded red)
Thanks a lot.

.png   Voltages.PNG (Size: 101.74 KB / Downloads: 2)

Developer question - gpu clock monitor

$
0
0
Hi!

May I have a developer question?

I would like to build gpu clock monitor into my own program. Something like that one value on the picture marked with orange:
 
.jpg   hwinfo64.jpg (Size: 168.34 KB / Downloads: 2)

How to obtain such value?

who vita x forskolin review have poorer v

$
0
0
away a huge discuss of the earnings of the low earnings groups. Also low earnings groups will not deductible vita x forskolin review programs were much less satisfied with many aspects of their proper care than adults in more comprehensive programs People these programs allocate substantial amounts of earnings to their proper care, especially those who vita x forskolin review  have poorer vita x forskolin review or reduced incomes. The study also discovered that adults in high-deductible vita x forskolin review programs are far more likely to delay or do not required proper care, or to skip medications, because of the price. Troubles are particularly pronounced among those with poorer vita x forskolin review or reduced incomes. Political leaders have also been vocal about their criticism of the HSAs. Congressman John Conyers, Jr. issued the following statement criticizing the HSAs "The President's insurance strategy technique options not about covering the without being insured strategy, developing vita x forskolin review insurance strategy security technique strategy cost-effective, or even driving down the expense of vita x forskolin review proper care. Its real purpose is to ensure it is simpler for businesses to dump their insurance strategy technique strategy pressure onto workers, give tax breaks to the wealthy, and boost the profits of banks and cost-effective brokers. The vita x forskolin review proper care recommendations concocted at the behest of special interests do nothing to help the average The 

Available: smartphone with a 15 apps to boost your productivity

$
0
0

RX 480 Wrong GPU Freq and FAN RPM

$
0
0
PrintScreen
The GPU freq and the FAN RPM value is duplied by 1.87 and that value get to be shown.

Unit conversion

$
0
0
Hi Martin,

Seems HWiNFO wont except input 0,001 value for multiplier at Custom Tab when trying to convert X.XXX MB to X GB. It will return to 0.
It will correctly convert from X.XXX MB to X GB if I input multiplier 0.001.
I have set:
1. decimal separator to "," ;
    thousand separator to "." ;
at General Settings tab as same as Windows Settings.
2. Customize sensor  thousand separator to "." at Custom tab.

Invalid "FeatureSet" key in HKLM\HARDWARE\DESCRIPTION\System\CentralProcessor

$
0
0
When I look at
[HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0]
I see this (it is Italian and it means "DWORD value (32 bit) not valid")

  [Image: th_014966962_untitled_122_222lo.jpg]
    
 
The content is this one
Quote:Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0]
"Component Information"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
"Identifier"="Intel64 Family 6 Model 42 Stepping 7"
"Configuration Data"=hex(9):ff,ff,ff,ff,ff,ff,ff,ff,00,00,00,00,00,00,00,00
"ProcessorNameString"="Intel® Core™ i5-2500K CPU @ 3.30GHz"
"VendorIdentifier"="GenuineIntel"
"FeatureSet"=hex(4):fe,3f,19,21,00,00,00,00
"~MHz"=dword:00000cee
"Update Signature"=hex:00,00,00,00,17,00,00,00
"Update Status"=dword:00000002
"Previous Update Signature"=hex:00,00,00,00,17,00,00,00
"Platform ID"=dword:00000002
 
I saved that key some time ago and this is what was contained in it
Quote:Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0]
"Component Information"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
"Identifier"="Intel64 Family 6 Model 42 Stepping 7"
"Configuration Data"=hex(9):ff,ff,ff,ff,ff,ff,ff,ff,00,00,00,00,00,00,00,00
"ProcessorNameString"="Intel® Core™ i5-2500K CPU @ 3.30GHz"
"VendorIdentifier"="GenuineIntel"
"FeatureSet"=dword:21193ffe
"~MHz"=dword:00000cee
"Update Signature"=hex:00,00,00,00,17,00,00,00
"Update Status"=dword:00000002
"Previous Update Signature"=hex:00,00,00,00,17,00,00,00
"Platform ID"=dword:00000002
 
That string was then (how?) changed from
"FeatureSet"=dword:21193ffe
into
"FeatureSet"=hex(4):fe,3f,19,21,00,00,00,00
The content is more or less the same but the key is... more or less different Big Grin
 
I tried to restore the original key changing the registry key writing on it, but after the PC is restarted, the "invalid" key pops out again (maybe it is restored taking the new key from somewhere else)
 
Also processors 1, 2, 3 have that same "invalid" key.
 
My questions are:
1. since I use HWInfo is it something that HWInfo changed in one of the latest version in the Registry?
2. since my PC is working regularly, do you know the utilization made for this key?
3. if that key is taken from somewhere else (as I said, if I change it then. after the PC is restarted the wrong key is there again) where is it reloaded from?
4. may I "repair" this thing (if any repairing is useful)?
5. do I have to be worried?

Thanks for any reply Wink

Asus Z170 Mk1 assistant fans + voltage readiings

$
0
0
In the past, I have been able to get the Assistant Fans 1 & 2 to display in HWIFO and in the Sensor Status gadget. I have gone through reinstalling HWINFO, which didn't resolve the issue.

 I then Clean Booted into Windows and uninstalled HWINFO with Revo Uninstaller and followed with JV16 Power Tools registry cleanup. This got the fans to show in the General and Advanced tabs of the Gadget options, but they still do not display even when checked.

In the course of trying to resolve this something happened which caused integer-only (no decimal places) display of voltages and powers. See screen shot. I have done little since the latest install except run the debug and report. This issue has come and gone after and between uninstall/reinstall, which I have done more than once.

Thanks for all your work on HWINFO. It provides fascinating and useful information.

.dbg   HWiNFO64.DBG (Size: 1.63 MB / Downloads: 1)

.htm   POD64.HTM (Size: 236.07 KB / Downloads: 1)

.jpg   gadget.JPG (Size: 36.98 KB / Downloads: 3)

HWiNFO vcore detection

$
0
0
So, I'm using an i7 4770k with an asus Z87-K mb. The CPU is set to sync all cores X43 multiplier, blck is 100 mhz, core voltage is set to manual at 1.23v, uncore is set to manual stock X35, svid control is disabled with vccin on auto. However, hwinfo doesn't show vcore, and there's a VIN4 metric that might be vcore but I'm not sure.

Cpu-z, hwmonitor and speedfan all show vcore between 0.888 and 0.912v, but it never goes below and above that no matter what, indifferent of cpu usage, so I'm pretty sure that's not the actual vcore, it can't be frozen/bugged either since it goes between 0.888 and 0.912v. With HWiNFO 64 I don't have a vcore reading, here are all the voltage metrics I have:


[Image: O04mlF.png][Image: MuvLJw.png]

The VIN4 metric is the only one that resembles anything like vcore. When idle it sits around 0.9V, when I start stress testing it goes wild between 1.15V and 1.3V, it switches very fast, never stays on the same value for more than a second or two. It can't be uncore voltage cuz I tried uncore voltage to manual 1.25V and then to 1.15V and the metric stayed the same, going between 1.15 and 1.3V when stress testing. But can it be vcore? My core voltage is set to manual 1.23V, so I have no idea why it would go to 1.3V at times if it was vcore. HWMonitor has the exact same metric with the same values except it's called VIN12 in there

GPU monitoring with multiple software.

$
0
0
Is there going to be conflicts/potential issues when multiple programs are monitoring the GPU particularly during gaming or stress testing? Does this concern HWiNFO? With my EVGA graphics card I don't have any choice but to run their Precision X overclocking software to control the fans, the EVGA GTX 1080Ti FTW3 does not have a standard fan controller. This means I cannot control fans exclusively with MSI Afterburner but I prefer to use Afterburner for it's OSD. This means three programs are monitoring not just the GPU but almost all other hardware also...

HWiNFO v5.83-3430 Beta released

$
0
0
HWiNFO v5.83-3430 Beta available.

Changes:
  • Enhanced sensor monitoring on ASRock Z270M-ITX.
  • Fixed a possible crash on some systems with larger VBIOSes.
  • Fixed enumeration of multiple VBIOSes in VFCT.
  • Enhanced sensor monitoring on MSI X470 series mainboards.
  • Enhanced sensor monitoring on ASUS X470 series mainboards.
  • Updated monitoring of stopped fan on Sapphire Radeon RX Vega GPUs.
  • Enhanced sensor monitoring on GIGABYTE X470 series mainboards.
  • Enhanced sensor monitoring on ASRock Z370M Pro4.
  • Fixed monitoring of Extension/Assistant fans on some ASUS 100-300 Intel series boards.

How many watt my CPU use ?

$
0
0
Hey,
I have Intel i3 350M@2.27ghz in my laptop, it uses about 6.2 - 7watts when at 0-7%load. Is that normal for a mobile processor ? It just goes to 8.5 watts under 100% load! 

Seriously, there is only 2-3 watt differences between 0-7% usage to maximum 100%.

I am really curious to know this, is my CPU using too much power when sitting (almost) idle or it's using really less power at 100% load ?

It's a 25TDP processor. I never saw it go beyond 8.5 - 9watt under 100% load but sometimes it shows 16-18watt (i don't know why, but it never hits 16-18 under 100% load for sure).

Anyway here have a laptop, please let me know 0-5%/100% power consumption and please list your processor TDP too!

Couple issues, BSOD and App Crash on Exit

$
0
0
Been quite some time since I have reported a bug here. Just moved on to a 64bit version of windows (Windows 7N Professional) and changed over to the 64bit version of HWInfo accordingly. While trimming down and debugging my install for minimizing I came across a couple issues with the last few Beta releases.

Issue #1:
Upon exiting HWinfo, there is a memory reference error that pops up upon close. The issue seems to occur pretty consistently. Reference Attachment: 1_HWINFO64.RAR

.png   errorhwinfo.png (Size: 5.93 KB / Downloads: 2)


Issue #2:
This requires specific circumstances to occur unfortunately...
- Driver Signing Enforcement must be disabled during startup or TestMode enabled.
- Program Compatibility Assistant Service must be disabled.
- Must happen very early during startup.

Afterward, when starting windows and starting up HWInfo upon boot, it will result in a series of different memory corruption related BSOD's. Such as unnamed BSODS of random codes, IRQL less or equal, system service exceptions, driver failures, etc. This, unfortunately, could not be debug logged during a BSOD as enabling debug logging and/or writing delayed the loading of HWInfo enough thus resulting in the issue to no longer occur. I have run multiple successful passes of memtest and disabled all overclocks to confirm this was not overclock related and it still occurred accordingly.

I do remember this issue occuring back when I used Server 2008 SP2 32bit as well with test mode enabled but it would instead cause a system hard lock requiring a reboot. I did not think much of it as I simply staggered it later on in my startup scripts to circumvent the issue a year ago so this could just be a niche issue afterall.

However, I have included the Debug logs accordingly.
Reference Attachment: 2_HWINFO64.RAR, 3_HWINFO64.RAR

.rar   1_HWiNFO64.rar (Size: 37.65 KB / Downloads: 1)

.rar   2_HWiNFO64.rar (Size: 40.94 KB / Downloads: 0)

.rar   3_HWiNFO64.rar (Size: 38.73 KB / Downloads: 0)

.htm   SCARAB-X64.HTM (Size: 283.72 KB / Downloads: 0)

GPU power

$
0
0
I have an amd 7950 and am wondering what the various power measurements mean
i'm seeing 2 power measurements for both core and memory- VRM power in and out
am i correct in assuming for example the core "GPU VRM power in" is the amount of power the core VRM receives and "power out" the amount that gets sent to the gpu core; the difference between them being the amount of heat the VRM itself produces
also how accurate are these measurements, wondering because i have no other way to figure out the power draw

love the program though, my only suggestion is adding a way to monitor multiple things in one graph

Gigabyte Z270N GAMING 5 and High Temps

$
0
0
Hello everyone,

I hope someone can help me. I have a query about some high temps (PCIEX16 and System 2) reported by hwinfo64. My motherboard doesn't, or at least shouldn't, have these sensors. What's worrying is that they are very high. What's even more worrying is that when I blow a hair dryer over my motherboard, these temperatures start climbing. This suggests to me that these sensors are actually present and the temperatures are valid unless they are not calibrated properly. Please tell me I'm wrong. I've attached a side-by-side comparison between hwinfo and Gigabyte SIV:

[Image: ojZSBg0.jpg]

Couple issues, BSOD and App Crash on Exit

$
0
0
Been quite some time since I have reported a bug here. Just moved on to a 64bit version of windows (Windows 7N Professional) and changed over to the 64bit version of HWInfo accordingly. While trimming down and debugging my install for minimizing I came across a couple issues with the last few Beta releases.

Issue #1:
Upon exiting HWinfo, there is a memory reference error that pops up upon close. The issue seems to occur pretty consistently. Reference Attachment: 1_HWINFO64.RAR

.png   errorhwinfo.png (Size: 5.93 KB / Downloads: 3)


Issue #2:
This requires specific circumstances to occur unfortunately...
- Driver Signing Enforcement must be disabled during startup or TestMode enabled.
- Program Compatibility Assistant Service must be disabled.
- Must happen very early during startup.

Afterward, when starting windows and starting up HWInfo upon boot, it will result in a series of different memory corruption related BSOD's. Such as unnamed BSODS of random codes, IRQL less or equal, system service exceptions, driver failures, etc. This, unfortunately, could not be debug logged during a BSOD as enabling debug logging and/or writing delayed the loading of HWInfo enough thus resulting in the issue to no longer occur. I have run multiple successful passes of memtest and disabled all overclocks to confirm this was not overclock related and it still occurred accordingly.

I do remember this issue occuring back when I used Server 2008 SP2 32bit as well with test mode enabled but it would instead cause a system hard lock requiring a reboot. I did not think much of it as I simply staggered it later on in my startup scripts to circumvent the issue a year ago so this could just be a niche issue afterall.

However, I have included the Debug logs accordingly.
Reference Attachment: 2_HWINFO64.RAR, 3_HWINFO64.RAR

.rar   1_HWiNFO64.rar (Size: 37.65 KB / Downloads: 1)

.rar   2_HWiNFO64.rar (Size: 40.94 KB / Downloads: 0)

.rar   3_HWiNFO64.rar (Size: 38.73 KB / Downloads: 0)

.htm   SCARAB-X64.HTM (Size: 283.72 KB / Downloads: 0)

Drive throughput queried despite disabled/hidden values.

$
0
0
Greetings again,

This time I am not sure if it is a bug or intentional...

I have drive scans disabled in the settings as well as S.M.A.R.T Support and ATA Statistics Support so as to reduce overhead by disabling drive monitoring accordingly. Despite this, the drives are still queried through the sensors constantly checking I/O and throughput. Further, after disabling and hiding these values in the sensors the drives are still queried for IOCTL_DISK_PERFORMANCE accordingly for each drive.

I did not notice this until I'd noticed the queries showing up through Process Monitor while checking file and drive accesses.

Now I may be wrong but doesn't hiding a value group prevent them from being queried at all or am I being mistaken?

.png   HWInfo_DriveIO.png (Size: 70.99 KB / Downloads: 1)

.htm   SCARAB-X64.HTM (Size: 137.48 KB / Downloads: 1)

.rar   HWiNFO64.rar (Size: 27.25 KB / Downloads: 0)
Viewing all 2655 articles
Browse latest View live