The "crashing" of PingPlotter isn't a known problem. Running as a service does require the /console switch, so maybe you're doing that? See here for details: http://www.nessoft.com/kb/59

If PingPlotter is closing when running as an application, is it possible that you have your terminal services server set up to log off (and close the session) rather than leave it running? If the console session gets closed, then all running applications (for that session) get closed too.

You say "crash", so I'm guessing that you're seeing some message / something that shows a crash. If there's any kind of error message, we'd love to see details about that. The pp_error_details.txt file in the PingPlotter Pro directory should be capturing more details of any error message - you can send that to support@pingplotter.com and we can take a look.

- Pete