A number of test across Storage Execution and Replication intentionally terminate server processes to test recovery.  Windows builds attempt to create a minidump in the exception handler triggered by process termination.  This can lead to "Loader Lock" where the process hangs while trying to write the minidump file.  

This appeared to be solved in, SERVER-116978 by loading the DbgHelp library at startup, but BFs have still occurred since. 

A few suggestions on how to fix this: 

• Remove minidump creation entirely
• Allow setting a server parameter or failpoint that enables/disables minidump writing to be used with tests that intentionally fail the server