According to Kerm, it feels like we are receiving reports of "bricked" CEs almost daily. The solution, although not entirely obvious to those affected, is to do 2nd+DELETE+Reset to reinstall the OS.
Help! My TI-84 Plus CE Stopped Working - crash while resetting RAM
TI-84 Plus CE is Bricked? - crash while uploading new OS
Troubleshooting a TI-84+ CE? - crash after inputting long math expression (MathPrint enabled?) and recalling a previous entry with 2nd+ENTER
Broken TI-84+CE ... Please Help - crash while running 2048
I think my boot code is corrupted (TI-84+CE) - crash while archiving C program from MEM menu
Freezing TI-84 Plus CE Graphing Calc - crash after battery died (report in thread that the calculator sometimes crashes sending C programs to archive)
The root cause is unknown. The CSE had protection against crashes and such, but it appears the CE's protection is not working. There must be a bug in the CE's code, but we must make a combined effort to swab through the OS code, maybe do some fuzzing, attach a debugger, and perhaps we can find it.
It could also be a defective batch of flash/RAM, in which case we should ask for serial numbers. On the back of the calculator there is engraved a long number and a code like K-0413A where the K indicates the factory (China, in this case), and the date is in MMYY format. (Source, although I don't know what the A stands for.)
Help! My TI-84 Plus CE Stopped Working - crash while resetting RAM
TI-84 Plus CE is Bricked? - crash while uploading new OS
Troubleshooting a TI-84+ CE? - crash after inputting long math expression (MathPrint enabled?) and recalling a previous entry with 2nd+ENTER
Broken TI-84+CE ... Please Help - crash while running 2048
I think my boot code is corrupted (TI-84+CE) - crash while archiving C program from MEM menu
Freezing TI-84 Plus CE Graphing Calc - crash after battery died (report in thread that the calculator sometimes crashes sending C programs to archive)
The root cause is unknown. The CSE had protection against crashes and such, but it appears the CE's protection is not working. There must be a bug in the CE's code, but we must make a combined effort to swab through the OS code, maybe do some fuzzing, attach a debugger, and perhaps we can find it.
It could also be a defective batch of flash/RAM, in which case we should ask for serial numbers. On the back of the calculator there is engraved a long number and a code like K-0413A where the K indicates the factory (China, in this case), and the date is in MMYY format. (Source, although I don't know what the A stands for.)