Windows 10: EseDiskFlushConsistency

  1.    29 Oct 2017 #1

    EseDiskFlushConsistency


    So since the 1709 upgrade, I'm seeing the following quite a few times in my event logs: "The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000." From my Google searches, I can deduce that this is benign and that I'm nowhere near the only one seeing this, but it's spammy as all getout. Is there any way to at least get it to stop logging it so darn much?
      My ComputerSystem Spec

  2.    17 Nov 2017 #2

    Hi RaveBlack actually Im trying to resolve weird unexpected reboots /crashing. This entry also appears in my log just before and after the computer crashes...Im not saying its responsible but I would also like to know what this does...
      My ComputerSystem Spec


  3. Posts : 1
    Windows 10 1709
       23 Nov 2017 #3

    I'm having the same trouble as mwake, anybody find a solution?
      My ComputerSystem Spec


  4. Posts : 480
    Win10 x64 Pro -2 desktops, 1 laptop
       14 Dec 2017 #4

    I'm seeing about 2 of these events an hour. No crashes, though.
      My ComputerSystem Spec

  5.    19 Jan 2018 #5

    found one possible solution on reddit:
    Stop "SmartByte Network Service" and disable it's start up

    Beta feature in Windows Update? : Dell
    hope it helps.

    Had a crash after exactly 24hrs of uptime again - with the Dell Services disabled... So decided to take it into my own hands - I've got 20+ years in the IT industry, so how hard could it be? :)
    Others reporting the problem with other Dell laptops pointed towards Killer Networking adapters - which the 7577 doesn't have... But the 7577 does have something called SmartByte, which comes from a company called Rivet Networks - and Rivet Networks is the company behind Killer Networking...
    My spidey senses are tingling...
    Stop "SmartByte Network Service" and disable it's start up...
    26 hours of uptime and counting
      My ComputerSystem Spec

  6.    20 Mar 2018 #6

    Bumpety bump

    I do experience all the above infrequently: unexplained BSODs without any reason, with very little information in MiniDMP files (NTOSKRNL.EXE, memory corruption), but slight hints of EseDiskFlushConsistency entry usually sitting in the EventLog before such crash takes place.

    My machine (both hardware & software) is definitely okay, Windows up to date, no dodgy software / drivers, have also recently run Verifier for couple of days as well and all was sweet.

    Judging by what I just read elsewhere (Reddit, MS Forums etc.) this remains complete mystery but my fingers are pointing towards it.

    So, any takers on this one?
      My ComputersSystem Spec


  7. Posts : 1
    Windows 10 Pro x64
       14 May 2018 #7

    krzemien said: View Post
    Bumpety bump

    I do experience all the above infrequently: unexplained BSODs without any reason, with very little information in MiniDMP files (NTOSKRNL.EXE, memory corruption), but slight hints of EseDiskFlushConsistency entry usually sitting in the EventLog before such crash takes place.

    My machine (both hardware & software) is definitely okay, Windows up to date, no dodgy software / drivers, have also recently run Verifier for couple of days as well and all was sweet.

    Judging by what I just read elsewhere (Reddit, MS Forums etc.) this remains complete mystery but my fingers are pointing towards it.

    So, any takers on this one?
    I just had this exact situation on build 17134. Have you been able to find out anything about preventing it?
      My ComputerSystem Spec

  8.    14 May 2018 #8

    I'm not getting any unexplained BSODs, but I'm still seeing these. Would've thought something would've been done about it in this latest upgrade, but no go.
      My ComputerSystem Spec

  9.    14 Aug 2018 #9

    This error started appearing on my research assistant's computer after I enabled RAMJET in System Mechanic 18 this morning. I had read somewhere that this message had to do with managing RAM. Disabling RAMJET ended the messages.

    I realize this won't solve everybody's problem with this error, but if you've got something running in the background that defrags RAM or otherwise makes more RAM available, that might be the reason you're getting this message.
      My ComputerSystem Spec


 

Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 22:43.
Find Us