Hello Bungie Support, I am experiencing a persistent and reproducible WEASEL error in Destiny 2 on PC/Steam. The game authenticates and loads my character normally, but I am disconnected after approximately 20 to 50 seconds. The error can appear while I am still in the menus or orbit, without launching an activity. I can sometimes reach the Tower, but the same error then occurs shortly afterward. My main connection is Ethernet with Open NAT. The same issue also occurs over Wi-Fi and a 4G/5G mobile hotspot. I also tested with my friend Steam account on the same PC and received the same error. Troubleshooting already completed: * All saved in-game loadouts were deleted and the game was tested again. This made no difference, so please do not suggest deleting the loadouts again. * Destiny 2 was completely uninstalled and reinstalled. * Steam file verification completed successfully. * Steam and Destiny 2 caches were cleared. * Steam and Windows overlays were disabled for testing. * Steam services and the Steam client were repaired/reinstalled. * BattlEye was completely reinstalled. * Windows Firewall and Microsoft Defender were checked. * Windows network settings and drivers were checked/reset. * DISM and SFC were completed, and Windows was restarted. * Ethernet, Wi-Fi and mobile-network tests produced the same result. * A second Steam account on this PC produced the same result. The game can briefly communicate with Destiny services: my character and menus load, and I have been able to claim store items and weekly rewards before being disconnected. The problem appeared suddenly and persists after all the tests above. Please investigate the server-side session, authentication and BattlEye/client-attestation logs for the account submitting this report. Generic NAT, reinstall and loadout troubleshooting has already been completed without success. Public diagnostic ZIP containing the WEASEL screenshot, Open NAT screenshot and privacy-sanitized DxDiag: [[url=https://we.tl/t-XBVQoEZd7mbbq9m7]Infos & Files.rar[/url]] Thank you. EDIT : BattlEye crashed, taking my PC down with it; the problem almost certainly stems from there. Additional hard evidence: Destiny 2 also caused a Windows BSOD while BattlEye was active. Bugcheck: PAGE_FAULT_IN_NONPAGED_AREA (0x50) Invalid read address: FFFFAB8BD1F45008 Faulting instruction: FFFFF800932708C5 Faulting module: BEDaisy.sys Module offset: BEDaisy.sys+0x7808C5 The kernel dump confirms that the faulting instruction belongs directly to BEDaisy.sys. Multiple BEDaisy.sys addresses are also present in the active crash stack, followed by FLTMGR.SYS. Driver Verifier was disabled. Considering that the WEASEL error occurs after 20–50 seconds across Ethernet, Wi-Fi and mobile tethering, and also with another Steam account on the same PC, a BattlEye client/driver or attestation issue now appears to be the most likely common cause. [url=https://we.tl/t-uYaqt1EeShpnaa2D]DUMP BSOD FILES[/url]