Brya/crota360 Random Critical Battery Warning

System Details

  • Device: crota360
  • OS: Windows 11
  • Firmware Type: UEFI Full ROM
  • Firmware Version: Mrchromebox-2603.2 (5/17/2026)
  • Internal storage type: NVMe

Summary of the Issue

Windows shuts down seemingly randomly. The battery icon appears to have an X icon and appears empty before the shutting down splash screen appears and the system powers off. Using a method to hide the “Shutting down” screen, the battery percentage appears properly.

Now that Windows has fully powered the system off: Assuming the battery was actually charged and not depleted, Windows will boot normally afterward until the issue re-occurs once again (persistent).

Steps to Reproduce

  1. Boot Windows with chrultrabook drivers

  2. Use normally

  3. At a seemingly random time, Windows will sound the critical battery sound and immediately shut down.

Expected Behavior

Windows should not have encountered a critical battery warning and initiated the critical battery percentage action until the battery was actually depleted. The event should have never occurred until the battery was actually reported as being within the critical battery percentage range.

(apologies if this is in the wrong category, wasn’t sure if this was more of a firmware bug report or if it learned towards windows support. to my knowledge, the Windows driver i suspect does not return the last received battery percentage to the system if a battery percentage is not returned in time so i’m not sure if this is a communication error or just a driver bug.)

I tried to look in event viewer for any abnormal logs during that time. So far after posting this, it has done this about a total of ~10 different times? What’s weird is I can’t seem to find anything abnormal in event viewer.

will extract cbmem, EC, and GSC logs hopefully sometime in the afternoon and send here. completely slipped my mind to grab those

Apparently after looking around, it seems it may have been a hardware issue. ChromeOS masked the issue without me ever knowing it was an actual problem. I have just set powercfg to have no critical battery actions.