Keep in mind, I suffered from this problem for probably more than a year. What would've happened is I would've just removed the first mod where I got a crash if it was enabled, unaware that it wasn't actually responsible. Now, what might have happened if I instead enabled mods one by one? Well, the crashes were dictated by how many mods I had enabled, so I wouldn't have been able to get a crash if I had only a few installed. I later found an issue to my problem, by using a fix originally made for New Vegas, but apparently works fine in other creation kit games (I've been using it for a few months now, and haven't had another crash, beside this one time I was screwing around on a test profile and forgot to enable that mod).
The only pattern I found, was that the likelihood of a crash was dictated by how much data my enabled mods took up. After going through my entire load order, I found that not ONE single mod was responsible. I eliminated my mods one by one (starting a new game each time to check if I still crashed at the cell borders in question). Just for an example, I finally decided to fix a cell border crash I was having.
You don't look for verification: you look for falsification.
