[2021] [Connectivity/Multiplayer]Error 3-0x00050001. Any fixes?

Originally Posted by EGGu_2
I've got error 3-0x00050001 recently and don't know how to resolve it. R6 files checked, drivers newest 466.47 (same issue on previous). Error usually happened on 7-8 second of matchmaking. Japan East\West servers.

System info:
Spoiler:  Show Computer: MSI MS-7B05
CPU: Intel Core i7-7820X (Skylake-X, U0/M0)
3600 MHz (36.00x100.0) @ 3900 MHz (39.00x100.0)
Motherboard: MSI X299 TOMAHAWK AC (MS-7B05)
BIOS: 1.F0, 06/01/2020
Chipset: Intel X299 (Kaby Lake)
Memory: 32768 MBytes @ 1200 MHz, 15-15-15-35
- 16384 MB PC19200 DDR4 SDRAM - Kingston KHX2400C15/16G
- 16384 MB PC19200 DDR4 SDRAM - Kingston KHX2400C15/16G
Graphics: MSI RTX 3080 Gaming X Trio
NVIDIA GeForce RTX 3080, 10239 MB GDDR6X SDRAM
Drive: ST2000DM001-9YN164, 1953.5 GB, Serial ATA 6Gb/s @ 6Gb/s
Drive: Samsung SSD 860 EVO 500GB, 488.4 GB, Serial ATA 6Gb/s @ 6Gb/s
Drive: ST1000NM0033-9ZM173, 976.8 GB, Serial ATA 6Gb/s @ 6Gb/s
Drive: SAMSUNG MZ7LN512HMJP-00000, 500.1 GB, Serial ATA 6Gb/s @ 6Gb/s
Drive: WDC WDS240G1G0A-00SS50, 234.4 GB, Serial ATA 6Gb/s @ 6Gb/s
Drive: ST31000524AS, 976.8 GB, Serial ATA 6Gb/s @ 6Gb/s
Drive: Samsung SSD 970 EVO Plus 500GB, 488.4 GB, NVMe
Sound: Intel Kaby Lake - High Definition Audio / cAVS (Audio, Voice, Speech) [A0]
Sound: NVIDIA GA102 - High Definition Audio Controller
Network: Intel Ethernet Connection I219-V
Network: Intel Dual Band Wireless-AC 8265
OS: Microsoft Windows 10 Professional (x64) Build 19043.1023

Originally Posted by EGGu_2
Yeah. Everything done step by step with this guide and I also chatted with support team - we goes around with this too - nothing helps.

I don't know how exactly this works BUT I'm almost sure that if I'm launching not Vulcan one game .exe - everything is working without errors for some time...

upd: I presume that it happens because of Nvidia Reflex somehow. After launching Vulcan Siege (after simple one Siege) - it's turned off by default (Reflex didn't work without Vulcan?) and game works fine. I've tried it couple of times but need more testing and checking by devs.

upd: Ok. It sometime works only right after closing not vulcan one session and launching vulcan one. If I launch Siege later with account re-login - it will not work... ((((
I've also turned off all GeForce Experience optimizations for a game to test this 3-0x00050001 issue.
p.s.: Sorry for my English plz

There's also some weird thing happening with servers shown for me. Most of the time I'm playing on East Japan, but sometimes I see this: