computing
  • 0

Solved Crashes Due To Event EseDiskFlushConsistency (916), ESENT

  • 0

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]test6513316.5GHz/3.5GHztest6513316.2v LLC=6
2x4GB Crucial-DDR4-2133CL15test65133165-15-15-36 2T 2133MHztest6513316.2v
MSI Armor RX 570 4GBtest6513316268Mhz coretest6513316.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]test31404562.8GHz/4.4GHztest6513316.39v LLC=6 | 2x4GB Crucial-DDR4-2133CL15test65133164-14-14-30 1T 2800MHztest6513316.37v
MSI Armor RX 570 4GBtest6513316395Mhz coretest6513316.168v/1920MHz BiosModded

Share

1 Answer

  1. 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.

    • 0