Virtual Watchdog Timeout

I have very annoying Virtual Watchdog Timeout issues sometimes in my RCM6700 software that otherwise works perfectly. But every once in awhile I will load a build onto a RCM (that works fine with zero WDT on another RCM in the programmer), and it will just give me VWDT errors over and over and just crash (very annoying when the RCM is installed in a enclosure and it has to be taken apart to get to the card) 
 

 I have a crash handler, but it gives me the address of the crash handler for the error (it seems) not the address of the ostensibly responsible code. Is there any way to figure out where exactly the software is getting stuck from the address the runtimeErrorHandler spits out?
 

 My error handler prototype is: 
 

 void myRuntimeErrHandler(int error_code, int more_info,int xpc_val, int address)

 

 Any help with this would be greatly appreciated. I'm loosing faith in these RCM processors fast with their inability to report what is actually gone wrong even when you write a error handler to report just that to you!