Windows 10: Event log full of ESENT event id 916

I've seen this discussed several times but nothing lately and nothing saying what to do about it.

Multiple times per hour - anything from 1 to 5 (so far) I get the following event logged:
Log Name: Application
Source: ESENT
Date: 12/29/2017 10:27:21 AM
Event ID: 916
Task Category: General
Level: Information
Keywords: Classic
User: N/A
Computer: Puget-116877
Description:
svchost (3644,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="ESENT" />
<EventID Qualifiers="0">916</EventID>
<Level>4</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-12-29T18:27:21.128090100Z" />
<EventRecordID>1695</EventRecordID>
<Channel>Application</Channel>
<Computer>Puget-116877</Computer>
<Security />
</System>
<EventData>
<Data>svchost</Data>
<Data>3644,G,0</Data>
<Data>
</Data>
<Data>EseDiskFlushConsistency</Data>
<Data>ESENT</Data>
<Data>0x800000</Data>
</EventData>
</Event>

About 37% of Application event records s on my PC are this record.

I see no problems on my PC that I can relate to the events so I doubt they are indicating a major problem, but they certainly clutter up the log making it more difficult to find significant event records. So I've got a few questions.

• Does everybody get these or are they specific to my hardware/software/whatever environment?
• What is EseDiskFlushConsistency this function" Is it something that can be disabled?
• Is there any way to block the recording of these records or to do a mass deletion of them?

:)

 

my screen flickers when ESENT and windows security auditing works

Occasionally my laptop's screen flickers. Every time it flickers I check the windows event log and I see two things at the exact time of screen flickering. 1. ESENT event id 916 2. Windows security auditing event id 4624 and event id 4672 . Sometimes it
flickers only once, sometimes two or three times consecutively. However reverse is not true, when these two events happen in the background my screen does not flicker every time. Although this does not cause any problem other than occasional annoyance, i'd
like to know if there is any solution.

 

ESENT Events 454 and 517...

Hi,

Event ID: 454 Source: ESENT

Related Thread

ESENT Event IDs

517 Event ID - no information

Related 517 Event ID thread

- "Generally error 517 is caused that there is no enough storage space for saving the backup. Please first check if there is enough free space on target location."

Windows Security Log Events

Hope this helps.

 

Some information here: https://www.reddit.com/r/Dell/commen...indows_update/

 

Not sure about disabling that log in Event Viewer, but you can clear the Event Viewer - Clear All Event Logs in Event Viewer in Windows Performance Maintenance Tutorials

 

I saw that but it didn't provide much advice except "I wouldn't worry too much about it".

I notice that the timing of the events reported by one person doesn't match mine at all. Mine seem to have no timing relationship with each other.

I'd rather not clear all the events. That would make it really hard to find the important ones. I couldn't tell whether filering first and doing a Clear would delete just the filtered records or all of them so I think I'll live with the records.

 

Hi,

That's what matters but there's no way I can think of to stop it though. It's informational and pretty harmless and a coding error it seems.

Cheers, *Wink

 

It's just an informational entry. It does not indicate any kind of error condition. Ignore it for now and eventually MS will fix it or someone will come up with a way to get rid of it.

I had hundreds of them in my Event Viewer as well. I just cleaned the entire Event Viewer logs since my system is running well and is not having any problems. I've not had any since 2:19PM when I cleared it.

 

Same thing after las recent update....

 

What if this is a way for the disk flush to happen for spectre or meltdown fix?