Part of your experience seems understandable. The delivery date in your signature indicates you’re driving a 2011 Volt, so you wouldn’t have a kWh Used number on your energy usage display to use as a gauge of estimating how close you were to fully depleting the battery. The 43 EV miles driven suggests you were just about at that point.
The "hard stop" apparently caused something to make the computer think the gas engine was no longer available, or perhaps that you had no gas. Under such conditions, the car would move into Propulsion Reduced Mode. Then, after driving 2 more miles, the computer’s "on-the-fly " estimate of the battery state of charge said the programmed minimum soc had been reached, and, because it thought your gas engine was not available, the car died completely.
After sitting with the power off for a time, the computer had time to gather additional data, and revised the SOC estimate to determine it was actually still above the minimum point, and so allowed you to continue driving to your destination.
You later then turned the car back on and all seemed to be working... which makes me recall an incident reported some time ago, where after a trip to the service department, a Volt driver had a similar Reduced Propulsion/no engine available episode derived from a seeming lack of gas engine access, caused by a failure to reconnect the module letting the computer know there was gas in the tank. Perhaps you experienced something similar, a loose connection that lost contact because of the hard stop, which later moved slightly to reestablish the connection and remove the problem.
The "hard stop" apparently caused something to make the computer think the gas engine was no longer available, or perhaps that you had no gas. Under such conditions, the car would move into Propulsion Reduced Mode. Then, after driving 2 more miles, the computer’s "on-the-fly " estimate of the battery state of charge said the programmed minimum soc had been reached, and, because it thought your gas engine was not available, the car died completely.
After sitting with the power off for a time, the computer had time to gather additional data, and revised the SOC estimate to determine it was actually still above the minimum point, and so allowed you to continue driving to your destination.
You later then turned the car back on and all seemed to be working... which makes me recall an incident reported some time ago, where after a trip to the service department, a Volt driver had a similar Reduced Propulsion/no engine available episode derived from a seeming lack of gas engine access, caused by a failure to reconnect the module letting the computer know there was gas in the tank. Perhaps you experienced something similar, a loose connection that lost contact because of the hard stop, which later moved slightly to reestablish the connection and remove the problem.
