Jump to content

Garmin Oregon 650 crashing


lee737
Followers 4

Recommended Posts

I've noted several 'types' of crash with this unit - normally seems fairly random, resolved with a power cycle, very irritating nonetheless.....

 

In the past month or so though - twice, a reproducible crash has occurred - without warning, trying to search for a waypoint crashes the unit. The first time it occurred I would enter the search letter, say 'W', hit the tick, then the unit would be locked, with a screen corruption looking pattern overlying the normal display. Then yesterday, the same thing happened, when I was searching for a waypoint, hit the S key to start searching, and that locked the unit, literally, the S button enlarged like you had just typed it and that was it, was totally unresponsive.

These last problems were different to the normal crashes - the power button was unresponsive, so it took a battery removal to get the unit functioning, but then the problem would recur, in exactly the same way.

 

Now the solution - deleting the pocket query files worked to restore the unit to normal function, albeit without any caches..... :(

Last time this happened, I just transferred new PQ files in, and all was OK, until yesterday....

 

I've googled this a lot, and can't find any solutions, has anyone had this and found a better solution?

 

I'm worried this will occur in a remote area when I need the GPS to navigate, and don't have a laptop to get it working. Suffice to say, this could be the last Garmin we buy......

 

cheers

Lee

Link to comment

It is unclear if your work around is to delete the PQ then reload the same PQ or a different PQ. If it is reloading the same PQ, you can do this in the field by using an SD card in the GPS and placing the caches on the card. You will need to create a Garmin/GPX directory on the card first. When the system hangs, remove the card and restart the system without the card which will clean out the internal database. Insert the card with the caches and restart.

Link to comment

The first time it happened, I loaded fresh PQ files, this time, I haven't added new ones yet, just deleted the old. I'll put the new PQs on the SD card now, so next time it happens dry.gif, I'll try your suggestion and see what happens. To be honest - I love this unit when it is working, but it crashes too often to be taken seriously as a potential piece of safety-critical equipment, I won't get rid of my Gecko yet....

Link to comment

It's one of many issues in the Garmin lines that are well known to the user base, reported to their support department, and seemingly utterly ignored by QA/engineering.

 

https://garminoregon6xx.wikispaces.com/Common+Issues#x-Crash Reports

 

My Oregon 650 is the least stable Garmin device I've ever owned in modern times. The Oregon 450 used to crash only a few times a day instead of a few times an hour. That was about on par with the Colorado 400, so the 6xx experience really is much worse in my experience.

Link to comment

If your Oregon crashes tat often there's a serious problem. My 600 crashes occasionally (weeks/months in between crashes). The 4.40 firmware looks very stable lately but with earlier versions (2.x, 3.x) I've had crashes that made me jump through several hoops to get the unit restarted and it often would corrupt the profile in use (as in several changed settings). My Colorado 300 crashed a few times too in it's days but I guess that the more complex a GPS becomes the higher the risk of a crash. DOS5 didn't crash as much as later Windows versions. My GPS12XL never crashed :blink:

Link to comment

Every crash I have ever seen is due to bad HTML in a cache description. This started many years ago and continues through to the current units. GSAK fixed the problem way back in the past, so if you use it, the crashes should disappear.

 

Well, if you're navigating towards a WP that you entered yourself there's no HTML around and even then (older firmware) I've had crashes. So that's just using the GPS and map, no caches whatsoever.

 

Most of the crashes I've seen was changing profiles. Go to: WP >> change profile from geocaching to automotive... crash but not always, just occasionally. I was never able to "make" it crash by doing what I did before.

Link to comment

Every crash I have ever seen is due to bad HTML in a cache description. This started many years ago and continues through to the current units. GSAK fixed the problem way back in the past, so if you use it, the crashes should disappear.

I use GSAK with the Garmin export macro and get the occasional lockup on my Oregon 600 and GPSMAP 62s, both when trying to load a cache description.

 

Only once have I had the Oregon 600 lock up while logging a cache as found.

Link to comment

Every crash I have ever seen is due to bad HTML in a cache description. This started many years ago and continues through to the current units. GSAK fixed the problem way back in the past, so if you use it, the crashes should disappear.

I use GSAK with the Garmin export macro and get the occasional lockup on my Oregon 600 and GPSMAP 62s, both when trying to load a cache description.

 

Only once have I had the Oregon 600 lock up while logging a cache as found.

 

Do you use the current GSAK? I have not have a lockup or crash for many years. I remember back when this all started and the units would crash all of the time. There were various issue because Groundspeak does not check for closure and coding errors in the cache page html. The Garmin units do not have very good html decoders and when you get an unclosed bit of code, strange things happen. Maybe GSAK does not catch all the errors, but it has worked for me.

Link to comment

Based on leads in this thread, I just installed GSAK, added my PQs, then exported a GPX file for the Garmin. Turned unit on, tried to navigate to a cache, locked up on first one! I had to remove batteries to get it going, but it hasn't skipped a beat since then, and I haven't been able to reproduce the crash, maybe it needed the power cycle to refresh....

Can this be done on the Oregon without removing the batteries? - because that is a real nuisance.....

Link to comment

Do you use the current GSAK? I have not have a lockup or crash for many years. I remember back when this all started and the units would crash all of the time. There were various issue because Groundspeak does not check for closure and coding errors in the cache page html. The Garmin units do not have very good html decoders and when you get an unclosed bit of code, strange things happen. Maybe GSAK does not catch all the errors, but it has worked for me.

 

I've never used anything but GSAK since 2006 (always latest versions) and had crashes. Maybe I've just had less crashes than I would have without it :ph34r:

BTW, I export with GarminExport macro and since I have my Oregon 600 I use GGZ instead of GPX, additional waypoints are exported as POI. I manually delete the GGZ file and GPI files (in both directories) before loading the unit again but don't do restarts in between. So far firmware 4.40 seems the best I've had since 2.60 (might be 2.80, not sure).

Link to comment

I use GSAK with the Garmin export macro and get the occasional lockup on my Oregon 600 and GPSMAP 62s, both when trying to load a cache description.

 

Only once have I had the Oregon 600 lock up while logging a cache as found.

 

Do you use the current GSAK? I have not have a lockup or crash for many years. I remember back when this all started and the units would crash all of the time. There were various issue because Groundspeak does not check for closure and coding errors in the cache page html. The Garmin units do not have very good html decoders and when you get an unclosed bit of code, strange things happen. Maybe GSAK does not catch all the errors, but it has worked for me.

Yes, I always use the current version of the GarminExport Macro and GSAK.

 

I have a suspicion that the recent lockups I've had on both the Oregon 600 and the GPSMAP 62s are somehow related to recent firmware changes that were made across mutiple devices. Prior to those changes being made, my GPSMAP 62s never had a lockup.

I've only had the Oregon 600 for about 6 weeks and never ran it on the original firmware that it came with, so I can't compare that.

Link to comment

The only time I've noticed a crash/lock-up on my Oregon 600 is when I try to do too many things too quickly. It doesn't happen often, but often enough to be noticeable. unfortunately when it freezes, nothing works, including the power button, so it does require pulling the batteries to reset it.

Link to comment

The only time I've noticed a crash/lock-up on my Oregon 600 is when I try to do too many things too quickly. It doesn't happen often, but often enough to be noticeable. unfortunately when it freezes, nothing works, including the power button, so it does require pulling the batteries to reset it.

 

Having to pull the batteries to reset just rubs in the salt.... Should never be needed in any well engineered electronic.

There is no reason that these units should be less reliable than my iPhone, given how many fewer tasks they have to do, and the cost of the unit.

Link to comment

The only time I've noticed a crash/lock-up on my Oregon 600 is when I try to do too many things too quickly. It doesn't happen often, but often enough to be noticeable. unfortunately when it freezes, nothing works, including the power button, so it does require pulling the batteries to reset it.

 

Having to pull the batteries to reset just rubs in the salt.... Should never be needed in any well engineered electronic.

There is no reason that these units should be less reliable than my iPhone, given how many fewer tasks they have to do, and the cost of the unit.

 

It's annoying, but in the grand scheme of things, I still like carrying around my GPS over my phone. Like I said, the problem happens infrequently, and I'm still happier with my 600 replacing my 450.

 

Of course, the key is to never pay full price for these things. [:)]

Link to comment

I made some changes, and the same problem has recurred today.

 

This time, I loaded a single GPX file (exported from GSAK) onto the SD card, holds about 2500 caches approx - the same ones as before, but before, they were in straight PQ GPX files.

Was going OK today, apart from a map-freeze (yes, another bug!), then the dreaded seize up on trying to search for a WP in WP manager. Not as bad, was able to turn the unit off with the power button this time.

 

Removing the SD card solves the problem, but leaves the unit sans-caches, re-inserting the SD card reproduces the problem exactly.

 

I assume it is the caches, but could be the SD card also?

Link to comment

Try a master reset, shouldn't be crashing like that unless you're in the habit of loading corrupted files.

 

Mind you I don't use GSAK, but Basecamp to install my data. Maybe 3rd party programs screw it up?

 

Tried the master reset, reinstalling fw etc, no luck. I unpack and copy the PQ-files directly to the device. However I think there could be a memoryleak somewhere, the device is full and simply crashes. Since most current devices share the codebase, similar crashes happen across different models.

Link to comment

Every crash I have ever seen is due to bad HTML in a cache description. This started many years ago and continues through to the current units. GSAK fixed the problem way back in the past, so if you use it, the crashes should disappear.

 

This says it all......I've had crashes on 3-62S units and one 450 and it always boiled down to this.....it happened with old ver GSAK, so far the new is 100%.

Link to comment

This says it all......I've had crashes on 3-62S units and one 450 and it always boiled down to this.....it happened with old ver GSAK, so far the new is 100%.

 

I'm never more than 1 version behind and yet...

 

Another crash today (after saying on this forum my 600 is behaving for some time now).

 

400 caches GGZ file, WPs as POI as always. Firmware 4.40

First WP of a multi, no great fix under treecover. Suddenly "lost satellite reception". I walk 50m to a more open spot, see sats in sat view but no lock after a few minutes. Switched off, then on again. Startup screen "Garmin" stays frozen for minutes. Switching off won't work. Remove batteries, reload batteries, switch on.. Garmin startup screen remains frozen. Remove... put in new batteries.. again, the same.. After a few cycles, remove and replace batteries connect via USB to Android tablet. Switches on but startup screen freezes. Unit not recognized as mass storage. Remove batteries.. try USB a few times.. Finally gave up. Switched on and started to put everything back in my backpack when suddenly, after maybe 10 minutes with frozen screen, I see the maps and caches getting loaded. The rest of the day the 600 worked flawless. All WP within 5m under treecover.

After this crash all data was still present, track, tripcomputer..

 

I'm sure it will do an excellent job but then again I'm also sure it will crash on me again.

Link to comment

I've had a 650 for a year or so and am constantly plagued by crashes. Just came back from a weekend caching and the GPSr, must have crashed about 15 times over those three days. I really can't afford to replace the unit at this stage so suspect I'll just have to live with it but it really shouldn't be happening in a unit costing as much as it does. My little old Oregon 200 never hung once over the 3 years that I had it.

Link to comment

So disappointing, that for such a great unit that it can be so unstable - I now think my crashes are due to GC GPX files and/or the particular SD card I had. I've gone back to not running an SD card, and so far no lethal crashes since.

I've now gone so far as to carry my trusty 10 yr old Garmin Gecko with us, and have coords for critical caches written down! On the weekend we drove to the summit of a 3600' mountain, the last thing I want is a frozen GPS once there....

Keep backups of your GPX folder, I recently lost every WP I had added, still don't know how that happened either.....

Lee

Link to comment

I've had a 650 for a year or so and am constantly plagued by crashes. Just came back from a weekend caching and the GPSr, must have crashed about 15 times over those three days. I really can't afford to replace the unit at this stage so suspect I'll just have to live with it but it really shouldn't be happening in a unit costing as much as it does. My little old Oregon 200 never hung once over the 3 years that I had it.

 

Have you tried the suggestion above?

Link to comment

Glad I have the Etrex 20 and Montana then, can't recall the last time they 'crashed' :)

Trusty old 450 with last released code crashed exactly once during my 2015 caching year (1184 caches found), and it was my own fault in part for adding an errant *.gpx file from a 3rd party source. I'm guessing Robert's experience with the 450 was a bit earlier in the development cycle.
Link to comment

I'm beginning to wonder if it is a particular cache that crashes mine.....

I have a 100km radius database in GSAK - if I export all of these, the GPSr reliably hangs if I try and search for a waypoint....

If I do the same, but limit the caches to those in an 85km radius, it works ok.

Link to comment

I'm beginning to wonder if it is a particular cache that crashes mine.....

I have a 100km radius database in GSAK - if I export all of these, the GPSr reliably hangs if I try and search for a waypoint....

If I do the same, but limit the caches to those in an 85km radius, it works ok.

 

Probably it's one (or more) caches with "special" characters that causes this.

Try exporting 85-100 Km and see if the problem persists. You can then try other filters (trads only, multi only..) That way you might find the culprit i.e. 90Km, trad....

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...
Followers 4
×
×
  • Create New...