I have had all of these issues on both of my Win7 64 machines. Occasionally the only way to kill the 100% one is to kill the process in the task manager. Like you, 8 out of 10 times I get some sort of imporper behavior. The database error is much more annoying to a point I tried uninstalling and reinstalling PEP2. I can even make it happen on a clean install with the Level3_template file from Philips. It is fairly random, but when it happens the only way to get it to work again is a reboot. Restarting the ProntoDataService makes it appear normal, but then it doesn't write any changes I make to the database. I haven't sent anything to Philips yet as I am trying to find a consistent path to make it fail.