Swear to fucking god the same will happen for GPUs in the next 6-12 months.
EVERYWHERE I looked researching why my RTX 4090 was idling with maxed out mem clock @ 10000MHz not dropping a bit. All the forums, articles and Nvidia themselves gave super standard troubleshooting suggestions before just saying yeah those gpu’s fuckin run spicy.
I underclocked, un-installed, reinstalled, ran it in other PC’s, white washed my drivers, updated bios, flashed bios, pretty sure i biosed my bios, even used recommended windows retarded power throttling setting… fuckin nothing.
Finally during one of my “Fuck Microsoft” tantrums I started belligerently stripping every fucking Windows 11 service, software and apps that would let me. Full on preppared to nuke the whole fuckin PC, not just the OS.
No fucking clue what did it or where it was all I know was it was somewhere in the control panel memory settings/disk optimization-ish/file history/virtual memory area or at least felt like it was from around that before I started aggressively clicking delete one at a time for my entire file history cuz ya know file history has had a bug lasting thru 2 generations of windows now that won’t let you batch delete old files history files. Either way fucker all of a sudden sounded slightly less fans at top seepdy sounding, checked to see if I was loosing it but sure as fuck it really was bringing the gpu back to normal.
Its been humming like a champ ever since. Idles at 5001 runs at 10000 range with curve optimizer. Was able to re-set everything up on a clean install using a local microsoft account, deleted my actual microsoft account, haven’t updated a fucking thing, been running FOLON with 231 enabled mods on 195 plugins. OH and I forgot to mention how noone believ3d me at nvidia that the 4090 when initially bought was running just like this with no issues. Needless to say I’m in stage 2-1/2 of my migration to Linux. Idc if I’m dead wrong about this experience I will never go back to Windows for my erryday desidnated driver or use it more that the 3 pc games I usually play through any year. No internet single player screaming fallacies speech to text into copilot to ruin that cunt fucker and tell people I multi task while gaming.
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
Swear to fucking god the same will happen for GPUs in the next 6-12 months.
EVERYWHERE I looked researching why my RTX 4090 was idling with maxed out mem clock @ 10000MHz not dropping a bit. All the forums, articles and Nvidia themselves gave super standard troubleshooting suggestions before just saying yeah those gpu’s fuckin run spicy.
I underclocked, un-installed, reinstalled, ran it in other PC’s, white washed my drivers, updated bios, flashed bios, pretty sure i biosed my bios, even used recommended windows retarded power throttling setting… fuckin nothing.
Finally during one of my “Fuck Microsoft” tantrums I started belligerently stripping every fucking Windows 11 service, software and apps that would let me. Full on preppared to nuke the whole fuckin PC, not just the OS.
No fucking clue what did it or where it was all I know was it was somewhere in the control panel memory settings/disk optimization-ish/file history/virtual memory area or at least felt like it was from around that before I started aggressively clicking delete one at a time for my entire file history cuz ya know file history has had a bug lasting thru 2 generations of windows now that won’t let you batch delete old files history files. Either way fucker all of a sudden sounded slightly less fans at top seepdy sounding, checked to see if I was loosing it but sure as fuck it really was bringing the gpu back to normal.
Its been humming like a champ ever since. Idles at 5001 runs at 10000 range with curve optimizer. Was able to re-set everything up on a clean install using a local microsoft account, deleted my actual microsoft account, haven’t updated a fucking thing, been running FOLON with 231 enabled mods on 195 plugins. OH and I forgot to mention how noone believ3d me at nvidia that the 4090 when initially bought was running just like this with no issues. Needless to say I’m in stage 2-1/2 of my migration to Linux. Idc if I’m dead wrong about this experience I will never go back to Windows for my erryday desidnated driver or use it more that the 3 pc games I usually play through any year. No internet single player screaming fallacies speech to text into copilot to ruin that cunt fucker and tell people I multi task while gaming.
The important thing is that you’re not bitter.
It goes as low as 405mhz on Linux for me (4070ti)
Luuuuucky. Lol can’t wait to run benchmarks from a Linux os when its all said and done.
I don’t think this is related to the OS. What displays do you have connected?
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
JFC, win_blows_.