Windows error 0x00000161, 353

Detailed Error Information

MAX_SESSIONS_REACHED[1]

MessageThe maximum number of sessions has been reached.
Declared inwinerror.h

This appears to be a raw Win32 error. More information may be available in error 0x80070161.

LIVE_SYSTEM_DUMP[2]

This is a Blue Screen of Death stop code. More information is available in the Knowledge Base article Bug Check 0x161: LIVE_SYSTEM_DUMP.

HRESULT analysis[3]

This is probably not the correct interpretation of this error. The Win32 error above is more likely to indicate the actual problem.
FlagsSeveritySuccess

This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.

Reserved (R)false
OriginMicrosoft
NTSTATUSfalse
Reserved (X)false
FacilityCode0 (0x000)
NameFACILITY_NULL[3][1]
DescriptionThe default facility code.[3][1]
Error Code353 (0x0161)

Questions

1vote
1answer

.NET application handle leak, how to locate the source?

I have a .NET application running in production environment (WINDOWS XP + .NET 3.5 SP1) with a stable handle count around 2000, but in some unknown situation, its handle count will increase extremely fast and finally crash itself(over 10,000 which monitored by PerfMon tool). I've made a memory dump from [...] read more
windows
performance
memory-leaks
windbg

Comments

Leave a comment

(plain text only)

Sources

  1. winerror.h from Windows SDK 10.0.14393.0
  2. https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
  3. https://msdn.microsoft.com/en-us/library/cc231198.aspx

User contributions licensed under CC BY-SA 3.0