We had this too. For us it was initially triggered by running Firefox or VS Code but latterly, just like you, from boot.
In some rare cases it sorted itself out after a long time. Never seemed to happen if the machine was not on a network.
Collecting diagnostic logs was pretty difficult since the systems were so unresponsive. We checked the forum and your post is the first we've seen mirroring our experience.
We opened a support case but never got to the bottom of it.
Since then we've downgraded all our workstations to v10.1 since it's supported until late next year.
