an3k
-
Posts
22 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by an3k
-
-
-
On 7/4/2018 at 11:28 AM, Fiery said:
Issue #3 (first 2 RAM slot labels on OSD Panel): Maybe it's because you've previously edited the OSD item labels and AIDA64 remembers that label that you've previously specified. You can reset those OSD items if you close AIDA64, go to AIDA64 installation folder, open AIDA64.INI for editing (using e.g. Notepad), find the lines starting with OSDItem_TDIMMTS and remove those lines from the AIDA64.INI file.
I followed your advise. I now have the wrong naming again (A1,A0,B1,B2,C1,C2,D1,D2). After removing those lines, starting AIDA again and configuring the OSD Panel I now see these lines in the ini file:
OSDItem_TDIMMTSA1=<ORD>128</ORD><SHOW>1</SHOW><FONTNAME>Segoe UI</FONTNAME><FGCOLOR>5242703</FGCOLOR><TEXTSIZE>11</TEXTSIZE><BOLD>1</BOLD><ITALIC>0</ITALIC> OSDItem_TDIMMTSA2=<ORD>129</ORD><SHOW>1</SHOW><FONTNAME>Segoe UI</FONTNAME><FGCOLOR>5242703</FGCOLOR><TEXTSIZE>11</TEXTSIZE><BOLD>1</BOLD><ITALIC>0</ITALIC> OSDItem_TDIMMTSA3=<SHOW>0</SHOW><FONTNAME>Segoe UI</FONTNAME><FGCOLOR>5242703</FGCOLOR><TEXTSIZE>16</TEXTSIZE><BOLD>1</BOLD><ITALIC>0</ITALIC> OSDItem_TDIMMTSB1=<ORD>130</ORD><SHOW>1</SHOW><FONTNAME>Segoe UI</FONTNAME><FGCOLOR>5242703</FGCOLOR><TEXTSIZE>11</TEXTSIZE><BOLD>1</BOLD><ITALIC>0</ITALIC> OSDItem_TDIMMTSB2=<ORD>131</ORD><SHOW>1</SHOW><FONTNAME>Segoe UI</FONTNAME><FGCOLOR>5242703</FGCOLOR><TEXTSIZE>11</TEXTSIZE><BOLD>1</BOLD><ITALIC>0</ITALIC> OSDItem_TDIMMTSB3=<SHOW>0</SHOW><FONTNAME>Segoe UI</FONTNAME><FGCOLOR>5242703</FGCOLOR><TEXTSIZE>16</TEXTSIZE><BOLD>1</BOLD><ITALIC>0</ITALIC> OSDItem_TDIMMTSC1=<ORD>132</ORD><SHOW>1</SHOW><FONTNAME>Segoe UI</FONTNAME><FGCOLOR>5242703</FGCOLOR><TEXTSIZE>11</TEXTSIZE><BOLD>1</BOLD><ITALIC>0</ITALIC> OSDItem_TDIMMTSC2=<ORD>133</ORD><SHOW>1</SHOW><FONTNAME>Segoe UI</FONTNAME><FGCOLOR>5242703</FGCOLOR><TEXTSIZE>11</TEXTSIZE><BOLD>1</BOLD><ITALIC>0</ITALIC> OSDItem_TDIMMTSC3=<SHOW>0</SHOW><FONTNAME>Segoe UI</FONTNAME><FGCOLOR>5242703</FGCOLOR><TEXTSIZE>16</TEXTSIZE><BOLD>1</BOLD><ITALIC>0</ITALIC> OSDItem_TDIMMTSD1=<ORD>134</ORD><SHOW>1</SHOW><FONTNAME>Segoe UI</FONTNAME><FGCOLOR>5242703</FGCOLOR><TEXTSIZE>11</TEXTSIZE><BOLD>1</BOLD><ITALIC>0</ITALIC> OSDItem_TDIMMTSD2=<ORD>135</ORD><SHOW>1</SHOW><FONTNAME>Segoe UI</FONTNAME><FGCOLOR>5242703</FGCOLOR><TEXTSIZE>11</TEXTSIZE><BOLD>1</BOLD><ITALIC>0</ITALIC> OSDItem_TDIMMTSD3=<SHOW>0</SHOW><FONTNAME>Segoe UI</FONTNAME><FGCOLOR>5242703</FGCOLOR><TEXTSIZE>16</TEXTSIZE><BOLD>1</BOLD><ITALIC>0</ITALIC>
I guess I can figure out what A1 and A2 is but I still wonder how AIDA suddenly thinks there's A0 now.
On 7/4/2018 at 11:28 AM, Fiery said:Issue #6 (background polling of sensor readings): It's most likely caused by another AIDA64 hardware monitoring module that keeps running in the background even with the OSD Panel disabled/hidden. On PC1 make sure to check if you have other modules enabled, like Desktop Gadget, LCD, External Applications or Logging.
I checked everything and noticed I had one LCD enabled. I disabled it and made sure nothing else is enabled. However background polling is still happening.
-
3 hours ago, Fiery said:
It's rather difficult for us to track your individual issues because it's flooding a single topic and causing single posts to become very long. After resolving these issues please post new issues into separate, new topics. That way we'll be able to sort them out much easier, and focus on them individually.
Ok
3 hours ago, Fiery said:Issue #5 (missing PSU readings): +3.3V current reading fails on your AX1500i PSU. I'm not sure why that is, but in the dump it's clearly failing. That causes the missing +3.3V power reading as well (since +3.3V power is calculated by multiplying +3.3V voltage and +3.3V current readings). That also causes the missing PSU power reading, since PSU power is calculated by adding up +3.3V power, +5V power and +12V power. Corsair RMi PSUs do not monitor -12V voltage rail.
Corsair iCUE as well as Corsair LiNK (the software) as well as HWiNFO64 can read the PSU power readings. Based on how quickly these values are shown and how often they're updated it looks like not all values are transmitted with every request but only eg. every third request.
3 hours ago, Fiery said:Issue #6 (CPU temperature): We're pretty sure we're using the right sensor chip rail to measure CPU temperature on your motherboard. If it's not in line with other software's measurements, it's not really the fault of our software
What about the weird temperature spikes and drop in the Stability Test screen for CPU (not CPU Package)?
-
I noticed a new issue, please see attached screenshots.
CPU sensor temperature is different to those in SpeedFan (buggy), MSI Afterburner and HWMonitor.
Additionally there is a huge temperature rise when load is applied to the CPU and a huge drop when there is no load anymore.
-
I wonder if my AIDA64 Business license also included support or just more features?!
-
I thought so. No problem
I'll multi-quote the stuff still present. Thanks for taking time to read&answer while writing code to improve AIDA 
PC 1) ASUS Rampage V Edition 10, Core i7-6950X, Corsair AX1500i, Corsair (Asetek) H115i.
PC 2) ASUS Rampage V Edition 10, Xeon E5-2680 v3, Corsair RM650i, Corsair (Asetek) H115i.
QuoteIssue 1
For most of the time PC 1 had a sensor called "Water Pump" for which I had to set a correction so that the pump RPM are shown correctly. I had to do the same for PC 2. Since some weeks PC 1 now additionally shows "Pump #1" for which I don't need a correction. PC 2 still just shows "Water Pump". On both systems Embedded Controller (EC) support is enabled and Embedded Controller (EC) bank switching is disabled.
Cause 1)
I found out the reason for this behavior. As soon as Asetek LC sensor support is enabled two new sensors appear, "Temperature #1" and "Pump #1". However, on PC2 the same option is enabled too but I don't get these two sensors shown at all.
How come that Asetek LC sensor support on PC1 shows these two additional sensors while on PC2 it does nothing? Driver issue?
QuoteIssue 2
On PC 1 the RAM slots are named A1, A2, B1, B2, C1, C2, D1 and D2. On PC 2 they're named A1, B1, E1, F1. You replied with "SPD chips are wired in a different way on Broadwell-E (i7-6950X) and Haswell-EP (Xeon E5-2680 v3) processors. Different SPD controllers are connected to the same DIMM slots, and that is why the DIMM thermal readings labels differ across those CPUs." but I checked the DMI information in AIDA and saw this
PC1
PC2
QuoteIssue 3
I also have a new problem now that labels RAM on PC1 as A0, A1, B1, B2, C1, C2, D1, D2 in the OSD Panel but it still remains A1,A2,B1,B2,C1,C2,D1,D2 in AIDA itself. Is A0 actually A1 and A1 actually A2 or is A1 still A1 and A0 actually A2? How come these differences between AIDA and its OSD Panel?
QuoteIssue 4
Sometimes AIDA does not show the installed RAM modules in Computer > Summary even though it does know the installed modules. The installed modules should be shown in category "Motherboard" between System Memory and BIOS Type. I also noticed that sometimes not the whole information is read from the DIMM, see last screenshot.
QuoteIssue 5
The following sensors cannot be read from the AX1500i but from the RM650i: +3.3V [Current], +3.3V [Power], Power Supply [Power].
The following sensors cannot be read from the RM650i but from the AX1500i: -12V [Voltage]
QuoteIssue 6
Both PSUs have a red hardware LED that lights up whenever sensor data is being read. I noticed that on PC2 (RM650i) the PSU doesn't send any data as soon as the AIDA OSD is hidden (but AIDA still running in system tray). On PC1 the PSU (AX1500i) keeps sending data even when the OSD is hidden. It only stops after AIDA is completely closed.
-
Any updates? PC1 got rid of the Asetek AIO and gets cooled by a complete custom loop so no interference from these anymore.
It would be awesome if AIDA could show the wattage the AX1500i eats/provides just like the RM650i. I posted the USB PSU Dump a while back.
-
Check in the BIOS if that sensor shows a weird value, a straight zero or something negative.
-
Do you have a Corsair PSU? If so is it an AXi or HXi/RMi? Disable the option of the PSU you don't have. If you don't have a Corsair disable both.
Additionally if you don't have a Corsair Commander (hardware thingy you need to buy) disable Corsair Link sensor support. This is NOT for the software!
Test now if it still freezes.
Disable Embedded Controller (EC) bank switching
Test for freezes again.
Disable one of the three remaining Low-level XYZ operations options and test for freezes after each change.
If it's still freezing disable GPU sensor support.
If it still freezes it is a different cause that is just triggered by AIDA, eg. driver or hardware issue.
-
You're welcome. At first use AIDA is too overwhelming to understand it's power but once you played a little bit you see it's way better than other tools, especially because you can configure it how you like it. You want to test OSD Panel or SensorPanel
-
I also noticed a possible bug.
While AIDA is not able to list the RAM on PC2 (but on PC1) it is generally able to read the data of the installed modules.
PC1
PC2
PC2
-
On 2/22/2018 at 4:55 PM, an3k said:
On PC 1 the RAM slots are named A1, A2, B1, B2, C1, C2, D1 and D2. On PC 2 they're named A1, B1, E1, F1.
Regrading this issue I found the DMI information in AIDA. Core i7-6950X is PC1, Xeon E5-2680v3 is PC2.
I assume AIDA isn't using the DMI to name the RAM slots but some extremely complex and patent pending algorithm instead?
Or is it because PC2 has two Memory Arrays (with 4 slots each; because of the CPU) and PC1 has just one (with 8 slots)?
-
On https://www.aida64.com/downloads you can read the following:
QuoteHere you can download a free 30-day trial of AIDA64 Extreme and AIDA64 Engineer. During the trial period AIDA64 may offer limited functionality, and may not display all data on the information and benchmark result pages.
I assume you haven't bought AIDA64 yet but use the 30-day trial which may not show GPU or HDD temps but TRIAL instead.
-
Hehe yeah. PC1 as well as PC2 both have a Corsair H115i (Asetek). PC1 additonally has a watercooled graphics card from Corsair which uses a H50 or H55 (also Asetek).
To verify that the two sensors are not from the graphics card I enabled the option so see the sensor values and then set the H115i from "Performance" (~3100 RPM) to "Quiet" (~2000 RPM) in the Corsair LINK software. Both sensors ("Water Pump" = physical fan header on the mainboard and "Pump #1" = Asetek LC sensor support) went down from ~3100 RPM to ~2000 RPM.
How come that Asetek LC sensor support on PC1 shows these two additional sensors while on PC2 it does nothing?
-
On 2/22/2018 at 4:55 PM, an3k said:
For most of the time PC 1 had a sensor called "Water Pump" for which I had to set a correction so that the pump RPM are shown correctly. I had to do the same for PC 2. Since some weeks PC 1 now additionally shows "Pump #1" for which I don't need a correction. PC 2 still just shows "Water Pump".
For most of the time PC 1 showed Temperature #1, #2 and #3 (I connected the ASUS addon card). Suddenly "Temperature #4" showed up. PC 2 does not even show "Temperature #1" (no ASUS addon card).
I found out the reason behind these too issues. As soon as Asetek LC sensor support is enabled two new sensors appear, "Temperature #1" and "Pump #1".
However, on PC2 the same option is enabled too but I don't get these two sensors shown at all. Maybe a driver issue?
-
You have to manually find out what name in AIDA each physical sensor has. The easiest would be to disconnect one sensor and restart AIDA. If Temperature #3 is missing you know that the one you disconnected is Temp #3. Reconnect it, restart AIDA and rename Temperature #3 to something you like. Do the same with the remaining sensors.
We had to do such things for ages before mainboards got plenty of fan headers with names printed next to the connector.
-
I do have Corsair LINK installed on both systems. Same version on each. In AIDA I had "Corsair Link sensor support" enabled but since it didn't made any change on both systems I disabled it because I don't want another software hooked up in the "sensor reading process". I have the same amount of sensors with or without that option enabled. I guess it's for Corsair Commander stuff (Fan Controller, etc.) that can only be read through Corsair LINK software?
Both PSUs have a red hardware LED that lights up whenever sensor data is being read. I noticed that on PC2 (RM650i) the PSU doesn't send any data as soon as the AIDA OSD is hidden (but AIDA still running in system tray). On PC1 the PSU (AX1500i) keeps sending data even when the OSD is hidden. It only stops after AIDA is completely closed.
EDIT: Regarding 7) the Fan is indeed not sending out data, the BIOS simply shows "0". I just need to check if the fan or the sensor itself is damaged.
EDIT 2: The fan is borked. A different one immediately let the sensor pop up in AIDA with some logical RPMs.
-
I just installed the update and made sure both options are enabled but sadly it doesn't make any difference at all. I still have the very same sensors available on PC1 and PC2 I had before the update.
-
I don't have Corsair AXi sensor support or Corsair HXi/RMi sensor support
PC1
PC2
PC2 nVIDIA SMBus Dump
-
1) PC1 is identical with PC2 and on PC1 I only had Waterpump for most of the time until Pump #1 suddenly appeared. Both systems are also running the identical set of software and also the same versions (AIDA64, Corsair LINK, etc.). On both systems Embedded Controller (EC) support is enabled and Embedded Controller (EC) bank switching is disabled since I never needed bank switching and read that it causes troubles and can cause damages.
2) Roger
3) Silly manufacturers
4) Right, the AX1500i of PC1 is more sophisticated than the RM650i of PC2 but the later provides more sensor readings.
5) PC1: nVIDIA GeForce GTX1080, PC2: nVIDIA GeForce GTX1050Ti
6) See 4)
7) I'll check that
8) Roger, Roger
Thanks for your feedback so far, hope it's a AIDA64 problem regarding those sensors and not a hardware issue (simply because I don't want to dissemble and RMA anything
)
PC1
PC2
-
Hi everybody,
I have two Computers.
PC 1) ASUS Rampage V Edition 10, Core i7-6950X, Corsair AX1500i, Corsair (Asetek) H115i.
PC 2) ASUS Rampage V Edition 10, Xeon E5-2680 v3, Corsair RM650i, Corsair (Asetek) H115i.
For most of the time PC 1 had a sensor called "Water Pump" for which I had to set a correction so that the pump RPM are shown correctly. I had to do the same for PC 2. Since some weeks PC 1 now additionally shows "Pump #1" for which I don't need a correction. PC 2 still just shows "Water Pump".
For most of the time PC 1 showed Temperature #1, #2 and #3 (I connected the ASUS addon card). Suddenly "Temperature #4" showed up. PC 2 does not even show "Temperature #1" (no ASUS addon card).
On PC 1 the RAM slots are named A1, A2, B1, B2, C1, C2, D1 and D2. On PC 2 they're named A1, B1, E1, F1.
On PC 1 I don't get a sensor reading of "+3.3 V Power" or "Power Supply" but "GPU TDP%". On PC 2 I do get "+3.3V Power" and "Power Supply" but no "GPU TDP%". I also don't get "+3.3 V Current" on PC 1 but on PC 2. However, I do get "+3.3 V" and "+3.3 V Standby" for Voltage on both PCs and PC 1 even gets "-12 V" Voltage but not PC 2.
On PC 1 I do get "CPU" and "CPU OPT" fan speed readings. On PC 2 I only get "CPU" and once for a very short time (some hours) "CPU OPT".
Is that normal? And if not, how can I tell AIDA64 Business to forget everything about sensors and read all available ones in again?
Thanks
Reset available sensors & missing and duplicate sensors (Asus Rampage V Edition 10)
in Hardware monitoring
Posted
Thanks!
I'm going to test a blank installation. Since I use the "portable" version I assume all configuration files are within the AIDA64 directory and nothing is stored in Registry, %LOCALAPPDATA% or %APPDATA%.
I'll reply if I found something regarding these issues.