Seen here while Mongo Orchestration is trying to start a sharded cluster with two mongos servers, two standalone shards, and a single-node config server as replica set:
https://evergreen.mongodb.com/version/57a7b8373ff12252cd00010a
The config server crashes:
2016-08-08T01:47:30.552+0100 I CONTROL [rsSync] *** unhandled exception (access violation) at 0x000000013FE6F0A3, terminating
2016-08-08T01:47:30.552+0100 I CONTROL [rsSync] *** access violation was a read from 0x0000000000000000
2016-08-08T01:47:30.552+0100 I CONTROL [rsSync] *** stack trace for unhandled exception:
2016-08-08T01:47:31.077+0100 I CONTROL [rsSync] mongod.exe ...\src\mongo\db\repl\replication_coordinator_external_state_impl.cpp(499) mongo::repl::ReplicationCoordinatorExternalStateImpl::shardingOnDrainingStateHook+0xa3
It appears not to happen unless auth is enabled. This is a nightly build from git hash 9cf1165c. Log and minidump attached. I believe that I can repro on demand.