Search the Community
Showing results for tags 'amd'.
Found 4 results
Due to the enermous number of requests we've been receiving since the Ryzen market launch, concerning various confusions about AIDA64 and Ryzen, hereby we post a clarification. AIDA64 is currently not 100% compatible with the recently unveiled AMD Ryzen high-performance x86 processors. It's because AIDA64 still has a few issues that we need to fix. However, in order to fix those issues, we first need to run a series of very long benchmark tests on Ryzen, and that -- among with the bug fixes themselves -- will take several days to complete. As for the bugs and limitations we so far discovered: UPDATE: We have fixed #3, #4, #5 and #7 in the latest AIDA64 v5.90.4200 stable update, which is now 100% compatible with AMD Ryzen processors: https://www.aida64.com/downloads/latesta64xe 1) A number of minor hardware detection issues were already fixed in the latest AIDA64 beta update. 2) The list of Turbo and XFR PStates are invisible on Ryzen, so it's not possible to properly enumerate or track them using a software. When a core of the AMD Ryzen processor goes into idle, the core will report the clockspeed of the P2 power state (e.g. 2200MHz on the Ryzen 7 1800X) and enter into the core-c1 (CC1) or core-c6 (CC6) sleep state. While the VID remains detectable in these states, the states are power gated and the true frequency is not known to the OS or monitoring utilities. As indicated from the “fine-grained Pstate” commentary released at Ryzen Tech Day, the AMD Ryzen’s processor true frequencies in these modes are significantly lower than reported via the “last known” P2 reading. AMD engineering tells us that V/f changes can be executed at 1ms intervals, indicating that the act of monitoring the states with the resolution necessary to accurately capture this behavior would also prevent cores from entering into the ultra low-power CC1 or CC6 states. 3) L1 cache bandwidth and latency scores, as well as memory bandwidth and latency scores are already accurately measured. 4) L2 cache and L3 cache scores indicate a lower performance than the peak performance of Ryzen. The scores AIDA64 measure are actually not incorrect, they just show the average performance of the L2 and L3 caches rather than the peak performance. It will of course be fixed soon. 5) Even though AIDA64 warns about a potential lack of optimization, the CPU and FPU benchmarks should be indicative of the full potential of Ryzen. We may be able to tweak e.g. the FPU Julia benchmark to squeeze even more performance out of Ryzen, but we don't expect the improvement to be substantial. 6) The CPU Hash benchmark provides an exceptionally great score on Ryzen due to the hardware accelerated SHA instructions capability of Ryzen. It's absolutely normal that hardware acceleration boosts CPU computing performance by such a margin. 7) AM4 motherboards are not yet supported by the latest AIDA64 stable build of v5.80.4000. Make sure to use the latest AIDA64 beta build to have accurate sensor measurements on ASRock, Asus, Biostar, Gigabyte, and MSI AM4 motherboards. We will post further updates to this topic as we progress with our bug fixing efforts on our Ryzen test systems.
RealCybertron posted a topic in Hardware monitoringI bought my PC recently, and I noticed that my system temperature is pretty high. I ran multiple tests with AIDA 64, HWInfo and HWMonitor and they all showed some problems which I do not know to solve on my own. First of all, my CPU voltage is not stable and can go very very high. For example while playing some games, the voltage hits up to 1.5V and so the temp hits for about 72C. I'm using a stock Spire cooler so this is very dangerous. I tried to change my CPU voltage in my motherboard to 1.2V but to no avail. My PC started, it loaded up my config and the screen turned off while the EZ debug led lighted up. I never tried overclocking but I changed the curve of my GPU fan speed, as it was also getting hot during gaming. One last thing, a small red led is always lit up between my CPU socket and RAM. I asked about its purpose to a technician and he said to me that it shows that my motherboard is getting power. I thought it was a little bit ridiculous and I still don't know its purpose. Maybe it's an indicator for over voltage? My specs: Ryzen 1500x with Spire cooler GTX 1080 graphics card 8x2 2400 mhz ram MSI b350 mortar motherboard 650w 80+ power supply Windows 10 as OS I can provide pictures of my system and its benchmarks/monitoring
3ogdy posted a topic in Hardware monitoringHi everyone, I've been experiencing this strange issue for quite some time now and haven't bothered to investigate until very recently. My BIOS can read CPU temps just fine. I happen to be the owner of a G15 Keyboard and AIDA64 is a great tool for monitoring temps, Voltages, and many other things straight from the LCD. To the point: My CPU temperature is displayed as 0ÂºC in AIDA64 Extreme 5.60.3700. I know the NH-D15 is an amazing cooler and all, but it looks like it's a bit too good, haha. It is not displayed at all on my G15 LCD. On the LCD, the CPU voltage appears as 0V. N/A for the actual consumption in W. GPU usage is also nto on the LCD - instead of getting VRAM and processor temps (for the GPUs) I get N/A on the LCD. I get N/A for VRM and RAM temps too. System in question: Windows 7 Ultimate x64 SP1 FX-8350 Sabertooth 990FX R2.0 (it has ThermalRadar for CPU temp monitoring and fan configuration - the CPU temp appears listed over there in pretty normal readings...45ÂºC on average - even DRAM and USB3.0 ports have their temps displayed there. Same goes for voltages) HD6950 Crossfire 32GB of RAM CoreTemp works just fine, reporting per core temps and voltages correctly.