Mind 2 Randomly Shuts Off

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:

  1. 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.

  2. 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.

Hello @mayne921

May I ask if this phenomenon occurs frequently? What is the frequency of the issue?

I just had my 4th random shutdown in the past 25 days; the last time at 4/1/26 at 1901 ET I had just awakened the XPlay/Mind from sleep and minutes later all lights turned off and had to boot again. There doesn’t appear to be a pattern. I still see lots of thermal throttling logs in Event Viewer.

Hello @mayne921

  1. Please confirm whether the above situation occurs when using the Mind host alone, in order to troubleshoot whether it is related to xPlay management.

  2. Try resetting the system to see if the issue can be resolved.

Good suggestion. I’ll detach the Mind from XPlay for a while and respond back if 1) random shut down, 2) 1 week goes by without issue.

That did seem to be the issue as I stopped getting random shutdowns after 3 weeks.

Hi Khadas team,

Many users including me are suffering random hard shutdown on Mind2 after upgrading to BIOS 1.07. Windows logs show Kernel-Power Event ID41, which indicates sudden power loss.

This issue only appears after BIOS 1.07 update. The power management sampling seems too sensitive and falsely triggers power cutoff, even when the standby battery is healthy. We cannot downgrade BIOS due to anti-rollback lock.

We have tried all troubleshooting steps: full power reset, load BIOS default, disable Modern Standby, use official 65W PD adapter. The problem still occurs, even under idle condition.

Could you please share your plan and estimated timeline to release a patched BIOS to fix this bug?

RMA is inconvenient for users without spare PC. It would be great if you could add an option in BIOS to relax battery detection threshold or skip standby battery check temporarily.

Thanks.

maybe you can check the mind 2 battery info ,I had random shutdown these days,but with no ID41 IN windows log,later I check battery,it drop from 5400mwh(design capacity) to 16xxmwh and battery health is below 30% with just 6x full charge cycles。So,if you are using the smart charging(charge to 80% and stop to protect battery),then some sudden high power demand or ac error,shut down is inevitable.

I tried drain the battery to 0% and connect to ac and back to 100%,sometimes it will get back to something like 50xxmwh,but the BMS on battery is definitly messed up.

I am trying to disable the smart charge setting(in mind app) to let it charge to 100%,and after that I didn’t encounter any random shutdown anymore,maybe more power helps.

I am trying to reach to the support team to see if they can provide a new battery.

following is what I get from “powercfg /batteryreport”

I would like to share my experience, as it seems to be the same issue reported by other users.

I recently bought a Khadas Mind 2 (155H / 64GB / 2TB) with the xPlay monitor. I immediately updated the BIOS and EC to 1.07 / 1.10 and started using the device.

The next day, after leaving it suspended overnight, I couldn’t wake it up. Since then, I have been trying to reproduce and troubleshoot the issue. After reading other user’s reports, I noticed very similar behavior after the BIOS/EC update.

My Mind 2 can become completely unresponsive after being left unused for some time. It is not necessarily suspended or hibernated, sometimes it is simply idle with the monitor turned off. When this happens, there is no video signal and the device does not wake up or power off normally, even though it remains connected to the original Khadas power adapter.

A full power reset may eventually recover it, but I often have to go through reset BIOS two or three times, or try powering it on and off many times, before I randomly get an HDMI signal again. The problem can happen again after another period of inactivity. I also stopped using the xPlay monitor for now, trying to minimize the frequency of these incidents.

I have seen the same behavior on the latest Linux Mint, so it does not seem to be a Windows-only issue. I get several kernel errors that seem to be related to power management, and sometimes the kernel crashes on both operating systems.

At this point, I wonder if this could be related to the EC firmware or power management.

Since several users seem to be experiencing similar problems, could the Khadas team confirm whether there are any known issues with BIOS 1.07 or EC 1.10, and whether a fix is already in progress?

If possible, it would also be great to know when we might expect a BIOS/EC update to fix these issues.

I would really prefer a firmware fix over an RMA.

Thanks for looking into this.