The log files provided appear to show an access violation as the cause of the crash. This means that the blueprint was likely trying to refer to something that either did not exist / had not been set yet. If you were able to create a new copy of the blueprint that works then it would be best to just stick with that.
We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will follow up.