[solution] windows doesnt shutdown on maximus boards

[Stukow]

after i got my Maximus Hero 8 Board i had 2-3 stressful weeks because Windows wouldnt shutdown fully and properly the shutdown page with the shutdown message stays until i get a bsod after about 10mins the board is still alive fans rotate lights are up the graphic card is still alive!

so i searched and did much things to solve this problem changed settings in the bios changed ram banks and position plugged in and out usb devices deinstalled programs and many things to find a solution but 99% of the advices also found in here didnt help near to giving up making some last trys i found the solution so here it is.

Some of the Autostart services from Intel probably installed with the drivers from the Asus Mainboard Site cause the problem so we need to deactivate them.


Press the Windows button now in the search bar type msconfig on the window popping up go to servicesand search for the Intel services now deactivate them by unclick the checkmark that is it now your Board should shutdown fully and properly!


[IMG" TARGET="_blank">http://fs5.directupload.net/images/151225/temp/49ib4uty.jpg[/IMG]"]

[Nate152]

Hi matchadoabout

Welcome to the ROG forum !

If you're using AI Suite III try uninstalling it from your programs and run this cleaner.

http://rog.asus.com/forum/showthread.php?34503-AI-Suite-III-Cleaner

My pc won't shut down if it's not completely stable specifically the ram, if you're not using AI Suite III try raising a few voltages.

On the extreme tweaker tab try:

CPU VCCIO voltage 1.20v - 1.25v
CPU System Agent voltage 1.20v - 1.25v

If it still isn't shutting down try the Dram voltage at 1.40v - 1.45v

Let us know if this helps.

[matchadoabout]

Tried those voltages and have had no luck so far. 😞 I also don't have AISuite III installed and have used that cleaner.

[Dho7rX]

Oh damn. I got 6700K, 4x 4Gb DDR3200 cl15 corsair on the asus rog z170 maximus 8 extreme, coolermaster vanguard 1000w, Sapphire R9290x tri-x 4Gb and an intel ssd. On windows 10 64bit i got the same restart issue after shutdown. Never had the issue on windows 7 tho. Need some help please

[matchadoabout]

I've pretty much given up at this point and disabled USB3.1/Thunderbolt from the BIOS in Onboard Devices Configuration to allow proper shutdown. I actually kinda regret this purchase of a Maximus VIII Impact. Since it didn't have M.2, it's premium only snowballed with an Intel U.2 SSD. USB3.1 Type-C, after all was the deciding factor between this board and my other option. Without it, it's not really worth it. I could have settled with a Z170 mini-ITX board with M.2.

[matchadoabout]

Sorry for the double post but this may be valuable to people. I didn't really give up on my Maximus VIII Impact and have finally fixed my problem.

Here's what I did:

1. Disabled Fast Boot and CSM before installation
2. Installed Windows 10 using an image made from Rufus
3. Updated Windows 10
4. Installed drivers from Asus support page except for Bluetooth and Ethernet. (They seem to be outdated)
5. Installed i219-V drivers from Intel's site
6. Go to Device Manager and change the power management of the Ethernet port (i219-V) and UNTICK Wake on pattern match.

I feel like the last step made all the difference.

[MaXeLL]

matchadoabout wrote:
Sorry for the double post but this may be valuable to people. I didn't really give up on my Maximus VIII Impact and have finally fixed my problem.

Here's what I did:

1. Disabled Fast Boot and CSM before installation
2. Installed Windows 10 using an image made from Rufus
3. Updated Windows 10
4. Installed drivers from Asus support page except for Bluetooth and Ethernet. (They seem to be outdated)
5. Installed i219-V drivers from Intel's site
6. Go to Device Manager and change the power management of the Ethernet port (i219-V) and UNTICK Wake on pattern match.

I feel like the last step made all the difference.

I'll report in a few days if this resolve this issue on my motherboard (Maximus VIII Extreme)!

[matchadoabout]

All right. Keep me posted. It would be interesting to find out if this is a more widespread case than only my board.

[Janne-71]

For me all that i needed to do was Aisuite 3 uninstall. Also uninstalled some other motherboard disc programs, most of them.

[dimigr73]

Hello all,

I also have the random shut down issue (monitor, keyboard, mouse turn off but the case power button is on and the fans still active).
The problem is that it's happening randomly (as many of you have noticed). I have installed everything from ASUS CD, so I guess I should start uninstalling...

However, due to the fact that this problem occurs in a variety of boards, operating systems, installed programs (with or without AI SUITE 3) and BIOS versions (mine is 1701), I think maybe the problem lies elsewhere.
Maybe some weird power management and/or SSD behaviour?

EDIT: I have 3 case fans which are controlled by the PC case integrated fan controller, so the only fan connected on the board is the CPU fan.

[matchadoabout]

Back again for more updates from my side. It worked fine for the past while until I decided to mess with the Ethernet driver settings again. I was trying to enable wake on LAN and somehow I've retriggered the issue. I've played around with the Ethernet options and there's no clear cut solution from that end. It seems to SOMETIMES be prevented by combinations of settings.

Now, I'm leaning to the common solution that I've seen while searching around. On top of my solution above, disabling the Intel Management Engine from the device manager seems to help quite a bit. The issue with this is that wake on LAN seems to be causing my PC to turn on immediately after some shut downs. Must be because I turned off IMEI. In other forums, the solution seems to be to install an older version of the management engine (version 9.5). Unfortunately, we can't use this version on our motherboards.

At this point, I'm not sure anymore if this whole issue is a Windows thing, Intel drivers issue or even a BIOS/UEFI problem. It's looking like a mixture of all because i can sometimes get rid of the problem by clearing CMOS or fresh installing Windows.