Jump to content
AIDA64 Discussion Forum

All Activity

This stream auto-updates     

  1. Today
  2. Squall Leonhart

    FPU VP8 not using 100% of CPU

    the spectre patch is not responsible for the util issue here, the effect of the patch halves performance of fpu vp8.
  3. Try disabling screen power management.
  4. It's not really Fiery's fault, but there some new information Re the cause It was a bit premature to mark this thread fixed just because an issue with 1803 was found and worked around, some of us are not even on Win10.
  5. Yesterday
  6. Last week
  7. smilejarik

    What is "normal" for laptop?

    Maybe it will help somebody else. No it wasn't normal for this laptop, now everything is running on 100% as it should: http://prntscr.com/k78aqz I just set this setting inside BIOS: https://prnt.sc/k77t7s So thermal control is set to performance now and it works, otherwise there is no reason to have more powerful processor if it gives you 75% of the power only.
  8. Hello, I'm running an i7-2600k@4.5 GHz and while comparing benchmark results to reference, I noticed that my system is scoring lower than expected in FPU VP8 (7050, give or take ~100). From checking task manager it became apparent that only 90% of CPU time is used, I believe that these missing 10% just about correspond to the lower score. This is under Win7 x64. I'm aware that some benchmarks scale more with memory than clockspeed, like PhotoWorxx, but this doesn't seem to be the case here as I'm getting the same score whether running DDR-1333 or 2133. All of the other benchmarks seem to scale as expected. I've checked a lot of things like power limit in BIOS, turbo on/off etc, but no difference. Some posts even suggest that the Meltdown/Spectre patches are responsible for this (https://www.reddit.com/r/intel/comments/7q554s/meltdownspectre_patch_8700k_wrong_core0_multi_fpu/), so I tried turning those off via registry, but still no difference.
  9. It happened again. It seems that only CPU temp is affacted. CPU Diode and other sensors are working fine. However, all fan speeds seems to depend on CPU temp, so that in the image below, fan won't spin up. To me it seems like prolonged pooling to fan speed can still cause the issue, no matter accessing via EC or WMI.
  10. Kirayagami

    Need advance

    Hello people, I just built new PC and the first thing i decided to do after instaling windows, drivers etc... was to run Aida64 test. Surprisingly the test stopped after just 10-12 seconds, with red message above "Warning: Hardware failure detected! Test stopped". I ran more tests and i found out, that if I uncheck "Stress system memory" the test runs OK. So my question is, is something wrong with my RAM or what is causing it? Components: GPU: ASUS ROG STRIX GAMING GeForce GTX 1080 DirectCU III O8GB-11GBPS CPU: AMD RYZEN 7 1700 Motherboard: ASUS PRIME X370-A RAM: CORSAIR 16GB KIT DDR4 3000Mhz CL15 Vengeance LPX Thanks in advance!
  11. Hi Fiery, I was trialing the C6H new BIOS 6201 and latest AIDA 64 Beta version. The fan issue seems to be better, but I got some weird issue. After some CPU-heavy tasks, the CPU temperature reading is off, it now drops very slowly from 65 to 59 in about 5 minutes. On the other hand, HWInfo64 actually have a correct reading, please see attachment. I can't explain it, as HWInfo and AIDA64 should both be reading off the ASUS WMI sensor by now.
  12. I can confirm they are not gone. I will get a KMODE exception every single time if I forget and don't close AIDA64. X99 FTW K 6850K 1080 Ti Win10 1803 all updated and stable as a rock except for this. I've been paying for AIDA for nearly a decade. I'd hate to stop using it because of this. So..right now my paid until 1/30/2020 license is kinda useless. Long Live Lavalys
  13. Did the BIOS update and latest AIDA64 beta fix your problem completely? I'm asking because I still get fan issue even with latest BIOS on C6H and latest AIDA64. I turned off EC support and is using WMI to read sensor data. Does this mean that I may have other programs that is causing the trouble?
  14. So i was going to follow a OC guide and have never used OC og AiDA64 before, but the basic part of the oc guide was that i used the system stability guide However, 10 sec into the test i get the "hardware failure detected!" - but if i uncheck stress system memory i got no issues at all. With everything on basic"auto" in bios i cant locate the problem and dont know how to fix it or what that error actually means? what to do? i got: Nvidia GTX 1060-3GB AMD Ryzen 3 1200- Corsair Vengeance LPX DDR4 3000 C15 2x4GB Samsung 850 Evo 250GB b350 pc mate motherboard
  15. Why is the "Total Power-On Time" shown as N/A for all HDDs? For all SSDs it is shown in days/hours, read from data of ID 09. Tested with aida64 v5.92, 5.95 and 5.97. Edit: Beta 5.97.4657 shows it for an Hitachi HDT721010SLA360, but not for the drive on the screenshot.
  16. 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. 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.
  17. Earlier
  18. stable so far, so that was it, thanks for the bug fix.
  19. They aren't gone, they weren't readily reproducible in the first place. https://forums.geforce.com/default/topic/1061921/geforce-drivers/announcing-geforce-hotfix-driver-398-46/post/5833546/#5833546
  20. Hello it is possible to add it to the Sensor Panel ping, latency ? weather? even the current number of Celsius degrees? I am also missing when displaying the internet speed of KB / s change the measures to MB / s at high values. Or simply adding two decimal places at MB / s 0.00 because currently it can not be done?
  21. I Agree with him man, this is unacceptable.. The weird thing is is that only the ROG boards are affected as far as i know.. Gigabyte and MSI have no problems whatsoever.. They released an BIOS with the implementation but its still not fixed.. I hope they release new BIOS soon with the implementation.
  22. I'm also having the same problem with the AIDA64 for Android app most of the people are having this bug it's really annoying Please help! Blackmart | YouTube GO
  23. Mayo0666

    Share your SensorPanel

    Well noted Fiery, i will go for a Samsung Tablet 7"
  24. Fiery

    Share your SensorPanel

    We generally recommend either going for a cheap 2nd hand TFT monitor (that you can connect via DSub or DVI or HDMI), and then you can use the SensorPanel module as well as put any other window on it -- since it would just be a secondary monitor in Windows... Or if you're ready to spend more $$ on the project: go for a USB connected monitor like Asus MB169B+ : https://www.asus.com/hu/Monitors/MB169BPlus/ Or pick up an Android tablet that you can use along with the AIDA64 RemoteSensor module on WiFi, or with the Odospace LCD module using USB connection. Any other LCD solutions are either not 100% stable (like Samsung SPF Digital Frames) or very expensive to purchase.
  25. Mayo0666

    Share your SensorPanel

    Hi all, I am actually working on a Samsung S3 mini phone as my monitor for AIDA. No Problems till now I would like to buy a 7" or 8" monitor that is simply to connect to AIDA but I am worried to buy a wrong monitor, Any suggestion for a monitor like that that surely works with AIDA? (and do not cost too much.. ), probably an USB connection will not be enougth anymore...
  26. Issue #5 (missing PSU readings): As you can see, HWiNFO64 cannot measure +3.3V current or +3.3V power either, since it's not provided by your PSU for some reason. The total PSU power comes from a different PSU register, but we've never found that reading dependable or accurate enough to use it, especially the power in and efficiency values which are just estimates and can wildly differ from the actual values. Issue #6 (CPU temperature): My understanding is that the CPU temperature reading follows CPU load closely, so I cannot see an issue there. It would be odd and hard to explain if CPU temperature risen while CPU load drops, but I don't think that's the case.
  27. Ok 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. What about the weird temperature spikes and drop in the Stability Test screen for CPU (not CPU Package)?
  1. Load more activity
×