ERROR_SEGMENT_NOTIFICATION - 702 (0x2BE)
{Segment Load} A virtual DOS machine (VDM) is loading, unloading, or moving an MS-DOS or Win16 program segment image. An exception is raised so a debugger can load, unload or track symbols and breakpoints within these 16-bit segments.
Updated: Feb 21, 2026
Technical Background
ERROR_SEGMENT_NOTIFICATION is a specific error code that appears in the context of Windows API behavior, particularly when dealing with virtual DOS machines (VDMs) and MS-DOS or Win16 program segment images. This error is indicative of an event where a VDM is performing operations such as loading, unloading, or moving these 16-bit segments.
Error Details
The ERROR_SEGMENT_NOTIFICATION code is raised to notify the system that a virtual DOS environment is undergoing changes related to MS-DOS or Win16 program segment images. This event can be significant for developers and system administrators who are using debuggers or other tools to track these operations within the VDM.
Common Causes
- Invalid Parameter Values: Incorrect parameters passed during an operation involving a VDM or its segments could trigger this error.
- Incorrect Object Type: The operation might be performed on an object that is not a valid MS-DOS or Win16 segment image, leading to the error.
- Exceeding Limits: Attempting to load too many segments simultaneously may exceed system limits and result in this notification.
Real-World Context
This error typically occurs during operations involving virtual DOS environments. Developers working with legacy applications that require MS-DOS or Win16 compatibility might encounter this code when debugging or managing these environments.
Is This Error Critical?
The criticality of ERROR_SEGMENT_NOTIFICATION depends on the context in which it is raised. While not inherently a critical error, it can indicate issues related to resource management or incorrect operation parameters that need attention.
How to Diagnose
Reviewing Operation Context
- Examine the specific operations being performed within the VDM environment to ensure they are appropriate and correctly configured.
- Verify that all parameters passed to these operations are valid and correct.
Validating Parameters
- Ensure that any segment images or related files being manipulated are correctly identified and accessible.
- Check for any potential issues with file paths, permissions, or data integrity.
Confirming Object Types
- Validate that the objects being operated on are indeed MS-DOS or Win16 segment images. Incorrect object types can lead to this error.
How to Resolve
- Correct parameter usage by ensuring all input parameters are valid and correctly formatted.
- Adjust operation context if necessary, such as reducing the number of segments loaded simultaneously.
- Restore any corrupted data or files that may have been involved in the operation.
- Retry operations with valid inputs to ensure successful execution without triggering this error.
Developer Notes
Developers should be aware of the specific requirements and limitations when working with virtual DOS environments, especially those involving MS-DOS or Win16 segment images. Proper validation and parameter checking can help prevent such errors from occurring.
Related Errors
ERROR_INVALID_PARAMETER(0x57)ERROR_FILE_NOT_FOUND(0x2)ERROR_PATH_NOT_FOUND(0x3)
FAQ
Q: What does the ERROR_SEGMENT_NOTIFICATION code indicate?
A: It indicates that a virtual DOS machine is loading, unloading, or moving an MS-DOS or Win16 program segment image.
Q: Can this error be ignored?
A: While not critical, it may indicate issues with resource management. Addressing the underlying cause can prevent potential problems.
Q: How often does this error occur?
A: The frequency of occurrence depends on the specific operations being performed within virtual DOS environments.
Summary
ERROR_SEGMENT_NOTIFICATION is a specific Windows API error code that indicates changes in MS-DOS or Win16 segment images within a VDM. Developers and system administrators should be aware of this error to ensure proper handling of legacy applications and avoid potential issues related to resource management.