Thanks for reporting this, we have managed to find the bug causing this issue.
If you load a bank which references a global parameter and the bank which defines the global parameter is not loaded then it produces this error.
We are currently working on a fix for this.