Which apps do you have installed and which do you have running in the background. This is usually the reason for instabillities.
You surely installed more than just the market hack and if yes which.
Here's what I have installed:
- TaskPanel Lite (Had Advanced Taskkiller Free)
- Weather Widget - Free
- OI File Manager
- Robo Defense
- Dolphin Browser
- Browser (a theme for Dolphin Browser)
- Battery Status - Free
- Google Maps
- Simple Last.fm Scrobbler
- Last.fm - Personal Radio
- DoggCatcher (installed yesterda)
- Market4Archos (apk from the forum, installed yesterday)
- Squeeze Commander
Now, I read some threads around the forum, and I do hear you when you say that apps are what usually causes crashes. But I really don't think this is the case here. Let me repeat that my Archos crashed multiple times with NO APPS installed whatsoever, except from the stock ones, which come installed by default. That also excludes the memory overload problem.
Moreover, I don't use many of the apps above (like Quickipedia or Deezer) - I keep them for just in case, if I need them once in a blue moon. And whenever I use more than the usual Gmail, Browser, Music player and maybe ReaderScope, I always make sure that I have at least 30 MB of free memory.
Don't get me wrong: I am not complaining. I made a conscious decision to drop 300 euros on an Android device, when I could've gotten an iTouch or a Zune or something of the kind. I've been using Linux boxes and and off since 1996 so I am well aware of the problems (and huge benefits) that go along with open source software.
However, I do think there's a problem here. When I install Debian, openSUSE or Ubuntu, I get a free piece of software and nobody promises anything - take it or leave it. When I drop 300 bucks on a hyped media player however, I expect it to do basic things at least halfway decently. I don't expect it to "just work" - I could've gotten an iPod for that - but I do expect it to not crush and die right after full reinitialization and firmware reflashing.
Also, I still don't understand what memory overload and application crushing has to do with the firmware... I am not that technically literate, but I assume the firmware is installed in non-volatile ROM memory, which should not be accessible to applications. How is it possible that repeated Android crushes due to memory shortage or application crushes leads to corrupted firmware and the need to reflash the firmware repeatedly until it works "properly"?