KLN90B fans,
I have good news for you. I have found and fixed a bug* in 0.77B that was causing most of the crashes. It may have been the only crash-worthy bug, it certainly has the potential to have caused quite a bit of trouble any and everywhere.
I have a replacement KLN90B.dll for you to test if you would like. Simply drop it over the existing kln90b.dll in 'gauges' if you already have 0.77B installed. It will self-identify as 0.79B with a date of 2017-01-21. It is compatible with the database formats in 0.77B. If you are still using 0.76B, please install 0.77B then place this dll over the one in 'gauges' to test.
But wait, there's more!
This version also has implemented the OTH5 thru OTH10 pages. These are the fuel management and air data pages and they are very nice to have!
Also, a couple of minor bugs were corrected in the VNAV functionality and so far as I can tell it works correctly. It is also now implemented on the Super Nav-5 page also. And, regardless if you are using VNAV or not, if you enter a selected altitude on NAV 4 page then you will get an alert tone (C-chime) when you approach the altitude (in climb or descent) and the same tone if, once you are at altitude, you drift more than 300 feet from it.
http://fscaptain.net/downloads/kln90b_79B_test.zip
Enjoy the KLN90B, and please let me know if you experience crashes with this version, with all the details you can supply if you do.
Dutch
* Bug details: the problem was obvious right on the NAV 2 page on the opening screen, and when I realized that after all this time, it led to the solution. Did you notice that in 0.77B your present position was often shown in relation to an ILS and not only a VOR? That is not correct behavior. The problem was the ILS navaids were being loaded into the VOR database as VORs. But when any was accessed to be used, it would crash. You could verify this by scrolling through the VOR database. When you came to one starting with an I the KLN crashed. It was trying to handle an ILS as a VOR. Since there are many places where VORs are accessed internally as part of the nearest navaid list, this had the potential to cause seemingly random crashes.
I don't know if this is the only serious crash problem but it might be. Only testing will confirm.