Let me start by saying that you are off the path, over the guard rail and leaning over the cliff...this kind of calling from LV is very difficult to get right and you are much better off creating a wrapper DLL that exposes an API that is "friendlier" to LabVIEW and do the structure manipulation within the wrapper DLL. I've posted before about the dangers of the byte alignment, data types and pointers, but let me just focus on a couple things here.
First - to correct a misunderstanding about the original data structure - there is no cluster contained within a cluster. The MemBlockStruct does not contain another cluster, but instead has a pointer to clusters. This is not something that you can recreate in LabVIEW as there are no pointers. You can replace the pointer entries in the cluster with int32 values, but that is all. If you define a cluster within a cluster in LabVIEW, the memory is contiguous. That is not the case with MemBlockStruct. (Note this also means in the GetNodeInfo that you don't need to wrap the HANDLE integer in a cluster - it is just an integer.
Second - The example VI image you have shown uses dbl types as the elements of your cluster. The C structure calls for integers. This means that it expects the elements in the structure to be 32-bits long, and the LabVIEW structure is defining them to be 64-bits. This means that the data fields are not going to line up correctly.
I'm going to get quite a reputation on this board by always being so negative about cluster->structure mapping, but it is only because I'm looking out for you. If you do just the slightest thing wrong, and are lucky, then you end up with that error message. If you are not so lucky, then you end up with a memory corruption that might not show up for minutes, hours or days later. This is one of the reasons why people like LV over C/C++ - these kinds of memory errors can be nightmares...I know - I've been there.
So, I'll just sign off with a plea to go with a wrapper DLL if at all possible. I know that this is sometimes difficult due to needing to create some C code and building it into a DLL, but you'll save yourself a ton of heartache later.