2.55MP might also be the problem. Some of the apps you are running might be assuming 2.43 and accidentally causing problems.
You are not running into malicious ASM caused corruption, you are running into accidental corruption. I wouldn't think that the flash is nearing end of life, unless you've been heavily abusing it.
I would highly suggest re-sending the OS and then documenting what you've done if any of the mentioned issues happens again.

Quote from: Sorunome on January 16, 2017, 12:15:29 pm

IIRC to be able to overclock an 83+SE/84+/SE you'll need to add a resister to some pin on the CPU. After that, as @Eeems pointed out, a lot of things might be unstable if you actually overclocked the CPU.

The z80 itself is designed to run at up to 24MHz, which you'll be able to do with overclocking, however, the OS itself will always slow down the clock speed all over the place, so you'd only have a performance boost in dedicated ASM programs which take use of it.

A very important thing where NOT to overclock is when writing to flash, as the flash controler is too slow to handle the overclocked calc. This may be the reason why TI limited the clock speed to 15MHz

Well,  to bad TI complicated this... Now I have to spend extra time optimizing BASIC programs.

I wouldn't say they complicated things. I'd say they probably worked within the constraints they had and produced something fairly stable that wasn't intended to be used outside of the constraints they setup.

1.Probably KermMartian or Tari (both from Cemetech) has that info. :-P

Well @KermMartian is also over here.

2.At the random,  typically occurs during periods when I frequently garbage collect.

Sounds like a potential bug with garbage collecting. What do you have installed on your calculator in terms of apps?

3.Also randomly... Worse manifestations happened when I had viruses on my calc.

Again, going to need to know more about this "virus" before we can really say anything.

4.I meant virus scanner,  not a pc style background AV program. The virus showed up after using one specific app ( http://www.ticalc.org/archives/files/fileinfo/309/30917.html) There were strange files such as ''HACK'' and others. Memory menu had infinite up scroll.

AV programs started out as just a scanner, and at their core they still are. That said, no the complexity needed to detect problem apps/programs would be larger then what you could implement on the device. Just read the code of what you are going to install on your calculator before running to avoid problems.
You may want to report that file so that the ticalc maintainers can look into it if there is some malicious code. It could have just been a bug in it's code that is leaving things in a bad state.

No, I thought that program was needed only on the TI-83+. What causes these issues anyway?

UPDATE: I downloaded this fixer and now the problematic games work WITHOUT problems. Thanks alot!!!!!! I am hoping to one day find out what the hell causes this (detailed answer with all info you know, please...).

According to the description it is not for the 83+ it is only for the 83+SE, 84+, and 84+SE

This is a LCD driver fix for the 83+SE, 84+, and the 84+SE. This correct display problems that have been occuring in new model calculators. You see these problems in games like Fall Down, Desolate, Doom, and others. This fix is not for 83+, Sorry.

I'm glad it fixed things for you, as for why it did, I would recommend reading the readme: http://www.ticalc.org/cgi-bin/zipview?83plus/asm/programs/alcdfix.zip;Readme.txt

Aaaahh.... So TI doesn't know to use binary?! Or are they doing this to confuse users?

Nope, they are just using the International System of Units (SI) version of the Kilobyte which states that since kilo used as a prefix means 1000 (10³), a Kilobyte is 1000 bytes. Basically they are using the internationally accepted Metric measurement.

Wait, so TI is actually admitting that TI-84+SEs have more than 24 KiB of RAM? I thought they never would do that 

They just say that it's got 24KB of available RAM. (Notice the KB not the KiB)

I would suggest adding a readme to the repository outlining how to use the command line tool. As well as outlining how to use the ti83f.py module in your own code.
Another good thing to add to your code would be docstrings.

Omnimaga is practically dead.

Not really dead. Most of the staff just have very busy lives. That said, please just stick to continuing the conversation instead of asking people to post on other sites instead of this one.

Here is a list of tutorials. Quite a few of them will be kinda out of date, but they will still be useful.