Crashes due to event EseDiskFlushConsistency (916), ESENT

Hidde663 / My first build
July 5, 2018 at 07:39:58
Specs: Windows 10 Pro 64bit, i5-6600K[delid]@4.8GHz/4.4GHz@1.39v LLC=6 | 2x4GB Crucial-DDR4-2133CL15@14-14-14-30 1T 2800MHz@1.37v
For the past 2 days I've had applications randomly crash/hang for multiple seconds, even complete shutdowns. (no warnings/popups or anything)

Every time it happens i check event viewer and every time i see the event:
The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000 (event-id: 916) which had just been triggered seconds before.

At this point i do not know what to do, perhaps uninstalling some windows update packages or reinstalling windows 10...

But from what i can find on the web about it things like that wont help.

All i can find about this subject is that this event (916) has something to do with either pagefile and/or "search indexing"

Does anyone know how to overcome this pesky issue?

edit: mogaming's last post kinda sums up whats going on..:
https://forums.overclockers.co.uk/t...

PS, I've under-clocked my system to be sure its not hardware related.

System specs are currently:

i5-6600K[delid]@3.5GHz/3.5GHz@1.2v LLC=6
2x4GB Crucial-DDR4-2133CL15@15-15-15-36 2T 2133MHz@1.2v
MSI Armor RX 570 4GB@1268Mhz core@1.056v/1750MHz BiosModded
ASUS Z170-K
Samsung 250GB SSD 850 EVO (37GB free)
Corsair VS450 (450watt)
OS Windows 10 Pro 64bit (fully up-to-date as of 04-July-2018)

i5-6600K[delid]@4.8GHz/4.4GHz@1.39v LLC=6 | 2x4GB Crucial-DDR4-2133CL15@14-14-14-30 1T 2800MHz@1.37v
MSI Armor RX 570 4GB@1395Mhz core@1.168v/1920MHz BiosModded

message edited by hidde663


See More: Crashes due to event EseDiskFlushConsistency (916), ESENT

Reply ↓  Report •

#1
July 5, 2018 at 11:21:31
it seems to be memory corruption related, narrowing it down now

i5-6600K[delid]@4.8GHz/4.4GHz@1.39v LLC=6 | 2x4GB Crucial-DDR4-2133CL15@14-14-14-30 1T 2800MHz@1.37v
MSI Armor RX 570 4GB@1395Mhz core@1.168v/1920MHz BiosModded


Reply ↓  Report •

#2
July 5, 2018 at 12:24:37
Which Win10 build are you running? I think the latest is version 1803 (OS build 17134).

From the minimal searching I did, I ran across a few posts blaming the EseDiskFlushConsistency error on graphics drivers & another mentioned McAfee.


Reply ↓  Report •

#3
July 5, 2018 at 13:48:50
i havent crashed yet, since my last post

I'm using Microsoft Windows [Version 10.0.17134.137] according to WMIC, so you're correct :)

ive loosend memory timings, aswell as CPU cache clock, turned all my other Overclocks back one, gonna do some stress testing now.

seems like EseDiskFlushConsistency is just a cleanup after a program closes, so also when something else made the program crash.

anyways will let you know what happens

current settings:

i5-6600K[delid]@4.7GHz/4.0GHz@1.4v LLC=6
2x4GB Crucial-DDR4-2133CL15@14-14-14-36 1T 2800MHz@1.37v
MSI Armor RX 570 4GB@1355Mhz core@1.156v/1850MHz BiosModded

i5-6600K[delid]@4.8GHz/4.4GHz@1.39v LLC=6 | 2x4GB Crucial-DDR4-2133CL15@14-14-14-30 1T 2800MHz@1.37v
MSI Armor RX 570 4GB@1395Mhz core@1.168v/1920MHz BiosModded


Reply ↓  Report •

Related Solutions

#4
July 6, 2018 at 06:46:28
The problem disappeared completely, but i cannot guarantee what caused the issue, so i guess it can be marked as solved.

But my guesses so far are either:

[1] Memory corrupting caused by physical memory/CPU ring(/cache) clock/incorrectly trained physical memory.
[2] CPU degradation caused by high voltage
[3] Software issue(application)
[4] video driver issue (using a beta driver from AMD)

Again the Microsoft OS update does not seem to be the issue, the event just happens to be triggered every time an application closes (unexpected or not it does not matter), clearing RAM, page file, whatever.

Again, unless the issue re-appears I cannot conclude what caused it...

i5-6600K[delid]@4.8GHz/4.4GHz@1.39v LLC=6 | 2x4GB Crucial-DDR4-2133CL15@14-14-14-30 1T 2800MHz@1.37v
MSI Armor RX 570 4GB@1395Mhz core@1.168v/1920MHz BiosModded


Reply ↓  Report •

#5
July 6, 2018 at 13:35:43
"Again, unless the issue re-appears I cannot conclude what caused it..."

I can go through these logs & look for clues.

Please download Farbar Recovery Scan Tool and save it onto your Desktop. If your default download location is not the Desktop, drag it out of it's location onto the Desktop.
http://www.bleepingcomputer.com/dow...
If we have to run Farbar more than once, refer this SS.
http://i.imgur.com/yUxNw0j.gif
Note: You need to run the version compatible with your system. If you are not sure which version applies to your system download both of them and try to run them. Only one of them will run on your system, that will be the right version.
Double-click to run it. When the tool opens click Yes to disclaimer.
Press Scan button.
It will make a log (FRST.txt) on the Desktop.
The first time the tool is run, it makes also another log (Addition.txt) on the Desktop.
The logs are large, upload them using one of these. No time delays/Captcha-I'm not a Robot/account/registration needed. Give us the links please.
http://www.fileconvoy.com/index.php


Reply ↓  Report •

#6
July 6, 2018 at 21:07:57
If the logs are not conclusive then your best option is to bring back slowly to your original settings One at a time only and wait a few days between. I would however recommend going with the non-beta driver though. It is very possible that loosening the RAM timings a tad might be enough if it was the memory getting flaky. You should run Memtest86 through at least one complete cycle of their tests and some recommend more than once when overclocking memory or playing with the timings. The key to a 24/7 rig that is overclocked on the high side is to make only one setting adjustment, test, and then real world test for days or maybe a week once you get near the limits. If things get flaky then back off on one setting only and retest to compare the results.

You have to be a little bit crazy to keep you from going insane.


Reply ↓  Report •

#7
July 7, 2018 at 03:43:07
I'm already back at my highest stable overclock, no need to spend time on fixing this issue anymore, but thanks for the suggestion.

If it does re-appear I'll send some logs ;)

i5-6600K[delid]@4.8GHz/4.4GHz@1.39v LLC=6 | 2x4GB Crucial-DDR4-2133CL15@14-14-14-30 1T 2800MHz@1.37v
MSI Armor RX 570 4GB@1395Mhz core@1.168v/1920MHz BiosModded


Reply ↓  Report •

Ask Question