I do not think this is a registry or installation problem.
Usually the "memory cannot be read" is an error that cannot be changed into a
VB error, and therefore cannot be trapped, and it is caused by a component that is not written in
VB, or a bad call to a Windows API.
Things to look for: because the problem is on exiting the application, look for all the allocated resources, all API calls, third party components, database connections, etc. The problem is not in the Unload code: when the app exits, under the scenes
VB tries to deallocate all resources, close file handles and database connections, disconnect to server atc. It is not easy to find. Usually what I do is to remove (or commenting out) parts of code, one oer time, until the error disappear
Good luck,
Marco