Streets & Trips 2009 Closes Unexpectedly

I have S&T 2009 on two computers; the program on my Vista Basic netbook closes occasionally without any obvious cause. It closes without saving or offering to save the current .est file I'm working on. I've looked closely at the Event Viewer, and the only S&T-related event is the following. This event, however, does not always coincide with a closure, so I'm not sure if it's related.

This closure seems different from the other crash problems I've read about in this forum. I've re-installed twice, and have no add-ons. Also, my desktop (Vista HP) shows these same events but has never had the same issue.

Does anyone have any ideas how to troubleshoot these incidents?

Log Name: Application
Source: RouteService
Date: 23-Nov-08 1:49:00 PM
Event ID: 11013
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Mini-Note
Description:
The description for Event ID 11013 from source RouteService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Successfully loaded MapPoint construction file.

I have S&T 2009 and this crash type occurs once a week: Blue screen, memory dump code. The OS restarts automatically and because I have a shortcut in my program startup folder so does the program. I also get a Send Error to Microsoft. I don't bother sending since when this occurs, I'm on the road and have no connectivity. Fortunately, I always save my route so all I have to do is reload. I also do a Save As to overwrite the saved route just in case there is any corruption.

That said, I had S&T 2007 and had no problems with it. Ever since I installed 2009, there has been a collection of issues that MS seems to know about but does nothing to reassure the clients. Customer service doesn't seem to be a high priority regarding bugs.

I am not pleased or impressed with the latest offering. They will probably fix this in the next year. That doesn't make me want to continue supporting Microsoft's bottom line if they can't (won't) support the version that suffers form poor craftsmanship.

I realize that my tone isn't very charitable but if I buy any other product, I expect that it works as designed and if there are issues they are resolved without additional cost to the customer. If the users continue to purchase and remain quiet about the issues then MS continues to play us for fools.

System: Intel Core 2 Duo 2.6Ghz, XP Pro, 4gb memory,, 250GB HD. Very little software other than S&T.