Shutdown Causing Reboot

krburd · 10 May 2011

I recently began having problems with my new Dell XPS 8300 running Window 7 Home Premium 64bit system automatically rebooting itself after shutdown. I spent 3 hours on phone with Dell tech support to no avail. We made sure we had the most current BIOS, he created a custom power management profile, we removed and reinstalled the network, graphics, and sound card drivers, we did several system restores dating back to times before the problem began.

This is a brand new system that has only been up and runnning for a week. Does anyone have any solutions to this problem? It seemed to begin after my most recent Windows update was installed. Dell's solution is to replace the mother board and hard drive which of course will require my having to again reinstall my own personal software.

Carolyn · 10 May 2011

Just like your computer can blue screen and reboot on startup, it can also do the same on shutdown. One thing to try would be pressing F8 while startup and entering the "Disable automatic reboot" boot sequence. That way, if you are getting a BSOD that's too quick to catch, you'll see it.

Also try this:

Download VEW by Vino Rosso http://images.malwareremoval.com/vino/VEW.exe
and save it to your desktop

Double click it to start it Note: If running Windows Vista or Windows 7 you will need to right click the file and select Run as administrator and click Continue or Allow at the User Account Control Prompt.
Click the check boxes next to Application and System located under Select log to query on the upper left

Under Select type to list on the right click the boxes next to Error and Warning Note: If running Windows Vista or Windows 7 also click the box next to Critical (not XP).

Under Number or date of events select Number of events and type 20 in the box next to 1 to 20 and click Run

Once it finishes it will display a log file in notepad
Please copy and paste its entire contents into your next reply

krburd · 10 May 2011

Thanks, Carolyn. I'm not getting the BSOD. I will attempt your suggested change this evening. One thing I did fail to mention in my post was that I added a PCI Express USB hub to my system to get addition USB ports on the back side of my system. I didn't have the shutdown problem immediately after installing it so I don't know if that would contribute to the problem or not. I'll remove it first to see if that resolves the issue. If not, I'll do the F8 sequence and see if that resolves the problem.

Carolyn · 10 May 2011

You're welcome.

I edited my post to include instructions for running VEW. Please do that in addition to my first recommendation.

krburd · 10 May 2011

Thanks for all your help.... The following is the report.

Code:

 
Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 10/05/2011 5:55:37 PM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 10/05/2011 3:58:51 AM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Cozi Express\CoziExpress.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest. Component 2: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest.
Log: 'Application' Date/Time: 10/05/2011 3:58:51 AM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Cozi Express\CoziExpress.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest. Component 2: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest.
Log: 'Application' Date/Time: 10/05/2011 3:41:21 AM
Type: Error Category: 0
Event: 5022 Source: McLogEvent
MCSCAN32 Engine Initialisation failed. Engine returned error : 3
Log: 'Application' Date/Time: 10/05/2011 3:21:06 AM
Type: Error Category: 0
Event: 11706 Source: MsiInstaller
Product: Roxio Creator 2011 -- Error 1706. An installation package for the product Roxio Creator 2011 cannot be found. Try the installation again using a valid copy of the installation package 'RCPROD.msi'.
Log: 'Application' Date/Time: 10/05/2011 3:19:44 AM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Cozi Express\CoziExpress.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.
Log: 'Application' Date/Time: 10/05/2011 3:19:44 AM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Cozi Express\CoziExpress.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.
Log: 'Application' Date/Time: 10/05/2011 2:06:17 AM
Type: Error Category: 0
Event: 5022 Source: McLogEvent
MCSCAN32 Engine Initialisation failed. Engine returned error : 3
Log: 'Application' Date/Time: 10/05/2011 1:57:06 AM
Type: Error Category: 0
Event: 5022 Source: McLogEvent
MCSCAN32 Engine Initialisation failed. Engine returned error : 3
Log: 'Application' Date/Time: 10/05/2011 1:46:45 AM
Type: Error Category: 0
Event: 5022 Source: McLogEvent
MCSCAN32 Engine Initialisation failed. Engine returned error : 3
Log: 'Application' Date/Time: 10/05/2011 1:42:15 AM
Type: Error Category: 0
Event: 5022 Source: McLogEvent
MCSCAN32 Engine Initialisation failed. Engine returned error : 3
Log: 'Application' Date/Time: 10/05/2011 12:44:56 AM
Type: Error Category: 0
Event: 5022 Source: McLogEvent
MCSCAN32 Engine Initialisation failed. Engine returned error : 3
Log: 'Application' Date/Time: 10/05/2011 12:40:04 AM
Type: Error Category: 0
Event: 2004 Source: Microsoft-Windows-PerfNet
Unable to open the Server service performance object. The first four bytes (DWORD) of the Data section contains the status code.
Log: 'Application' Date/Time: 10/05/2011 12:09:18 AM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Cozi Express\CoziExpress.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest. Component 2: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest.
Log: 'Application' Date/Time: 10/05/2011 12:09:18 AM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Cozi Express\CoziExpress.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest. Component 2: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest.
Log: 'Application' Date/Time: 08/05/2011 10:58:29 PM
Type: Error Category: 1
Event: 100 Source: CVHSVC
The event description cannot be found.
Log: 'Application' Date/Time: 08/05/2011 7:27:19 PM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Cozi Express\CoziExpress.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest. Component 2: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest.
Log: 'Application' Date/Time: 08/05/2011 7:27:19 PM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Cozi Express\CoziExpress.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest. Component 2: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest.
Log: 'Application' Date/Time: 08/05/2011 6:38:07 PM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Cozi Express\CoziExpress.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest. Component 2: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest.
Log: 'Application' Date/Time: 08/05/2011 6:38:07 PM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Cozi Express\CoziExpress.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest. Component 2: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest.
Log: 'Application' Date/Time: 08/05/2011 1:04:38 AM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Cozi Express\CoziExpress.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest. Component 2: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 10/05/2011 3:20:08 AM
Type: Warning Category: 0
Event: 1001 Source: MsiInstaller
Detection of product '{A12CF335-1B84-4781-9735-44E39C6D3DD0}', feature 'SoleFeature' failed during request for component '{7DEDB0E7-12F0-4FD8-8E7E-09E2CD98580E}'
Log: 'Application' Date/Time: 10/05/2011 3:20:08 AM
Type: Warning Category: 0
Event: 1004 Source: MsiInstaller
Detection of product '{A12CF335-1B84-4781-9735-44E39C6D3DD0}', feature 'SoleFeature', component '{96EF1F63-5B35-45A5-98F7-9D91982FC810}' failed. The resource 'C:\Program Files (x86)\Common Files\Roxio Shared\13.0\1033\Help\Jukebox_disc.chm' does not exist.
Log: 'Application' Date/Time: 10/05/2011 2:19:05 AM
Type: Warning Category: 0
Event: 1130 Source: .NET Runtime Optimization Service
.NET Runtime Optimization Service (2.0.50727.5444) - Version or flavor did not match with repository: Microsoft.MediaCenter.Mheg
Log: 'Application' Date/Time: 10/05/2011 2:19:03 AM
Type: Warning Category: 0
Event: 1130 Source: .NET Runtime Optimization Service
.NET Runtime Optimization Service (2.0.50727.5444) - Version or flavor did not match with repository: Microsoft.MediaCenter.Bml
Log: 'Application' Date/Time: 10/05/2011 2:18:54 AM
Type: Warning Category: 0
Event: 1130 Source: .NET Runtime Optimization Service
.NET Runtime Optimization Service (2.0.50727.5444) - Version or flavor did not match with repository: mcupdate
Log: 'Application' Date/Time: 10/05/2011 2:18:53 AM
Type: Warning Category: 0
Event: 1130 Source: .NET Runtime Optimization Service
.NET Runtime Optimization Service (2.0.50727.5444) - Version or flavor did not match with repository: mcplayerinterop
Log: 'Application' Date/Time: 10/05/2011 2:18:52 AM
Type: Warning Category: 0
Event: 1130 Source: .NET Runtime Optimization Service
.NET Runtime Optimization Service (2.0.50727.5444) - Version or flavor did not match with repository: mcGlidHostObj
Log: 'Application' Date/Time: 10/05/2011 2:18:52 AM
Type: Warning Category: 0
Event: 1130 Source: .NET Runtime Optimization Service
.NET Runtime Optimization Service (2.0.50727.5444) - Version or flavor did not match with repository: MCESidebarCtrl
Log: 'Application' Date/Time: 10/05/2011 2:18:51 AM
Type: Warning Category: 0
Event: 1130 Source: .NET Runtime Optimization Service
.NET Runtime Optimization Service (2.0.50727.5444) - Version or flavor did not match with repository: LoadMxf
Log: 'Application' Date/Time: 10/05/2011 2:18:46 AM
Type: Warning Category: 0
Event: 1130 Source: .NET Runtime Optimization Service
.NET Runtime Optimization Service (2.0.50727.5444) - Version or flavor did not match with repository: Microsoft.MediaCenter.iTv.Media
Log: 'Application' Date/Time: 10/05/2011 2:18:45 AM
Type: Warning Category: 0
Event: 1130 Source: .NET Runtime Optimization Service
.NET Runtime Optimization Service (2.0.50727.5444) - Version or flavor did not match with repository: Microsoft.MediaCenter.iTv
Log: 'Application' Date/Time: 10/05/2011 2:18:45 AM
Type: Warning Category: 0
Event: 1130 Source: .NET Runtime Optimization Service
.NET Runtime Optimization Service (2.0.50727.5444) - Version or flavor did not match with repository: Mcx2Dvcs
Log: 'Application' Date/Time: 10/05/2011 2:18:29 AM
Type: Warning Category: 0
Event: 1130 Source: .NET Runtime Optimization Service
.NET Runtime Optimization Service (2.0.50727.5444) - Version or flavor did not match with repository: ehshell
Log: 'Application' Date/Time: 10/05/2011 2:18:28 AM
Type: Warning Category: 0
Event: 1130 Source: .NET Runtime Optimization Service
.NET Runtime Optimization Service (2.0.50727.5444) - Version or flavor did not match with repository: Microsoft.MediaCenter.Sports
Log: 'Application' Date/Time: 10/05/2011 2:18:27 AM
Type: Warning Category: 0
Event: 1130 Source: .NET Runtime Optimization Service
.NET Runtime Optimization Service (2.0.50727.5444) - Version or flavor did not match with repository: Microsoft.MediaCenter.TV.Tuners.Interop
Log: 'Application' Date/Time: 10/05/2011 2:18:27 AM
Type: Warning Category: 0
Event: 1130 Source: .NET Runtime Optimization Service
.NET Runtime Optimization Service (2.0.50727.5444) - Version or flavor did not match with repository: Microsoft.MediaCenter.Playback
Log: 'Application' Date/Time: 10/05/2011 2:18:27 AM
Type: Warning Category: 0
Event: 1130 Source: .NET Runtime Optimization Service
.NET Runtime Optimization Service (2.0.50727.5444) - Version or flavor did not match with repository: Microsoft.MediaCenter.ITVVM
Log: 'Application' Date/Time: 10/05/2011 2:18:26 AM
Type: Warning Category: 0
Event: 1130 Source: .NET Runtime Optimization Service
.NET Runtime Optimization Service (2.0.50727.5444) - Version or flavor did not match with repository: Microsoft.MediaCenter.Interop
Log: 'Application' Date/Time: 10/05/2011 2:18:25 AM
Type: Warning Category: 0
Event: 1130 Source: .NET Runtime Optimization Service
.NET Runtime Optimization Service (2.0.50727.5444) - Version or flavor did not match with repository: Microsoft.MediaCenter.Shell
Log: 'Application' Date/Time: 10/05/2011 2:18:24 AM
Type: Warning Category: 0
Event: 1130 Source: .NET Runtime Optimization Service
.NET Runtime Optimization Service (2.0.50727.5444) - Version or flavor did not match with repository: ehiWUapi
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 10/05/2011 3:38:41 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 10/05/2011 9:44:07 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The dleeCATSCustConnectService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Log: 'System' Date/Time: 10/05/2011 9:44:07 PM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the dleeCATSCustConnectService service to connect.
Log: 'System' Date/Time: 10/05/2011 9:40:09 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The dleeCATSCustConnectService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Log: 'System' Date/Time: 10/05/2011 9:40:09 PM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the dleeCATSCustConnectService service to connect.
Log: 'System' Date/Time: 10/05/2011 9:37:28 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The dleeCATSCustConnectService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Log: 'System' Date/Time: 10/05/2011 9:37:28 PM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the dleeCATSCustConnectService service to connect.
Log: 'System' Date/Time: 10/05/2011 9:27:06 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The dleeCATSCustConnectService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Log: 'System' Date/Time: 10/05/2011 9:27:06 PM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the dleeCATSCustConnectService service to connect.
Log: 'System' Date/Time: 10/05/2011 3:39:03 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The dleeCATSCustConnectService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Log: 'System' Date/Time: 10/05/2011 3:39:03 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the dleeCATSCustConnectService service to connect.
Log: 'System' Date/Time: 10/05/2011 2:02:46 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The dleeCATSCustConnectService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Log: 'System' Date/Time: 10/05/2011 2:02:46 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the dleeCATSCustConnectService service to connect.
Log: 'System' Date/Time: 10/05/2011 2:01:14 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {F32D97DF-E3E5-4CB9-9E3E-0EB5B4E49801} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 10/05/2011 1:54:57 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The dleeCATSCustConnectService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Log: 'System' Date/Time: 10/05/2011 1:54:57 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the dleeCATSCustConnectService service to connect.
Log: 'System' Date/Time: 10/05/2011 1:44:37 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The dleeCATSCustConnectService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Log: 'System' Date/Time: 10/05/2011 1:44:37 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the dleeCATSCustConnectService service to connect.
Log: 'System' Date/Time: 10/05/2011 1:39:55 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The dleeCATSCustConnectService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Log: 'System' Date/Time: 10/05/2011 1:39:55 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the dleeCATSCustConnectService service to connect.
Log: 'System' Date/Time: 10/05/2011 1:39:53 AM
Type: Error Category: 0
Event: 7024 Source: Service Control Manager
The Windows Firewall service terminated with service-specific error Access is denied..
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 10/05/2011 9:43:12 PM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped. 
Log: 'System' Date/Time: 10/05/2011 9:43:12 PM
Type: Warning Category: 0
Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has stopped. Module Path: C:\Windows\System32\bcmihvsrv64.dll 
Log: 'System' Date/Time: 10/05/2011 9:39:00 PM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped. 
Log: 'System' Date/Time: 10/05/2011 9:39:00 PM
Type: Warning Category: 0
Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has stopped. Module Path: C:\Windows\System32\bcmihvsrv64.dll 
Log: 'System' Date/Time: 10/05/2011 9:31:24 PM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped. 
Log: 'System' Date/Time: 10/05/2011 9:31:24 PM
Type: Warning Category: 0
Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has stopped. Module Path: C:\Windows\System32\bcmihvsrv64.dll 
Log: 'System' Date/Time: 10/05/2011 4:04:26 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped. 
Log: 'System' Date/Time: 10/05/2011 4:04:26 AM
Type: Warning Category: 0
Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has stopped. Module Path: C:\Windows\System32\bcmihvsrv64.dll 
Log: 'System' Date/Time: 10/05/2011 3:21:48 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped. 
Log: 'System' Date/Time: 10/05/2011 3:21:48 AM
Type: Warning Category: 0
Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has stopped. Module Path: C:\Windows\System32\bcmihvsrv64.dll 
Log: 'System' Date/Time: 10/05/2011 2:01:21 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped. 
Log: 'System' Date/Time: 10/05/2011 2:01:21 AM
Type: Warning Category: 0
Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has stopped. Module Path: C:\Windows\System32\bcmihvsrv64.dll 
Log: 'System' Date/Time: 10/05/2011 1:58:42 AM
Type: Warning Category: 0
Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has stopped. Module Path: C:\Windows\System32\bcmihvsrv64.dll 
Log: 'System' Date/Time: 10/05/2011 1:57:36 AM
Type: Warning Category: 0
Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has stopped. Module Path: C:\Windows\System32\bcmihvsrv64.dll 
Log: 'System' Date/Time: 10/05/2011 1:53:58 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped. 
Log: 'System' Date/Time: 10/05/2011 1:53:58 AM
Type: Warning Category: 0
Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has stopped. Module Path: C:\Windows\System32\bcmihvsrv64.dll 
Log: 'System' Date/Time: 10/05/2011 1:43:37 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped. 
Log: 'System' Date/Time: 10/05/2011 1:43:37 AM
Type: Warning Category: 0
Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has stopped. Module Path: C:\Windows\System32\bcmihvsrv64.dll 
Log: 'System' Date/Time: 10/05/2011 1:32:00 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped. 
Log: 'System' Date/Time: 10/05/2011 1:23:27 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.

krburd · 10 May 2011

p.s. I also followed your instrustions regarding f8 and disable auto reboot. That didn't fix the problem. I also did the same in the startup and recovery area under the system icon.

Gator88 · 08 Jun 2011

I am having the exact same problem on my Dell XPS 8300 after putting in a PCIe USB expansion card! Dell needs to get on this problem!

I was trying to install aRosewill RC-503, 4+1 ports USB 2.0 card purchased from Newegg. What card was krburd trying to install?

iautom8u · 12 Jun 2011

I have/had the exact same problem with my new Dell XPS 8300 running Window 7 Home Premium 64bit. After installing a PCIe USB expansion card I had the shut down loop. Removed the card and problem gone. Mine was a Belkin card from Newegg.

uveith · 19 Aug 2011

I just had the same issue. After several attempts with boot options I decided finally to send it into sleep mode twice. after that the system shuts down normally - I think remembering that I had a similar issue on an older system a couple of months/years ago.

gregrocker · 19 Aug 2011

Look for repeat errors in Performance log: troubleshooting steps