lite-C doesn't have bounds checking, so invalid array indices themselves (even negative ones) won't cause errors.
But you could try the following in order to narrow down the problem:

Constantly check if ss_ledgendDeathsText == NULL. If true, log the memory locations of ss_ledgendDeathsText and all arrays, structs etc. in question. Then find the address that is closest to ss_ledgendDeathsText. This might be the evildoer.

Hm, interesting...
I might just do that.

Still, the number of arrays and structs I have is immense. This will take some time to do...

Another thing: if I log the address of an array, it logs the beginning of the array, right? so if the array is pretty long, can I be sure that it is always in one piece?

Physical probably not, but the OS will map one large chunk of virtual memory to the physical memory.