Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Heat will eventually reduce the life span of the card, but most of the time cards go obsolete long before this happens. (Unless you're really poorly vented and you cook the card to death.)
As for the GPU staying at 100%, have you checked to make sure the game process (TheSurge2.exe) isn't still running? Hung at exit in the background?
It's also possible the AMD driver has a Vulkan related but causing it to remain active after the game process closes.
And you can always check the windows event log to see if anything unusual is recorded. AMD driver may well be writing some error there too.
Hello, Here's a link to my dxdiag[drive.google.com].
Hi,
Thanks for the info, I'll try to look at the logs in event viewer as I have failed to see any process related to Surge 2 remain active through task manager.
I have NZXT's CAM installed and the notification portion keeps exploding with messages about GPU usage exceeding 100%, about 150 times so that caused me to panic and stop playing until I find a fix of sorts. The GPU temps are fine while the game is running never reached 70 degrees, (monitoring that with Afterburner/RivaTuner in-game).
It has been known to cause crashes and other issues at times with new/updated games.
May or may not be related, not sure. I'd just make sure it's up to date as they may have already added some fix to work better with Surge 2.
I'd like to give an update on my situation. The patch seems to have completely fixed the issue for me. So, thanks.