Reagan,
Thanks for your help, unfortunately I had already done that and it's been happening ever since 2.0
I got around it by shutting the service down before I hibernate, and then starting it back up once waking up
It's kind of a work around but hey, at least it works