Oh my god don’t ask me that. It’s so embarrassing. I built this pc as my 2nd build ever. I got into computers super late in life so learned with the first then just as I was finishing rhe zen 5 cpus came out and 4090’s so I went right into build 2 right whe they came out. I wasn’t patient. I didn’t understand a fucking lick about how resolution, frame rate, or refresh rate or even what the difference between a monitor and TV were. So I have 2 reasonably priced Samsung 27" 4k monitors with standard 60hz… but wait there’s more. Then I saw this waaaay too good to be true deal that I was waaaaah to ignorant and impulsive to know was not what I wanted so I bout the 32" fuckin quad HD 165hz curved screen sceptre on Amazon. Soooooooo dumb. Sooooooooo useless. Every fuckin monitor I bought was bought with specs that are usess for it’s purpose or missing the only spec I thought I was building a pc for.
Anyway I totally think I know where you are going with this tho cuz yes the screens were causing tons of issues for me but I was able to get all three running together at their native resolutions and refresh rates. The high clocks and temps from the monitors were more causing me to have to reinstall my nvidia drivers with fresh installs and wasn’t ever an idling issue. They were crashes from running out of their ranges and me trying to muscle them into proper scaling sizes so their orientation wasn’t all fucky going screen to screen
What I was alluding to with regards to idle mclk behaviour is that there are two factors at play: vertical balanking interval (intrinsic to available display modes for each physical monitor) and combined display bandwidth (cumulative of all connected displays to the adapter).
Your mclk will idle high with ‘incompatible’ VBIs, and it’ll also idle high to sustain a lot of display throughput.
This can be observed regardless of GFX vendor, though symptoms may vary somewhat between them. I suppose it could be considered a limitation of GDDR (the same behaviour was never really observed on HBM GPUs like the Vega 64 or Radeon VII)
That said, friends of mine with nvidia gpus have fixed various multi-display specific issues using nvidia profile inspector
Oh my god don’t ask me that. It’s so embarrassing. I built this pc as my 2nd build ever. I got into computers super late in life so learned with the first then just as I was finishing rhe zen 5 cpus came out and 4090’s so I went right into build 2 right whe they came out. I wasn’t patient. I didn’t understand a fucking lick about how resolution, frame rate, or refresh rate or even what the difference between a monitor and TV were. So I have 2 reasonably priced Samsung 27" 4k monitors with standard 60hz… but wait there’s more. Then I saw this waaaay too good to be true deal that I was waaaaah to ignorant and impulsive to know was not what I wanted so I bout the 32" fuckin quad HD 165hz curved screen sceptre on Amazon. Soooooooo dumb. Sooooooooo useless. Every fuckin monitor I bought was bought with specs that are usess for it’s purpose or missing the only spec I thought I was building a pc for.
Anyway I totally think I know where you are going with this tho cuz yes the screens were causing tons of issues for me but I was able to get all three running together at their native resolutions and refresh rates. The high clocks and temps from the monitors were more causing me to have to reinstall my nvidia drivers with fresh installs and wasn’t ever an idling issue. They were crashes from running out of their ranges and me trying to muscle them into proper scaling sizes so their orientation wasn’t all fucky going screen to screen
What I was alluding to with regards to idle mclk behaviour is that there are two factors at play: vertical balanking interval (intrinsic to available display modes for each physical monitor) and combined display bandwidth (cumulative of all connected displays to the adapter).
Your mclk will idle high with ‘incompatible’ VBIs, and it’ll also idle high to sustain a lot of display throughput.
This can be observed regardless of GFX vendor, though symptoms may vary somewhat between them. I suppose it could be considered a limitation of GDDR (the same behaviour was never really observed on HBM GPUs like the Vega 64 or Radeon VII)
That said, friends of mine with nvidia gpus have fixed various multi-display specific issues using nvidia profile inspector