Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
  • Location

WilleHelm's Achievements


Newbie (1/14)



  1. Hello Fiery, I admit it is their first run with 21H1. They have been reinstalled all at once. So it could be a consequential problem. Previously they ran 20H2 with a late beta of v6.32. Actually there has not been changed much in my install routine. Just newer versions of everything, as I have done for so many years. I don't use AMD OverDrive or any other tool that monitors something, and certainly not ASUS AI Suite. If it wasn't for Samurize where I record minimum values as well, it would propably never catched my eye. Would EC 'Bank Switching' do any good?
  2. Hello, on my three AM3+ machines (AMD FX-9000 CPU, ASUS Sabertooth 990FX R2.0) I have noticed that some sensor values randomly disappear and reappear between refresh cycles (5s in my case). Sometimes within the first minute, but certainly within 5-10 minutes. While idling as well as under load under Windows 10 21H1 x64. That is in WMI and the sensor page where I actually have seen the list shrinking one line and expanding again! So the whole sensor is gone for a period of time. The following voltage values are affected so far: DIMM (VDIMM), CPU/NB (VCPUNB) and HyperTransport (VHT). I can reproduce it with major v6.33.5700 and beta v6.33.5725. It does not happen with previous major releases like v6.32.5600. Only required sensor types are selected: Regards, Wilhelm
  3. I had an idea, which at first seemed like a much easier any possibly more useful approach, but after thinking it over it could be even worse. I thought of an option to output millivolts instead of volts (multiply by 1000), so that up to 3 decimal places can be shown without separator! The problem is, to reflect that change either sensor ID labels have to be renamed vom V to mV , or even the sensor IDs themselfes , or additional IDs carrying mV as unit - and there are a lot of voltage sensor IDs, although I just use five of them.
  4. You are right that many or even most other tools display and export data with dots, regardless of regional settings. If it was just for visual observation, I wouldn't care at all. I've lived with this situation for years now. Maybe I am the only one in need for such an option. At least I have not found another thread here regarding this matter. Although it is not a vital thing to have system monitoring, but since I'm sitting in home office it became especially annoying because I have to use my PC for work as well and I have to rethink what symbol to use locally everytime I calculate something, while any remote system uses the other/usual symbol naturally. To make a long story short, it would be a great relief to have this option. But I don't like the thought of generating a pile of work for you. In turn I cannot imagine a use case for changing the degree symbol either. How does "Automatic" work here? Is a fixed dropdown list easier to implement than a free input like the degree option offers? For safety on your side, I do not recommend switching the fixed dot to the symbol that's being set in the user localization, although I think 99% should definetly work anyway with that as default.
  5. Thanks for replying so fast! My concern is with the voltages, where for example the 12V rail has some decimals. These values are going to be written to WMI (or Registry, it doesn't matter) and a tool called Samurize uses that for metering. Anything I want to do with it is not going to work, until I change decimal symbol in Windows from comma to period. So far I couldn't find an issue on Samurize side, as these values are actually generated by AIDA64 using a period, as seen on the Sensor page as well as the Registry. Samurize evidently uses Windows decimal symbol that is set in my regional settings, which I find rather sophisticated for that aged tool, but is hindering in this case. PS: AIDA64s translation option to German does not do the trick, I've tried that.
  6. I was wondering about that on AMD/AM4 machines for some time too. But while being cosmetical, it would help a lot to quickly identify at what speed components are connected at without doing benchmarking or the need to use other tools just for that purpose. Not only for NVMe SSDs, but also things like secondary graphics cards and 10Gbit network cards are dependend on fast interconnection. Putting it into the wrong slot may cause halfing or even quatering of the bandwitdth. I've experienced this on any AM4 system I have used so far: ASUS ROG STRIX B350-F GAMING // Ryzen 1600 ASUS PRIME B450M-A // Ryzen 1800X ASUS PRIME X470-PRO // Ryzen 2600X GIGABYTE B550 AORUS PRO // Ryzen 3600 & Ryzen 5600 Being the same on any Ryzen generation, AM4 chipset and two makers of mainboards, it can only be a (cosmetical) serial fault that still persists, or AIDA64 misinterpreting something. If it is the former, I suspect other tool makers reading out the same PCIe 2.0 values, but transforming them into the expected values guessed from the present CPU and MB combination. Judging by your words, dear Fiery, "Apparently on your system the motherboard fails..." you suggest that you either know it should work, or you havn't had the opportunity yet. What could it be?
  7. Hello! By using German (or Austrian) regional formats in Windows, it is common to have decimal and digit group separators swapped. Therefore it is mostly impossible to make use of decimal values generated by AIDA64, because the decimal symbol is ignored or wrongly interpreted. I'd love to see an option to change that symbol, like it is already implemented for the degree symbol! It would help me a lot, because the only workaround I have is to manually alter the Windows defaults for my language setup which affects everything.
  • Create New...