Data could not be received because Current.GPX is invalid.

I am still trying to figure it out but I starting to think that my zumo (and the 2 I exchanged) have a problem always seeing the SD card which causes multiple different problems.

1) Most notable is that I would have to reboot so the zumo could find the SD card to use my custom POIs.

2) caused numerous shutdowns for no known reason.

3) after a shutdown one time the current.gpx was totally corrupt and the system was having such a hard time dealing with the corrupt file that it created a current1.gpx file and was using that file. Mapsource would not correctly read it or send waypoints to it. I finally loaded my backup files onto the GPS, deleted all current.gpx file and did a master reset.

Since then I moved all my custom POIs to the internal memory and haven't had any more shutdowns or quirks of anykind. I occasionally check my jpegs and every so often the Jpegs/SD card is missing. I tried a 2nd sd card from the same manufacturer with the same results. 3 zumos and 2 micro SD's all with the same problems.

I am suspecting corrupt data transfer with the custom POIs on the SD card as the cause of the shutdowns and other problems.

I bought another SD today from a different manufacturer and I'm going to start testing it tomorrow.

I use SanDisk almost exclusively, and never a problem. Kingston is crap these days.

I have an old Palm Tungsten T3 and have had the same problem with it. From time to time it won't find the SD card, sometimes a restart will correct the problem, sometimes not. I finally fixed the problem by using some contact cleaner on the SD card and then plugging it in and removing it several times while the contacts are still wet. Try this fix with your GPS but be sure to use a contact cleaner that is safe on plastics.

Both cards that keep failing were SanDisk, 8GB and a 1GB.

Bought a Laxar today. 2 Lexar 8GB sitting side by side and 1 said HIGH SPEED and cost more. Bought it.

Did you try formatting them with FAT 32?

I formatted the 1GB recently, FAT 32. I think I did the 8GB a zumo or 2 ago.

I have not tried the contact cleaner as both these cards work fine in all the different phones they've been in. I might try this next if it fails again.

Contact cleaner can melt plastic. Just use a pencil eraser...

Mav293, SD cards are not related to your issue, since the current.gpx file is located in your nuvi's internal memory.

Save a copy of the I:/Garmin/gpx/Current.GPX file the next time it happens. Then we can see what the invalid data is that causes the Mapsource error. You could email it to me (waasup at rogers dot com) if you need help. Or you could open it with an XML editor like XML Notepad 2007 to show you where the error is.

The current.gpx file contains both your favourites and track logs, and is recreated each time you power on your nuvi.

I noticed that from the Nuvi, if I clear or delete the track Log, then plug it into the PC, use mapsource and retrieve the waypoints then it works. I'm suspecting that when the Nuvi writing the track log data to the current.gpx file, something got corrupted.

I'll see if there is a pattern of what is causing this. It could be the new software 5.40 because I remember before upgrading the software, this doesn't happen

Thank you all.

The GPS has contacts for the SD card too. But you can't get to them dependably to clean them. The procedure I described will clean them as well as the ones on the card. I used an old can of TV tuner cleaner that IS safe on plastic. There are a few contact cleaners that are NOT safe, that's why I cautioned to be sure to use one that was.

Do NOT use a pencil eraser to clean the contacts. Pencil erasers will leave an oily deposit that will attract and retain dirt.

I know the current.gpx is in internal memory but I am suspecting that when the GPS mis-reads data from the POIs on the SD card that its processing becomes corrupt and it in turn writes bad data out to its track log.

I found the current.gpx corrupt immediately after a string of shutdowns. This string of shutdowns was preceeded by a 2 or 3 soft reboots to get the GPS to read the SD card.

Anyway, since moving the POIs to internal memory I haven't had the 1st problem.

I am continuously viewing my jpeg's to see if the new SD card goes missing like the last 2 cards did. Its been good so far with the new card but its only been 1 day. I need to heat this card up while operating the GPS on the dash like the other cards for a few weeks.

I've never seen it, but a Q-Tip with a little 99% isopropyl alcohol can cure that in a New York minute.

I received the error message "Data could not be received because J:/GPX/Current.gpx is invalid". I have always used internal memory for my POIs. Why am I receiving this error message when I try to retrieve my POIs from my old Garmin to transfer over to my new Garmin?

A poi file has an extension of gpi when it is loaded to the Garmin.

Current.gpx is the file that holds your Favorites, Routes and Tracks. It is an "output" file that is created each time your Nuvi is booted up. It is located in the GPX folder on your Nuvi.

As mentioned, your custom POIs are in a file(s) with a .gpi extension. These files are stored in the POI folder on your Nuvi. They have nothing to do with the current.gpx file.

The error message your getting could well be a sign of a corrupted file system on your Nuvi or some fault in the internal drive itself. If possible, I suggest you take a full backup of your Nuvi including any hidden system folders like .system and contact Garmin support on Monday to obtain their advice. An invalid current.gpx file is very rare.

Corrupt current.gpx on 1390LMT

I have seen that the current.gpx have been corrupt on my 1390LMT. Google Earth would not load it, MapSource complained about it too. But neither would say what or where the problem was. GeePeeEx would at least give me a position in the file where the problem was. That way I could find that in the file at that position there were at least 1000 binary zeroes. I could edit out the binary zeroes, but MapSource still did not like the file. Further examination showed that some of the value field had wrong info in them, for instance the speed would have a timestamp value. After a lot of editing I could make it into a file that MapSource would accept.

To get rid of the problem in the 1390LMT I cleared the tracklog. After a few trips I checked the tracklog and everything was looked OK with MapSource. But sometimes after this I have also had the same problem with the corrupt tracklog reoccur. I am usually not interested in checking my whereabouts so I just reset the tracklog to solve the problem.

This might not be the same problem that you are having. I will check if this goes away when I update the firmware in the 1390LMT the next time, but for now I can live with it.

JCA

I too have seen corrupt a tracklog on one of my 765Ts. The GPS immediately recovered by saving the tracks out to a new archive file and cleared the current tracklogs. It was 1 or 2 firmwares ago for the 765T that fixed itself before I learned about firmware updating.

I found it when I noticed a very different size on an archive file and went to open it to see what was going on and nothing would open it. It was my first time looking at a GPX file and learning. The GPS simply missed writing the close to a track point properly which threw the whole file off. It was a fun learning experience.

The SD card still imtermittently is unavailable to view my JPEGs but the zumo 660s has otherwise been operating flawlessly. I have cleaned the contacts, changed the cards and this has continued on all 3 zumo 660s (2 exchanges).

I still believe that if I place the custom POIs back on the SD card I will start to have my shutdown problems again.

Garmin has said that no other owners are reporting this problem and can only offer another exchange. Lucky lucky me!

Thank you for everyone replies and comments. Just to clarify, I'm not using any SD card. I believe the issue is the Nuvi software somehow corrupt the trip log.