ESENT Errors windows 10

Thor · Apr 5, 2017

Lately my machine freezes often for 10 - 50 seconds sometimes it would freeze but I can still move between windows but it wont do anything other times it would freeze to such a degree that I cannot move my mouse curser.

I have no idea what this can be I noticed it after that last "major" update.

This is recently from my event viewer, but again I am not entirely sure what I am looking at although these time stamps correlate to the freezes.

Code:

Log Name:      Application
Source:        ESENT
Date:          4/5/2017 5:34:39 PM
Event ID:      533
Task Category: (1)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Thor
Description:
taskhostw (2084) WebCacheLocal: A request to write to the file "C:\Users\Princess Thor\AppData\Local\Microsoft\Windows\WebCache\V01.log" at offset 126976 (0x000000000001f000) for 4096 (0x00001000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ESENT" />
    <EventID Qualifiers="0">533</EventID>
    <Level>3</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-04-05T15:34:39.199127200Z" />
    <EventRecordID>36660</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Thor</Computer>
    <Security />
  </System>
  <EventData>
    <Data>taskhostw</Data>
    <Data>2084</Data>
    <Data>WebCacheLocal: </Data>
    <Data>C:\Users\Princess Thor\AppData\Local\Microsoft\Windows\WebCache\V01.log</Data>
    <Data>126976 (0x000000000001f000)</Data>
    <Data>4096 (0x00001000)</Data>
    <Data>36</Data>
  </EventData>
</Event>

Code:

Log Name:      Application
Source:        ESENT
Date:          4/5/2017 5:34:39 PM
Event ID:      508
Task Category: (7)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Thor
Description:
taskhostw (2084) WebCacheLocal: A request to write to the file "C:\Users\Princess Thor\AppData\Local\Microsoft\Windows\WebCache\V01.log" at offset 126976 (0x000000000001f000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (36 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ESENT" />
    <EventID Qualifiers="0">508</EventID>
    <Level>3</Level>
    <Task>7</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-04-05T15:34:39.202056900Z" />
    <EventRecordID>36661</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Thor</Computer>
    <Security />
  </System>
  <EventData>
    <Data>taskhostw</Data>
    <Data>2084</Data>
    <Data>WebCacheLocal: </Data>
    <Data>C:\Users\Princess Thor\AppData\Local\Microsoft\Windows\WebCache\V01.log</Data>
    <Data>126976 (0x000000000001f000)</Data>
    <Data>4096 (0x00001000)</Data>
    <Data>36</Data>
  </EventData>
</Event>

Code:

Log Name:      Application
Source:        ESENT
Date:          4/5/2017 5:36:16 PM
Event ID:      508
Task Category: (7)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Thor
Description:
wuaueng.dll (1028) SUS20ClientDataStore: A request to write to the file "C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.edb" at offset 57524224 (0x00000000036dc000) for 16384 (0x00004000) bytes succeeded, but took an abnormally long time (40 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ESENT" />
    <EventID Qualifiers="0">508</EventID>
    <Level>3</Level>
    <Task>7</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-04-05T15:36:16.226340400Z" />
    <EventRecordID>36665</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Thor</Computer>
    <Security />
  </System>
  <EventData>
    <Data>wuaueng.dll</Data>
    <Data>1028</Data>
    <Data>SUS20ClientDataStore: </Data>
    <Data>C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.edb</Data>
    <Data>57524224 (0x00000000036dc000)</Data>
    <Data>16384 (0x00004000)</Data>
    <Data>40</Data>
  </EventData>
</Event>

Code:

Log Name:      Application
Source:        ESENT
Date:          4/5/2017 6:14:42 PM
Event ID:      508
Task Category: (7)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Thor
Description:
svchost (1692) TILEREPOSITORYS-1-5-21-1675508909-3288585533-1148783822-1001: A request to write to the file "C:\Users\Princess Thor\AppData\Local\TileDataLayer\Database\EDB.log" at offset 1904640 (0x00000000001d1000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (22 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ESENT" />
    <EventID Qualifiers="0">508</EventID>
    <Level>3</Level>
    <Task>7</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-04-05T16:14:42.194939400Z" />
    <EventRecordID>36666</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Thor</Computer>
    <Security />
  </System>
  <EventData>
    <Data>svchost</Data>
    <Data>1692</Data>
    <Data>TILEREPOSITORYS-1-5-21-1675508909-3288585533-1148783822-1001: </Data>
    <Data>C:\Users\Princess Thor\AppData\Local\TileDataLayer\Database\EDB.log</Data>
    <Data>1904640 (0x00000000001d1000)</Data>
    <Data>4096 (0x00001000)</Data>
    <Data>22</Data>
  </EventData>
</Event>

Code:

Log Name:      Application
Source:        ESENT
Date:          4/5/2017 6:30:10 PM
Event ID:      508
Task Category: (7)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Thor
Description:
DllHost (6368) Microsoft.Windows.Cortana_cw5n1h2txyewy_NOEDP_LEGACY_IDB: A request to write to the file "C:\Users\Princess Thor\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\AppData\Indexed DB\edb.log" at offset 516096 (0x000000000007e000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (35 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ESENT" />
    <EventID Qualifiers="0">508</EventID>
    <Level>3</Level>
    <Task>7</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-04-05T16:30:10.209819200Z" />
    <EventRecordID>36670</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Thor</Computer>
    <Security />
  </System>
  <EventData>
    <Data>DllHost</Data>
    <Data>6368</Data>
    <Data>Microsoft.Windows.Cortana_cw5n1h2txyewy_NOEDP_LEGACY_IDB: </Data>
    <Data>C:\Users\Princess Thor\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\AppData\Indexed DB\edb.log</Data>
    <Data>516096 (0x000000000007e000)</Data>
    <Data>4096 (0x00001000)</Data>
    <Data>35</Data>
  </EventData>
</Event>

Code:

Log Name:      Application
Source:        ESENT
Date:          4/5/2017 6:30:10 PM
Event ID:      507
Task Category: (7)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Thor
Description:
SearchIndexer (6656) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 24215552 (0x0000000001718000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (33 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ESENT" />
    <EventID Qualifiers="0">507</EventID>
    <Level>3</Level>
    <Task>7</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-04-05T16:30:10.210795600Z" />
    <EventRecordID>36671</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Thor</Computer>
    <Security />
  </System>
  <EventData>
    <Data>SearchIndexer</Data>
    <Data>6656</Data>
    <Data>Windows: </Data>
    <Data>C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb</Data>
    <Data>24215552 (0x0000000001718000)</Data>
    <Data>32768 (0x00008000)</Data>
    <Data>33</Data>
  </EventData>
</Event>

Any idea? (I know it says faulty hardware, but I am not buying it.)

gregmcc · Apr 5, 2017

Does the system event log report any hard drive issues?

Thor · Apr 5, 2017

gregmcc said:
Does the system event log report any hard drive issues?

None that I can see?

It's a ADATA SP900 SSD if I remember correctly.

gregmcc · Apr 5, 2017

Check your drive for errors.
sfc /scannow

Thor · Apr 5, 2017

One moment

Thor · Apr 5, 2017

gregmcc said:
Check your drive for errors.
sfc /scannow

Thor · Apr 5, 2017

I just experienced it again. Convinced this is it, here is all the errors.

Code:

Log Name:      Application
Source:        ESENT
Date:          4/5/2017 9:52:27 PM
Event ID:      510
Task Category: (7)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Thor
Description:
taskhostw (2084) WebCacheLocal: A request to write to the file "C:\Users\Princess Thor\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.jfm" at offset 0 (0x0000000000000000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (36 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 61 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ESENT" />
    <EventID Qualifiers="0">510</EventID>
    <Level>3</Level>
    <Task>7</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-04-05T19:52:27.189368300Z" />
    <EventRecordID>36700</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Thor</Computer>
    <Security />
  </System>
  <EventData>
    <Data>taskhostw</Data>
    <Data>2084</Data>
    <Data>WebCacheLocal: </Data>
    <Data>C:\Users\Princess Thor\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.jfm</Data>
    <Data>0 (0x0000000000000000)</Data>
    <Data>8192 (0x00002000)</Data>
    <Data>36</Data>
    <Data>0</Data>
    <Data>61</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        ESENT
Date:          4/5/2017 9:52:27 PM
Event ID:      510
Task Category: (7)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Thor
Description:
taskhostw (2084) WebCacheLocal: A request to write to the file "C:\Users\Princess Thor\AppData\Local\Microsoft\Windows\WebCache\V01.log" at offset 270336 (0x0000000000042000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (36 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 62 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ESENT" />
    <EventID Qualifiers="0">510</EventID>
    <Level>3</Level>
    <Task>7</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-04-05T19:52:27.188391800Z" />
    <EventRecordID>36699</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Thor</Computer>
    <Security />
  </System>
  <EventData>
    <Data>taskhostw</Data>
    <Data>2084</Data>
    <Data>WebCacheLocal: </Data>
    <Data>C:\Users\Princess Thor\AppData\Local\Microsoft\Windows\WebCache\V01.log</Data>
    <Data>270336 (0x0000000000042000)</Data>
    <Data>4096 (0x00001000)</Data>
    <Data>36</Data>
    <Data>0</Data>
    <Data>62</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        ESENT
Date:          4/5/2017 9:52:27 PM
Event ID:      510
Task Category: (7)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Thor
Description:
taskhostw (2084) WebCacheLocal: A request to write to the file "C:\Users\Princess Thor\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat" at offset 86671360 (0x00000000052a8000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (36 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 62 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ESENT" />
    <EventID Qualifiers="0">510</EventID>
    <Level>3</Level>
    <Task>7</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-04-05T19:52:27.187415100Z" />
    <EventRecordID>36698</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Thor</Computer>
    <Security />
  </System>
  <EventData>
    <Data>taskhostw</Data>
    <Data>2084</Data>
    <Data>WebCacheLocal: </Data>
    <Data>C:\Users\Princess Thor\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat</Data>
    <Data>86671360 (0x00000000052a8000)</Data>
    <Data>32768 (0x00008000)</Data>
    <Data>36</Data>
    <Data>0</Data>
    <Data>62</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        ESENT
Date:          4/5/2017 9:52:27 PM
Event ID:      533
Task Category: (1)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Thor
Description:
taskhostw (2084) WebCacheLocal: A request to write to the file "C:\Users\Princess Thor\AppData\Local\Microsoft\Windows\WebCache\V01.log" at offset 270336 (0x0000000000042000) for 4096 (0x00001000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ESENT" />
    <EventID Qualifiers="0">533</EventID>
    <Level>3</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-04-05T19:52:27.186438300Z" />
    <EventRecordID>36697</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Thor</Computer>
    <Security />
  </System>
  <EventData>
    <Data>taskhostw</Data>
    <Data>2084</Data>
    <Data>WebCacheLocal: </Data>
    <Data>C:\Users\Princess Thor\AppData\Local\Microsoft\Windows\WebCache\V01.log</Data>
    <Data>270336 (0x0000000000042000)</Data>
    <Data>4096 (0x00001000)</Data>
    <Data>36</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        ESENT
Date:          4/5/2017 9:52:27 PM
Event ID:      533
Task Category: (1)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Thor
Description:
taskhostw (2084) WebCacheLocal: A request to write to the file "C:\Users\Princess Thor\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.jfm" at offset 0 (0x0000000000000000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ESENT" />
    <EventID Qualifiers="0">533</EventID>
    <Level>3</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-04-05T19:52:27.185462100Z" />
    <EventRecordID>36696</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Thor</Computer>
    <Security />
  </System>
  <EventData>
    <Data>taskhostw</Data>
    <Data>2084</Data>
    <Data>WebCacheLocal: </Data>
    <Data>C:\Users\Princess Thor\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.jfm</Data>
    <Data>0 (0x0000000000000000)</Data>
    <Data>8192 (0x00002000)</Data>
    <Data>36</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        ESENT
Date:          4/5/2017 9:52:09 PM
Event ID:      533
Task Category: (1)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Thor
Description:
taskhostw (2084) WebCacheLocal: A request to write to the file "C:\Users\Princess Thor\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat" at offset 86671360 (0x00000000052a8000) for 32768 (0x00008000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ESENT" />
    <EventID Qualifiers="0">533</EventID>
    <Level>3</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-04-05T19:52:09.639116300Z" />
    <EventRecordID>36695</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Thor</Computer>
    <Security />
  </System>
  <EventData>
    <Data>taskhostw</Data>
    <Data>2084</Data>
    <Data>WebCacheLocal: </Data>
    <Data>C:\Users\Princess Thor\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat</Data>
    <Data>86671360 (0x00000000052a8000)</Data>
    <Data>32768 (0x00008000)</Data>
    <Data>36</Data>
  </EventData>
</Event>

MANY MORE -> https://gist.github.com/ErikThiart/fd839845047462a9869baabad41dee77 (there is too many to list here the character limit gets hit)

backstreetboy · Apr 5, 2017

Upgrade to the Creators update https://support.microsoft.com/en-us/help/3159635/windows-10-update-assistant

Thor · Apr 5, 2017

backstreetboy said:
Upgrade to the Creators update https://support.microsoft.com/en-us/help/3159635/windows-10-update-assistant

Not sure what to do there it says thanks for upgrading to windows 10

Thor · Apr 5, 2017

I am on windows 10 - 10.0.14393 Build 14393

backstreetboy · Apr 5, 2017

Thor187 said:
Not sure what to do there it says thanks for upgrading to windows 10

Suppose to take you to the Update Assistant anyway here's the ISO https://mdl-tb.ct8.pl/getDirect.php?fileName=Win10_1703_English_x64.iso

Thor · Apr 5, 2017

Thor187 said:
I am on windows 10 - 10.0.14393 Build 14393

backstreetboy said:
Suppose to take you to the Update Assistant anyway here's the ISO https://mdl-tb.ct8.pl/getDirect.php?fileName=Win10_1703_English_x64.iso

Am I not on it?

Thor · Apr 5, 2017

Primary SSD looks good to me so cannot be a harddrive issue.

gregmcc · Apr 5, 2017

Hmm - no errors found. Could be weird Windows bug. Are all your drivers/firmware etc up to date?

backstreetboy · Apr 5, 2017

Thor187 said:
Am I not on it?

No this is the latest fresh off the press Creators update build 10.0.15063 version 1703.

Thor · Apr 5, 2017

gregmcc said:
Hmm - no errors found. Could be weird Windows bug. Are all your drivers/firmware etc up to date?

Dammit I hate MS so god damn much. I updated everything as I first thought it was graphics related

backstreetboy said:
No this is the latest fresh off the press Creators update build 10.0.15063 version 1703.

Okey let me get that!

This is what happens:

then

backstreetboy · Apr 5, 2017

Thor187 said:
Dammit I hate MS so god damn much. I updated everything as I first thought it was graphics related

Okey let me get that!

This is what happens:

then

It's probably still rolling out for all regions. Try running it tomorrow morning again or download the ISO I shared, mount it and hit on setup.exe

Thor · Apr 5, 2017

backstreetboy said:
It's probably still rolling out for all regions. Try running it tomorrow morning again or download the ISO I shared, mount it and hit on setup.exe

Will the ISO overwrite my files or just kick a update?

backstreetboy · Apr 5, 2017

Thor187 said:
Will the ISO overwrite my files or just kick a update?

It'll ask you but the default AFAIK is to save your files and apps.

Thor · Apr 5, 2017

MMMM i will run it tomorrow way to tired to concentrate right now.

Thanks for the help btw. I downloaded it so long.

Join the MyBroadband community

Get started

ESENT Errors windows 10

Honorary Master

Honorary Master

Honorary Master

Honorary Master

Honorary Master

Honorary Master

Honorary Master

Honorary Master

Honorary Master

Honorary Master

Honorary Master

Honorary Master

Honorary Master

Honorary Master

Honorary Master

Honorary Master

Honorary Master

Honorary Master

Honorary Master

Honorary Master