@cmb:
If you only had, say, 256 MB RAM, but configured a large state table size that could consume more than 256 MB RAM, and hence you caused the system to run out of kernel memory, it can't do anything but crash.
In previous testing state amount of ram was 2048MB and in current testing state amount of ram is 3072MB and for while without crash ;) , but thank you for your suggestion.
@cmb:
If you're not being prompted for a crash report, you've broken something in that in your changes too. The files would be under /var/crash/.
I did backup the .vmdk file from crashed state and the /var/crash/ folder is contain one file only named: minfree! why crash file did not created? I can't remember did any changes or recompile binary related to collect or write crash file, can you help me to find an scope to look for broken "collect or write crash file" relate please?
@cmb:
If you can replicate the crash on an unmodified pfSense 2.3, then I'm interested in more specifics. As is, this thread is about your modified product and seems to have no relation to stock releases.
I'm very interested too but it's better to find the problem in mine.
Thank you again!