| Previous | Next |
| STATUS_CRASH_DUMP | STATUS_REPARSE_OBJECT |
STATUS_BUFFER_ALL_ZEROS
The operation found no nonzero data in the buffer
This success status communicates a property of the range examined by the returning component: every byte was zero. Memory, storage, compression, cloning, or sparse-data code can use that fact to avoid copying or storing an explicit payload. The exact consequence depends on the API that returned the status.
It does not prove that the range is unallocated, sparse, permanently zero, or backed by the system zero page. Another thread or device can modify writable data after the check. Preserve the operation context and synchronization rules before using the result as an integrity or persistence assertion.
What to inspect
- Record the API, buffer address, length, and whether the range can change concurrently.
- Confirm whether the result permits skipping a write, creating a sparse range, or only optimizing an internal copy.
- Do not substitute this status for a cryptographic or persistent-storage verification.
References
- Microsoft: Memory management functions
- ReactOS source: virtual memory manager
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.