Windows 10: Windows 10 (64 bit) hangs during update with ESENT event id 508 and 510

Discus and support Windows 10 (64 bit) hangs during update with ESENT event id 508 and 510 in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello, My windows 10 pc works fine normally. Today i started windows update and pc started lagging a lot, applications would resond after 30-40... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by NileshTambe1, Sep 11, 2019.

  1. Windows 10 (64 bit) hangs during update with ESENT event id 508 and 510


    Hello,

    My windows 10 pc works fine normally. Today i started windows update and pc started lagging a lot, applications would resond after 30-40 seconds.

    Checked event viewer and found events 508 and 510.

    Cannot post event details as pc has sort of frozen and i am using mobile to post this. Waiting for the update to get installed. Then i will be able to post event details. Meanwhile, if anyone could suggest some solutions i would be grateful.

    Thanks.


    Edit: Event details

    ****************************************************************************************************************************************************************

    Log Name: Application

    Source: ESENT

    Date: 11-09-2019 14:06:59

    Event ID: 508

    Task Category: Performance

    Level: Warning

    Keywords: Classic

    User: N/A

    Computer: ****

    Description:

    taskhostw (2360,D,0) WebCacheLocal: A request to write to the file "C:\Users\niles\AppData\Local\Microsoft\Windows\WebCache\V01tmp.log" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (89 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="2019-09-11T08:36:59.206927400Z" />

    <EventRecordID>7720</EventRecordID>

    <Channel>Application</Channel>

    <Computer></Computer>

    <Security />

    </System>

    <EventData>

    <Data>taskhostw</Data>

    <Data>2360,D,0</Data>

    <Data>WebCacheLocal: </Data>

    <Data>C:\Users\niles\AppData\Local\Microsoft\Windows\WebCache\V01tmp.log</Data>

    <Data>0 (0x0000000000000000)</Data>

    <Data>4096 (0x00001000)</Data>

    <Data>89</Data>

    </EventData>

    </Event>

    ****************************************************************************************************************************************************************


    Log Name: Application

    Source: ESENT

    Date: 11-09-2019 14:08:29

    Event ID: 510

    Task Category: Performance

    Level: Warning

    Keywords: Classic

    User: N/A

    Computer:

    Description:

    taskhostw (2360,D,0) WebCacheLocal: A request to write to the file "C:\Users\niles\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat" at offset 32768 (0x0000000000008000) for 32768 (0x00008000) bytes succeeded, but took an abnormally long time (29 seconds) to be serviced by the OS. In addition, 4 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 1217 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="2019-09-11T08:38:29.207485600Z" />

    <EventRecordID>7721</EventRecordID>

    <Channel>Application</Channel>

    <Computer></Computer>

    <Security />

    </System>

    <EventData>

    <Data>taskhostw</Data>

    <Data>2360,D,0</Data>

    <Data>WebCacheLocal: </Data>

    <Data>C:\Users\niles\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat</Data>

    <Data>32768 (0x0000000000008000)</Data>

    <Data>32768 (0x00008000)</Data>

    <Data>29</Data>

    <Data>4</Data>

    <Data>1217</Data>

    </EventData>

    </Event>

    ****************************************************************************************************************************************************************



    Log Name: Application

    Source: ESENT

    Date: 11-09-2019 14:02:23

    Event ID: 533

    Task Category: General

    Level: Warning

    Keywords: Classic

    User: N/A

    Computer:

    Description:

    qmgr.dll (7280,T,0) QmgrDatabaseInstance: A request to write to the file "C:\ProgramData\Microsoft\Network\Downloader\qmgr.db" at offset 0 (0x0000000000000000) for 16384 (0x00004000) 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="2019-09-11T08:32:23.415620300Z" />

    <EventRecordID>7712</EventRecordID>

    <Channel>Application</Channel>

    <Computer></Computer>

    <Security />

    </System>

    <EventData>

    <Data>qmgr.dll</Data>

    <Data>7280,T,0</Data>

    <Data>QmgrDatabaseInstance: </Data>

    <Data>C:\ProgramData\Microsoft\Network\Downloader\qmgr.db</Data>

    <Data>0 (0x0000000000000000)</Data>

    <Data>16384 (0x00004000)</Data>

    <Data>36</Data>

    </EventData>

    </Event>

    ****************************************************************************************************************************************************************

    :)
     
    NileshTambe1, Sep 11, 2019
    #1
  2. alpha45 Win User

    Occur several warning: ESENT origin; event id 508, 510, 533


    Occur several warning: ESENT origin; event id 508, 510, 533
    SettingSyncHost (3644) {8DD9444F-A80E-497B-8417-F165C45BF16F}: A write request in the file "C:\Users\Piero\AppData\Local\Microsoft\Windows\SettingSync\remotemetastore\v1\meta.edb" all'offset 3686400(0x0000000000384000) to 16384 (0x00004000 )bytes has not been completed for 36 seconds. The problem is likely due to faulty hardware. Contact your hardware vendor for assistance in locating the problem.
    Thank you

    Windows 10 (64 bit) hangs during update with ESENT event id 508 and 510 [​IMG]
     
    alpha45, Sep 11, 2019
    #2
  3. JohnBurns Win User
    Occur several warning: ESENT origin; event id 508, 510, 533


    FWIW , alpha, I have the same problem occasionally, but there are no hardware problems. I can't provide you an answer to solve this, but I believe it's just a quirk of Windows 10 reacting to something we may have installed that it does not like. Sorry I can't be of more help, but I have tried everywhere I know to find a solution with no success. Will post here if I am ever successful.
     
    JohnBurns, Sep 11, 2019
    #3
  4. vram Win User

    Windows 10 (64 bit) hangs during update with ESENT event id 508 and 510

    Event ID 508 and 510


    Looks Fine to me:


    Windows 10 (64 bit) hangs during update with ESENT event id 508 and 510 [​IMG]
     
Thema:

Windows 10 (64 bit) hangs during update with ESENT event id 508 and 510

Loading...
  1. Windows 10 (64 bit) hangs during update with ESENT event id 508 and 510 - Similar Threads - bit hangs during

  2. Windows 10 hangs during update with ESENT event id 508 and 510

    in Windows 10 BSOD Crashes and Debugging
    Windows 10 hangs during update with ESENT event id 508 and 510: Hello, My windows 10 pc works fine normally. Today i started windows update and pc started lagging a lot, applications would resond after 30-40 seconds. Checked event viewer and found events 508 and 510. Cannot post event details as pc has sort of frozen and i am using...
  3. System Freezing - ESENT 533, 508, 510

    in Windows 10 Support
    System Freezing - ESENT 533, 508, 510: Hi there, Last night the programmes on my PC all froze a couple of times. Each time it lasted for about 3 minutes, then they started working again. The first time it was when I was trying to open a web page. The second time it happened when I pressed the home button. When I...
  4. System Freezing - ESENT 533, 508, 510

    in Windows 10 Drivers and Hardware
    System Freezing - ESENT 533, 508, 510: Last night the programmes on my PC all froze a couple of times. Each time it lasted for about 3 minutes, then they started working again. The first time it was when I was trying to open a web page. The second time it happened when I pressed the home button. When I...
  5. Windows 10 64 bit PRO - IRSTRSV event id 0

    in Windows 10 Drivers and Hardware
    Windows 10 64 bit PRO - IRSTRSV event id 0: Windows 8.1 64bit PRO updated to Windows 10 PRO - intel rst 14.5.2.1088 by station-drivers I see this irstrtsv error in the Event Viewer. id event 0 The description for Event ID 0 from source irstrtsv cannot be found. Either the component that raises this event is...
  6. Event ID 508 and 510

    in Windows 10 Support
    Event ID 508 and 510: Any idea what could be causing these errors? No idea how to start tracking down the cause. Computer is working fine. Already ran sfc and dism checks. All came back ok. Event ID 508: SettingSyncHost (8060) {E555163A-3067-4CFE-913F-A8D40DDE1723}: A request to write...
  7. CertificateServicesClient Event ID 64

    in Windows 10 Performance & Maintenance
    CertificateServicesClient Event ID 64: Since fall creators update have this in event viewer no other problems. Warning 20/10/2017 15:42:19 CertificateServicesClient-AutoEnrollment 64 None Certificate for local system with Thumbprint bc 12 3b b8 35 dc 72 9b 43 95 af 52 cc 5f 05 28 8d e3 28 af is about to expire...
  8. Occur several warning: ESENT origin; event id 508, 510, 533

    in Windows 10 Performance & Maintenance
    Occur several warning: ESENT origin; event id 508, 510, 533: Occur several warning: ESENT origin; event id 508, 510, 533 SettingSyncHost (3644) {8DD9444F-A80E-497B-8417-F165C45BF16F}: A write request in the file "C:\Users\Piero\AppData\Local\Microsoft\Windows\SettingSync\remotemetastore\v1\meta.edb" all'offset...
  9. Event log full of ESENT event id 916

    in Windows 10 Performance & Maintenance
    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...
  10. Event ID 64?

    in Windows 10 Support
    Event ID 64?: I just started getting this error everytime I reboot and during random use, it says Certificate for local system with Thumbprint ae 22 de 20 00 9d 5e 94 81 7a 12 38 0d 90 fe 9f 40 9d 62 17 is about to expire or already expired. Is this something I should be concerned about?...