Message 10096
Available since version: 2026.2.0
Description
This error is raised when using the GPU solver. It occurs when either the water surface elevation or the velocity magnitude at the specified 2D cell has exceeded the configured Stability Limits ==. Unlike the CPU solver, the GPU kernel reports both checks as a single combined message.
Suggestions
Ensure the stability limits in Stability Limits == reflect the expected flow conditions. The first argument is the water surface upper bound (mRL or ftRL) and the second is the velocity upper bound (m/s or ft/s).
The simulation time at which the error occurs may help to diagnose the issue. If the error occurs early in the simulation or at initialisation, it is likely a model configuration, initial condition or boundary condition mismatch. Check that the water surface upper bound exceeds the maximum topographic/bathymetric elevation, this is a common cause of error. If the error occurs later and the model configuration appears correct, the region surrounding the offending 2D cell warrants further investigation.
For model instability, review the model setup in the vicinity of the cell shown in the GIS messages output file. Common causes include a timestep that is too large for the mesh resolution, poor mesh quality near the affected cell, and extreme or incorrectly specified boundary conditions.
While the error will be reported at the first cell that exceeds the stability limit, the root cause may originate from a nearby cell. To track where instability begins add a secondary output block with high temporal resolution at a time just prior to the error. See ERROR 10097 for an example output block.
The command Write Restart At Time == can also be useful to start a follow-up run close to the time of the error.