System Refuses to Power Down

Having trouble with a notebook that refuses to power down. The model is "Hasee K480N" which may not make any sense to most of you. It's a Ivy Bridge system on HM76.


The notebook used to work just fine but suddenly refuses to power off at the end of a shut down. The same issue is experienced under both Windows and Linux.

The notebook always get stuck at the last screen before shut down with the screen back light still on. The HDD will spin down (which means no log can be found) but the disk indicator LED stays on and rest of the system won't turn off. The only way to power the thing down is to hold the power button for a few seconds to force a shut down.

S3 sleep doesn't work either. It won't wake up and forcing a shut down results in RAM data loss.

Rebooting does work, but with a very long (5~10 seconds) delay at the last screen before going off.

The only trick I've tried so far is loading BIOS/UEFI defaults which doesn't help.


Any ideas?


Edit:
When shutting down from Grub, I get a "Unexpected extended opcode: 0x82; ACPI shutdown failed" message.

 

Sounds like a hardware or BIOS issue. If Windows and Linux are both having the shutdown issue, then it is more likely a hardware component than a software component. It may be driver issue, but it would have to be an important driver like the GPU, chipset, etc.

More information is needed. Are you running on AC or battery? Have you made any hardware changes to the system about the time this started? If it just started suddenly, were you doing anything different, like you were playing a GPU intensive game for the first time? Usually the power on a power off is controlled by the motherboard. The idea now is to try and eliminate any possibility it's you hard drive/SSD or the OSes installed on it.

 

Thanks for the reply.

I'm sure no hardware changes were made. Not sure about BIOS config but there shouldn't be any change right before the issue was discovered (not my own notebook, and I wasn't around when the issue was noticed), and resetting BIOS settings doesn't help.

Even booting from USB results in the same behavior, so any OS/driver/software cause is very unlikely. Running on battery, AC or AC with battery removed don't make any difference.

The system was not running anything heavy before the problem appeared. Before the first time it went wrong, it was just doing note taking in a class. The system had been doing long renders before without any issue.

 

Perhaps your system experienced a short? Have you tried sending it out for repair?

 

2nd that. Something's gotta give is the phrase that comes to mind. Any if one hardware component is not wanting to shutdown, it can hold up the rest of them. If you feel so inclined (and if the BIOS allows it) you can run a PSA [POST Systems Assessment]. It's the diagnostics option when the boot menu options come up after hitting F12...or whatever you push to make the boot selection come up after POST. The diagnostics will test the chipset, RAM and CPU for any hardware errors.

 

The issues I've seen with this problem have all been software related (specifically: the O/S and/or drivers).

Has a re-install been attempted as a possible fix?

If this is a HDD based setup, make sure that the drive is scanned fully (chkdks c: /f ... so that any bad sectors can be mapped out and not used anymore)... actually, this could apply to any storage subsystem (even an SSD).


Good luck.

 

Thanks for the replies.

I can't find any PSA option on this machine.

Booting from 2 on-disk operation systems and 2 bootable USBs result in the same behavior, so any OS/driver issue is unlikely to be the cause.


I accidentally tried to shutdown from Grub, got a " Unexpected extended opcode: 0x82; ACPI shutdown failed" message. I tried disabling ACPI by the acpi=off option and the system crashes at shutdown.

Any ideas?

 

ACPI failure? That indicates a motherboard failure...or at least the voltage control circuits are going faster than a gremlin in sunlight.