Screen goes black and comes back on with an unexpected crash or logs user off every 10 seconds
Reported by
rjohn...@eesd.net,
Sep 29 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 Platform: 8530.90.0 (Official Build) stable-channel cyan Steps to reproduce the problem: 1. log on Chromebook 2. 10-15 seconds screen goes black 3. comes back to crash or login screen What is the expected behavior? What went wrong? This issue has been randomly happening around our domain. Temporary fix - RESET COOKIES in Admin console, go to www.google.com/settings/chrome/sync and reset sync. This is a temp fix but some users have it happening again Crashed report ID: How much crashed? Whole browser Is it a problem with a plugin? N/A Did this work before? Yes Chrome version: 53.0.2785.129 Channel: stable OS Version: Flash Version: Shockwave Flash 23.0.0.162-r1 ACER C738T is the device we have noticed most. We currently have version set to no restrictions and stable channel for all devices
,
Oct 4 2016
Maybe not quite the same but we have had issues on Acer C720, C730 and R11. When using the device users are experiencing 'cut outs' screens going black and then coming back on and also a crash report coming up as well.
,
Oct 5 2016
We are having the same 'cut-outs' - hopefully I described it well. Please add anything you know about it
,
Oct 5 2016
Same issue here on R11. V52 & V53.
,
Oct 11 2016
We had the same issue. Fixed it by manually updating every chromebook to the latest version, 53.x.x.x
,
Oct 11 2016
Is there an ID in chrome://crashes?
,
Oct 22 2016
I'm seeing similar behavior on freshly provisioned Chromebooks running Chrome v53 (stable). As the user profile downloads upon first login, I can see the launch bar at the bottom start to populate w/shortcuts and flicker. The Chrome browser crashes. All these events repeat a number of times until the user session is ultimately killed by an apparent reboot. I eventually got a successful login by disabling the wifi radio intermittently during the login process. I've logged in with various user accounts to see whether the behavior is user-specific, and it's not.
,
Oct 25 2016
This seems to be only happening on our ACER C738T (R11) devices. We are all on latest STABLE - it begins to flash off and on (crashes) - happens so quickly I can't get an ID in chrome://crashes. This is the one I could get off the PC Chrome: Crash ID 06212cb9-53ae-442c-b2e8-76b9a52c3208
,
Oct 25 2016
I've been seeing this behavior on HP G1 Chromebooks
,
Nov 18 2016
,
Nov 19 2016
rjohnson@: I couldn't find crash report with ID 06212cb9-53ae-442c-b2e8-76b9a52c3208. Usually IDs are in the form of long decimal numbers with a bunch of zeroes at the end. Could you check if you have one?
,
Dec 6 2016
I'm a happy user of 4 HP chromebooks. This morning Fedex delivered a new Acer 14 model CB3 431. The gold aluminum case is gorgeous! Out of the box an issue: after connecting to internet and logging in to google account, after 10 seconds, the screen flashes black, then logs me out. Over and over. Strange thing: it works fine in Guest Mode. Finally, it has just gone black and won't respond to anything. I suspect it is some Google precaution against a strange computer logging in to my account, but I don't know for sure. This didn't ever happen on my HP and Toshiba chromebooks. Did I mention I'm a chromebookophile? Best computer ever for any price, imho. Googling forums like this one, I see this is a known issue. I called Acer. They said call Amazon. I called Amazon, and they are replacing the unit. Hope the new unit works, since the hardware is stunningly beautiful !
,
Dec 7 2016
Closing due to inactivity. Please reopen if you are able to get a crash id from chrome://crashes .
,
Dec 7 2016
It doesn't produce a Crash log. It seems to be much less frequent on 55 than on 53 or 54.
,
Dec 7 2016
The issue was tied to an out-of-date ChromeOS version on new Chomebooks we received. Before performing enterprise enrollment (which disabled guest account access per our Chrome policies), we'd need to log in as guest and perform a ChomeOS update. Then, after enterprise enrollment, our Chromebooks behaved normally. |
||||
►
Sign in to add a comment |
||||
Comment 1 by svoge...@epasd.org
, Oct 4 2016