PDA

View Full Version : PC restarts on shutdown



Filthygamer
14-01-2016, 02:48 PM
Hi there,

Wee conundrum with my friend's new PC he built.

Everytime he goes to shut it down, the PC powers off for a second or two, and then reboots itself. We've turned off every WOL or other sleep affecting power setting we could find, both in Windows and the BIOS, to no avail. Tried disabling the component through device manager, and fiddling around with those settings, nothing worked. Even tried booting into Linux via USB and that won't shut down properly either.

Taking out the network card seems to fix the issue, and yet when we put it into my own rig it was fine. Putting my own card into his PC works as well, however his own card doesn't play nice with his own PC and we've run out of ideas as to what could be causing it!

Parts list of friends build: http://nz.pcpartpicker.com/p/dN6pf7

Any suggestions would be appreciated! It's driving him nuts!

wratterus
14-01-2016, 03:10 PM
Are you sure that it's not BSODing on shutdown then rebooting? You can check the event logs and see what it's doing during the shutdown process, incase anything there looks suspect.

Speedy Gonzales
14-01-2016, 03:10 PM
Looks like the restarting can happen if a pin is bent on the CPU. I would remove it and check the CPU or the socket

Filthygamer
14-01-2016, 03:25 PM
Thanks for your replies. We've already disabled that setting that tells the PC to restart on a BSOD or power loss, didn't work. Don't thiiink it would be the CPU, but if worse comes to worse will remove and reinstall. Odd that the PC shuts down fine without the network card though (or with another network card, for that matter).

Here's the relevant info from event viewer if it helps:


Level Date and Time Source Event ID Task Category
Warning 14/01/2016 2:43:14 PM e1dexpress 27 None "Intel(R) Ethernet Connection (2) I219-V
Network link is disconnected.
"
Information 14/01/2016 2:43:14 PM Microsoft-Windows-WLAN-AutoConfig 10001 None "WLAN Extensibility Module has successfully started.

Module Path: C:\Windows\System32\IWMSSvc.dll
"
Information 14/01/2016 2:43:13 PM Microsoft-Windows-Winlogon 7001 (1101) User Logon Notification for Customer Experience Improvement Program
Information 14/01/2016 2:43:13 PM Service Control Manager 7045 None "A service was installed in the system.

Service Name: Nal Service
Service File Name: C:\Windows\system32\Drivers\iqvw64e.sys
Service Type: kernel mode driver
Service Start Type: demand start
Service Account: "
Information 14/01/2016 2:43:13 PM Service Control Manager 7026 None "The following boot-start or system-start driver(s) did not load:
cdrom
dam"
Information 14/01/2016 2:43:12 PM Microsoft-Windows-WLAN-AutoConfig 4000 None "WLAN AutoConfig service has successfully started.
"
Information 14/01/2016 2:43:12 PM Microsoft-Windows-DHCPv6-Client 51046 Service State Event DHCPv6 client service is started
Information 14/01/2016 2:43:12 PM Microsoft-Windows-Dhcp-Client 50036 Service State Event DHCPv4 client service is started
Information 14/01/2016 2:43:12 PM Microsoft-Windows-FilterManager 6 None File System Filter 'storqosflt' (10.0, ‎2015‎-‎10‎-‎30T15:37:39.000000000Z) has successfully loaded and registered with Filter Manager.
Information 14/01/2016 2:43:12 PM Microsoft-Windows-FilterManager 6 None File System Filter 'luafv' (10.0, ‎2015‎-‎10‎-‎30T15:34:43.000000000Z) has successfully loaded and registered with Filter Manager.
Information 14/01/2016 2:43:12 PM Microsoft-Windows-Wininit 14 None Credential Guard (LsaIso.exe) configuration: 0x0, 0
Information 14/01/2016 2:43:10 PM Microsoft-Windows-Ntfs 98 None Volume \\?\Volume{9fa5808d-0000-0000-0000-100000000000} (\Device\HarddiskVolume2) is healthy. No action is needed.
Information 14/01/2016 2:43:10 PM Microsoft-Windows-Ntfs 98 None Volume E: (\Device\HarddiskVolume1) is healthy. No action is needed.
Information 14/01/2016 2:43:09 PM Microsoft-Windows-Ntfs 98 None Volume D: (\Device\HarddiskVolume5) is healthy. No action is needed.
Information 14/01/2016 2:43:08 PM MEIx64 2 None Intel(R) Management Engine Interface driver has started successfully.
Information 14/01/2016 2:43:08 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 3 in group 0 exposes the following power management capabilities:

Idle state type: ACPI Idle (C) States (3 state(s))

Performance state type: ACPI Performance (P) / Throttle (T) States
Nominal Frequency (MHz): 3501
Maximum performance percentage: 100
Minimum performance percentage: 22
Minimum throttle percentage: 22"
Information 14/01/2016 2:43:08 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 2 in group 0 exposes the following power management capabilities:

Idle state type: ACPI Idle (C) States (3 state(s))

Performance state type: ACPI Performance (P) / Throttle (T) States
Nominal Frequency (MHz): 3501
Maximum performance percentage: 100
Minimum performance percentage: 22
Minimum throttle percentage: 22"
Information 14/01/2016 2:43:08 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 1 in group 0 exposes the following power management capabilities:

Idle state type: ACPI Idle (C) States (3 state(s))

Performance state type: ACPI Performance (P) / Throttle (T) States
Nominal Frequency (MHz): 3501
Maximum performance percentage: 100
Minimum performance percentage: 22
Minimum throttle percentage: 22"
Information 14/01/2016 2:43:08 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 0 in group 0 exposes the following power management capabilities:

Idle state type: ACPI Idle (C) States (3 state(s))

Performance state type: ACPI Performance (P) / Throttle (T) States
Nominal Frequency (MHz): 3501
Maximum performance percentage: 100
Minimum performance percentage: 22
Minimum throttle percentage: 22"
Information 14/01/2016 2:43:08 PM NETwNb64 7036 None The \Device\NDMP1 service entered the Intel(R) Dual Band Wireless-AC 7260 #2 state.
Information 14/01/2016 2:43:07 PM Microsoft-Windows-FilterManager 6 None File System Filter 'npsvctrig' (10.0, ‎2015‎-‎10‎-‎30T15:40:23.000000000Z) has successfully loaded and registered with Filter Manager.
Information 14/01/2016 2:43:05 PM Microsoft-Windows-FilterManager 6 None File System Filter 'FileCrypt' (10.0, ‎2015‎-‎10‎-‎30T15:37:49.000000000Z) has successfully loaded and registered with Filter Manager.
Information 14/01/2016 2:43:05 PM Microsoft-Windows-Ntfs 98 None Volume C: (\Device\HarddiskVolume3) is healthy. No action is needed.
Information 14/01/2016 2:43:05 PM Microsoft-Windows-FilterManager 6 None File System Filter 'Avgmfx64' (6.2, ‎2015‎-‎11‎-‎07T03:49:34.000000000Z) has successfully loaded and registered with Filter Manager.
Information 14/01/2016 2:43:05 PM Microsoft-Windows-FilterManager 6 None File System Filter 'Wof' (10.0, ‎2015‎-‎10‎-‎30T15:38:16.000000000Z) has successfully loaded and registered with Filter Manager.
Information 14/01/2016 2:43:05 PM Microsoft-Windows-FilterManager 6 None File System Filter 'FileInfo' (10.0, ‎2015‎-‎10‎-‎30T15:37:17.000000000Z) has successfully loaded and registered with Filter Manager.
Information 14/01/2016 2:43:04 PM Microsoft-Windows-Kernel-Boot 30 None The firmware reported boot metrics.
Information 14/01/2016 2:43:04 PM Microsoft-Windows-Kernel-Boot 32 None The bootmgr spent 0 ms waiting for user input.
Information 14/01/2016 2:43:04 PM Microsoft-Windows-Kernel-Boot 18 None There are 0x1 boot options on this system.
Information 14/01/2016 2:43:04 PM Microsoft-Windows-Kernel-Boot 25 None The boot menu policy was 0x1.
Information 14/01/2016 2:43:04 PM Microsoft-Windows-Kernel-Boot 27 None The boot type was 0x0.
Information 14/01/2016 2:43:04 PM Microsoft-Windows-Kernel-Boot 20 None The last shutdown's success status was true. The last boot's success status was true.
Information 14/01/2016 2:43:04 PM Microsoft-Windows-Kernel-General 12 None The operating system started at system time ‎2016‎-‎01‎-‎14T01:43:04.499071600Z.
Information 14/01/2016 2:42:46 PM Microsoft-Windows-Kernel-General 13 None The operating system is shutting down at system time ‎2016‎-‎01‎-‎14T01:42:46.512553200Z.
Information 14/01/2016 2:42:46 PM Microsoft-Windows-Kernel-Power 109 (103) "The kernel power manager has initiated a shutdown transition.

Shutdown Reason: Kernel API"
Information 14/01/2016 2:42:46 PM Microsoft-Windows-Kernel-Power 109 (103) "The kernel power manager has initiated a shutdown transition.

Shutdown Reason: Kernel API"
Information 14/01/2016 2:42:41 PM Microsoft-Windows-WLAN-AutoConfig 4001 None "WLAN AutoConfig service has successfully stopped.
"
Warning 14/01/2016 2:42:41 PM Microsoft-Windows-WLAN-AutoConfig 10002 None "WLAN Extensibility Module has stopped.

Module Path: C:\Windows\System32\IWMSSvc.dll
"
Information 14/01/2016 2:43:12 PM EventLog 6013 None The system uptime is 8 seconds.
Information 14/01/2016 2:43:12 PM EventLog 6005 None The Event log service was started.
Information 14/01/2016 2:43:12 PM EventLog 6009 None Microsoft (R) Windows (R) 10.00. 10586 Multiprocessor Free.
Information 14/01/2016 2:42:41 PM Microsoft-Windows-Dhcp-Client 50037 Service State Event DHCPv4 client service is stopped. ShutDown Flag value is 1
Information 14/01/2016 2:42:41 PM Microsoft-Windows-DHCPv6-Client 51047 Service State Event DHCPv6 client service is stopped. ShutDown Flag value is 1
Information 14/01/2016 2:42:41 PM EventLog 6006 None The Event log service was stopped.
Information 14/01/2016 2:42:34 PM Microsoft-Windows-Winlogon 7002 (1102) User Logoff Notification for Customer Experience Improvement Program
Error 14/01/2016 2:42:33 PM Service Control Manager 7031 None The User Data Access_35cc1 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.
Error 14/01/2016 2:42:33 PM Service Control Manager 7031 None The User Data Storage_35cc1 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.
Error 14/01/2016 2:42:33 PM Service Control Manager 7031 None The Contact Data_35cc1 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.
Error 14/01/2016 2:42:33 PM Service Control Manager 7031 None The Sync Host_35cc1 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.
Error 14/01/2016 2:42:33 PM Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."
Information 14/01/2016 2:42:33 PM User32 1074 None "The process C:\Windows\Explorer.EXE (TOMDESKTOP) has initiated the power off of computer TOMDESKTOP on behalf of user TOMDESKTOP\Andrew for the following reason: Other (Unplanned)
Reason Code: 0x0
Shutdown Type: power off
Comment: "

dugimodo
14-01-2016, 03:35 PM
Are you sure it's being shut down and not just put into standby? I've had a few PC's over the years that just refuse to stay asleep and have always ended up just not using the standby feature.
Apart from the WOL setting it can often be caused by a USB device such as a mouse or keyboard, there are many places you can attempt to disable this. The BIOS may have a setting, the power management settings can have a setting, and the device driver may have an "allow this device to wake the computer" setting (might be able to do that for the network card as well). Check the scheduler as well to make sure there are no scheduled tasks that might be waking it.

If it's an actual shutdown then nothing short of the power button should be starting it and there may be a hardware issue.

Driftwood
14-01-2016, 04:50 PM
"Taking out the network card seems to fix the issue, and yet when we put it into my own rig it was fine. Putting my own card into his PC works as well, however his own card doesn't play nice with his own PC and we've run out of ideas as to what could be causing it"

Could be a clue here?

wainuitech
14-01-2016, 06:03 PM
Sounds like the wireless card is still using WOL somehow.

Check this --- Go to device manager, network adapter, your wireless network card...right click, proprieties , power managment. Check if "allow this device to wake up computer from standby mode" if its enabled- disable it.

Since its doing it on both windows and Linux that rules out the Windows install as the main cause.

Filthygamer
14-01-2016, 09:54 PM
"Taking out the network card seems to fix the issue, and yet when we put it into my own rig it was fine. Putting my own card into his PC works as well, however his own card doesn't play nice with his own PC and we've run out of ideas as to what could be causing it"

Could be a clue here?

Not quite sure what you mean here? We've established that that network card is the issue, so could it just be a faulty card that needs returning?

Thanks everyone for your replies. Have turned off the device manager power setting which still didn't fix it. Have also tried shutting down the PC with the power button physically disconnected from mobo, still restarted! There's got to be a WOL setting somewhere that we've missed, can't find anything in the BIOS which suggests that it is though - have turned off all the USB wake and WOL settings in there that could be found. Can't imagine the power supply would be at fault either, the build comes well under 550W.

Might have to RMA the card and see if a new one fixes it.

wainuitech
14-01-2016, 10:09 PM
It can also be a Power Supply Or a fault on the motherboard or the card shorting somewhere - have you tried a different PCI slot ?.


Taking out the network card seems to fix the issue, and yet when we put it into my own rig it was fine.

It "may" be the card but you would expect it to play up and repeat the same problem on your computer, which you says it doesn't.

One test you can try -- Go into the device manager again, right click the card, and DISABLE it. See what happens.

Welcome to the world of fault finding :)

I had a PC that wouldn't shutdown years ago, its problem was a faulty case, something about the case was causing it. Only after totally removing all the components assembling on the workbench and testing out of the case found the problem.

linw
16-01-2016, 09:33 AM
And sometimes it is just a matter of holding your mouth right! Never had a faulty case yet, WT!! I await that one with anticipation - not.

Interesting and frustrating problem. Hope something 'clicks' soon.

wainuitech
16-01-2016, 12:59 PM
And sometimes it is just a matter of holding your mouth right! Never had a faulty case yet, WT!! I await that one with anticipation - not.

Interesting and frustrating problem. Hope something 'clicks' soon. The faulty case that was causing the problem, it was a problem when everything was tightened it would put a slight twist in the case, causing the Motherboard to short.

Had a Silverstone case last year, went to slide in the HDD, and WTF !! the bay was riveted incorrectly, on one side the machine must have been having a bad day as the tray was on a angle skipping the bottom connection points and was actually riveted a whole bay higher. Drilled out the rivets on one side, riveted it back where it was meant to be and it was fine.

linw
18-01-2016, 09:58 AM
I also remember the olden days when you only used three screws to hold disk drives to avoid distorting the drive!