| Previous | Next |
| STATUS_NDIS_ERROR_READING_FILE | STATUS_NDIS_RESOURCE_CONFLICT |
STATUS_NDIS_ALREADY_MAPPED
The driver is trying to map the same NDIS file handle twice
STATUS_NDIS_ALREADY_MAPPED is a file-handle lifetime error, not a filesystem lookup error. NdisMapFile maps an already open file only when it is currently unmapped; while mapped, the caller has exclusive access to the file contents until NdisUnmapFile releases that mapping.
Look for an initialization path that retries without unwinding, a shared helper that maps a firmware image for two consumers, or an error path that skips the unmap call. The fix is normally deterministic lifetime management around map, use, unmap, and close operations.
Evidence that narrows it
- Track each
NdisMapFile,NdisUnmapFile, andNdisCloseFilecall for the same file handle. - Ensure retry paths do not re-enter the mapping operation while an earlier mapping remains active.
- Separate this from
STATUS_NDIS_ERROR_READING_FILE, which occurs while obtaining file contents.
References
- Microsoft: NdisMapFile
- Microsoft: NdisCloseFile
- Microsoft: NdisOpenFile
- Microsoft: MS-ERREF NTSTATUS values
Looking for a different code? Search another status or error code.