- Joined
- Sep 21, 2021
- Messages
- 46 (0.04/day)
- Location
- Germany
Processor | AMD Ryzen 7 3800 XT @ 4250 MHz, 1.275V |
---|---|
Motherboard | MSI B550-A Pro, chipset: 3.09.01.140, BIOS A.50 (7C56vA5), Agesa 1.2.0.0 |
Cooling | Scythe Mugen 5 Rev B, 4x CoolerMaster SickleFlow 120 PWM [100% RPM @ 70°C] |
Memory | 2x 16 GB G.Skill F4-3600C16-16GVKC, Dual Channel, Dual Ranks, 1.35V |
Video Card(s) | ASRock RX 5700 XT Challenger Pro 8GB, driver 21.9.1, S.A.M. enabled, 155W undervolt |
Storage | 2x 2TB NVMe |
Display(s) | 1x 1920x1080p 60Hz, 1x 2560x1440p 60Hz |
Power Supply | 650W: 20A 3,3V; 20A 5V; 54A 12V; 80+ Gold |
Benchmark Scores | timespy: GPU ~9800, CPU ~10600 |
I am wondering how the RX 5700 XT memory clock is controlled,
and if there is such a thing as "GPU memory spread spectrum"?
Adrenalin 20.11.2 (nov 2020) changed the memory clock behavior,
or at least changed how the value is displayed to the user (on a driver level).
- Stock RX 5700 XT memory clock is 1750 MHz (GDDR6 Micron)
- GPU-Z reports 1750 MHz default memory clock (on first tab)
- but on the sensors tab the memory clock fluctuates from 1742 - 1754 MHz (under load)
- any driver before 20.11.2 was always reporting 1750 MHz stable, no fluctuation
- installing 20.8.3 for example will still show 1750 MHz stable (even today).
So to get to my question:
Could this be a driver enforced "spread spectrum"?
(or has it always been running like this and they changed the way it is displayed?)
and if there is such a thing as "GPU memory spread spectrum"?
Adrenalin 20.11.2 (nov 2020) changed the memory clock behavior,
or at least changed how the value is displayed to the user (on a driver level).
- Stock RX 5700 XT memory clock is 1750 MHz (GDDR6 Micron)
- GPU-Z reports 1750 MHz default memory clock (on first tab)
- but on the sensors tab the memory clock fluctuates from 1742 - 1754 MHz (under load)
- any driver before 20.11.2 was always reporting 1750 MHz stable, no fluctuation
- installing 20.8.3 for example will still show 1750 MHz stable (even today).
So to get to my question:
Could this be a driver enforced "spread spectrum"?
(or has it always been running like this and they changed the way it is displayed?)