Weird power drop according to MSI AFTERBURNER on RTX 2080 Ti.

Avatar image for sew333
sew333

93

Forum Posts

0

Wiki Points

0

Followers

Reviews: 0

User Lists: 0

#1 sew333
Member since 2006 • 93 Posts

Hello. My card on stock,no oc. Aorus Rtx 2080 Ti Wateforce Xtreme. Today i run firestrike and looking on msi afterburner. For a moment ( exactly 1 second ) gpu power drop for 1 second and clock ,look.

Here,gpu power 58% and clock 1575mhz,but gpu load 96% ( why 96% ? ):

And bum normal again:

Normal clock, 1980mhz:

Any ideas? Rest pc no oc. Psu is Corsair 850 RmX,9900K on stock. Why that happened?

GPU connected from 2 separate cables.

I mean why gpu clock dropped,gpu power dropped,but gpu load not dropped?

Pc is on stock,no oc. All is stable,no crashing,nothing like that i see in games. Today for split second in firestrike. I cant reproduce this even when running heavy tasks in background , no matter what clock not dropping again. ( during that test of course )

So question. Sell psu or gpu and be free , or just what now?

Avatar image for Yams1980
Yams1980

3637

Forum Posts

0

Wiki Points

0

Followers

Reviews: 26

User Lists: 0

#2 Yams1980
Member since 2006 • 3637 Posts

I haven't run that benchmark before so I'm not familiar with it. Maybe it was loading a new area and assets for that brief moment when the power level dropped? GPU's go almost idle when they are waiting for something to load.

You should benchmark other games and see if it happens during normal gameplay and not inbetween loading screens.

Avatar image for BassMan
BassMan

10773

Forum Posts

0

Wiki Points

0

Followers

Reviews: 127

User Lists: 0

#3  Edited By BassMan
Member since 2002 • 10773 Posts

Nothing to worry about. It was probably loading a new scene. If your games are not being affected, it doesn't matter what the graph says.

Avatar image for sew333
sew333

93

Forum Posts

0

Wiki Points

0

Followers

Reviews: 0

User Lists: 0

#4 sew333
Member since 2006 • 93 Posts

It happened in middle of the test. I cant reproduce that again. I tried to reproduce this by running heavy tasks in background during test but clock not dropping again. Dunno why it happened before.