Jump to content

Oregon - Memory Full


jlally

Recommended Posts

I have an Oregon 400t. I attempted loading a lot of maps into an 8gb card. I put the card in the Oregon. I turned it on and got the Message: Memory Full. The unit seems to be frozen. It does not work. It looks like the onbard memory is corrupted. Any ideas on how to reset?

 

John

Link to comment

Did you try pulling out the SD card to see if that helped?

 

If that doesn't work you can try a master reset as described here:

 

http://garminoregon.wikispaces.com/Miscellaneous#toc0

 

If that doesn't work see if Garmin support will give a "region" file for the Oregon that forces the unit into mass storage mode and a procedure to load it. I'm not sure if such a thing exists but its fixed a lot of similar type problems on the Colorado.

 

GO$Rs

Link to comment

Probably a call to Garmin tech support to see if you can get a region file that will force the unit into a mode where you can delete files, etc. Let us know what you find.

 

GO$Rs

Yes, the "system software missing" error at startup that I got magically on my 400t killed that unit. I'm exchanging it for an Oregon and now it looks like there are to many ways to somehow corrupt these GPSr's. If a solution develops from this I think I want to know what it is.

Edited by Ratsneve
Link to comment

My Oregon has the same Problem - freezes with the memory full message.

 

Did somebody already develop a solution. I would like to travel with the device day after tomorrow.

Ist there any other way for a hardwarereset - maybe with a pin at the small hole on the backside of the device ?

Link to comment

My Oregon has the same Problem - freezes with the memory full message.

 

Did somebody already develop a solution. I would like to travel with the device day after tomorrow.

Ist there any other way for a hardwarereset - maybe with a pin at the small hole on the backside of the device ?

 

Mine did the same thing. With 400mb of free internal memory I got Memory Full messages, Waypoint Memory Full, and Routing Memory Full messages yesterday. I only had one route loaded, two waypoints loaded and one gpx file of 1800 caches at 8.1 mb. After coming home last night and uploading my found caches to the GC.com field notes page I unplugged it from the pc and went to turn the Oregon back on and then it happened... screen fade out. It will not turn back on. Nor will it go into mass storage mode. I called Garmin today and they were very interested in it. They said to ship it back to them because they wanted to get their hands on the unit and see for themselves what was going on with it. They are going to send me a new unit. I have to say that they were very nice and seemed eager to get their hands on mine. The sad part is that this happened to my last Oregon too. I took that one back to REI and exchanged it for this new one. ;)

Edited by Warriorrider
Link to comment

My Oregon has the same Problem - freezes with the memory full message.

 

Did somebody already develop a solution. I would like to travel with the device day after tomorrow.

Ist there any other way for a hardwarereset - maybe with a pin at the small hole on the backside of the device ?

That small hole is probably for your barometric altimeter. I wouldn't go sticking a pin in there.

Link to comment

It looks like GARMIN does not have any solution until now to solve this bug.

Returning the unit seems to be the only solution.

I hope there might come any workaround.

 

Hopefully the next firmware will fix this. After having two Oregon's in a row that quit working after displaying memory full mesages, I am kind of gun shy now with the new unit on the way to me.

Link to comment

I wonder if keeping the memory as free as possible will help this problem from happening until Garmin comes up with a fix. I am interested to see what happens and a Oregon owner myself.

 

The tech that I spoke to said that I should not load any maps into internal memory. He said that it is recomended to use sd cards for maps. This is somewhat disapointing to me. I use the 24K topo map that is preloaded on sd card. I should be able to use the built in memory for other maps like City Nav etc. and switch as needed. NOT switch cards. :laughing:

Link to comment

that would mean that Memory Full is the memory of the internal space.

i am not sure if Memory Full eventuelly means no memory for all processes.

 

hope you understand what i mean.

similar to a windows-pc:

is it

1) the prozessor has not enough memory

or

2) drive c: has not enough space

Edited by freeday
Link to comment

that would mean that Memory Full is the memory of the internal space.

i am not sure if Memory Full eventuelly means no memory for all processes.

 

hope you understand what i mean.

similar to a windows-pc:

is it

1) the prozessor has not enough memory

or

2) drive c: has not enough space

 

I had over 400 mb's of free space left on internal memory when I got my Memory Full mesages. I had only one route built when I got the Route Memory Full mesages. I only had two wayoints loaded when I got the Waypoint Memory Full mesages. Sounds like processor does not have enough memory?

Link to comment

I had over 400 mb's of free space left on internal memory when I got my Memory Full mesages. I had only one route built when I got the Route Memory Full mesages. I only had two wayoints loaded when I got the Waypoint Memory Full mesages. Sounds like processor does not have enough memory?

 

I've got 384MB free internally on mine (no microSD card installed yet). I installed both City Nav NT 2009 maps of Canada and a portion of TOPO Canada v2 on mine and no probs yet. :laughing:

 

I have a 400t.

Edited by blacknugget
Link to comment

I don't think these Memory Full messages have anything to do with the amount of space left on the drive. The comment from the Garmin tech about not loading maps onto internal memory are suspicious given that's what the 400t does and every time I've seen the error I have had 100's of MB free.

 

My best guess to these Memory Full messages is that they have something to do with the internal databases where the the OR manages waypoints (2000 max) and current tracklog (10000 points max). This is something we don't have visibility into except for the percent utilization numbers we can see on the Setup>Reset page.

 

I haven't had the permanent failure that some are seeing which prevents the unit from booting but I have seen Memory Full messages. So far I have been able to get rid of them. The first time I saw the message was after loading a large gpx file with geocaches and waypoints. Deleting the file, restarting, deleting all waypoints, reloading the file and restarting seemed to fix the problem for a few weeks when it came back a second time. This time was right after loading a small gpx file with geocaches and waypoints (another larger file was already installed). I did the same thing as above to clear out the waypoints and reloaded and once again I was fine for about a week. The third and most recent failure did not start after loading a gpx file. It came during a long driving trip with the tracklog turned on. During the trip I noticed that the tracklog was 92% and not changing after I got the Memory Full message. When I connected to the PC the tracklog stopped near where I got the first Memory Full message. It seemed like the auto archiving mechanism for the tracklog got stuck causing the tracklog to overflow and stop collecting.

 

At that point I Master Reset the Oregon clearing the tracklog and waypoints and I haven't seen the problem for about 2 weeks now.

 

There's definitely some sort of resource leak and I have no idea why some people have a more permanent version of the failure. But, please, keep sending these issues to Garmin so that they get the attention they need.

 

GO$Rs

Link to comment

I don't know if it makes a difference or not but mine is a 300 that I sent back with the memory errors.

 

Thats an interesting point has anyone had trouble with the 400 series? do the premanent failures only happen on the 300s. I wonder if the memory structure is a little different due to the preloaded maps...just a random thought.

Link to comment

I don't know if it makes a difference or not but mine is a 300 that I sent back with the memory errors.

 

Thats an interesting point has anyone had trouble with the 400 series? do the premanent failures only happen on the 300s. I wonder if the memory structure is a little different due to the preloaded maps...just a random thought.

 

My other Oregon that also quit working with memory errors was also a 300.

Link to comment

There's definitely some sort of resource leak and I have no idea why some people have a more permanent version of the failure. But, please, keep sending these issues to Garmin so that they get the attention they need.

 

GO$Rs

These Memory Full errors that you have successfully fixed so far are being described on Oregons (300s?) and not Colorados--correct? And the "more permanent version of the failure" is what I recently had occur on my Colorado which was a System Software Missing error and failure to boot in any fashion. Are you saying that you think these errors may relate or am I mistaken and the System Software Missing error on the Colorado is something else and not related to this Memory Full error on the Oregon (300s?)? My Colorado was a 400t and its "exchange" will be an Oregon 400t. Both 400t's, even after preloaded maps, have considerably more free memory remaining (> 1 GB).

Edited by Ratsneve
Link to comment

I don't know if it makes a difference or not but mine is a 300 that I sent back with the memory errors.

Do you know why Garmin asked you to return the unit for exchange/repair rather then try any g-o-cashers-like simple clearing schemes first?

 

I don't think there is a way to do a reset or anything else if the unit will not power up. When I told them that my Oregon would not turn on or go into mass storage mode when plugging into my PC they immediately said that I would need to send it in. They gave me no other options.

Link to comment

There's definitely some sort of resource leak and I have no idea why some people have a more permanent version of the failure. But, please, keep sending these issues to Garmin so that they get the attention they need.

 

GO$Rs

These Memory Full errors that you have successfully fixed so far are being described on Oregons (300s?) and not Colorados--correct? And the "more permanent version of the failure" is what I recently had occur on my Colorado which was a System Software Missing error and failure to boot in any fashion. Are you saying that you think these errors may relate or am I mistaken and the System Software Missing error on the Colorado is something else and not related to this Memory Full error on the Oregon (300s?)? My Colorado was a 400t and its "exchange" will be an Oregon 400t. Both 400t's, even after preloaded maps, have considerably more free memory remaining (> 1 GB).

 

All of these problems are on the Oregon. There seem to be two classes of Memory Full errors, those that can be cleared up by deleting waypoints, tracks, etc and those that can't. The later seems to require a return to Garmin.

 

GO$Rs

Link to comment

All of these problems are on the Oregon. There seem to be two classes of Memory Full errors, those that can be cleared up by deleting waypoints, tracks, etc and those that can't. The later seems to require a return to Garmin.

 

GO$Rs

But...but I've just switched over from the Colorado to the Oregon! Will there be no end to these troubles? God damnit Garmin! :lol: [sorry, I thought Groundspeak would change the expression to Dog-gone-it or something.]

 

So I visit the local REI today looking to look at a PN-20 and discover from the salesperson that REI has been having trouble with DeLorme's QC or some such--nothing specific. But REI had a whole display section of nothing but Garmin--not one PN-20.

Edited by Ratsneve
Link to comment

All of these problems are on the Oregon. There seem to be two classes of Memory Full errors, those that can be cleared up by deleting waypoints, tracks, etc and those that can't. The later seems to require a return to Garmin.

 

GO$Rs

But...but I've just switched over from the Colorado to the Oregon! Will there be no end to these troubles? God damnit Garmin! :lol:

 

Ive had four Colorado's and am about to get my fourth Oregon. I sure hope this is the last Garmin that I need for awhile.

Link to comment

Ive had four Colorado's and am about to get my fourth Oregon. I sure hope this is the last Garmin that I need for awhile.

 

Hmmm...sounds like maybe you are doing something repetitive that reproduces this problem. That sounds like an excessive amount of returned products. Are these all 300 series? Hasn't Garmin asked what exactly you did? If you can reproduce the problem, why can't Garmin? I would think after 7 defective units they should be able to identify the problem.... :lol:

Link to comment

Ive had four Colorado's and am about to get my fourth Oregon. I sure hope this is the last Garmin that I need for awhile.

 

Hmmm...sounds like maybe you are doing something repetitive that reproduces this problem. That sounds like an excessive amount of returned products. Are these all 300 series? Hasn't Garmin asked what exactly you did? If you can reproduce the problem, why can't Garmin? I would think after 7 defective units they should be able to identify the problem.... :lol:

Strange and sad isn't it? But it seems that Garmin's first and maybe only line of defense is to authorize an RMA exchange. I've seen this happen countless times in this forum. You never learn and I don't think Garmin tech support ever learns what causes the problems. At some point someone learns of a future software update I guess and the whinning dies out until something new flares up.

Link to comment

At least according to the users on the wiki this doesn't seem to be specific to 300's. A user reported a 400t with the permanent failure this morning. The thread is here:

 

http://garminoregon.wikispaces.com/message/view/home/5190967

 

There does seem to be one common theme. Many times this problem seems to start immediately after loading large gpx files. At least in my case I know the gpx didn't exceed the waypoint or geocache limit but it probably had 400 waypoints and 1100-1200 geocaches. It might be prudent to keep your gpx files small until Garmin figures this out. I'm guessing that they will given the number of RMA's generated for this one.

 

GO$Rs

Edited by g-o-cashers
Link to comment

2.4 claims to have a fix for the issue.

 

http://forums.Groundspeak.com/GC/index.php?showtopic=203211

 

GO$Rs

 

I have a 300, and am trying load 3.1 GB of maps (city navigator, and topo maps) to a 4GB microsd card. I build the mapset and store it on the unit. When I put the microsd card into the unit, it powers on and begins loading maps.

 

After a few seconds it gives me a "Memory Full" message, repeats it several times and then the GPS totally dies. Loading fewer maps on the microsd card seems to work, although I haven't tested it since upgrading to 2.4. Anyone have any ideas what may be causing the problem?

 

There's over 800MB free on the internal memory, and 500 free on the sd card still.

Link to comment

2.4 has a fix for this issue, why not just try the upgrade?

 

GO$Rs

 

I did, I wasn't clear in my post. I hadn't tested a smaller mapset in 2.4 to see if reading the card worked at all. Previously on 2.2 I had tried one at about 2.8GB and it worked, but since upgrading to 2.3 and 2.4 I haven't tried a smaller one.

 

I did test it at 3.1 GB and it still produced the memory full error repeatedly, then shut down. Has anyone loaded more than 3GB of maps on a microsd card and had it work properly? The only thing on this card is the garmin directory and inside that is the gmapsupp.img file generated by mapsource.

 

Thanks for any info you may have, I'm getting very frustrated with this.

Link to comment

There were some reports of people around here trying >3GB .img files on an SD card without any issue. When you built the 3.1 GB .img file how many map segments did it have? You should be able to see this in Mapsource once you've selected the maps to download.

 

GO$Rs

 

I just tried building a mapset with 2989 MB, and it still fails. Funny thing this time, it doesn't provide any sort of error message, instead it simply shuts off in the middle of loading maps.

 

I'm loading city navigator and an older topo mapset, so the older topos are smaller regions. Total maps 3,337. It takes about 24 hours to build the mapset using mapsource, so every time I try making it smaller its a bit of a while to test.

 

Any ideas or suggestions?

Link to comment

There were some reports of people around here trying >3GB .img files on an SD card without any issue. When you built the 3.1 GB .img file how many map segments did it have? You should be able to see this in Mapsource once you've selected the maps to download.

 

GO$Rs

 

I just tried building a mapset with 2989 MB, and it still fails. Funny thing this time, it doesn't provide any sort of error message, instead it simply shuts off in the middle of loading maps.

 

I'm loading city navigator and an older topo mapset, so the older topos are smaller regions. Total maps 3,337. It takes about 24 hours to build the mapset using mapsource, so every time I try making it smaller its a bit of a while to test.

 

It´s not the size of the file - maybe the 8GB-card is to big. I have a 4GB card and loaded it with about 3,6GB map and it works fine.

I´m guessing you´ve got trouble with either a too big data-card for the device or too many waypoints (+500), which gave me some trouble - and a replacement of the device by Garmin.

Link to comment

It´s not the size of the file - maybe the 8GB-card is to big. I have a 4GB card and loaded it with about 3,6GB map and it works fine.

I´m guessing you´ve got trouble with either a too big data-card for the device or too many waypoints (+500), which gave me some trouble - and a replacement of the device by Garmin.

 

I called Garmin tech today and asked about the max size the Oregon 300 could take and he said 5 gig. Maybe that is the problem with larger cards??

Link to comment

This might help:

 

I sent an e-mail to Garmin regarding "HC" micro SD cards (any more acronyms, anyone?) for my Oregon 300..."HC" stands for "high capacity". Here's the answer, though I'm not sure if the 5GB limit applies to "non-HC" SD cards:

 

Thank you for contacting Garmin International.

 

Yes, the Oregon will accept the HC cards, up to 5GB.

 

With Best Regards,

 

Damon A

Product Support Specialist

Outdoor/Fitness Team

Garmin International

913-397-8200

800-800-1020

913-397-8282 (fax) Att: Damon A

www.garmin.com

Link to comment

I sent an e-mail to Garmin regarding "HC" micro SD cards (any more acronyms, anyone?) for my Oregon 300..."HC" stands for "high capacity". Here's the answer, though I'm not sure if the 5GB limit applies to "non-HC" SD cards:

 

I am not certain, but I believe that standard SD cards max at 4GB, and micro SD cards max at 2GB. I am not positive on those numbers, but they appear to be the limit of what I've seen available for purchase...

Link to comment

2.4 claims to have a fix for the issue.

 

http://forums.Groundspeak.com/GC/index.php?showtopic=203211

 

GO$Rs

YES, but there are still broken Oregons with the newest firmware.

There are some guys in europe with the newest firmware and the unit does not work anymore.

I hope Garmin will fix it in a few years :laughing: I really do not know, why Garin is waiting so long.

 

On travelling, i never would take an Oregon with the current firmware.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...