Recently getting intermittent hang crashes

[Shado]

Windows 10, 64-bit, AMD 6750XT, 64GB RAM.

 

All drivers up-to-date.  Graphic drivers reinstalled as part of troubleshooting. (DDU uninstall, fresh install).

 

Recently started playing again.  On occasion, the game crashes to a black screen with a spinning windows icon on the mouse.  Clicking with the mouse turns the black screen white and I get the prompt that CoH isn't responding and to kill the process. 

 

Not crashing with other games.  No unique profiles with CoH in the Adrenaline settings.  Sometimes can play for hours with no issues. (Alt tabbing, logging in and out on different characters, etc... no issues.)  Then, without any reason that I can find, I'll crash repeatedly within 5-15 minutes of logging in.  Crashes AMD driver.  Have to manually restart the driver and/or the system.  Not sure if there's an issue with the 24.12.1 drivers or not.  Didn't have issues with crashes in the past, but I know the that Homecoming had an update or two since I last played as well.

 

System is otherwise stable, but once I crash CoH once, I seem unable to play it without crashes for the rest of that day.  (Makes no sense.. full restart should clear any issues with driver crash or cached items in memory)  No thermal issues.  Can hop into any other game without issue after reboot or restarting GPU drivers. (Don't Starve Together, Enshrouded, Grounded, Smalland, 7 Days to Die, and Pantheon are other games I've played recently).

 

I've looked for logs, but I'm not seeing any in Program Files (x86)\Homecoming\logs

 

I've seen reference in this forum to a \crash folder, but it does not exist on my system.

 

Event Viewer shows that amduw23g stops responding and then recovers second before cityofheroes.exe version 1.0.6484.64 stops working with Windows.

 

So as best I can tell it's a driver conflict with the most recent AMD driver and the current version of Homecoming.  Is there a known issue?  A known last working driver or setting change that works with 2024.12.1?

 

Thank you.

Edited February 10 by Shado

[Shado]

Would there be any reason that Pandora running in Firefox in the background would be a culprit?

[GM Crumpet]

6 hours ago, Shado said:

Would there be any reason that Pandora running in Firefox in the background would be a culprit?

It might be causing a clash, does it change anything if you close Pandora  and firefox down completely?

[Shado]

I've tried running Firefox without a Pandora tab open, I've tried turning off hardware acceleration in Firefox, and just not having any Firefox process running in the background.  Still have crashes. 

[Shado]

Just for those that might encounter similar issues, my current working theory on the issues I've experienced is the Discord Overlay.  What started as just a CoH crashing issue, slowly spread into other, older games.  (Though newer than CoH)  Each gave different errors, but always appeared as crashing GPU drivers, or related to... The Discord overlay is the common denominator that is currently proving to be the solution (as in, disabling it entirely).  Should I learn otherwise, I'll update this thread.

[Marine X]

( Copied from a previous post )

 

You may want to check your connection to see if anything is going on there. While connected to game server, type in the Chat " /netgraph 1 " without quotes, " /netgraph 0 " turns it off. Even though you can play other games with no issues there may be an issue getting to the Homecoming server due to the path it uses to connect.

While it is on ,in the lower right corner of the screen, you will see a series of bars, what these mean is as follows...

 

Interpreting the netgraph:

Spike shape: The height of the bar representing server ping time in milliseconds. Short is good, long is bad.

Green bars represent received packets.

Short = normal/good

Long = low bandwidth.

Yellow bars represent retransmitted packets.

Short = ISP/Router issues

Red bars represent dropped packets

Short = ISP/Router issues

Blocks of Red = Interrupted communications

 

You can also try pinging the server, at a Command Prompt, ( search pc for cmd and it should be in the results ), type the following:

" ping 51.161.76.201 -t " without quotes and hit enter. if the response time varies greatly or hangs there is a connection issue.