Windows 10: Windows 10 shuts down, but PC won't

Thanks Brink, I will try that shortcut.

To me, the problem feels like a hardware issue. Windows seems to fully shutdown, the monitor goes into standby, and there's no obvious hung software. What seems to be happening is perhaps Windows isn't passing off the 'power off' command to the BIOS, maybe? Everything about the shutdown is normal except the motherboard stays powered. Fans and all LED's (and lights on the motherboard). All i can do then is force-power it off. It's definitely a weird issue, and not something I've encountered in all my years of building PC's.

I've googled this and others have had the same problem, with different motherboards and different versions of Windows.

I tried your shortcut and it worked the one time I used it. I'll keep trying it, and let you know if it eventually fails (or not).

 

The shortcut will at least help to rule out a possible hung app, but yeah it could be some sort of hardware or driver issue as well.

 

Sorry about basically double-posting above. I thought my 1st one didn't get sent, it apparently went to page 2 and I didn't notice.

As far as mobo drivers, I've been over those extensively, and everything seems to be up to date.

 

Update: the shutdown failed on the 2nd attempt using the provided shortcut, so I guess that rules out a hung application?

 

Yep. *Sad

You might see if the shutdown logs may reveal anything, but not sure it will if hardware related.

Read Shutdown Logs in Event Viewer in Windows Windows 10 Performance Maintenance Tutorials

If all else fails, you might consider a clean install.

 

I followed that guide and it didn't reveal anything of interest. No errors were reported by the OS and nothing really to differentiate a good shutdown from a bad one. This seems to further point to it being a hardware/bios issue.

BIOS revisions for my mobo

When I built the PC on May 6, the mobo shipped with the 1.10 bios installed. I updated to 2.00 which stopped serious issues I was having with system stability, including increasing the amount of voltage the CPU was getting. It stopped all my BSOD's and freezes.

However, I *think* this power-off issue also started then and it just occurred to me that, in thinking back, I don't think the power off issue happened until the 2.0 bios.

I'm wondering if I should try the 1.3 bios, which includes the CPU/voltage/etc fixes I need but isn't 2.0 which may be the source of the shutdown problem.

Thanks again for all your help.

 

It's worth a try to see.

 

If you disconnect all hard drives, and powered up the computer, wait for the no boot device error, then press & hold the power button, does the power supply shut down ?

Alternatively if you have other bootable media, and you boot from that, are you able to power down ?

Might be helpful to isolate MB, processor, power supply apart from Windows.

 

I had to disable in BIOS, the onboard Broadcom Netlink Gigabit ethernet NIC.
Doing that returned normal Power supply operation. Sleep, Shutdown, Hibernation, now normal.
The pc, being wireless, did not have me suspecting the onboard NIC & W10 CU compatibility problems.

Find some weird things in computers. *Tongue

 

update: I did several new things in trying to locate the problem

• successfully flashed the BIOS from 2.0 to 1.3
• left the BIOS settings mostly at defaults
• RAM left at default 2133mhz, for now, not running the XMP profile (3000mhz)
• unplugged USB printer from motherboard

So far, since flashing the BIOS to 1.3, i haven't had any failures (2 shutdowns, 2 sleep, all successful). Though I've learned this doesn't mean much - i've had strings of successes before, only for it to fail again. But it's a start.

If after 3 or 4 days of no failures, I'll do things one at a time, like plug in the printer, enable the RAM's XMP profile, etc. and see if I start getting failures or hopefully not, and I can attribute the success to the 1.3 bios.

 

Since rolling back to the 1.30 BIOS, i haven't had any more issues. 5 days and something like 20 or 22 consecutive shutdown/sleep with no failures.

Considering this one resolved. Thanks to all for the help.
@me75006: for good measure I disabled the secondary ethernet NIC in the BIOS also, thanks for the tip.

 

Great news. You might report that issue to your motherboard manufacturer to see if it may help them to fix the issue in a future BIOS version release.