Search results

Don't forget that the Intel DTS sensors for the CPU were created for one main purpose, to monitor when the CPU is overheating so it can protect itself by throttling. They were not designed for users to monitor CPU temperatures, at least in the beginning. So all it needs to do is be fairly...

The Intel Management Engine (IME) software has evolved over the years, from the Intel AMT software (remote PC management in enterprise environments) to the latest versions that include an IME firmware component that is part of the BIOS (like an option ROM.) All Intel chipset boards from the...

Since HWiNFO must poll or request the temperature data from the drive, it does that once each "Scan Interval", which is 2000ms (2 seconds) by default. The drive responds to the request, which causes the activity light to flash. No other way exists for HWiNFO to get the temperature data besides...

Oops, what am I doing not trying 4.23-1973... yes it is perfect! I'd add a screenshot, (if you'd like one) but trust me, it is fine. I'll fool around with the CPU input voltage a bit, but I'm sure it will be fine. I'll let you know if I find anything, but I highly doubt it. Thank again...

So it is common to multiply a data value by some factor to get the true value? Interesting. It looks like the VIDs for this voltage have 10mv steps according to the Haswell Desktop processor datasheet. I'll watch for the next release and report back about the Vcore/CPU Input voltage reading...

Thanks Martin, I appreciate your efforts. I certainly believe your reading, HWiNFO has shown me a few "secrets" like this in the past. Let's see what else I can find... :dodgy:

Thanks Martin, I appreciate it! I'm honored to contribute to the accuracy of HWiNFO in a very small way. :D I forgot to mention the new versions of A-Tuning are posted in the Beta driver and utility section on a board's download page. For my own understanding of this, the "multiplied by...

The new versions of A-Tuning will display the CPU Input voltage, labeled as Vcore, as ~1.800V. New UEFI versions for my board now display CPU Input voltage and core voltage (VID?) correctly... I assume... I have CPU Input voltage set to Fixed, at 1.800V, but see a small fluctuation in the...

No, that is what is seen in the main HWiNFO display with tree, for the processor, that you mentioned in your reply to Stasio's first post in this thread. Vcore on my board does not match those voltage settings in the UEFI. [attachment=714] As I said in my first post, the readings are 19mv...

Thank you anyway Martin, I understand, I was just hoping to get a nice reading like the Gigabyte Z87 boards do, or I should say what you've been able to provide for them. :-/ The ASR Z87 Vcore reading in HWiNFO seems like it is one half of the CPU Input voltage. That is, when I have CPU Input...

Thanks for pointing out the offset and Target voltage displayed in the main window/tree. Using Adaptive CPU voltage, set to 0.800V in the UEFI, HWiNFO reports 819mv. I had CPU, LLC/Ring, and iGPU all set to 0.800V in the UEFI, and they all are reported as 819mv in HWiNFO. I hate false BIOS/UEFI...

Hi Martin, I'm back to create more work for you ;) You may recall my thread about the Vcore and VID readings on my ASRock Z87 Extreme 6 board, with an i5-4670K. I also understand that you are at the mercy of the sensor chip used on a board, the (lack of) information provided by the...

Thanks, I'll try that, maybe it will work. Not included in the downloads for my board. Martin, Thanks, I'll try that version from ASR, but it's listed as an older version (1.0.26) compared to my board's version (1.0.36), if those numbers matter between boards. UPDATE: All the drivers and...

Yes Martin, I did have the VID fields disabled, since I thought that the VID (Voltage Identification ) value (in earlier Intel CPUs?) was a data item that causes a specific voltage to be sent to the CPU, rather than the actual voltage itself. The VID values for a core shown did not match the...

I should have known better, sorry Martin, that AIDA64 value seemed plausible and was close to what I saw using Intel XTU (who knows if XTU is right?) Also, so obvious (Duh!) a VID for each core has been displayed by HWiNFO64 for a long time. Before Haswell, the Vcore into the CPU was one...

Well, I've changed my mind about the "Vccin" and "Vcore" values in v4.18-1930 and v4.19-1945 Beta, respectively. They are both not the correct CPU core voltage, but I realize that is because you don't have enough information for my board, hopefully. Actually, the Beta version is worse with my...

Hi Martin, I'm using HWiNFO64 v4.18-1930 on my Haswell based PC (ASRock Z87 EX 6 board with Nuvoton NCT6776 chip, i5-4670K CPU, Windows 8 Pro 64bit), and it is working fine. I don't see any posts about HWiNFO64 and Haswell PCs in the forum, so just some comments, FYI information, and questions...

You are welcome, it is well deserved! :) I recall now that I see the Uncore Clock on an X58/i7-930 system, which I believe is fairly new to HWiNFO. Just FYI, I'm not using the integrated graphics (GT) on either PC. I have the GT voltage turned down via a GT voltage offset setting in the...

Every time I install the latest version of HWiNFO, I find new data items and options that are really useful! I get different options depending on the PC platform of course, I doubt I can remember all of the new ones I like, such as: CPU Thermal Throttling, and now per-core, does that actually...

PCH stands for Platform Control Hub, which contains most if not all of what the early generation CPU Southbridge support chips contained, plus some of those that were in the Northbridge. Many of the functions in those two older chips are now on the CPU itself, and in the not to distant future...