Related

Basecamp crashes when I plug in my handset 4.5.1

Former Member
Former Member over 9 years ago
Just once I'd like to plan a trip without consulting this forum due to crashes :mad:

Basically I can start up basecamp fine as long as my GPS unit (etrex 20) is not plugged in. The crash occurs about 20 seconds after plugging in my unit - "basecamp has stopped working" (as if it ever worked). This has been happening to me for several versions of basecamp & I'm surprised to see that it's not fixed yet. Many hours of editing/deleting .txt files got me a fix on a previous version of basecamp on this same computer but I can't remember what I did. With the new update the problem is back again.

With the Etrex usb setting set to garmin mode it will read the GPS clean and not crash but I can not transfer date. In mass storage mode basecamp will crash before it loads up and displays data from the handset. What else didn't work? Uninstall/re-install of basecamp. Removing the GPX folder from the etrex. Banging head against the nearest hard surface. So does anyone have ideas for a fix? The etrex firmware is up to date as are all drivers and software on the computer.

Problem signature:
Problem Event Name: BEX
Application Name: BaseCamp.exe
Application Version: 4.5.1.1
Application Timestamp: 55ce7179
Fault Module Name: BaseCamp.exe
Fault Module Version: 4.5.1.1
Fault Module Timestamp: 55ce7179
Exception Offset: 00a50758
Exception Code: c0000409
Exception Data: 00000000
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 7331
Additional Information 2: 7331169974f8cc38b358643b720b4dea
Additional Information 3: 4cf7
Additional Information 4: 4cf7ca5bac07266ba1e2d6b80641845a

Other annoyances include not being able to use the micro SD TOPO maps I paid for in the basecamp software without having the GPS unit plugged in and transferring the authority from the micro SD card to the computer. Obviously that (glitch?) makes using basecamp virtually impossible when combined with this crash.
  • 0 over 9 years ago
    First Basecamp has always worked perfectly well with my Etrex20 so the issue must be with your system somewhere.

    Second you can arrange things so you don't need your Etrex plugged in to view the maps. Either copy the map files to a virtual disk or to a card or memory stick, Basecamp will then read the files from there.
  • Former Member
    0 Former Member over 9 years ago
    I was looking for helpful suggestions, things I may not have thought of that would allow basecamp to load and interface with my etrex. The very nature of bugs is the interaction of hardware and software so your suggestion that "the issue must be with your system somewhere" is entirely useless conjecture for me and anyone else having this problem.

    But I came here because I'm interested in solving this problem. Bugs like mine date back to 2010 according to my searches. The things I've tried that pertain to previous basecamp version crashes have not worked for me this time. Once I get back from my trip (leaving the failed etrex at home) I'll try just about anything including your suggestion to mount the maps on a virtual drive to see if I can get basecamp to start up.

    As some background, I built this computer personally from all new parts and all new software - it's a mid range i5 gaming system on win 7 x64. Clean system with all available updates installed.
  • Former Member
    0 Former Member over 8 years ago
    Like a maroon trapped on a desert island called Garmin, I send this message in a bottle:

    It has been nine months from the last time I was having this problem. Since then I have rebuilt my system and re-installed windows. Basecamp still crashes when I plug in my handset. In trying to solve my problem I've found myself re-directed to this thread that I myself started. There are no other stability problems with my system, this is the only program experiencing crashes.

    As an alternative I'm attempting to load some very large GPX files into my smartphone. Hopefully this will allow me to never return to this place again.
  • 0 over 8 years ago
    Then likely an issue with your handset/cable ... if you're able to try another to see if it still crashes. No one else seems to have this issue.
  • Former Member
    0 Former Member over 8 years ago
    I know you're trying to help but sometimes the most likely problem is not the problem that's occurring. My cable is fine. I've tried every usb cable in the house and they all work equally. Also my handheld unit functions as it did from day one and works fine on other systems as well as when it's not paired with base camp on my system. Also here's a link where others circa 2013 are having the same problem https://forums.garmin.com/showthread.php?33936-Basecamp-stopped-working and here's one from this year: http://www.gpspower.net/garmin-discussions/340172-basecamp-keeps-crashing.html- I can trace the problem back further if you like. I've been having this problem for years and have tried everything obvious. What I'm looking for is a real solution, preferably one that involves editing the basecamp program files as that's how I fixed it before. Unfortunately an update killed my fix, which brings me here. The crash occurs whether or not a micro sd card is inserted in the handheld. It happens no matter the order of plugging in vs. starting the program. It happens no matter who occupies the white house.


    Problem signature:
    Problem Event Name: BEX
    Application Name: BaseCamp.exe
    Application Version: 4.6.2.0
    Application Timestamp: 56be57c5
    Fault Module Name: BaseCamp.exe
    Fault Module Version: 4.6.2.0
    Fault Module Timestamp: 56be57c5
    Exception Offset: 00ae4978
    Exception Code: c0000409
    Exception Data: 00000000
    OS Version: 6.1.7601.2.1.0.256.48
    Locale ID: 1033
    Additional Information 1: 82d0
    Additional Information 2: 82d0823dc4e0dc475c424e262b8594ae
    Additional Information 3: 8bd6
    Additional Information 4: 8bd67982fa10077c466caaac69769862

    Read our privacy statement online:
    http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt
  • 0 over 8 years ago
    Most of those crashes were being caused by a corrupted files on the device, removing them cured the issue. Some others that go back a way were resolved with a BaseCamp update. I know you don't want to accept it but the likelihood is that the problem is somewhere in your setup, I've used BC for many years and never had it crash with any device (and I have 5) connected.

    If you're convinced it's not your system then you'll probably need to wait until one of the BaseCamp developers checks in ... but that's fairly infrequent these days :(
  • Former Member
    0 Former Member over 8 years ago
    ...Also my handheld unit functions as it did from day one and works fine on other systems as well as when it's not paired with base camp on my system...


    Does your sentence above mean that you have successfully connected your handheld to BaseCamp on other systems since this problem reoccurred?

    If so, I would suggest doing a backup of your present BaseCamp data, then erasing all the data in BaseCamp and then trying to connect to your handheld. I am tending to agree with the moderator, you probably have a bad data file somewhere on the device or perhaps even in your BaseCamp library.
  • Former Member
    0 Former Member over 8 years ago
    Yea in the links I tried finding files on my etrex similar to the ones described and could not find anything.

    I noticed on my device manager my handset shows up under the "disk drives" section, where it shows up as "Garmin GARMIN Card USB device" and "Garmin GARMIN Falsh USB Device." Switching the USB mode from "Mass Storate" to "Garmin" mode has allowed me to start basecamp without crashing. The up side is that Basecamp has allowed the handset to upload tracks from a ride I did a while back. However I can't get the TOPO US 100k official map v5 (mounted to the original micro SD card) to load into BaseCamp. It doesn't happen automatically like it has in the past and I can't seem to find a way to do it manually. Changing the handset to Mass Storage mode after basecamp has loaded doesn't seem to have any effect.
  • Former Member
    0 Former Member over 8 years ago
    Does your sentence above mean that you have successfully connected your handheld to BaseCamp on other systems since this problem reoccurred?

    If so, I would suggest doing a backup of your present BaseCamp data, then erasing all the data in BaseCamp and then trying to connect to your handheld. I am tending to agree with the moderator, you probably have a bad data file somewhere on the device or perhaps even in your BaseCamp library.


    Basecamp is a fresh install on a fresh windows install so there's not a lot to delete.

    I deleted the data on the handset and it still crashes when loading the library when I plug in the handset with basecamp running (handset in mass storage mode). Is there a way to do a factory reset with the handset? I'd couple that with a uninstall/reinstall of base camp ideally.
  • 0 over 8 years ago
    Press and hold Menu and Enter (joystick) then briefly press the on/off button.

    Continue holding the Menu and Enter buttons until the question comes up: Do you really want to erase all user data?

    Select Yes, this will return the device to it's factory settings and erase all user data (but not maps).