Discord Memory Speed Issue

[Exxor]

I am having this very strange bug with the desktop Discord app. My graphics card has run stable for over a year with a +102 on the GPU core, +100 on the GPU memory. It runs at 3600MHz all day long, no hitches or anything. However, over the past few days, Discord received an update, and now whenever Discord is running, my memory speed gets brought down to 3000MHz for the entire duration that Discord is running. I looked at what my GPU is doing using Nvidia Inspector, and when I have a game running, it runs at 1405MHz GPU clock, and 3602MHz memory clock. Which is P0. Its able to run full-tilt like that perfectly fine. Then when I run Discord, the GPU clock stays at 1405MHz, but the memory clock drops to 3005MHz. When Discord runs, it puts the memory down to its P2 state, which is 3005MHz. Yet the GPU clock stays at 1405MHz. I've tried every step and instruction to reverse this, yet when it occurred two days ago, a full uninstall and reinstall rectified the issue. It wasn't until earlier today that Discord pushed another update and the problem reared its head again. I'm at wits end here, and I'm starting to think that it might be an Nvidia driver issue.

PS.: Neglected to mention that my graphics card is the PNY GTX 960 4GB.

 

[RJARRRPCGP]

I thought it was a Radeon RX 580 at first, (woops) as my RX 580 runs at 1405 MHz.

If there's a watt limit for the reason, I sure wouldn't expect that! I would expect the core to be the first thing it drops the frequency on.

More likely a video driver issue, indeed.

 

[Toothless]

Hardware acceleration on?

 

[Exxor]

Hardware acceleration on?

It happens regardless of whether hardware acceleration is on or not. I've tried just about everything. I've been relegated to using the browser version because of this issue. I wouldn't doubt a driver issue because even though I always update my graphics drivers through use of DDU and ensuring that each update to my graphics drivers is as clean as possible, this nonsense still happened. So perhaps its an issue with Nvidia's drivers.