[SOLVED] Discord using 100% of gpu then blackscreening for a few sec

[Zykrim]

Hi, i recently upgraded to a 5700 xt from a 970, but i run into a problem with both discord and league of legends where they suddenly use 100% of the gpu. Eventually blackscreening and coming on again with amd telling me the "wattman" settings have been reset or something. I cant even seem to close discord from task manager to prevent this i just have to wait for it to hopefully end quick. Sometimes i even have to reset the whole computer because the screen doesnt turn on again. Is this a common problem for the 5700 series? And has anyone else experienced this and know a fix? answers will be much appreciated! (just for info I havent overclocked it or done anything in the settings the only thing ive done is install the latest driver for it).

 

[Ketchup79]

What power supply do you have?

 

[Zykrim]

What power supply do you have?

This one https://www.evga.com/products/product.aspx?pn=210-gq-0650-v1

 

[Ketchup79]

Power is good. Can you upload any dump files for us to review? Are you running any temperature monitoring software?

 

[Zykrim]

Power is good. Can you upload any dump files for us to review? Are you running any temperature monitoring software?

How do i find these dump files and im running msi afterburner, the temp never got over 71 celsius

 

[Ketchup79]

C:\Windows\Minidump. You may have to tell Windows to show hidden files if you aren't doing so already.

 

[Zykrim]

C:\Windows\Minidump. You may have to tell Windows to show hidden files if you aren't doing so already.

I enabled show hidden files, but still cant seem to find minidump in the windows folder

 

[Ketchup79]

Well, there is a blue screen, and there is a dump. All dumps will be preceded by blue screen, but a dump will not follow all blue screens. When you see a blue screen, it is in on the screen long enough to read? If you go to Event Viewer, Windows Logs, System, are there any Warnings or Errors around the time of the crash?

 

[Zykrim]

Well, there is a blue screen, and there is a dump. All dumps will be preceded by blue screen, but a dump will not follow all blue screens. When you see a blue screen, it is in on the screen long enough to read? If you go to Event Viewer, Windows Logs, System, are there any Warnings or Errors around the time of the crash?

its not a bluescreen it goes black completely for a few secs then comes back

 

[Ketchup79]

My bad. So if you just get rid of Wattman (temporarily at least) does the problem go away?

 

[Zykrim]

My bad. So if you just get rid of Wattman (temporarily at least) does the problem go away?

Im going to be honest here i dont really know what wattman is, I couldent find it in amd adrenaline. Do you know how i go about removing it?

 

[Ketchup79]

You can try disable, or you can uninstall and reinstall your AMD drivers, with the reinstall being manual, choosing not to add Wattman (what I would do).

https://community.amd.com/thread/237941

 

[Zykrim]

You can try disable, or you can uninstall and reinstall your AMD drivers, with the reinstall being manual, choosing not to add Wattman (what I would do).

https://community.amd.com/thread/237941

Alright just reinstalled it ill see how it goes! Thanks for all the help much appreciated! 😀

 

[S.I.R.O.]

Have had pretty much the same problem(also have a 5700xt), discord will just blackscreen after a while(so that I have to end task then start it again. For some reason, my gpu is at 100% load (due to discord according to nzxt cam). It seems like discord doesn't close down fully(refuses to close even when using task manager).

 

[zero_l0gic]

Its problem with drivers. AMD is “fixing” it for 2 months now. Great card <Mod Edit> support. Have the same problem.

 

[Aysell]

I upgraded from a 970 to a 5700xt and had no issues for ~2 months while getting the latest drivers.

then i moved it to a new mobo together with the OS drive and started having problems. Nothing worked, except for a clean instal of windows. I suggest you try that,

Also a friend with a vega64 encountered this from the 19.10.1 driver, went back to 19.9.2 and problem gone.