Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Do any internal components got damaged?


  • Total voters
    3

mr.johnlocke8

macrumors newbie
Original poster
Sep 8, 2018
1
0
Opened a discussion here as well:
https://discussions.apple.com/thread/8528117

Hey

Yesterday, after playing with my MacBook's pmset settings, I closed the lid (while plugged in), and after 4 hours I just unplugged it and went to sleep. This morning I'm waking up to an extremely hot, battery drained (3%) MacBook. I immediately plugged it to the charger and opened the lid to help it cool down.

After a couple minutes, I was curious to why he won't sleep during the night, so I ran
pmset -g log | grep -i "wake from"

and this is what I've found out:

2018-09-07 22:59:09 +0300 DarkWake DarkWake from Standby [CDN] due to /HibernateError: Using BATT (Charge:100%) 6 secs

2018-09-07 22:59:21 +0300 DarkWake DarkWake from Standby [CDN] due to /HibernateError: Using BATT (Charge:100%) 6 secs

2018-09-07 22:59:32 +0300 DarkWake DarkWake from Standby [CDN] due to /HibernateError: Using BATT (Charge:100%) 7 secs

...

2018-09-08 07:10:13 +0300 DarkWake DarkWake from Standby [CDN] due to /HibernateError: Using BATT (Charge:4%) 8 secs

2018-09-08 07:10:26 +0300 DarkWake DarkWake from Standby [CDN] due to /HibernateError: Using BATT (Charge:3%) 6 secs

2018-09-08 07:10:37 +0300 DarkWake DarkWake from Standby [CDN] due to /HibernateError: Using BATT (Charge:3%) 7 secs



Notice the time, and more importantly the cause - "HibernateError".
This is my pmset:

$ pmset -g custom
Battery Power:
lidwake 0
autopoweroff 0
autopoweroffdelay 600
standbydelay 600
standby 1
ttyskeepawake 0
hibernatemode 0
gpuswitch 2
powernap 0
hibernatefile /var/vm/sleepimage
displaysleep 1
sleep 1
tcpkeepalive 0
halfdim 1
acwake 0
lessbright 1
disksleep 1

AC Power:
lidwake 0
autopoweroff 0
autopoweroffdelay 600
standbydelay 3600
standby 1
ttyskeepawake 0
hibernatemode 0
powernap 0
gpuswitch 2
hibernatefile /var/vm/sleepimage
displaysleep 5
womp 0
networkoversleep 0
sleep 5
tcpkeepalive 0
halfdim 0
acwake 0
disksleep 5


I think that what have may caused it was the fact that I closed the lid while it was plugged, went for 4 hours (during that time my MacBook went into standby mode), and then just unplugging it. I think that if I were to open the lid after unplugging it, and letting it go to standby when on battery power, this wouldn't have happen.

I'm also worried about any hardware damage (mainly the battery, due to deep discharge and heating). Am I worrying for nothing?

I couldn't find something about this error on Google, so I decided to ask here, as it seems like a place where I could get good help.

Thank you very much for reading, John.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.