Seem like a permission problems, the pid change is probably due to the services failing to launch properly and retry to launch it again. Check if the services can log anything and see what is happening there, inside the Windows Computer management application, you can enable the services log. Also check the log of Jenkins itself.
Make sure the Jenkins folder and workspace are available to the wanted user into folder permissions. Another thing to consider, the services tools into Windows will have hard time to access GUI context, so if you run tests that run GUI elements, you may want to run the services as a logable user to have the proper context.
Take care with network map drive, if any are used, services doesn't see them as user does.
NOTE mounting Windows drive for services:
Jerome