Blank screen after Tinybooter

I’m using a chipworkx module and I’m very satisfied with it. But today something strange happened. I disconnected the DevKit with the chipworkX module from power source. After some time I connected the DevKit with the power source again but the chipworkx module won’t start. On the screen the normal output of Tinybooter occurs:
ChipworkX
Tinybooter Mode
Version 4.1.5.1
Debug USB1
LCD 480x272
IP 0.0.0.0
MAC 00.00.00.00.00.00
Managed Heap Size 49283072
Custom Heap Size 0
Starting Application at 0x10010000

Normally the output changes, but now the screen becomes white and nothing happens. It seems that the GHI firmware isn’t there any more.

Then I tried to enter only tinybooter by resetting the DevKit while pressing up and down buttons. Tinybooter started and I released the 2 buttons. After a few seconds I pressed the up and down button again to leave the Tinybooter mode and now the module was starting normally.
After this “workaround” everything is working normal, but I’m very irritated about it. Is ist possible that a “normal” loss of power stopps the board working and can only be repaired manually?

I am assuming a power issue unless it happens often with reliable power.

Dear Gus, thank you for your quick reply.
What do you mean by power issue? My power source is reliable and stable!

The error occured after disconnecting the DevKit from the power source manually. Does this mean, that every electrical power outage can lead to such an error?
And why can I manually correct the error-state?

Losing power should not cause problems. Not sure why.

I think there must be several reasons for the scenario, that the screens blanks after tinybooter instead of starting firmware and application. And at least one of these reasons happens on my chipworkx.
don’t you think so? Can you tell me some reasons?