| Previous | Next |
| ERROR_FILE_HANDLE_REVOKED | ERROR_ENCRYPTED_IO_NOT_POSSIBLE |
ERROR_IMAGE_AT_DIFFERENT_BASE
an executable image was mapped at a different base address and relocations were applied.
ERROR_IMAGE_AT_DIFFERENT_BASE indicates this condition: The loader could not place a PE image at its preferred virtual address, so it mapped the image elsewhere and processed its relocation table. The message is generally informational when fixups succeed.
Where the result appears
- loader diagnostics for DLLs whose preferred address range is occupied.
- debugger or tracing output during process startup.
- legacy images built with fixed or overlapping base addresses.
- ASLR operation that intentionally randomizes image placement.
What to collect
- image path, preferred image base, and actual mapped base.
- whether the image contains a valid relocation directory.
- loader events and any later STATUS_CONFLICTING_ADDRESSES or relocation failure.
- build flags such as DYNAMICBASE, fixed-base settings, and architecture.
Handling and recovery
Do not fail an application solely because of this status when loading completed. Investigate only when relocation cost, missing relocations, pointer assumptions, or a later loader error causes a real problem. Modern binaries should support ASLR and avoid relying on a fixed address.
Common misinterpretation
Mapping at a different base is not the same as loading the wrong file. It describes virtual-address placement of the intended image.
References
Looking for a different code? Search another status or error code.