PC Graphics

[GR_BKP]

Hi, 

After a year of useing my Sapphire Nitro+ RX5700 XT I have a problem with it.

After a while from turning on the computer, the utilization and junction temperature reaches the maximum, and launching the 3DMark test or game ends with a Wattman module error that cuts the card.

Funny is - when i turn on Windows Task Manager (and leave it running in the background) in one second problem ends. Temperature and utilization GPU drops to normal.

add info:
Sapphire Nitro+ RX5700 XT Adrenaline 22.2.3
Windows 10 64
AMD Ryzen 7 3700X
MB Gigabyte X570

[elstaci]

Are the GPU fans working at maximum speed when it overheats?

Do you have the GPU card Overclocked using  AMD Wattman?

Seems like when the GPU card is under load it overheats but under light loads it doesn't. Which does seem to indicate a problem with the GPU card's Heat sink or Fans.

I would open a Sapphire Warranty ticket and see if they recommend you RMA the GPU card. Possibly the Thermal paste or pads have gone bad after a year.

[GR_BKP]

Thx for reply!

Are the GPU fans working at maximum speed when it overheats?
Yes, fans works OK, also I managed more rpm that normal, but it's not reduce temperature.

Do you have the GPU card Overclocked using  AMD Wattman?
No. Card is in factory settings.

Seems like when the GPU card is under load it overheats but under light loads it doesn't. Which does seem to indicate a problem with the GPU card's Heat sink or Fans.

I would open a Sapphire Warranty ticket and see if they recommend you RMA the GPU card. Possibly the Thermal paste or pads have gone bad after a year.
I will loose guarantee if change thermal paste or pads by myself (i asked seller).

But... why does this not occur when task manager is enabled? 

When the GPU utilization and junction temperature prevent the computer from working, just turn on the task manager and in a second the GPU utilization drops to a minimum and junction temperature to normal ...

[elstaci]

I wasn't suggesting that you change the thermal paste or pads yourself. I meant to send it to Sapphire Warranty for them to do it and to verify that your GPU card is good and not defective.

In my opinion, a GPU card shouldn't overheat no matter what you do software wise unless you manually overclocked it.

but to eliminate the AMD Driver,uninstall the AMD driver and just use MS Basic Display Adapter and see if the same thing keeps happening. If it does then the problem is hardware related and not software.

If it doesn't overheat with the MS Basic Display driver then try installing a previous AMD driver from here: https://www.amd.com/en/support/previous-drivers/graphics/amd-radeon-5700-series/amd-radeon-rx-5700-s...

Otherwise I suggest you ask Sapphire Warranty if you need to RMA your GPU card to be checked. 

If the GPU card worked fine for about a year and now it is overheating it is possible the thermal paste or pads went bad or are not doing the job it used to do in the past when it was new. Also if the GPU fins are dirty will also cause the GPU card to overheat. So make sure the GPU fins and fans are clean.   just guessing.

Also check your PSU outputs. Bad power could  make your GPU card to overheat. Run OCCT GPU and PSU Stress test to see if it passes or fails. keep an eye on Temperatures, Fan speeds, and PSU Outputs.

[GR_BKP]

Thanks again

First what I checked was dirty on funs and fins - they are clean.

I done stress check by 30 second yesterday - pass.

I will delete AMD Adrenaline and install MS driver today and write if it helped

But still wondering me why after turn on windows task manager everything back to normal in one second... specialy junction temperature... (that is why I thought it is software problem...)

[elstaci · Accepted solution]

Once you uninstall the AMD driver the MS Basic Display Adapter will automatically be installed by Windows. No need to install it yourself. you can set the Resolution to the same one as your Monitor.

Yes, I do agree it is strange that by opening Task Manager the temperature goes to normal.

Try this before you uninstall the AMD driver and to eliminate any 3rd party running in the background that could be causing your GPU to overheat.

Start your computer in a Clean Windows Desktop except don't disable the AMD driver and then wait and see if the GPU continues to overheat: https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-...

It is very easy to do and undo.

IF it doesn't then enable half of the background startups and see if the problem now starts again. If it does then by process of elimination locate the services or program that is causing the GPU to overheat.

But still, your GPU card shouldn't overheat at all unless something is overclocking the GPU Card or something is wrong with your cooling system on the GPU card.

NOTE: Also run in a elevated Command Prompt or Powershell the following command :  SFC /scannow

This will check your Windows OS for corruption or missing core files.

[GR_BKP]

@elstaci - Thank you very very much for your help!

That was it!

NOTE: Also run in a elevated Command Prompt or Powershell the following command :  SFC /scannow

This will check your Windows OS for corruption or missing core files.

I had a few file issues which this scan solved

[elstaci]

What was the problem? 

The GPU card is not overheating anymore?

[GR_BKP]

I tried all your advice one by one and checked if problem still existed.

GPU stopped overheating after scanned

After the scan was done, there was information about several wrong files that were immediately solved. I don't know which one. But if you want and give any hints on how to get them out of the log file, I'll check it.

[elstaci]

So you are saying it was Windows corruption itself that was causing the overheating of your GPU card?

That is a new one for me.

Thanks for the update.

You can check in C:\Windows\Logs\CBS file.

[GR_BKP]

Exactly, windows fault
I know where the log is, but I don't know which lines are showing this error.

[elstaci]

In the Windows Log CBS File go all the way to around the bottom of the file. It should have a summary of what was done.

I wonder how a corrupt Windows file can cause a GPU card to overheat the way yours did. It must have affected the AMD Driver's control of the GPU card in some way.

If Windows corruption can cause a AMD GPU card to overheat there must be some connection between the AMD Driver and Corrupted Windows file.

Granted without any Windows corruption the GPU card wouldn't have overheated but if AMD should try to find out how a Windows corrupt file was able to cause a AMD GPU card to overheat probably through the AMD driver itself, in my opinion. This also might explain other Users complaining about overheating GPU cards with newer AMD drivers.

@Matt_AMD 

[GR_BKP]

Yes it is strange, like case with turned on Win Task Manager.

Here is finishing part of log, maybe you or someone will help.

2022-03-10 11:43:23, Info                  CBS    Read out cached package applicability for package: Package_for_KB4589212~31bf3856ad364e35~amd64~~10.0.2.4, ApplicableState: 0, CurrentState:112
2022-03-10 11:43:23, Info                  CBS    Skipping package [Package_for_KB4593175~31bf3856ad364e35~amd64~~19041.680.1.0] since it is permanent
2022-03-10 11:43:23, Info                  CBS    Skipping package [Package_for_KB4598481~31bf3856ad364e35~amd64~~19041.740.1.1] since it is permanent
2022-03-10 11:43:23, Info                  CBS    Package Format: PSFX
2022-03-10 11:43:23, Info                  CBS    Read out cached package applicability for package: Package_for_KB5000736~31bf3856ad364e35~amd64~~10.0.1.3, ApplicableState: 112, CurrentState:112
2022-03-10 11:43:23, Info                  CBS    Appl:LCU package and revision compare set to explicit
2022-03-10 11:43:24, Info                  CBS    Package Format: PSFX
2022-03-10 11:43:24, Info                  CBS    Appl:Feature On Demand package without explicit comparator, using GE on build version
2022-03-10 11:43:24, Info                  CBS    Appl:Feature On Demand package without explicit comparator, using GE on build version
2022-03-10 11:43:24, Info                  CBS    Read out cached package applicability for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.1566.1.8, ApplicableState: 80, CurrentState:80
2022-03-10 11:43:24, Info                  CBS    [Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.1566.1.8] is a top-level package and is deeply superseded
2022-03-10 11:43:24, Info                  CBS    Appl:LCU package and revision compare set to explicit
2022-03-10 11:43:24, Info                  CBS    Package Format: PSFX
2022-03-10 11:43:24, Info                  CBS    Appl:Feature On Demand package without explicit comparator, using GE on build version
2022-03-10 11:43:24, Info                  CBS    Appl:Feature On Demand package without explicit comparator, using GE on build version
2022-03-10 11:43:24, Info                  CBS    Read out cached package applicability for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.1586.1.7, ApplicableState: 112, CurrentState:112
2022-03-10 11:43:24, Info                  CBS    Skipping package [Package_for_ServicingStack_1310~31bf3856ad364e35~amd64~~19041.1310.1.0] since it is permanent
2022-03-10 11:43:24, Info                  CBS    Skipping package [Package_for_ServicingStack_1371~31bf3856ad364e35~amd64~~19041.1371.1.0] since it is permanent
2022-03-10 11:43:24, Info                  CBS    Skipping package [Package_for_ServicingStack_1490~31bf3856ad364e35~amd64~~19041.1490.1.0] since it is permanent
2022-03-10 11:43:24, Info                  CBS    Skipping package [Package_for_ServicingStack_1525~31bf3856ad364e35~amd64~~19041.1525.1.0] since it is permanent
2022-03-10 11:43:24, Info                  CBS    Skipping package [Package_for_ServicingStack~31bf3856ad364e35~amd64~~19041.1022.1.1] since it is permanent
2022-03-10 11:43:24, Info                  CBS    Skipping package [Package_for_ServicingStack~31bf3856ad364e35~amd64~~19041.1081.1.2] since it is permanent
2022-03-10 11:43:24, Info                  CBS    Skipping package [Package_for_ServicingStack~31bf3856ad364e35~amd64~~19041.1161.1.1] since it is permanent
2022-03-10 11:43:24, Info                  CBS    Skipping package [Package_for_ServicingStack~31bf3856ad364e35~amd64~~19041.1220.1.0] since it is permanent
2022-03-10 11:43:24, Info                  CBS    Skipping package [Package_for_ServicingStack~31bf3856ad364e35~amd64~~19041.860.1.0] since it is permanent
2022-03-10 11:43:24, Info                  CBS    Skipping package [Package_for_ServicingStack~31bf3856ad364e35~amd64~~19041.925.1.1] since it is permanent
2022-03-10 11:43:24, Info                  CBS    Skipping package [Package_for_ServicingStack~31bf3856ad364e35~amd64~~19041.985.1.1] since it is permanent
2022-03-10 11:57:20, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2022-03-10 11:57:20, Info                  CBS    TiWorker signaled for shutdown, going to exit.
2022-03-10 11:57:20, Info                  CBS    Deleting the contents of directory: \\?\C:\Windows\CbsTemp
2022-03-10 11:57:20, Info                  CBS    Deletion of: \\?\C:\Windows\CbsTemp successful
2022-03-10 11:57:20, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2022-03-10 11:57:20, Info                  CBS    Execution Engine Finalize
2022-03-10 11:57:20, Info                  CBS    Execution Engine Finalize
2022-03-10 11:57:20, Info                  CBS    Lock: Lock removed: TiWorkerClassFactory, level: 30, total lock:3
2022-03-10 11:57:20, Info                  CBS    Lock: Lock removed: CCbsWorker, level: 5, total lock:2
2022-03-10 11:57:20, Info                  CBS    Ending the TiWorker main loop.
2022-03-10 11:57:20, Info                  CBS    Starting TiWorker finalization.
2022-03-10 11:57:20, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2022-03-10 11:57:20, Info                  CBS    CBS Engine already deactivated
2022-03-10 11:57:20, Info                  CBS    CBS Engine already deactivated
2022-03-10 11:57:20, Info                  CBS    CbsCoreFinalize: ComponentAnalyzerFinalize
2022-03-10 11:57:20, Info                  CBS    CbsCoreFinalize: PackageTrackerFinalize
2022-03-10 11:57:20, Info                  CBS    CbsCoreFinalize: CoreResourcesUnload
2022-03-10 11:57:20, Info                  CBS    CbsCoreFinalize: SessionManagerFinalize
2022-03-10 11:57:20, Info                  CBS    Lock: Lock removed: CSIInventoryCriticalSection, level: 64, total lock:10
2022-03-10 11:57:20, Info                  CBS    Lock: Lock removed: CCbsSessionManager, level: 11, total lock:9
2022-03-10 11:57:20, Info                  CBS    CbsCoreFinalize: CapabilityManagerFinalize
2022-03-10 11:57:20, Info                  CBS    CbsCoreFinalize: PublicObjectMonitorFinalize
2022-03-10 11:57:20, Info                  CBS    CbsCoreFinalize: Enter vCoreInitializeLock
2022-03-10 11:57:20, Info                  CBS    CbsCoreFinalize: WcpUnload
2022-03-10 11:57:20, Info                  CBS    CbsCoreFinalize: DrupUnload
2022-03-10 11:57:20, Info                  CBS    CbsCoreFinalize: CfgMgr32Unload
2022-03-10 11:57:20, Info                  CBS    CbsCoreFinalize: DpxUnload
2022-03-10 11:57:20, Info                  CBS    CbsCoreFinalize: SrUnload
2022-03-10 11:57:20, Info                  CBS    CbsCoreFinalize: CbsEsdUnload
2022-03-10 11:57:20, Info                  CBS    CbsCoreFinalize: CbsTraceInfoUninitialize
2022-03-10 11:57:20, Info                  CBS    CbsCoreFinalize: CbsEventUnregister
2022-03-10 11:57:20, Info                  CBS    CbsCoreFinalize: AppContainerUnload
2022-03-10 11:57:20, Info                  CBS    CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2022-03-10 11:57:20, Info                  CBS    Ending TiWorker finalization.
2022-03-10 11:57:20, Info                  CBS    Ending the TrustedInstaller main loop.
2022-03-10 11:57:20, Info                  CBS    Starting TrustedInstaller finalization.
2022-03-10 11:57:20, Info                  CBS    Lock: Lock removed: WinlogonNotifyLock, level: 8, total lock:6
2022-03-10 11:57:20, Info                  CBS    Ending TrustedInstaller finalization.