On the last two occasions I had a freeze I was doing exactly the same thing. This is the first time I have been able to repeat it. I had selected a saved flight and re-loaded it. This was a flight where I forgot to save the panel state, I only saved through FSX. When it loaded all was fine except that the FMS was not controlling things; it had the route in but for some reason it was not activated. I did that and it asked me to identify which was the active leg, which I did. Then came the point at which the freeze occurred. VNAV had disconnected and I soon realised why, there was no entry on the CRZ page for the cruise level. I entered the FL and the EXEC button lit up. As I pressed the EXEC button the freeze occurred. All this happened in exactly the same way on two occasions and I bet I can reproduce it at will. Hope this helps. Iain Smith

A lot of the panel freeze topics I've read (not all, but a lot) seem to share a common trait, change that affect vnav or cause the fmc to recalculate it. In this case, entering the cruising alt would cause it to calculate a new t/d & descent path/profile.Maybe I'm wrong, but that's my impression.

Yesterday I experienced a freeze without touching VNAV or FMC... immediately after touchdown I pressed F1 and after F2, started to brake and I got the freeze, no posibility to control many things, not able to use surfaces controls, stop the engines ... displays remained frozen.I don't think that it is a memory problem, I have an i7-2600K, 2x4GB DDR3, GTX260...