locked
Windows does not fully shutdown--case lights and fans remain on RRS feed

  • Question

  • Hi all.

    My computer (Win 7 64-bit) is not shutting down properly. When I click "Shut Down," Windows appears to carry out the shut down process, and the display then goes blank. But power to my case persists; fans and LED lights remain on. I have no idea if this is even a hardware (motherboard, power supply, conflict) issue or software issue (OS, BIOS, etc). Any ideas how I can pinpoint/troubleshoot the problem?

    I tried booting into safe mode and shutting down from there, but after a couple seconds the process then froze on the Windows Shut Down screen.

    My system specs are:

    Motherboard: Gigabyte GA-P67A-UD3R-B3 (rev 1.x) (latest version of BIOS is installed)

    BIOS: Latest for my motherboard (F9 I believe)

    Processor: Intel Core i7

    Memory: 8 GB DD3-1600 (4 x Kingston KHX1600C9D3K2)

    Hard Drive: Western Digital Caviar Blue 1TB WD10EZEX (brand new)

    Power supply: 700W Stronger SPSN-070P

    GPU: Radeon 6850

    This is a fresh Windows install, and all Windows updates are up-to-date

    Thanks in advance.

    Friday, January 16, 2015 4:14 PM

Answers

  • OK got it.  I'm in talks with Gigabyte support right now and have described all the troubleshooting steps I've carried out.  Hopefully they agree that my NIC is fried and take pity on me.  We can consider this resolved now, or we can wait to hear what Gigabyte says.  I'd be more apt to wait for their decision--I promise to update this thread!  But if mods want to close this, they can.
    • Proposed as answer by Michael_LS Thursday, January 22, 2015 2:09 AM
    • Marked as answer by cagross99 Thursday, January 22, 2015 2:11 AM
    Wednesday, January 21, 2015 2:31 PM

All replies

  • If you leave it for a while, say 5-10-15 minutes does it then shut down? Its possible a process / service is having trouble being shut down which Windows is waiting for.

    I would make sure that you are running with the latest motherboard / peripheral drivers, the proper ones from the manufacturers, not the built in Windows drivers even if they appear to be working. Windows needs to instruct the BIOS to turn off the PC, if it's having problems talking to the BIOS for whatever reason it may not be able to tell the BIOS to shut off the PC, even if Windows has shutdown.


    Friday, January 16, 2015 5:16 PM
    • Proposed as answer by Michael_LS Monday, January 19, 2015 8:25 AM
    Friday, January 16, 2015 6:06 PM
  • Thanks for the reply.

    >> If you leave it for a while, say 5-10-15 minutes does it then shut down?

    No.  I've left for a few hours a couple times (overnight once) and it still doesn't shut down.

    I double check all my drivers, thanks.

    Saturday, January 17, 2015 12:56 AM
  • Thanks for that.  It has some good suggestions which I'll run through.
    Saturday, January 17, 2015 12:56 AM
  • If the above procedure doesn't work, try a clean boot and see if you can shut down.

    https://support.microsoft.com/kb/929135?wa=wsignin1.0

    Jerry

    Saturday, January 17, 2015 3:20 AM
  • Hi cagross99,

    What is your current situation?

    Could the computer be shutdown properly by now?

    If issue insists, type the following command in CMD:

    shutdown –s –f –t 0

    In case some application preventing Windows from shutdown, you may also take a look at:

    Why won't my computer turn on or off quickly?

    Best regards


    Michael Shao
    TechNet Community Support

    Monday, January 19, 2015 8:30 AM
  • Thanks for the follow up.  I've put this solution route on hold slightly because I encountered another error that is probably more culpable.  My motherboard is using an incorrect BIOS.  It is using the BIOS for a different model number motherboard.  I would like to pursue this solution in-full before carrying out the rest of the solutions on this page.  What's the protocol then?  Should I mark a as the solution?  Or can we put this on pause somehow?
    Monday, January 19, 2015 8:53 AM
  • OK now that I've investigated some more, it appears my onboard LAN card is having an issue.  My computer is not detecting it ('unknown device' in device manager), and I cannot load the driver because my computer constantly thinks it's in sleep mode (that's the error message when I try to install the driver).  I'm not sure if this is the cause of my issue, but another reply in this thread was a link to a page that indicated that ethernet controller power settings might be the cause.  Since I'm having a problem with ethernet controller power settings, so I guess I should resolve those first and see if that fixes my issue.  

    I also tried the clean shutdown and clean boot suggestions in this thread, but to no avail.

    Monday, January 19, 2015 1:59 PM
  • Have you now re-flashed your Bios with the correct version?

    Were you using an incorrect Bios when Windows was installed? If so, you may need to either repair install or reinstall Windows.
    Monday, January 19, 2015 4:41 PM
  • No I was mistaken about the BIOS--I have in-fact been using the correct version the entire time.  Luckily I wasn't able to install the other, incorrect BIOS version.

    I also just removed all of memory except for a single 2GB stick, reset my BIOS to optimized settings, and re-installed Windows (only 32 bit this time).  After, the first thing I tried to do was install my onboard (Realtek) LAN driver, using the driver from my motherboard's website.   But it failed, indicating it could not detect the NIC--that it was possibly in sleep mode.  

    I've tried many things to 'wake up' my NIC:

    1.  Take RAM out and leave it out for 10 mins, to 'reset' the motherboard.
    2.  Remove all other peripherals (CD drive, wireless card).
    3.  Ensure the onboard NIC is not disabled in BIOS

    Any other ideas would be appreciated.

    Monday, January 19, 2015 5:01 PM
  • It is possible that it is dead/damaged. If all else fails, buy a replacement. Both PCI and PCI-E gigabit adapters are quite cheap.
    Monday, January 19, 2015 5:19 PM
  • This NIC is onboard my motherboard, so buying a replacement for it specifically isn't easy.  But a working LAN isn't my issue.  My issue is the shutdown problem--which I thought might be related to my NIC issue.  But I just disabled the onboard NIC in BIOS in hopes of alleviating it, but I still have the shutdown issue.

    Are there Windows error/event viewers I can view that might shed more light on this issue?  If so, how do I enable/access them?

    Tuesday, January 20, 2015 1:00 AM
  • Click Start => type "ev" => from the list which appears, click "Event Viewer" => in Event Viewer, expand "Windows Logs" and select "System"
    Tuesday, January 20, 2015 4:01 AM
  • OK thanks.  I will give that a shot this evening.  I'll post curious events here.  I'll also carry out a shut down on a working computer for comparison.
    Tuesday, January 20, 2015 4:08 AM
  • OK below my event logs for the shutdown process, from 2 different systems:  the system with the shutdown issue (system 1) and a system with working shutdown (system 2).  The broken system reports 1 error during shutdown:

    The Superfetch service terminated with service-specific error The operation completed successfully..

    I can share the details from the event viewer if you'd like, but it's a lot of gibberish.  The most interesting would be:

    [Name]  Service Control Manager 
    [ Guid]  {555908d1-a6d7-4695-8e1e-26931d2012f4 


    Unfortunately they are not identical systems  They are both running Win 7 32 bit, but the broken system (system 1) has no Windows Updates and no extra software installed.  The working system is up to date with Win updates, and has some more software installed.  I also have event log (*.evtx) files of each shutdown process, showing details.  

    Here are the full logs:

    System 1:  Broken shutdown

    Information 1/20/2015 7:33:15 PM Microsoft-Windows-Kernel-General 13 None The operating system is shutting down at system time ‎2015‎-‎01‎-‎20T12:33:15.375698400Z.
    Information 1/20/2015 7:33:11 PM Microsoft-Windows-Kernel-Power 109 (103) The kernel power manager has initiated a shutdown transition.
    Information 1/20/2015 7:33:11 PM Service Control Manager 7036 None The Windows Search service entered the stopped state.
    Information 1/20/2015 7:33:10 PM Service Control Manager 7036 None The Plug and Play service entered the stopped state.
    Information 1/20/2015 7:33:10 PM Microsoft-Windows-UserPnp 20010 (7010) "One or more of the Plug and Play service's subsystems has changed state. 

    PlugPlay install subsystem enabled: 'false' 
    PlugPlay caching subsystem enabled: 'false' 
    "
    Information 1/20/2015 7:33:10 PM Service Control Manager 7036 None The Cryptographic Services service entered the stopped state.
    Information 1/20/2015 7:33:10 PM Service Control Manager 7036 None The Windows Management Instrumentation service entered the stopped state.
    Information 1/20/2015 7:33:10 PM Service Control Manager 7036 None The Software Protection service entered the stopped state.
    Information 1/20/2015 7:33:10 PM Service Control Manager 7036 None The Distributed Link Tracking Client service entered the stopped state.
    Information 1/20/2015 7:33:10 PM Service Control Manager 7036 None The Desktop Window Manager Session Manager service entered the stopped state.
    Error 1/20/2015 7:33:10 PM Service Control Manager 7024 None The Superfetch service terminated with service-specific error The operation completed successfully..
    Information 1/20/2015 7:33:10 PM Service Control Manager 7036 None The Superfetch service entered the stopped state.
    Information 1/20/2015 7:33:10 PM Service Control Manager 7036 None The Diagnostic Policy Service service entered the stopped state.
    Information 1/20/2015 7:33:10 PM Service Control Manager 7036 None The Windows Event Log service entered the stopped state.
    Information 1/20/2015 7:34:11 PM EventLog 6013 None The system uptime is 10 seconds.
    Information 1/20/2015 7:33:09 PM Service Control Manager 7036 None The Diagnostic Service Host service entered the stopped state.
    Information 1/20/2015 7:34:11 PM EventLog 6005 None The Event log service was started.
    Information 1/20/2015 7:33:09 PM Service Control Manager 7036 None The User Profile Service service entered the stopped state.
    Information 1/20/2015 7:34:11 PM EventLog 6009 None Microsoft (R) Windows (R) 6.01. 7600  Multiprocessor Free.
    Information 1/20/2015 7:33:09 PM Service Control Manager 7036 None The DHCP Client service entered the stopped state.
    Information 1/20/2015 7:33:09 PM Service Control Manager 7036 None The Power service entered the stopped state.
    Information 1/20/2015 7:33:09 PM Service Control Manager 7036 None The Human Interface Device Access service entered the stopped state.
    Information 1/20/2015 7:33:09 PM Service Control Manager 7036 None The Diagnostic System Host service entered the stopped state.
    Information 1/20/2015 7:33:09 PM Microsoft-Windows-Dhcp-Client 50037 Service State Event DHCPv4 client service is stopped. ShutDown Flag value is 1
    Information 1/20/2015 7:33:09 PM Microsoft-Windows-DHCPv6-Client 51047 Service State Event DHCPv6 client service is stopped. ShutDown Flag value is 1
    Information 1/20/2015 7:33:09 PM Service Control Manager 7036 None The Group Policy Client service entered the stopped state.
    Information 1/20/2015 7:33:09 PM Microsoft-Windows-Winlogon 7002 (1102) User Logoff Notification for Customer Experience Improvement Program
    Information 1/20/2015 7:33:09 PM EventLog 6006 None The Event log service was stopped.
    Information 1/20/2015 7:33:09 PM USER32 1074 None "The process C:\Windows\system32\winlogon.exe (DUSKWOOD) has initiated the power off of computer DUSKWOOD on behalf of user duskwood\snarl for the 


    System 2:  Working Shutdown

    Information 20/01/2015 11:15:29 Microsoft-Windows-FilterManager 6 None File System Filter 'aswSP' (6.0, ‎2014‎-‎11‎-‎18T16:06:36.000000000Z) has successfully loaded and registered with Filter Manager.
    Information 20/01/2015 11:15:27 Microsoft-Windows-FilterManager 6 None File System Filter 'aswSnx' (6.0, ‎2014‎-‎11‎-‎21T18:16:29.000000000Z) has successfully loaded and registered with Filter Manager.
    Information 20/01/2015 11:15:15 Microsoft-Windows-FilterManager 6 None File System Filter 'FileInfo' (6.1, ‎2009‎-‎07‎-‎14T06:21:51.000000000Z) has successfully loaded and registered with Filter Manager.
    Information 20/01/2015 11:15:15 Microsoft-Windows-Kernel-General 12 None The operating system started at system time ‎2015‎-‎01‎-‎20T04:15:15.375199800Z.
    Information 20/01/2015 11:14:17 Microsoft-Windows-Kernel-General 13 None The operating system is shutting down at system time ‎2015‎-‎01‎-‎20T04:14:17.541276400Z.
    Information 20/01/2015 11:14:11 Service Control Manager 7036 None The Windows Image Acquisition (WIA) service entered the stopped state.
    Information 20/01/2015 11:14:11 Microsoft-Windows-Kernel-Power 109 (103) The kernel power manager has initiated a shutdown transition.
    Information 20/01/2015 11:14:08 Service Control Manager 7036 None The Windows Search service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The Intel(R) Management and Security Application Local Management Service service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The avast! Antivirus service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The Superfetch service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The Volume Shadow Copy service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The Windows Modules Installer service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The Windows Font Cache Service service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The IKE and AuthIP IPsec Keying Modules service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The Cryptographic Services service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The WLAN AutoConfig service entered the stopped state.
    Warning 20/01/2015 11:14:07 Microsoft-Windows-WLAN-AutoConfig 4001 None "WLAN AutoConfig service has successfully stopped.
    "
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The Software Protection service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The IPsec Policy Agent service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The Windows Defender service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The Windows Management Instrumentation service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The Windows Event Log service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The Microsoft Software Shadow Copy Provider service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The Security Center service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The Function Discovery Resource Publication service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The Extensible Authentication Protocol service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The Distributed Link Tracking Client service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The Intel(R) Management and Security Application User Notification Service service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The Desktop Window Manager Session Manager service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The Office Software Protection Platform service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The User Profile Service service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The Plug and Play service entered the stopped state.
    Information 20/01/2015 11:14:07 Microsoft-Windows-UserPnp 20010 (7010) "One or more of the Plug and Play service's subsystems has changed state. 

    PlugPlay install subsystem enabled: 'false' 
    PlugPlay caching subsystem enabled: 'false' 
    "
    Information 20/01/2015 11:15:50 EventLog 6013 None The system uptime is 35 seconds.
    Information 20/01/2015 11:15:50 EventLog 6005 None The Event log service was started.
    Information 20/01/2015 11:15:50 EventLog 6009 None Microsoft (R) Windows (R) 6.01. 7601 Service Pack 1 Multiprocessor Free.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The Power service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The PDQ Deploy service entered the stopped state.
    Information 20/01/2015 11:14:07 Service Control Manager 7036 None The Human Interface Device Access service entered the stopped state.
    Information 20/01/2015 11:14:06 Service Control Manager 7036 None The Diagnostic Service Host service entered the stopped state.
    Information 20/01/2015 11:14:06 Service Control Manager 7036 None The Diagnostic Policy Service service entered the stopped state.
    Information 20/01/2015 11:14:06 Service Control Manager 7036 None The DHCP Client service entered the stopped state.
    Information 20/01/2015 11:14:06 Microsoft-Windows-Dhcp-Client 50037 Service State Event DHCPv4 client service is stopped. ShutDown Flag value is 1
    Information 20/01/2015 11:14:06 Microsoft-Windows-DHCPv6-Client 51047 Service State Event DHCPv6 client service is stopped. ShutDown Flag value is 1
    Information 20/01/2015 11:14:06 Service Control Manager 7036 None The Diagnostic System Host service entered the stopped state.
    Information 20/01/2015 11:14:06 Service Control Manager 7036 None The Bonjour Service service entered the stopped state.
    Information 20/01/2015 11:14:06 Service Control Manager 7036 None The AMD External Events Utility service entered the stopped state.
    Information 20/01/2015 11:14:07 EventLog 6006 None The Event log service was stopped.
    Information 20/01/2015 11:14:06 Service Control Manager 7036 None The Group Policy Client service entered the stopped state.
    Information 20/01/2015 11:14:06 Service Control Manager 7036 None The Windows Update service entered the stopped state.
    Information 20/01/2015 11:14:05 Microsoft-Windows-WindowsUpdateClient 27 Windows Update Agent Automatic Updates is now paused.
    Information 20/01/2015 11:14:05 Microsoft-Windows-Winlogon 7002 (1102) User Logoff Notification for Customer Experience Improvement Program
    Information 20/01/2015 11:14:05 USER32 1074 None "The process C:\Windows\system32\winlogon.exe (TEACHER) has initiated the power off of computer TEACHER on behalf of user TEACHER\LENOVO for the following reason: No title for this reason could be found
     Reason Code: 0x500ff
     Shutdown Type: power off
     Comment: "
    Information 20/01/2015 11:14:02 USER32 1074 None "The process Explorer.EXE has initiated the power off of computer TEACHER on behalf of user TEACHER\LENOVO for the following reason: Other (Unplanned)
     Reason Code: 0x0
     Shutdown Type: power off
     Comment: "
    Information 20/01/2015 11:13:52 Microsoft-Windows-Eventlog 104 Log clear The System log file was cleared.


    Tuesday, January 20, 2015 1:10 PM
  • Maybe someone else can help you more with regard to your event logs, but nothing is leaping out from the above.

    If you boot into safe mode does the pc then shut down properly?

    Is this a laptop or desktop?

    If a laptop, what is the manufacturer/model?
    If a desktop, what is the manufacturer/model of the motherboard?

    Does/did the pc get it's internet through a landline?
    Tuesday, January 20, 2015 4:10 PM
  • Thanks for the reply.

    What about the Superfetch error?  Any idea what that means?

    Safe mode suffers from the same problem.

    This is a desktop.  Motherboard is a Gigabyte GA-P67A-UD3R-B3 (rev 1.x).  Latest BIOS is installed.

    Right now the PC doesn't get any internet at all.  I have a wireless card that I can install and use without issue.

    Tuesday, January 20, 2015 4:53 PM
  • What about the Superfetch error?

    Sorry, no idea. But I do know that it won't hurt to test after disabling the service (Click Start => type "se" => select "Services" from the list => find "Superfetch" in the Services window => right click and select "Properties" => set Startup type to "disabled"). Intel actually recommends disabling this service when using their SSD's.

    After that, about all I can think of doing are the following:

    1. In Power Options (click Start => type "po" => select "Power Options" from the list), click "Change Plan Settings" then click "Change Advanced Power Settings". Expand "USB settings", expand "USB selective suspend setting" then click on Enabled and change to Disabled.

    2. Work your way through Device Manager and for anything that has a "Power Management" tab in it's Properties, uncheck "Allow this device to wake the computer". This would include anything in the categories : Human Interface Devices, IEEE 1394 Bus host controllers, Keyboards, Mice and other pointing devices, Network adapters, Universal Serial Bus Controllers. Also swap out any connected peripherals.

    3. Disable all power management of all devices. As for 2. - except this time also uncheck "Allow the computer to turn off this device to save power"

    4. Reset your Bios using "Fail-Safe Defaults" instead of "Optimized Defaults." Also try disabling "PME Wakeup Event" and "Power on by ring" in Power Management Setup.

    5. If desperate, reflash Bios.

    I am curious about the LAN cable test (Smart LAN) in your Bios which should detect if the network adapter is connected to a switch. Are you able to test this? (Manual - page 46)

    And I asked about the internet connection because of the possibility of, for example, lightning strike on the phone line. If the Realtek Lan chip has been fried there may easily be other damage. 

    • Edited by mystifeid Tuesday, January 20, 2015 8:11 PM
    • Proposed as answer by Michael_LS Thursday, January 22, 2015 2:09 AM
    Tuesday, January 20, 2015 7:45 PM
  • Thanks for the reply.  I tried disabling the Superfetch service, but the issue remained.

    I also tried your other suggestions:

    1.  Disabled USB Selective suspend setting, but did not work.

    2.  In device manager, I made sure all power options were disabled.  There were only 2--keyboard and mouse--and they both had 'allow this device to wake the computer.'  I disabled, but nothing.

    3.  There were  no devices with this option ticked.

    4.  I loaded fail safe settings and disabled the 2 settings you mentioned, but nothing.

    5.  I did this, but nothing.

    I also connected my ethernet port to a working router and ran the SMART LAN test from BIOS.  It reported nothing.  When I highlighted "SMART LAN" and pressed enter, nothing was displayed on the screen (as if no NIC was found).

    I also downloaded and ran the Realtek Ethernet Diagnostic Utility.  It did not detect any NIC at all on my system.

    Would you agree that I've isolated the issue to a hardware issue pertaining to the ethernet controller?  If not, are there any additional tests/diagnostics I can run?

    Thanks for your patience.

    Wednesday, January 21, 2015 12:21 PM
  • There are always more tests but unfortunately it appears that the NIC is fried. Perhaps this damaged chip is causing your shutdown issue but as mentioned, perhaps there is more extensive damage. If you RMA this motherboard, you may be pleasantly surprised at the cost of a replacement.
    Wednesday, January 21, 2015 2:28 PM
  • OK got it.  I'm in talks with Gigabyte support right now and have described all the troubleshooting steps I've carried out.  Hopefully they agree that my NIC is fried and take pity on me.  We can consider this resolved now, or we can wait to hear what Gigabyte says.  I'd be more apt to wait for their decision--I promise to update this thread!  But if mods want to close this, they can.
    • Proposed as answer by Michael_LS Thursday, January 22, 2015 2:09 AM
    • Marked as answer by cagross99 Thursday, January 22, 2015 2:11 AM
    Wednesday, January 21, 2015 2:31 PM