If I read your note correctly, the immediate problem is seen to be with Pardiso, rather than Arpack, while finding the inverse of B.
Pardiso is a complex solver, with many phases and subroutine arguments; therefore, there are many ways in which mistakes can be made (wrong order of calls, incorrect arguments, etc.).
But even after working on it for days, it is giving faulty results. I hope that you meant to say that you worked on it for days, rather than the other possible meaning: Pardiso ran for many days before giving you incorrect results. If that is not the case, it is next to impossible to help, because of the sheer size of the problem.
How do you decide that the results are faulty? Is it possible to show us the evidence? Can you replicate the error with a reasonably sized B matrix?
I do not think that Pardiso's not giving any error messages is a big surprise. User errors that generate error messages are more easily corrected than errors that do not generate error messages. If the subroutine arguments contain such an error that Pardiso's normal checks are unable to dectect, no messages are to be expected.