PC won't power down after Windows 7 shutsdown

[ExodusTerminal]

Problem is in the title thread. Windows turns off, screen goes into power saving mode, but lights are still on and fans are still whirling. When I try to turn it off in save mode, it freezes on "shutting down computer".

It will restart although it takes ~30 seconds to do so.

Problem started last Friday. I haven't installed any new hardware since Wednesday, when I installed my HDD. I might have updated a driver, but I can't recall.

I've reset the BIOS back to original settings also, but that's had no luck.

Also, sometimes it takes very long to boot up - up to 2 minutes. Most of the time it takes ~20 seconds though.

Any suggestions?

 

[marsmimar]

Hello ET and welcome to Seven Forums.

Providing this isn't a hardware issue you may be able to roll back your computer prior to last Friday (when the problem started) by using a restore point.

http://www.sevenforums.com/tutorials/700-system-restore.html

You could also check for damaged or corrupt system files by running a system file checker scan from an elevated command prompt (option two.) If problems are found, run the scan 3 times and reboot the computer after each scan.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

One of the Forum experts prepared this troubleshooting guide:

http://www.sevenforums.com/tutorials/220165-troubleshooting-steps-windows-7-a.html

And this Microsoft forum thread may help:

Windows 7 after shutdown will not power off - Microsoft Community

 

[ExodusTerminal]

I don't believe it's a hardware issue since the PSU is supposed to be quite good + it restarts fine (albeit takes ~20 seconds after Windows actually shuts down).

Unfortunately I've disabled System Restore as I've been advised to do so on an SSD to conserve space.

Sfc scan reveals nothing.

Going through that guide, Malwarebytes scan is clean but for the last time I turned off my PC this event appeared in my EventViewer:

The server {60A90A2F-858D-42AF-8929-82BE9D99E8A1} did not register with DCOM within the required timeout.

Event ID: 10010, Source: DistributedCOM

What does this error mean?

Also, when I just booted my PC, the Error that came up in the Event Log is:

The attempt to install printer Fax into an offline operating system image failed with Win32 error code 87 (0x57). This can occur if the printer driver requires user input or displays a user interface (UI) during installation.

Event ID: 359.

However, I've never tried to install a Printer (nor have one connected)..

Thoughts?

 

[ExodusTerminal]

Whilst uninstalling the Drivers for my Graphics Card, the screen went dark and the system "screamed" instead of playing music. I gave it a minute to turn off, after which time I powered it down manually. When I restarted my PC, it could not longer detect my SSD which had Windows installed, but could detect my HDD.

I've installed Windows onto my HDD now, but I still can't see my SSD in the Bios, under Device Manager etc.

It seems to me that this confirms that it's a hardware fault, most likely the PSU.

Thoughts?

 

[Indianatone]

Whilst uninstalling the Drivers for my Graphics Card, the screen went dark and the system "screamed" instead of playing music. I gave it a minute to turn off, after which time I powered it down manually. When I restarted my PC, it could not longer detect my SSD which had Windows installed, but could detect my HDD.

I've installed Windows onto my HDD now, but I still can't see my SSD in the Bios, under Device Manager etc.

It seems to me that this confirms that it's a hardware fault, most likely the PSU.

Thoughts?

Was the SSD the drive you installed last week? I would be pointing a very big fat finger at that . Try removing the data and power cable to the SSD and see if the computer returns to normal. Bad drives can lock machines up and cause all kinds of weird issues. That fact you cannot see it in the bios or device manager is I suspect because it just died.
You need to RMA it under warranty.

 

[ExodusTerminal]

SSD was installed 2 weeks ago as it arrived first.

 

[Indianatone]

SSD was installed 2 weeks ago as it arrived first.

Does your system work normally without the SSD, if so you have figured out the cause of the erratic behaviour over the last few days?

 

[ExodusTerminal]

No it's still unable to shutdown.

 

[Indianatone]

No it's still unable to shutdown.

Can you try another Power Supply? Borrow one from a friend. What is the power supply? If it is an El Cheapo Brand it may have fried your SSD. Or vice versa.

I use Enermax in my machines but Corsiar and Silverstone are also good.

 

[ExodusTerminal]

It's a Corsair.

 

[Indianatone]

It's a Corsair.

What is the model number of your power supply? How old is it?. You installed a hard drive in your computer and now it will not shut down properly. Did you install all the motherboard drivers? You have removed an SSD drive which can no longer be detected by the bios or device manager. Why did you un-install the graphics card drivers? You installed Windows on your HDD after removing SSD, did you install all the drivers for the motherboard?
Seems to me the only thing left is either a faulty power supply or motherboard which is not turning off the PSU.

 

[ExodusTerminal]

PSU is a 650w TX2. It's also 2 weeks old.

I installed every motherboard driver I could find since Airlock does not bundle them altogether for some reason.

I uninstalled the GNU drivers so I could roll them back to a previous version as suggested here.

After installing to the HDD, I once again updated every relevant driver.
I

 

[Indianatone]

PSU is a 650w TX2. It's also 2 weeks old.

I installed every motherboard driver I could find since Airlock does not bundle them altogether for some reason.

I uninstalled the GNU drivers so I could roll them back to a previous version as suggested here.

After installing to the HDD, I once again updated every relevant driver.
I

OK. Are there any yellow exclamation marks in Device Manager? You really need to try another power supply at this point to rule that out. Are there any bios updates for your motherboard? If it is still the same after another power supply it can only be the power down signal from the motherboard is missing (or of course if the PSU is bad it has been ignoring the command).
It is certainly a peculiar problem that is for sure. But that is why you are here!