Memory test on Nuvi 1390?

I don't know of a memory test that will fix bad memory. If you find there is bad memory, then what will you do about it?

If you're running firmware 5.70, you may encounter this problem. I know I did. The two things I did that seemed to have solved the issue were to delete the following file:

X:/.System/sqlite/mlg_history.db

Then save your favorites and clear nonvol memory through the nüvi diagnostics menu. A hard reset may accomplish the same thing but I cannot say for sure since I didn't go that route. In any event, I haven't had a failed start since I did this and my 1300LM boots a lot faster as well.

No, not fix, but find/confirm.

Have information to ask for warranty repair from Garmin.

Yes, am running 5.70. Will give this a try. Thanks.

Do you mean the ram memory or the actual hard drive memory. Because if it is harddrive memory the Windows tools has a the ability the repair bad clusters which is what I had to do with my gps. Chkdsk is one of many such programs.

There is no actual Hard drive in there, only RAM and ROM. Chkdsk will and *did* clean up a lot of issues and allowed me to load the full mapset, but chkdsk does not actually do any comprehensive test of the memory.

The question is - what caused the corruption in the first place-?

Looking back at my first post in this thread... When the unit first crashed, chkdsk corrected issues such as this:

"The size of the \GPX\Archive\1.gpx entry is not valid.
\GPX\Archive\4.gpx is cross-linked on allocation unit 15869.
Cross link resolved by copying.
The size of the \Voice\English_American_Jack.vpm entry is not valid.
Removing trailing folder entries from \keyboards
Unrecoverable error in folder \.System\Diag\EventLogs.
Convert folder to file (Y/N)? Yes
Lost chain cross-linked at cluster 7127. Orphan truncated.
Lost chain cross-linked at cluster 7035. Orphan truncated.
Bad links in lost chain at cluster 1272 corrected."
....Plus a lot more cross-links and lost chains.

Since then the unit has has been pretty much ok with the occasional burp. Diagnostic logs are giving me the occasional RTL Trap error such as:

"Basic Shutdown Information:
Error Type: RTL Trap
Software Version: Software Version 5.70
Date: 12-17-11
Time: 05:47:21 AM

Error Number: 6E5D800E

General Registers:
R0 : 0x03A27A88 - R8 : 0x02D98808
R1 : 0x00000000 - R9 : 0x00000000
R2 : 0x01998818 - R10: 0x00000000
R3 : 0x01CB0440 - R11: 0x00000000
R4 : 0x01CB0490 - R12: 0x00000000
R5 : 0x01CB0490 - R13: 0x00000000
R6 : 0x2F6FDFFF - R14: 0x00000000
R7 : 0x000004C0 - R15: 0x00000000

RTL Information Line:
bad memory block pointers, r0=task ID, r1=rtrn, r2=first blk, r3=prev blk,r4=prev blk's next, r5=this blk, r6=next blk's prev, r7=next blk, r8=last blk"

I'm concerned it may have some intermittant/flaky memory and I'd like to be able to test it before the warranty runs out. The unit is about 7 months old now.

Perhaps I am just being paranoid, and if someone want to tell me that I would not be offended.

Sounds like if I clear NV memory, I lose my Favorites. What else would be lost? I do have a full backup saved.

Am I correct that the 'Favorites' is the 'GPX' folder - specifically the 'Current.gpx' file? Can I restore favorites simply by restoring the Current folder?

ddeerrff, you will need to rename the file to something other than current.gpx, then copy it to the GPX folder, restart your nuvi and your favorites will be restored.

If you do have a full backup, then why not just format it?

A format will log any bad sectors (blocks) and then keep them isolated from being written to. You can then do a restore and all should be well.

Well I should say I have a copy of all the files that I could copy, including the .system folder. I'm not confident in my ability to reload everything back on if I do an actual format.

to be cautious about the format. I know it has been done successfully by some forum members. But I have also read posts by users who bricked their nuvi by doing a format. I suspect if you format, then immediately restore all the files before disconnecting or rebooting the nuvi you will be OK. I think the problem can come in if you disconnect after the format. If the nuvi then refuses to mount as a USB drive, you are SOL.

Personally, I wouldn't do unless it was a last chance effort. A hard reset should be the first choice.

The problem isn't the device, but the firmware. It has a bug in it that generates the RTL Trap errors and Garmin has been made aware of the problem. The possible solution I presented above was a combination of two different attempts to fix the RTL Trap error, neither of which worked by themselves but seemed to work together.

OK, I deleted the .system\sqlite\mlg_history.db file. Then rebooted and from the diags cleared nonvol memory.

Rebooted again and had to go through the general config (tell it I was in the US, etc).

Could not figure out how to reload my favorites from my backups, so re-entered those manually. (Didn't have that many).

We'll see what happens.

Thanks to all that replied.

Hope I don't jinx myself, but so far so good. No aborted start ups, and no flakey behavior.

I encountered problems both yesterday and today, both with RTL Trap errors (the source of the spontaneous reboots) and with slow screen redraws.

I've reverted to 5.40 and expressed to Garmin my displeasure. If you find you continue to have problems and want to go back to 5.40, you can download the 5.40 firmware here. Garmin only keeps the current version of the firmware on the site, so the older firmwares have to be downloaded this way.