Most product drivers use the functionality of mfehidk.sys to perform work. When a driver is first started, it initiates communication with mfehidk.sys.
 

This initial communication isn't thread-safe in some versions of SysCore 15.6. If multiple drivers start at the same time, it's possible for two drivers to receive a pointer to the same data from mfehidk.sys. When one driver finishes with the data, it frees the memory, which leads to a crash when the other driver tries to access the freed memory. This race condition is fixed in SysCore 15.7.