I’m not sure if you could perform something like that, since there is no higher execution entry point in each module where you could handle all their exceptions.
On the other hand, if you try to achieve this scenario to know where the exception occurs and based on this perform a particular action, you could be able to know the name of the assembly by reading the property Exception.Source. To make this option valid,
you must initialize only one module per assembly.
Additionally, please take into account that once modules are loaded there is not way to unload them.
Please let me know if this helps.