| Previous | Next |
| STATUS_CRC_ERROR | STATUS_PORT_CONNECTION_REFUSED |
STATUS_SECTION_TOO_BIG
The mapping size cannot be represented or reserved
A section has a maximum size derived from explicit parameters, the backing file, and the target architecture. This status can occur when arithmetic overflows while calculating the mapping, an image declares an unreasonable SizeOfImage, or the requested range cannot fit in the available virtual address space.
The physical amount of free RAM is not the only relevant resource. A 32-bit process can exhaust contiguous address space even on a machine with ample memory, and malformed PE section alignment can expand an apparently small file into an invalid in-memory image size.
What to inspect
- Log the requested high and low size values, process bitness, file length, and any alignment rounding.
- Inspect PE SizeOfImage, SectionAlignment, section virtual sizes, and overflow at the final section boundary.
- Compare the requested view with the section maximum and the largest free address-space region.
- Reject untrusted size fields before multiplication or alignment to avoid wrapping into a misleading smaller value.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: CreateFileMapping
- Microsoft: PE and COFF format
- LLVM source: COFF object parsing
Looking for a different code? Search another status or error code.