Windows 10: 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:

Event ID 510:

:)

 

Getting ESENT errors; 508, 510 and 533

Hi,

Normally I know better than to go poking around in Event Viewer but I spotted these errors after accidentally opening it earlier this month. The errors do not appear to coincide with any visible problems with my PC like slowness or freezing. They read;

SettingSyncHost (5656) {D09E5797-D13B-4DEE-B53C-DF41EAAC375E}: A request to write to the file "C:\Users\username\AppData\Local\Microsoft\Windows\SettingSync\metastore\edb.log" at offset 229376 (0x0000000000038000) for 4096 (0x00001000) bytes succeeded, but
took an abnormally long time (28 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 (5656) {AF1A0CF2-AC96-4BAF-937D-5512EAE9FEF6}: A request to write to the file "C:\Users\username\AppData\Local\Microsoft\Windows\SettingSync\remotemetastore\v1\meta.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.

They are almost always pointing towards the SettingSync\remotemetastore folder. The ones that don't point to C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.jtx

The faulty hardware bit is the part has me concerned. I went as far back as I can and the first ESENT occurred on the 19th of May. I have noted that these occur every 10 days or so, latest was today (during an update) and before that was the 5th Jun.

I've run sfc /scannow (0 integrity violations), run chkdsk (0 problems), DISM, and used Crystal Disk Info which says my drive is healthy.

The drive is not full, approx 680GB free of 930GB.

Any help would be really appreciated - thanks!

 

My PC keeps freezing for ~1 min and I keep getting Event 533, 510, 508(ESENT) and 129(iaStorA)

Alright, i did some more tests.

Disabling Google Drive didn't solve the issue.

Clean installed Windows 10 twice diretly to Anniversary Update.

The first time, i have installed all my softwares. Issue persisted.

The second time, i have installed only the basics and blocked further updates from Octomber 10 (becouse i didn't notice this issue on that date). Issue persisted.

Most of the time its about an SO read/write delay in these files:

ESENT 533: %userprofile%\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.jfm

ESENT 533: %userprofile%\AppData\Local\Microsoft\Windows\WebCache\V01.log

ESENT 508: %userprofile%\AppData\Local\Microsoft\Windows\WebCache\V01.log

ESENT 508: %userprofile%\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.jfm

ESENT 508: %userprofile%\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\AppData\Indexed DB\IndexedDB.jfm

ESENT 508: %userprofile%\AppData\Local\TileDataLayer\Database\EDB.log

ESENT 508: %userprofile%\AppData\Local\TileDataLayer\Database\vedatamodel.jfm

ESENT 510: %userprofile%\AppData\Local\Microsoft\Windows\WebCache\V01.log

ESENT 510: %userprofile%\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.jfm

Sometimes this file also appears in the logs:

%userprofile%\AppData\Local\Comms\UnistoreDB\store.vol

Its too much coincidence to be a faulty SSD. My last attempt will be replacing it with my old one.

After some digging on the internet, i couldn't find much about it. Whats going on? Its just me and the OP?

 

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.

 

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

 

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.

 

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.

 

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.

 

Looks Fine to me:

 

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

 

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

 

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.

 

K I dunno what else. Hopefully someone finds something. Try to do a search on a search engine and pend time looking for something that can be useful I guess.

 

Long shot but could it be storage drivers? I would create restore point before attempting up date.

Did you change port?

Ken

 

I googled the model of my drive and still no firmware but I did find where people had some reliability issues with my particular drive.

I'm just going to continue regular backups and ignore it. If the NAND gods would allow the common peasant an affordable 1TB SSD, 'ol spinning rust would go bye bye. Sadly, it'll be at least 5 yrs before they drop below the $150 mark *Sad