I would like to remind that, PHNL scenery range it's 8 nm. Before that area, we simply don't do anything.
The only thing related to PHNL in some way, that loads before that range, are the AFCAD with the approach procedures so, an error in the approaches, might cause a crash.
Note that, with PHNL 1.0.2 and up, the supplied AFCAD does not contain ANY approaches: they are coming from the MS default AFCAD.
And, sorry to repeat it but, when you are trying to FIND if the crash is related to the scenery, you need to use a default airplane.
If the crash happens only after a long flight, it means the possible memory leak is happening WAY before approaching the airport area, the fact that the actual *crash* happens there, might be simply because, if the airplane caused a memory exhaustion during the flight, what caused the crash was just the act of loading a new scenery, and that might have been any scenery but, of course, a with a large airport scenery, it's more probable, without the scenery having anything to do, other than just be large enough. But the problem was the memory was already dangerously low. If the problem was the scenery, it should crash regardless of how much memory is available.