OWSTIMER.EXE Crashing

The OWSTIMER.EXE can crash when the SharePoint services or service application configuration is corrupted. This can happen during patch installation and server configuration updates. When OWSTIMER.EXE crashes, you will notice error messages in the event log and SharePoint logs such as:

• “The SharePoint 2010 Timer service terminated unexpectedly.  It has done this XXX time(s).  The following corrective action will be taken in 30000 milliseconds: Restart the service.”
• Failed to open the file 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Resources\XXXXXX.en-US.resx'.
• <nativehr>0x8000ffff</nativehr><nativestack></nativestack>
• SharePoint Web Services Round Robin Service Load Balancer Event: Initialization Process Name: OWSTIMER
• Various round robin endpoint failures for SharePoint services

You can try the following to correct this issue:

• Make sure that the appropriate services are started on the frontend and application server.
• Make sure that an antivirus is configured properly on the SharePoint servers and it is not causing the OWSTIMER.EXE to crash.
• Make sure that the domain account running the services and service application is valid and has a correct password.
• Reset IIS
• On the central administration server, re-provision the service applications by issuing the following command:
  
  Get-SPServiceApplication | ForEach-Object {$_.Provision()}
  
• Restart the application and frontend servers.
• Run the SharePoint Configuration Wizard on all the servers.

Hope that helps!