Just about pulling my hair out trying to figure this out, it's been hard to play the game like this. I get progressively longer load times the longer D2 is running, the occasional beet error when queuing in Gambit and Crucible, and massive frame rate drops immediately upon loading in (particularly in crucible).
System Specs:
CPU: AMD Ryzen 1700x @ 3.4 GHz (stock)
Mobo: Gigabyte AX370-Gaming K7
GPU: AMD RX 580 8GB (stock settings), 19.2.3 drivers
Memory: G.Skill something-or-others @ 3200Mhz 2x8GB (They're Samsung B-Dies if that helps at all)
Storage: Samsung 860 Pro NVMe 512 GB
OS: Windows 10 64 bit
Internet: 300 mbit symmetrical fiber, hardwired to router, zero packet loss to google or bungie.net
Things I've Tried with no luck:
- Lowering quality to the medium preset
- Moving the D2 install directory to my secondary SSD (Samsung 840 Evo)
- Battle.net scan and repair tool, no problems detected
- Uninstalling Battle.net and D2, then removing associated directories in %APPDATA% and similar areas, then reinstalling
- Memtest full test of whatever their default test suite is, no errors
- Prime95 for about 8 hours, no stopped workers
- Unigine Heaven for 1 hour, no artifacting or crashes
- Checked the smart status on all of my storage devices, all healthy
- Port forwarded all necessary ports
- "ping google.com|bungie.net -n 100" multiple times to test for large packet loss, no packet loss detected.
- Shutting off windows firewall and windows defender via registry settings.
- Tethering from cell phone (near full bars LTE)
- Overclocking everything, all stable after stress testing (CPU 3.8GHz, RAM 3600Mhz, GPU I forget off the top of my head)
- Lowering the memory clock to 2133 MHz
- Making sure temps stay in check, all are well below the concern threshold.
- Tried old GPU (AMD R9 380x), no help and worse performance.
- Updating bios to an almost bleeding edge version. No difference
- RMAing my CPU, it was affected by the Ryzen linux segfault bug. Didn't make a difference.
- Verifying the silly things. Memory is in dual channel mode, GPU is in a 16x slot, NAT is open, etc.
The only thing that worked was using my old computer (AMD Phenom II x6 @ 4Ghz, 8 GB DDR3 forget the frequency, AMD R9 380x, Windows 7 64 bit). I had reasonably quick load times and no beet errors. However the framerates were not great and barely playable. Moving my new GPU over to it seemed to help, but it still had issues with CPU heavy situations.
There is a mention of long load times on AMD systems in the PC known issues list, but I'm not sure if its still valid as the list hasn't been updated since last August. If this is still valid, does anyone have a workaround?
Anyone have any other ideas on this? I would really like to play the game in a normal capacity.
Any help is appreciated.
-
7 RepliesHello Koof. Appreciate you reaching out to us about your issue. [url=https://www.bungie.net/en/Help/Article/46903]BEET[/url] indicates that you are experiencing a general networking issue. You may want to review our [url=https://www.bungie.net/en/Help/Article/46903]BEET[/url] article for more information about your issue.