When the power cable is connected and the computer is put in sleep mode it wakes up fine. If I unplug the cable after the computer was put in sleep mode, or if I put it to sleep mode after I have unplugged it, it will shutdown unexpectedly and start fresh.

Computer works fine when I unplug it when it's on. The only problem seems to be the combination of sleep mode and being unplugged (for now).

QUESTION: should I suspect battery issues at this point? My guess is the battery does not keep voltage high enough when the power cable is off.

Adding some screenshots showing when this started to happen after: enter image description here

ADDENDUM: windows 10 battery report: https://pastebin.com/raw/Rz1ehZBm


Believe it or not, maybe one of the battery cells is dead. One cell could cause what you're experiencing. The voltage does come up, but since a cell is dead the capacity is diminished. Another example of this would be, you unplug it, and start a program, that will cause the CPU to spike, probably the hard drive to spin up and the power draw too much for the battery soon after the BMS (battery management system) reports low voltage, computer believes battery is low and turns itself off, or dies before shutdown.

You could just try to discard windows or some other program playing tricks by going into the BIOS and unplugging it, if it dies immediately... you'll know it's probably hardware.

  • Thanks for the suggestions - not sure i understood the last suggestion though. My computer does not die if I unplug it, I would doubt that it will die in BIOS as well. I have not tried to the suggestion with CPU spike, I think I will be able to just load the CPU with special utilities that exit. – Mindaugas Bernatavičius Aug 13 '19 at 4:53
  • 1
    From the error I grasped that the machine was randomly turning off, since it said it didn't turn off cleanly. Hmm my guess if it's just during suspend is either driver issue, or BSOD during wake up. The reason I say this is because this seems to happen during S state changes. Have you contacted their support? there might be a recall or there might be a driver update. Another option you could try is disabling also C-states if possible in the bios and checking if the issue still occurs. – ddemuro Aug 13 '19 at 5:50

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.