M3 Pro Max battery completely drained overnight - No battery history now

[KFrench]

I just got a new M3 Pro Max last month. It was charged when I want to sleep and I woke up to a completely drained laptop. I turned it back on and it quickly charged up to full again. No servers or anything running and the laptop sleeps on its own normally. The battery was at 0%. The weirdest part about all this is the battery history is *completely empty*

Any idea what happened or what I can check? This Mac is brand new and in mint condition.

Here are some logs showing when the computer died. The internal clock also completely reset after the computer shutoff. I had to resync the time manually in the settings:

```
2024-07-19 20:22:23.720558-0600 0x1ea97c Default 0x0 1670 8 dasd: [com.apple.duetactivityscheduler:scoring] 0:com.apple.mds.Migration.0:3F7A34:[
{name: Battery Level Policy, policyWeight: 1.000, response: {Decision: Must Not Proceed, Score: 0.00, Rationale: }}
], FinalDecision: Must Not Proceed}
2024-07-19 20:22:23.739361-0600 0x1ea97c Default 0x0 1670 8 dasd: [com.apple.duetactivityscheduler:scoring] 0:com.apple.mds.Migration.1:27FDDE:[
{name: Battery Level Policy, policyWeight: 1.000, response: {Decision: Must Not Proceed, Score: 0.00, Rationale: }}
], FinalDecision: Must Not Proceed}
2024-07-19 20:22:24.166606-0600 0x1eb54f Default 0x0 1695 0 contextstored: (BiomeStreams) [com.apple.Biome:BiomeCompute] BMComputeSourceClient for stream Device.Power.BatteryLevel connection interrupted
1976-04-01 00:00:06.343224+0000 0xb9b Default 0x0 0 0 kernel: (AppleSmartBatteryManager) AppleSmartBatteryManager started
1976-04-01 00:00:00.602534+0000 0x9b1 Default 0x0 51 8 powerd: [com.apple.powerd:battery] Battery time remaining posted(0x1000000004fffff) Time:-1 Source:AC
1976-04-01 00:00:00.602839+0000 0x9b1 Default 0x0 51 8 powerd: [com.apple.powerd:battery] Battery capacity change posted(0xb0007). Capacity:7 Source:AC
1976-04-01 00:00:00.611154+0000 0x9f8 Default 0x0 51 8 powerd: [com.apple.powerd:BDC] Battery change detected
1976-04-01 00:00:00.613186+0000 0x9f8 Default 0x0 51 8 powerd: [com.apple.powerd:BDC] BDC data path /var/db/Battery/BDC
1976-04-01 00:00:00.642428+0000 0xad2 Default 0x0 82 0 WindowServer: (BrightnessControl) [com.apple.BCBrtControl.AppleBacklight:default] capabilities = {
```

 

[russell_314]

It could be trying to do some type of indexing since it’s new. I would leave it plugged in overnight at least for the first week or so

 

[KFrench]

It could be trying to do some type of indexing since it’s new. I would leave it plugged in overnight at least for the first week or so

It is not brand brand new. About 3 weeks old. I have used it constantly for the entire 3 weeks. The main concern here comes in two parts:

1. Macs should not run themselves to 0% and hard crash, especially while idle
2. Battery history logs should never be wiped, even if the system suddenly stops.

 

[fehhkk]

Settings -> Screen Time -> App and Website usage and see what went on through overnight

 

[KFrench]

Settings -> Screen Time -> App and Website usage and see what went on through overnight

Cool feature. It was off for me unfortunately. I just turned it on in case this happens again.

 

[FreakinEurekan]

Battery history is cleared on reboot, so that part sounds normal.

 

[bradman83]

No servers or anything running and the laptop sleeps on its own normally.

Was the lid closed? Did you manually put it to sleep? Or was it running and you just walked away from it expecting it would automatically to go sleep?

 

[KFrench]

Was the lid closed? Did you manually put it to sleep? Or was it running and you just walked away from it expecting it would automatically to go sleep?

Locked, but lid open

 

[specialstyle]

I suppose it could've crashed and drained itself in that state, but that is very weird, especially since the internal clock changed time.

I would reset the SMC, leave it plugged in for a couple of days, check on it, and then do the test again. Is there a chance it was set to update MacOS automatically? Wondering if it could've started updating, and crashed during a firmware update or something odd like that.

 

[benwiggy]

If it wasn't just a one-off, then take it to an Apple Store. After paying all that money, I'd expect it to be flawless!