ESENT Event ID 916 Causes Game Freeze and Eventual Crash

[BetaTime]

Event ID 916 has always been a prominent event in the Application log, for about as long as I've had Windows 10. I've never had cause for concern over it, though it does take up quite a bit of real estate. However, since purchasing my first Microsoft game (Sea of Thieves), I have been able to correlate freezes and eventual crashes to these events. There are a number of different instances of the event, from "DllHost" to "svchost" to "SettingSyncHost" claiming to be responsible. Sometimes there will be a flood of instances right in a row (usually during gameplay and just before a freeze).

I have done a lot of research online about this event, as well as this "EseDiskFlushConsistency" flag that says it's enabled. An example of the verbiage is here:

SettingSyncHost (7524,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.

And, while there are no shortage of questions on Microsoft, Technet and numerous third party forums, there are apparently ZERO solutions. No one, not even Microsoft has an answer or an explanation on how to disable this service or if it can be disabled at all. At least, as far as they're willing to offer up.

Some suggestions have been to disable any Qualcomm hardware or disable auto-trim for SSDs. Unfortunately, neither of these has worked. At this point, any explanation other than "this warning is harmless" from Microsoft themselves would be welcome.

What is ESENT?

What is EseDiskFlushConsistency?

Can EseDiskFlushConsistency be disabled? If so, how?

Can the application and/or hardware utilizing this service be determined? If so, how?

Does ESENT have any relationship with the Software Protection service?

Any light that can be shed on this issue would be WONDERFUL! I know that I'm not the only one experiencing these problems, as evidenced by a simple search for Event ID 916, EseDiskFlushConsistency or ESENT.

I will gladly post any system information that may be helpful to the cause, but at this point in my research, I've come to believe that this issue is specific to Windows 10.

Thank you in advance!

 

 

More...