Event 7031 System Control Manager

Hi,

Thank you for posting in Microsoft Community

A quick question before we proceed.
-Are you facing any error/issue?

It is generated by the Service Control Manager when it detects that a specific service terminated ungracefully.

Please refer article for more information.

http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows+Operating+System&ProdVer=5.2&EvtID=7031&EvtSrc=Service+Control+Manager

Reply with necessary information and I’ll be happy to help you further.

Thank you.

I'd like to add some more information on this problem.

First of all, the errors occur at Windows shutdown or restart not at Windows startup.  This can be ascertained by starting Windows and then doing a restart after about 5 minutes.  When Windows comes back checking the Event Log will show the time stamps for these errors to have occurred when you shutdown/restarted not when you came back up.  In addition to the 4 services mentioned I have the same error with the VMware Workstation Service.

If you do a sc query on all these services they all say they ACCEPTS_PRESHUTDOWN which I think might be a factor in the problem.  Here is the output of one of the services:

C:\Windows\system32>sc query UserDataSvc_Session1

SERVICE_NAME: UserDataSvc_Session1
        TYPE               : e0  USER_SHARE_PROCESS INSTANCE
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_PRESHUTDOWN)  ** My Bold
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

My guess is that when you shutdown or restart Windows these services are ended and because of the ACCEPTS_PRESHUTDOWN option the service tries to restart itself.  Of course it can't because you are shutting down.  The question remains why does it give the error message and why does it want to restart when the system is shutting down?

Seeing that the error happens at shutdown makes it less of a concern than if the error happened at startup IMO.  The fault might lie in the services and/or the way they are defined in the Registry.  Also, you can't rule out the Shutdown procedure.

Btw... Other than the VMware service, the others don't appear when you run service.msc.  You can see them in task manager under the services tab and of course in the Registry.

Hope this added info helps to find a solution to this problem.

Can i also say that these services do not appear in my "Services.msc" screen.

As the event viewer entry states to "restart the service" as its not listed in Services to be able to do this.

it would be nice for a response.

Keep in mind that these are 'hidden services'  You can see them in task manger under the services tab.  Again let me repeat. These messages are generated when you shutdown or restart Windows.  Of course everything ends during this time.  The question is why are these services trying to restart themselves at shutdown/restart when they obviously can't or shouldn't.

Their properties show that they are supposed to restart if stopped unexpectedly, but not at shutdown IMO.  This makes no sense to me.  I really don't think this is causing any problems whatsoever because you are shutting them down when Windows is shutting down.  If it happened at startup then that may be a problem.

Either the services are setup incorrectly or the shutdown function is not acting correctly for these services.  Shutdown should end them without them trying to restart.

******* And where has MS been on this issue?  I've seen it on every Windows 10 machine I've come across.  Even a Windows 10 VM with just the OS on it creates these messages. *****

Okay solved the sync_host by disabling the service using regedit(see below), but still have the User data access, user data storage and contact data session errors.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OneSyncSvc]

change the value for "Start" to 4 (original is 2)
This will disable the service and no more errors
We can turn it back on when there is a fix!

"Had to do this using regedit as the service is not listed in services"