Jump to content

FatBoyNL

Members
  • Posts

    80
  • Joined

Everything posted by FatBoyNL

  1. Thanks for this update. I can confirm the Northbridge Clock speed is now showing the UCLK speed correctly on my AM5 rig (i.e. 3000 or 1500 MHz for 6000MT/s DDR5). Very nice work👍
  2. AIDA64 always shows a Northbridge Clock speed on AMD AM5 systems as ~1867/~933MHz afaik (depending on 1:1 or 1:2 settings). (EDIT: while using two sticks of 6000MT/s DDR5 RAM, that is. Faster RAM will probably show other figures) But what's the source of this Northbridge Clock? According to BIOS and other monitoring software, there are no devices using that particular speed/frequency in my AMD AM5 system.
  3. Confirmed, I have the same issue with my RTX 4080 on v7.00.6716 Beta.
  4. Update: I filed a bug report last week, but didn't get any response yet. Or even a confirmation e-mail. Latest beta shows 'same same but different' results btw Recording 2023-12-20 185007.mp4
  5. Hi guys, When I open AIDA64 and go to: Computer - Sensor settings, two different CPU readings are shown incorrectly: Current Values: CPU Power Values: CPU Both CPU readings are clearly not showing actual/current values. Every new reading seems to be automatically added to the one before that (for about 5-10 seconds), and then that counting process starts all over from zero (I guess). What I'm seeing is a sequence like this for "Current Values - CPU" (in incremental steps repeating itself after every few seconds): 6.00A - 38.00A - 66.00A - 98.00A - 130.00A - 164.00A - up to about 250.00A, and then same type of additional counting starts all over again starting with a value close 0A and then counting upwards. It's almost the same issue for "Power Values - CPU", but those readings seem to be more random than the example above: Values are fluctuating but going upwards from around 2.00 W up 250+W (while only typing this): so I'm just assuming both values can't be correct. Does anyone know a solution, fix or workaround for this issue? Currently running AIDA64 7.00.6705 beta, but the issue was already present in 6.92 and later beta versions. Thanks in advance, FatBoyNL Recording 2023-12-14 154149.mp4
×
×
  • Create New...