Using blockMesh to create own mesh results in Segmentation Violation

[radioaktivity]

Using blockMesh to create own mesh results in Segmentation Violation

I was about to modify the case of the incompressible NACA shape by adding a 2D-Mesh which I created via blockMesh.
The Base-Tutorial case was running without problems but modifications on the mesh result in errors.
I was playing around with patch names, initial conditions, binary or non-binary mesh-files, I set the FFD-points but the resulting error is always the same.

The Following error appears :

Finalising parallel run
Checking if we need to compress the mesh files
Checking if we need to compress the mesh files
I/O    : uncollated
[0]PETSC ERROR: ------------------------------------------------------------------------
[0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range
[0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[0]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind
[0]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors
[0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run  [0]PETSC ERROR: to get more information on the crash.
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
with errorcode 59.
NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.
--------------------------------------------------------------------------
[2]PETSC ERROR: ------------------------------------------------------------------------
[2]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range
[2]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[2]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind
[2]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors
[2]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run  [2]PETSC ERROR: to get more information on the crash.
[3]PETSC ERROR: ------------------------------------------------------------------------
[3]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range
[3]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[3]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/docum
entation/faq.html#valgrind
[3]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors
[3]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run  [3]PETSC ERROR: to get more information on the crash.
[ca2afbc648ee:00518] 2 more processes ha
ve sent help message help-mpi-api.txt / mpi-abort
[ca2afbc648ee:00518] Set MCA parameter "orte_base_help_aggregate" to 0 to see all help / error messages

Is this caused by a naming error or did I miss a step?
Thanks in advance for your help.

For reference i put my blockMeshDict and my preProcessing.sh file in the attachment.
preProcessing.txt
blockMeshDict.txt

[friedenhe]

Check if you can run simpleFoam for your mesh. If yes, check if you have the empty boundary condition. DAFoam does not support empty BC.

[radioaktivity]

Yes the mesh was working with simpleFoam. It was the empty boundary conditions that caused the error. Thank you very much.