What does Windows error code 361 (ERROR_DAX_MAPPING_EXISTS) mean?

 
Could be also:
ConstantTypeOS
CLUSTER_CSV_VOLUME_ARRIVAL_LIVEDUMPBugCheck CodeWindows
Previous Next
ERROR_NOT_SUPPORTED_ON_DAX ERROR_CLOUD_FILE_PROVIDER_NOT_RUNNING

ERROR_DAX_MAPPING_EXISTS

Active DAX mappings keep the volume in use

ERROR_DAX_MAPPING_EXISTS is a Win32 system result. A process has memory mapped persistent storage through DAX. Operations such as dismount, reconfiguration, or maintenance cannot proceed while those mappings remain active.

What the result means

The volume still has active direct-access mappings that prevent the requested operation.

What to check

  • Identify processes that hold mappings or open handles to the volume.
  • Stop application access through its normal shutdown or quiesce mechanism.
  • Account for services, background agents, and stale worker processes.
  • Verify that mappings are actually released before retrying volume operations.

Recommended handling

Coordinate application shutdown, unmap views, close handles, and then retry. Avoid terminating processes without understanding persistent-memory consistency and recovery requirements.

Developer notes

Design DAX users with explicit quiesce and maintenance hooks. Track mapping lifetime deterministically and flush required data before unmapping.

References


Looking for a different code? Search another status or error code.