Chrome Version: 67.0.3396.57 (Official Build) beta (64-bit)
OS: ChromeOS

This issue is very hard to reproduce. It happened to me now several times (3+?) over many months:

Get an update, see "reboot to update notification" in shelf. DON't reboot for a day or two. See how network gets worse and worse (until you cannot even connect to the network anymore (you might get a message like "the network is too far away"?!?). Close the lid of the notebook.
Wait a minute. Re-open the notebook. Screen stays black and notebook is dead.

Press power button for long time (10s+) wait if the system comes back. press short or long and wait. Repeat at least 5 times or longer until the system comes back.
Now you will get a message "The system is applying a critical update" and after that everything is fine. Note that even the network comes now back (in my case with all bars - so not a too far away issue at all).

What steps will reproduce the problem?
(1) Get an update (see notification in shelf). 
(2) DON't reboot for a while
(3) After time network stops connecting
(4) Then the system will be dead.
(5) fiddle around with power button for many, many times (long press, short press, ..)
(6) System comes back "applying critical update"
(7) everything ok

What is the expected result?

Either 
a. System is stable until you reboot
   or
b. A message is shown "You have to reboot now!"

And then - leaving the system in a "dead state" in which the customer will probably package it up and restore to a store is not good.


What happens instead?

System gets into an unstable state, failing e.g. with unrelated issues like not able to connect anymore.
System is entirely dead suddenly and a lot of power button pressing will start it eventually (which is not clear to the user).

>>> I did file a feedback report, but couldn't find the reference number after filing AND I couldn't find it in listnr either. But I filed it 05/30 around 9am.


Please use labels and text to provide additional information.

If this is a regression (i.e., worked before), please consider using the
bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help
us identify the root cause and more rapidly triage the issue.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.