| Previous | Next |
| STATUS_BAD_DLL_ENTRYPOINT | STATUS_LPC_REPLY_LOST |
STATUS_BAD_SERVICE_ENTRYPOINT
The service entry callback violates its required ABI
Windows service entry and control callbacks are invoked through defined function prototypes. This status indicates that the callback left the stack pointer inconsistent, which usually points to an incorrect calling convention, wrong parameter list, architecture mismatch, or corrupted function pointer rather than a normal service-start failure.
Allowing the service process to continue can cause delayed crashes when the caller restores registers or returns through a damaged stack. The binary must be rebuilt with the documented prototype and matched headers; changing service configuration or account permissions cannot repair an ABI mismatch.
What to inspect
- Verify ServiceMain and handler declarations, WINAPI usage, exported names, and the function pointer passed to the dispatcher.
- Confirm that every object file and library uses compatible architecture and calling-convention settings.
- Use a debugger to compare stack and return-address state around the callback invocation.
- Separate this defect from Service Control Manager timeout, logon, dependency, and access errors.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: linking an executable to a DLL
- Microsoft: PE and COFF format
- Microsoft Windows SDK metadata: ntstatus.h
Looking for a different code? Search another status or error code.