I am using chem_opt=202 MOZART-MOSAIC-aq and using mozbc to write in chemical boundary and initial conditions from CAM-Chem.
I had a couple of successful runs before:
1) chem_opt = 201 + bc + ic
2) chem_opt = 202 + ic;
However, chem_opt = 202 + bc + ic always failed with varying error messages
1. Using 96 cores:
d01 2017-06-10_00:00:00 Input data is acceptable to use: wrfbdy_d01
forrtl: severe (174): SIGSEGV, segmentation fault occurred
double free or corruption (out)
2. Using 96 cores but significantly increase requested memory to avoid memory issue:
d01 2017-06-10_00:00:00 Input data is acceptable to use: wrfbdy_d01
then it just hangs there, no more information and not proceeding, just timeout
3. Using 196 cores:
the program can get over wrfbdy without error, but then have errors later:
d02 2017-06-10_00:00:00 Input data is acceptable to use: wrfinput_d03
corrupted size vs. prev_size
4. Using 196 cores, also significantly increase request memory:
It's running! But after processing for 7min, the error comes back:
corrupted size vs. prev_size
I want to understand better what are these corruption messages and what are possible ways to fix them?
Does it mean I always need to use a very large number of CPU and memory?
A note is my wrfbdy_d01 has exactly 3000 4D variables. It is surprisingly large to me; is this normal?

Attached my namelist.input
Thanks for any help!
I had a couple of successful runs before:
1) chem_opt = 201 + bc + ic
2) chem_opt = 202 + ic;
However, chem_opt = 202 + bc + ic always failed with varying error messages
1. Using 96 cores:
d01 2017-06-10_00:00:00 Input data is acceptable to use: wrfbdy_d01
forrtl: severe (174): SIGSEGV, segmentation fault occurred
double free or corruption (out)
2. Using 96 cores but significantly increase requested memory to avoid memory issue:
d01 2017-06-10_00:00:00 Input data is acceptable to use: wrfbdy_d01
then it just hangs there, no more information and not proceeding, just timeout
3. Using 196 cores:
the program can get over wrfbdy without error, but then have errors later:
d02 2017-06-10_00:00:00 Input data is acceptable to use: wrfinput_d03
corrupted size vs. prev_size
4. Using 196 cores, also significantly increase request memory:
It's running! But after processing for 7min, the error comes back:
corrupted size vs. prev_size
I want to understand better what are these corruption messages and what are possible ways to fix them?
Does it mean I always need to use a very large number of CPU and memory?
A note is my wrfbdy_d01 has exactly 3000 4D variables. It is surprisingly large to me; is this normal?

Attached my namelist.input
Thanks for any help!