| Previous | Next |
| RPC_NT_ZERO_DIVIDE | RPC_NT_FP_DIV_ZERO |
RPC_NT_ADDRESS_ERROR
Server-side addressing fault in an RPC call
RPC_NT_ADDRESS_ERROR belongs to the Windows RPC runtime NTSTATUS facility. MS-RPCE extends the DCE/RPC model: generated stubs marshal parameters, the runtime binds to an endpoint and protocol sequence, and security or transport failures can be returned as RPC facility status values.
This status means the call reached server-side execution and an address fault occurred. It usually points to invalid pointer use in server manager code, unmarshaled data, or code reached from the remote procedure.
Do not diagnose it as a client socket address problem merely because the word address appears in the name. The RPC runtime is reporting a server execution exception, so server dumps and stub boundary checks are the relevant evidence.
What to check
- Map the fault to the interface operation and server process, not just to the client executable.
- Look for malformed conformant arrays, strings, or discriminated unions that reach unsafe server logic.
- Compare failures across 32-bit and 64-bit callers when pointer-size assumptions are suspected.
References
- Microsoft Open Specifications: MS-RPCE overview
- The Open Group: DCE 1.1 RPC introduction
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.