8.3 Freezing (Windows OS Thread)

Support Technical Support
175

Hey everybody,

Thank you for the patience while we’ve investigated this problem for you. At this point in time, I wanted to give you an update on the things the tech team have discovered in the past week. Brace yourselves - info dump incoming.

There are actually (at least) four different things being reported in this thread. I’m going to quickly address a couple things first, and then we’ll talk about the troubleshooting for the main issue - game client lockups.

  1. A memory leak has been reported to us, which is unrelated to the freezeups but which may make them worse. At this time we have been able to troubleshoot any instances of memory leaks with players by removing conflicting programs. This means removing addon managers and resetting the UI as well as closing other conflicting background applications and updating or uninstalling security programs if all else fails.
  2. Mac OS users have been posting in this thread. This is the incorrect thread for Mac issues, and this is covered by a known bug which is unrelated to this thread. If you are having client freezeups/system crashes on Mac OS, please post in this thread instead and keep an eye on it for updates.
  3. If you are not experiencing game lock ups and only seeing low FPS, this is not the correct thread. You should post your own thread instead so we can help you individually.

For players who are having lockups since 8.3 on Windows and who have Nvidia graphics cards, I have another step for you to try. Something appears to be causing your drivers to become critically unstable, and as far as we can tell a factory overclock of some graphics cards may have something to do with it. To see if you have a factory overclock, follow these steps:

  1. Update your graphics drivers to the latest version
  2. Right click on your desktop and click Nvidia Control Panel
  3. Click the Help menu near the top of the control panel and click on Debug Mode. A check mark should appear if it is enabled. If the option is greyed out, you do not have a factory overclock active.
  4. If you previously used the DirectX 11 Legacy work around, feel free to try again with DirectX 12 instead. If it makes things worse, you can go back to DirectX 11 Legacy.

Note: if you cannot access Nvidia Control panel by this method, you need to reinstall your drivers or reach out to Nvidia for more help. There may be a more major driver problem that you are having resulting in Nvidia Control Panel becoming broken. If this fixes the problem, please report it to Nvidia as well and let us know that it worked for you in this thread.

You may also want to try the steps at this post if you have not yet, but I suspect the above step will work better for Nvidia users.

Thanks again for all the patience through all this. I’ll be keeping an eye on the thread and we’ll provide any more updates we can as we get more feedback.

1 Like