Tellie,
Based on what you posted, this does not look like a DLL issue. It looks more like a NULL pointer issue.
You might consider posting the full exceptq report. It may contain relevant information that you might not recognize as relevant. If you do, please make sure to use the most recent exceptq available at
www.warpcave.com/betas. It includes some enhancement that can make working with gcc apps a bit easier.
Also, make sure you have debuginfo installed for the DLLs mentioned in the Call Stack or the Symbols on the Stack sections.
FWIW, NULL pointer errors typically occur because there's an unexpectly missing resource or because the app runs out of memory and neglected to check for this. Given that your exception occurs at startup, I would suspect the former cause is more likely.
I agree with others that you should consider trying 4.1.11. Otherwise, there's no way to know if it will resolve your issue.