Windows 10: Esent 447 And Pc Freezing

First of all, my problem is that when I enter a game on the computer, my computer freezes frequently within 1-2 weeks and automatically closes applications such as discord and rust. now it keeps giving this error Someone can help me pls??? :C



:)

 

ESENT error causes computer to freeze

After i installed the Fall Creators Update, my computer keeps randomly freezing. I looked in the Event Viewer, and i see this

"DllHost (5888,G,98) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000."

How do i disable or remove ESENT/EseDiskFlushConsistency? it causes my computer to freeze up CONSTANTLY when im playing games, and for most competitive games that i play, each second is crucial... i lost a few games
worth money because of this.

Again, never had this issue till i installed the Fall Creators Update

 

PC freezes when navigating to any drive or folder

I looked up the Event Viewer right after another computer freeze, which occur when I try to save a file of any kind - Word document, image, music. I found an information event that says "DllHost (10308,G,98) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000." However, I see this event having occurred many other times when I did not realize a freeze.

I googled it and found that others have also experienced computer freezes playing games related to this event. My Google search link is beta feature esediskflushconsistency is enabled in esent - Google Search.

I read some of the discussions, but I am not sure exactly what I can do to move forward.

As for the suggestions made in the other posts, I have update Roboform to 8.9. I also ran HD Tune. It gave a 100% green map after Error Scan and an empty list under the Health tab.

 

ESENT error, event ID 447, 467, 530, 537, 544

I've been getting the following errors in event viewer constantly every minute for a while. I've tried a couple of solutions throught command prompt, using System File Checker and DISM but neither gave me any results. I'm worried its a hardware issue.

Thanks in advance!

ESENT error 447:

svchost (3444,D,21) SRUJet: A bad page link (error -338) has been detected in a B-Tree (ObjectId: 14, PgnoRoot: 49) of database C:\Windows\system32\SRU\SRUDB.dat (49 => 2658, 14).

ESENT error 467:

svchost (3444,D,23) SRUJet: Database C:\Windows\system32\SRU\SRUDB.dat: Index UserIdTimeStamp of table {5C8CF1C7-7257-4F13-B223-970EF5939312} is corrupted (0).

ESENT error 530:

svchost (3444,D,22) SRUJet: The database page read from the file "C:\Windows\system32\SRU\SRUDB.dat" at offset 2514944 (0x0000000000266000) (database page 613 (0x265)) for 4096 (0x00001000) bytes failed verification due to a lost flush detection timestamp
mismatch. The read operation will fail with error -1119 (0xfffffba1).

The flush state on database page 613 (0x265) was 2 while the flush state on flush map page 0 (0x0) was 1.

If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

ESENT error 537:

svchost (3444,D,22) SRUJet: A request for a node on an empty page (Pgno: 1235) has been made (error -351) for a B-Tree (ObjectId: 18, PgnoRoot: 79) of database C:\Windows\system32\SRU\SRUDB.dat. This is typically due to a lost I/O from storage hardware.
Please check with your hardware vendor for latest firmware revisions, make changes to your controller's caching parameters, use crash consistent hardware with Forced Unit Access support, and/or replace faulty hardware.

ESENT error 544:

svchost (3568,D,22) SRUJet: The database page read from the file "C:\Windows\system32\SRU\SRUDB.dat" at offset 884736 (0x00000000000d8000) (database page 215 (0xD7)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection
timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1).

The flush state on database page 215 (0xD7) was 3 while the flush state on flush map page 0 (0x0) was 2.

If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.