I have never had random power shutdowns until updating BIOS to 1.07 (current EC firmware 1.10). I have endured numerous scenarios where I’m actively working with my Khadas Mind 2 attached to the XPlay monitor and everything just shuts off and I see the monitor display the battery on the screen. Looking at the Mind 2 attached and the light is completely off. In looking at the Event Viewer in Windows there is a ‘critical’ log about power loss. I found lots of thermal throttling logs prior to the shut off. Ambient temperature is 74F. I power the Mind 2 and XPlay either Anker Solix C300 on the USB-C 140 watt port or the Apple 90W MacBook Pro brick with a Belkin USB-C to USB-C 240W 9.9’ cable. This never happened prior to the BIOS update.
This is the critical error.
Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 3/23/2026 17:22:01 Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Mind2 Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: ](http://schemas.microsoft.com/win/2004/08/events/event\">) 41 10 1 63 0 0x8000400000000002 78854 System Mind2 0 0x0 0x0 0x0 0x0 0 0 0 16 false 2 12 false 0 12 false false 0 0 3 0
Show less
5:32 PM
--Claude Output—
This is the well-known Kernel-Power Event ID 41 (Task 63) — often called the “unexpected reboot” error. But the XML details tell a more specific story about why it happened.
What the key fields reveal:
The most telling detail is that BugcheckCode is 0 and all four BugcheckParameters are 0x0. This means Windows did not blue screen (BSOD). If it had crashed due to a software or driver issue, those fields would contain the stop code. Zero across the board means Windows didn’t get a chance to record anything — the power was just suddenly gone.
Other important clues: PowerButtonTimestamp is 0 and LongPowerButtonPressDetected is false, which rules out someone pressing or holding the power button. SleepInProgress is 0, so it wasn’t a failed sleep/wake cycle. WHEABootErrorCount is 0, meaning no hardware error was logged by the CPU/chipset error-reporting system.
Putting it together with your previous event:
This paints a clear picture. Your system was thermally throttling (the Event 37 you showed earlier), and then it abruptly lost power with no BSOD, no button press, and no sleep transition. The two most likely scenarios are:
-
Thermal shutdown — the CPU hit its critical temperature limit and the firmware cut power immediately to protect the hardware. This is the most likely explanation given the throttling you were already seeing.
-
PSU failure or instability — the power supply couldn’t keep up under load, especially if thermal conditions inside the case were also affecting the PSU.