Fiery

Thank you. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2215vk0gp7mfzyzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Yes, you need to select a PNG file that you need to create. What I can help you with is uploading the current gauge state images, so you can use Photoshop or some other image editing solution to alter them and create your own, personalized gauge states. Here's the file: http://users.aida64.com/gauge_state_images.zip Regards, Fiery

What I meant to say is that you can try (for a test run, not as a permanent downgrade) an older AIDA64 version, but I do not think it would help on this issue. We've already started investigating this issue on our own i7-3770K test system, but it would help a lot if you could right-click on the bottom status bar of AIDA64 main window --> System Debug --> PCI Dump. Please copy-paste the full results into this topic. Using that data we can check what goes wrong about PCH Diode measurement on your system -- and compare it against our i7-3770K system based on an Asus motherboard. Please note that if we cannot resolve this issue for you, you can ask for a refund on the $30 license upgrade and return back to an old AIDA64 release. We do everything we can to fix all bugs in AIDA64 (you can check other forum topics as a proof on that), so please provide us a bit more time to come up with a fix on this.

We've checked it with both AIDA64 and Everest (last version, v5.50), but we haven't seen a difference in the icons readability at 120dpi. What version of Everest did you use when you made the screen shot above?

Thank you, we'll add your motherboard in the next AIDA64 beta release. Regards, Fiery

We've asked our contact at AMD about this issue. What I can tell you right away is that since many Trinity processors seem to be affected by this anomaly, it definitely looks like it's a hardware issue rather than a software issue (or AIDA64 bug). I'll let you know in this topic once we get more info from AMD about this.

Please try to restart your computer, close any other hardware monitoring software that's running, and check out if the reading is "PCH Diode", and whether it's there or not. You can also try to downgrade to a previous AIDA64 release, but I don't think that would help. Please note that "PCH Diode" temperature readout is done via an undocumented Intel CPU method, and so it is not guaranteed to work on all processors out there. Some users are lucky, and they can see that reading all the time, but in some cases the processor doesn't provide a constantly reliable "PCH Diode" readout.

Thank you, but AIDA64 won't label any temperature readings as "PCH Temperature". It must be either "PCH" or "PCH Diode" inside the temperatures group. Can you please verify the actual label? I suspect it would be "PCH Diode".

Thank you for the feedback

Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2212b1qdtrcn9mzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Thanks, Fiery

Yes, as long as you clearly state in your application that it requires AIDA64 Extreme Edition to work properly. We would appreciate if you could place a link to www.aida64.com in your software's documentation and its about box to make it easier for users to find and download AIDA64. Please note that it is prohibited to embed AIDA64 in another software, regardless of the software's licensing scheme. Regards, Fiery

Do you mean the temperature value called "PCH Diode" ?

We'll soon completely drop all current memory benchmarks, so that issue will automatically solve itself

Yes, it's normal on Sandy Bridge-E and Sandy Bridge-EN/EP processors. We use a wide scanning range for the memory latency benchmark on those processors to make sure we can "hit" on the best latency score with all possible memory configurations (single-channel, dual-channel, triple-channel, quad-channel).

If you use the Sensor Item item type (and not the Simple Sensor Item), then it's quite easy: you just need to use the same width for the whole item, and also the same width for all units. It will then be perfectly aligned. Please note that unlike the Sensor Icons, OSD Panel and Desktop Gadget features of AIDA64, with the SensorPanel it takes a bit more efforts to achieve the looks you want to see. But it worth the efforts, because with the extremely flexible SensorPanel you can do a lot more than with the mentioned other AIDA64 features.

Please avoid opening multiple topics for the same issue. I've replied in your other forum topic. This topic is closed.

That's how it should look like, to make sure the text fits the icon area. As you can see, on the right-hand side the text doesn't fit in the Everest sensor icon: it's the wrong way to display the text there I suppose the visual distortion is caused by a non-standard DPI setting you applied. Is that the case?

Thank you for the data. I think everything's fine there actually. The Overclock page shows not the Vcore reading, but the CPU VID setting which stays intact even if you raise the Vcore.

In a virtualized environment there's no way to access the underlying host hardware, but only the virtualized hardware. So you need to run AIDA64 natively in order to monitor the thermal status and SMART details of your "real" hardware components. Regards, Fiery

Do you mean a voltage reading called "PCH Core" ? If yes, then please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full resuls into this topic. Thanks, Fiery

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. Thanks, Fiery

1) Please copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic. 2) Also, right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. If it's possible, please do those at both default Vcore and at 1.5V (overclock voltage). Make sure to use the latest AIDA64 beta. Thanks, Fiery

In order to avoid log files getting too large, logging is restarted after 24 hours of logging, and so a new log file is opened. If your log file still gets too large in 24 hours, you may want to make update frequency a bit longer. With a 1-second logging rate log files can indeed get a bit huge Alternatively, you can also check if the large log files can be opened better with another browser, e.g. Chrome or Safari. Regards, Fiery

Green line means a process is started, and the red line means a process is finished. If you don't like those lines, you can turn off process logging in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging / Log started and stopped processes. Regards, Fiery

Windows Gadgets have been removed from Windows 8 by Microsoft, because now they want to push "Metro" (or "Modern") style applications instead. I'm afraid AIDA64 cannot put that feature back into Windows 8 However, you can actually configure the SensorPanel to make it look exactly like a Windows Gadget, so we do not feel the lack of Gadgets a real issue about Windows 8. Regards, Fiery