Bogus event 2505

Folks, I believe I've solved this problem for my specific hardware setup because I've experienced zero disconnects in the past 3 days of fairly consistent usage. The last Server-Event ID warning I received was on 8/23. Since 8/28 I've been using my hardware a lot and no warnings/disconnects to report. My setup is probably pretty unique so I'll break it down by component and take from it what you will.

Computer - I recently upgraded my laptop from a Lenovo X1 Gen 7 to a Lenovo X1 Gen 10. Both were connected to a Lenovo Thunderbolt 4 Universal Dock (which is connected by ethernet to my home network, see below for more here). The Gen 7 only had TB3 capability. The Gen 10 is TB4 compatible. I had received warnings about USB resources with the Gen 7 - possible that there was a bandwidth issue here with the dock's wired ethernet?

Software - all of my drivers, software and Win 11 OS is up to date. This was of course an easy one to check and fix. I honestly don't believe anything I did here solved the problem. One other thing to note, the new laptop obviously starts off with a clean install of Windows 11. I have made zero changes to Windows from suggestions I have seen previously such as USB power, resetting winsock etc.

Network - I fell into a rabbit hole with my network, so bear with me here. I am not particularly sophisticated when it comes to networking but know enough to be dangerous. I learned that I had been improperly wiring my home network. I knew there was a problem because I had devices throughout my home randomly disconnecting or reporting 100mb connection speed (vs 1gb connectively as expected), this included the laptop/dock combo. The first step to solving this was finding someone who could diagnose my problems so I have to plug here - I ended up chatting with the people at trueCABLE who were extremely helpful with their time. What was wrong? Firstly, hardware - I am using a lot of Ubiquiti switches (including PoE) and APs which they said are very sensitive to wiring. Next, wiring, I was using some old Cat5e shielded cable to patch-in various devices which I couldn't reach with existing wiring (Cat5 unshielded from 1999 when the property was built). This shielded Cat5 cable was improperly terminated (not grounded) and likely not seated well in the tips which I crimped myself. They advised to discard all of this cable in favor of Cat6 Riser unshielded. Then they advised the priority of termination to devices should be as follows: 1) Keystone jack<->machine-terminated Cat6 patch cable (purchased from Installer Parts), 2) Cat6A field termination plugs, 3) RJ45 - if and only if you cannot use either of 1 or 2 to make the connection. The reason for this is well explained on their website but suffice to say that 1 and 2 make much stronger/better connections with the wires than 3. I can add that the shielded cable is stiff and hard to work with and moving it around a lot can create problems at the RJ45 tip.

So that's my story. I imagine that a lot of this is unique to my case but at least I can say the problem seems to be solved now. Hopefully this helps some others to troubleshoot as I believe nothing mentioned here was in the various lists of troubleshooting suggestions I had seen before.