Windows 10 not shutting down correctly

OK, so I know a lot of people have had this same problem: Windows 10 tries to shut down, but the fans keep spinning and the lights are still on. Now, I´ve tried both changing the action the power button performs, and disabling fast startup, but there´s been no change. I´ve recently changed the GPU, and I´ve tried swapping the PSU, but there´s been no change. My specs are as follows:

i7 2600k
Intel DP67BG Mobo
Hyper 212 EVO cooler
EVGA GTX 770 2GB now, EVGA GTX 650 before
Thermaltake TR2 600W PSU (Tried a generic 650W too)
Toshiba 500GB HDD
LG DVD
Single low-profile Kingston DDR3 4GB 1333MHz stick

Now, there´s several things I´d like to point out: first of all, this system was left on 24/7 from 2012 until a few months ago, having been used for the first half as a PC and server, and for the second half as a pfSense router (don´t judge me, I had no other PCs lying around, and once it was configured I was too lazy to replace this PC), and when I decided to repurpose it as a W10 PC one of the RAM sticks had failed.
Another thing is that this Mobo is a flawed Cougar Point B2, the ones with the failing SATA ports, so I don´t know if over time the issue could have extended to other parts of the system.

So, here´s the question: Are there any other W10 configurations I should change? Or should I try other Mobo/Ram/CPU?

PS: When the system shuts down, the Mobo code readout says "05", which means it entered ACPI State 5 (manual at http://www.intel.com/content/dam/support/us/en/documents/motherboards/desktop/dp67bg/dp67bg_productguide01_english.pdf )

FYI when you tell windows to shut down - it doesnt actually shut down - it writes a hybrid hibernation file and saves the kernel state. You need to disable fast boot in the BIOS if you actually want it to shut down completely.
As you mentioned the mobo is a bit iffy - so try shutting down from the cmd line with the right arguments and see if that helps. You can either do it manually each time - or write a batch file to do it for you.

open cmd as admin and type

shutdown /s /t 0 <--- here the 's' means shut down, and the /t 0 means time delay zero - so right away. You could change the /s to /r for a restart also. Note that this will shut down the computer right there and then, so be sure to save anything youre working on first.

more info here on arguments you can use

I remember trying that too a few days ago, and the result was the same. Reboots are fine, but shutdowns, even using the command, still don't work

Have you tried waiting 10 or 20 minutes? If I try to shut down after gaming it takes a while to cool off before it will shut off

I had this same issue with my PC for a while though it was intermittent for me. I fixed it by disabling Hybrid Sleep in the Advanced Power Options. It seems to be a known Windows 10 bug as I saw it on Forums quite a bit when i was trying to ID what was causing.

Actually I think I've turned all the Sleep Options to Disabled or equivalent at the moment because Win 10's Sleep options are horrible.........

Have you tried in cmd (admin maybe) powercfg -h off ?

This way it removes the hiberfile that screws things up when trying to use the drives without hassle.

@anon85933304 Yes, sometimes I would forget about it and it would still be on the next morning

@SnowHeart Will try today

@shu_kaze Will try today

1 Like

It's not related to the OP, unfortunately...but it still falls under this title.

But if anyone has a similar problem with an ASUS motherboard, there is a known issue with AISuite (speciffically the EPU functionality) that can cause AHCI to kind of go out of control.

The result is crashes (extremely rare), or more commonly the inability to shutdown or restart in a similar manner to that described by the OP: Everything turns off except the motherboard never finally shuts down. Even a manual power off (holding the power button) may still leave some things active, for example the audio trace LEDs on my X-99-A. When this happens, a manual restart will trigger a bios warning about failed overclock (even at stock speeds). [For me] simply entering the bios, then exiting resolves this warning while retaining all my OC settings.

Before shutting down, you can check the task manager. High CPU usage on either the "System" or "System and Compressed Memory" process indicates the bug has been triggered. As the bug appears to be triggered from the user-mode application, often times re-logging (logging out and back in, not shutting down) can fix it, although you may have to do this multiple times. If you see the above process stable at low CPU usage, it is safe to shut down.

Interesting this would happen to my laptop. I thought it was just updating

Sorry, had to do a few things these days and I forgot to post an update. Apparently, @SnowHeart ´s solution is the same as @shu_kaze - one is through the UI and the other one through CMD. And sadly, neither one worked :( I´ll probably try a blank install on another hdd just in case, even though the problem started right after installing W10. Thanks anyway to both

Can you shut down your machine properly when running Linux live cd or when you are in bios? I had similar sounding problem once. Windows failed to shut down all the time but also had problems with live cd's and even when pushing power button in bios. Luckily clearing CMOS solved that problem.

Maybe W10 upgraded my bios and broke some settings?

I have a similar issue, but it doesn't happen every time i shut down. But some times it sit there for 10mins with fan on then turns on sometime 20 - 30 mins or until I hold the power button.

So I have begin just pressing the power button to tun it off. Not the long press to force the motherboard to tun it off. Just a normal press just as if you wee tun on your pc. Also this gets around update and shutdown.

Sounds like a hardware issue to me. Windows is shutting down but the pc is not turning off?
Do you have any live linux distros you can put on a usb stick and try?

I'd be pulling out the power supply and checking the plugs, checking the motherboard over, pulling stuff out to see if something is causing it.