In the another scenario, we got same exception was when, Async method was called without await, creating orphaned thread.

Multiple invocation of the same method resulted in win32u!NtUserMsgWaitForMultipleObjectsEx+14, subsequently resulting in above error