We have identified an issue in BaseCamp where the application may crash when displaying Garmin Custom Maps that contain very large images. This issue can be identified by the mention of WIN_BADALLOCATION.CPP in the error information displayed. We are working on a solution to this issue for inclusion in future releases. Until this is available, it is possible to avoid the problem by deleting the problematic Custom Map.
Unfortunately, in most cases when this occurs, it will happen repeatedly when the application restarts. Because BaseCamp starts with the map positioned in the same place as when the application was last closed, it will encounter the same problem each time it restarts. This prevents deleting the Custom Map.
If you are comfortable editing the system registry, this can be avoided by deleting the saved map positions. These settings are saved in the system registry in the key located at:
HKEY_CURRENT_USER\Software\Garmin\BaseCamp\Settings\Products
Deleting this key (and all subkeys) will cause BaseCamp to start with a default map position, allowing you to delete the problematic Custom Map.