Event ID 508 and 510

Page 1 of 2 12 LastLast

  1. Posts : 284
    Windows 10 Pro 64-bit
       #1

    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 to the file "C:\Users\XXXXXXX\AppData\Local\Microsoft\Windows\SettingSync\remotemetastore\v1\edb.log" at offset 126976 (0x000000000001f000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (39 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.
    SettingSyncHost (8060) {731A258A-B005-44E9-8492-4C472E196DAB}: A request to write to the file "C:\Users\XXXXXXX\AppData\Local\Microsoft\Windows\SettingSync\metastore\meta.edb" at offset 933888 (0x00000000000e4000) for 16384 (0x00004000) bytes succeeded, but took an abnormally long time (33 seconds) to be serviced by the OS. In addition, 10 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 13 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
    SettingSyncHost (8060) {731A258A-B005-44E9-8492-4C472E196DAB}: A request to write to the file "C:\Users\XXXXXXX\AppData\Local\Microsoft\Windows\SettingSync\metastore\meta.jfm" at offset 0 (0x0000000000000000) for 8192 (0x00002000) 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.
    SettingSyncHost (8060) {E555163A-3067-4CFE-913F-A8D40DDE1723}: A request to write to the file "C:\Users\XXXXXXX\AppData\Local\Microsoft\Windows\SettingSync\remotemetastore\v1\meta.edb" at offset 688128 (0x00000000000a8000) for 16384 (0x00004000) bytes succeeded, but took an abnormally long time (24 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.
    SettingSyncHost (8060) {731A258A-B005-44E9-8492-4C472E196DAB}: A request to write to the file "C:\Users\XXXXXXX\AppData\Local\Microsoft\Windows\SettingSync\metastore\meta.edb" at offset 1327104 (0x0000000000144000) for 16384 (0x00004000) bytes succeeded, but took an abnormally long time (15 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 ID 510:

    SettingSyncHost (8060) {731A258A-B005-44E9-8492-4C472E196DAB}: A request to write to the file "C:\Users\XXXXXXX\AppData\Local\Microsoft\Windows\SettingSync\metastore\meta.edb" at offset 933888 (0x00000000000e4000) for 16384 (0x00004000) bytes succeeded, but took an abnormally long time (33 seconds) to be serviced by the OS. In addition, 10 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 13 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
    Last edited by SoDiMm; 08 Feb 2017 at 15:52.
      My Computers


  2. Posts : 30,175
    Windows 11 Pro x64 Version 23H2
       #2

    Hi Vram.

    When is the last time you ran chkdsk.

    The messages all say "likely due to faulty hardware". Likely your storage drive.

    Myself, I would ensure I had all my data copied off machine before running chkdsk and I would I would ensure I had boot media in hand in event I need it.

    With these two item done you can run chkdsk /r.
      My Computer


  3. Posts : 284
    Windows 10 Pro 64-bit
    Thread Starter
       #3

    I've scanned the drive within Windows multiple times. No issues found.
      My Computers


  4. Posts : 30,175
    Windows 11 Pro x64 Version 23H2
       #4

    Determine the manufacture of drive and see if they have tool for disk health.

    You can also check out CrystalDiskInfo from CrystalMark.info

    You may also want to change the port and or the cable between motherboard and storage drive. (One at a time so you get to root cause.)

    Be aware that changing ports while running Raid may cause serious issues.
      My Computer


  5. Posts : 5
    Win 7 64 Pro; Win 10 64 Pro
       #5

    Hi vram,

    Have you noticed any performance issues or problems with search on account of these errors?

    I haven't, and the web search I just did indicates to me that this is another of Microsoft's little blips. I've given up trying to fix them, because even if I find a purported solution, the problem returns until Microsoft fixes its code.

    I run chkdsk frequently, and all is well.

    Have a look at this load of horse puckey thread to reassure yourself that Microsoft has known about the problem for some time, but has not bothered to solve it. Also note that the solutions offered are generic, and do nothing.

    ESENT Event ID 508,510 and 533 warnings in Event Viewer - Microsoft Community

    Good luck.
      My Computer


  6. Posts : 284
    Windows 10 Pro 64-bit
    Thread Starter
       #6

    I stumbled across that thread when I first began researching this issue. Hopefully it's just a glitch in the OS and can be ignored. What worries me is that I haven't witnessed it on my other computers running Win10.

    I just built this PC back in August. The only thing I carried over from my old rig was the HDD, but it's less than a year old. It's a 1TB Western Digital Blue HDD.

    I will run Crystal Disk and report its findings.
      My Computers


  7. Posts : 284
    Windows 10 Pro 64-bit
    Thread Starter
       #7

    Looks Fine to me:

    Event ID 508 and 510-crystal_info.png
      My Computers


  8. Posts : 2,911
    Windows 10 Pro for the Bro
       #8

    Look up a way to update your hard drive's Firmware:


    Software and Firmware Downloads | WD Support
    Scroll down to: "WD Universal Firmware Updater for Windows"
    Click it and download that file. See if it works
      My Computer


  9. Posts : 284
    Windows 10 Pro 64-bit
    Thread Starter
       #9

    I bookmarked it for installation tomorrow morning. Will report back once I've updated/tested.
      My Computers


  10. Posts : 284
    Windows 10 Pro 64-bit
    Thread Starter
       #10

    Firmware updater only works for USB HDDs.

    Haven't found an actual manual firmware download for the drive yet, but admittedly haven't had the time today to really look.
    Last edited by SoDiMm; 11 Feb 2017 at 00:26.
      My Computers


 

  Related Discussions
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 02:08.
Find Us




Windows 10 Forums