| Previous | Next |
| STATUS_THREAD_IS_TERMINATING | STATUS_INCOMPATIBLE_FILE_MAP |
STATUS_BAD_WORKING_SET_LIMIT
The working-set minimum and maximum do not form a valid policy
Working-set controls must satisfy ordering, size, and platform constraints. A minimum greater than the maximum is an obvious example, but invalid flags, impossible values, or unsupported combinations can also be rejected. This is a parameter and policy problem, not evidence that the page file is corrupt.
Read back the current policy before modifying it and preserve the special values documented for trimming or resetting defaults. Hard-coding limits based on one machine is fragile because available memory, architecture, and privilege differ across systems.
What to inspect
- Log the exact minimum, maximum, flags, process architecture, and operating-system result.
- Validate special sentinel values separately from ordinary byte counts.
- After correction, measure actual faults and residency instead of assuming a larger range improves performance.
References
- Microsoft: SetProcessWorkingSetSize
- Microsoft: Process working sets
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.