Esent 508 ошибка windows 10 - Решение и исправление самых разных ошибок на TopOshibok.ru

Remove From My Forums

Question
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 Pro 64-Bit; ASUS P5G41T-M LE; RAM 4GB; CPU Intel Core Duo E8600 @ 3.33 GHz; Nvidia Quadro FX3700
- Edited by
  
  Monday, November 21, 2016 3:46 PM

Answers

Hi,

From my survey,

Esent Event ID 508 and 533 This warning can also be caused by an insufficient (or potentially even just low) amount of unused space on your currently running Operating System’s HDD/SSD

Esent Event ID 510 Event ID 510 is a performance warning, which indicates slow writing behavior, if the computer is connected to a server. This issue could be related with the performance of the server.

Therefore, I suggest to cleanup disk space and perform a defragmentation of the drives at first. Then run SFC command or DISM command to repair system files. After that, boot machine in the clean boot mode to check result again.

Regards

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com.
- Marked as answer by
  alpha45
  Thursday, April 20, 2017 1:38 PM

We’re hosting Server 2019 VM on a Synology NAS device.
That’s the only thing on the device.

The errors vary in what they say but are consistent in that I get them at least once every 1-2 days.
I’m usually able to determine whether some errors can be ignored, but the fact that these errors mention «This problem is likely due to faulty hardware.» frightened me into posting here.

Things I’ve tried: sfc /scannow, chkdsk /f /r, Windows Memory Diagnostic, checking for outdated drivers
None of the scans found any issues and all drivers are updated./

Here are a few errors from yesterday.

508: svchost (3580,D,50) SRUJet: A request to write to the file «C:\Windows\system32\SRU\SRUDB.jfm» at offset 0 (0x0000000000000000) for 8192 (0x00002000) 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.

510: svchost (3580,D,50) SRUJet: A request to write to the file «C:\Windows\system32\SRU\SRUDB.dat» at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (30 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 219583 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware
vendor for further assistance diagnosing the problem.

UPDATE: Getting error 533 as well: DFSRs (3104,D,0) \\.\C:\System Volume Information\DFSR\database_5456_22D3_5622_B620\dfsr.db: A request to write to the file «\\.\C:\System Volume Information\DFSR\database_5456_22D3_5622_B620\fsrtmp.log» at
offset 0 (0x0000000000000000) 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.

Edited by

Monday, August 26, 2019 1:05 PM

Источник

Hi there,

Users have complained to me that at about 3:00 every day, our file server slows down and applications hang. I finally found an indicator of this after looking at all scheduled tasks, backup plans, etc.

The Application logs in Event Viewer show every day for the last month at about 3:05pm warning (with one outlier at 5:45am):

Source: Esent
EventID: 508
svchost (5184) A request to write to the file «C:\Windows\system32\LogFiles\Sum\Svc.log» at offset 2904064 (0x00000000002c5000) 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.

I don’t know if this is exactly it, but it seems like it’s cause for concern. To rule out faulty hardware, I’m going to run a chkdsk after folks head out this evening. Just thinking out loud; my file server partition and the Windows Server 2012 partitions are on the same physical disk (yuck) but I do have a RAID1 setup going, so a bad disk won’t be the end of the world.

I’ve seen some other posts about this being caused by a dead battery on a RAID controller. so I’ll check that out too. I have half a terabyte free on this partition, so it’s not an issue of a full disk.

Any other known culprits of this issue?

Источник

Hi,

Hoping to get a few ideas on what might be the cause of this issue we are having.

Background

We have two hyper-v clusters running Server 2012R2.

Our AD environment is a mix of 2008R2 and one 2012R2 DC’s.

We have both 2008R2 and 2012R2 DC’s running virtualised on the Hyper-V clusters.

2008R2 DC is on a VHD disk.

2012R2 DC is on VHDX disk.

We have a number of other 2012R2 and 2008R2 servers on the clusters.

Issue

We have started seeing the above error being logged on the 2012R2 DC only. The 2008R2 DC’s do not show this error at all.

Event ID: 508

Source: ESENT

Level: Warning

svchost (2568) A request to write to the file «C:Windowssystem32LogFilesSumSvc.log» at offset 2023424 (0x00000000001ee000) for 4096 (0x00001000) 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.

lsass (628) A request to write to the file «\?Volume{538f044f-9c00-11e3-80c2-00155d1c0903}WindowsNTDSntds.dit» at offset 31342592 (0x0000000001de4000) for 8192 (0x00002000) 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.

Source: NTDS ISAM

NTDS (628) NTDSA: A request to write to the file «E:WindowsNTDSedb.log» at offset 1306624 (0x000000000013f000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (21 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 509

Source: NTDS ISAM

NTDS (628) NTDSA: A request to read from the file «E:WindowsNTDSntds.dit» at offset 243572736 (0x000000000e84a000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (21 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 23679 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further
assistance diagnosing the problem.

Troubleshooting So Far

AV exceptions are in place for scanning

Backup (DPM 2012) disabled for testing

Moved 2012R2 DC to another virtual host

Moved 2012R2 DC to another storage server

The server is fully patched with all latest updates available from windows update.

Any assistance is appreciated.

Regards,

Denis Cooper

MCITP EA — MCT

Help keep the forums tidy, if this has helped please mark it as an answer

My Blog

LinkedIn:

Edited by

Monday, February 24, 2014 9:29 AM

Hi,

Hoping to get a few ideas on what might be the cause of this issue we are having.

Background

We have two hyper-v clusters running Server 2012R2.

Our AD environment is a mix of 2008R2 and one 2012R2 DC’s.

We have both 2008R2 and 2012R2 DC’s running virtualised on the Hyper-V clusters.

2008R2 DC is on a VHD disk.

2012R2 DC is on VHDX disk.

We have a number of other 2012R2 and 2008R2 servers on the clusters.

Issue

We have started seeing the above error being logged on the 2012R2 DC only. The 2008R2 DC’s do not show this error at all.

Event ID: 508

Source: ESENT

Level: Warning

Source: NTDS ISAM

Event ID 509

Source: NTDS ISAM

Troubleshooting So Far

AV exceptions are in place for scanning

Backup (DPM 2012) disabled for testing

Moved 2012R2 DC to another virtual host

Moved 2012R2 DC to another storage server

The server is fully patched with all latest updates available from windows update.

Any assistance is appreciated.

Regards,

Denis Cooper

MCITP EA — MCT

Help keep the forums tidy, if this has helped please mark it as an answer

My Blog

LinkedIn:

Edited by

Monday, February 24, 2014 9:29 AM

Hi,

Hoping to get a few ideas on what might be the cause of this issue we are having.

Background

We have two hyper-v clusters running Server 2012R2.

Our AD environment is a mix of 2008R2 and one 2012R2 DC’s.

We have both 2008R2 and 2012R2 DC’s running virtualised on the Hyper-V clusters.

2008R2 DC is on a VHD disk.

2012R2 DC is on VHDX disk.

We have a number of other 2012R2 and 2008R2 servers on the clusters.

Issue

We have started seeing the above error being logged on the 2012R2 DC only. The 2008R2 DC’s do not show this error at all.

Event ID: 508

Source: ESENT

Level: Warning

Source: NTDS ISAM

Event ID 509

Source: NTDS ISAM

Troubleshooting So Far

AV exceptions are in place for scanning

Backup (DPM 2012) disabled for testing

Moved 2012R2 DC to another virtual host

Moved 2012R2 DC to another storage server

The server is fully patched with all latest updates available from windows update.

Any assistance is appreciated.

Regards,

Denis Cooper

MCITP EA — MCT

Help keep the forums tidy, if this has helped please mark it as an answer

My Blog

LinkedIn:

Edited by

Monday, February 24, 2014 9:29 AM

Whenever I am using google chrome my computer freezes up for about 30 seconds. After the 30 seconds I check my event viewer I get the ESENT issues 508 & 533. I have restored the PC 4 times now and still cannot seem to fix it. All my drivers are installed and up to date. My PC specs are:

EVGA GeForce GTX 970 04G-P4-2978-KR 4GB FTW GAMING w/ACX 2.0, Silent Cooling Graphics Card

CORSAIR RMx RM750X 750W ATX12V / EPS12V 80 PLUS GOLD

AMD FX-8350 Black Edition Vishera 8-Core 4.0 GHz (4.2 GHz Turbo) Socket AM3+ 125W FD8350FRHKBOX Desktop Processor

GIGABYTE GA-990FXA-UD5 R5 (rev. 1.0) AM3+ AMD 990FX SATA 6Gb/s USB 3.0 ATX AMD Motherboard

HyperX Fury Black Series 16GB (2 x 8GB) 240-Pin DDR3 SDRAM DDR3 1600

And the event details are:

— <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=»2016-08-18T17:52:12.241672100Z» />
<EventRecordID>382</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-99BECKT</Computer>
<Security />
</System>
— <EventData>
<Data>taskhostw</Data>
<Data>3880</Data>
<Data>WebCacheLocal:</Data>
<Data>C:UsersHugoAppDataLocalMicrosoftWindowsWebCacheV01.log</Data>
<Data>507904 (0x000000000007c000)</Data>
<Data>4096 (0x00001000)</Data>
<Data>36</Data>
</EventD

— <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=»2016-08-18T17:52:12.241672100Z» />
<EventRecordID>383</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-99BECKT</Computer>
<Security />
</System>
— <EventData>
<Data>taskhostw</Data>
<Data>3880</Data>
<Data>WebCacheLocal:</Data>
<Data>C:UsersHugoAppDataLocalMicrosoftWindowsWebCacheWebCacheV01.dat</Data>
<Data>98304 (0x0000000000018000)</Data>
<Data>32768 (0x00008000)</Data>
<Data>36</Data>
</EventData>
</Event>

And the General view:
taskhostw (3880) WebCacheLocal: A request to write to the file «C:UsersHugoAppDataLocalMicrosoftWindowsWebCacheV01.log» at offset 507904 (0x000000000007c000) 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.

Colif

: Jun 12, 2015

: 61,167

: 5,188

: 166,290

: 10,454

samsung ssd have 5 year warranties, you might want to rma yours and ask for a new one. Those scores are a little worrying

Colif

: Jun 12, 2015

: 61,167

: 5,188

: 166,290

: 10,454

Sorry haha. I have a 1 TB western digital HDD and a 250 Gb samsung SSD. And both barley have anything on them. After I ran the test with the link you gave me nothing worked but what information I did get was when I safe booted and I turned off all the 3rd party application that google chrome still froze.

Colif

: Jun 12, 2015

: 61,167

: 5,188

: 166,290

: 10,454

ESENT is a database used by Microsoft search, and indexing. There is very little information on google about these errors, which always helps. Its also used by the apps on the store.

Event 508:

If the event is just one odd occurrence, then it may be just a transient problem. If it happens on regular basis then the specified drive should be checked for problems (run chkdsk, make sure you have enough free space and physical memory — running low on memory may affect all the disk operations).

http://www.eventid.net/display-eventid-508-source-ESENT-eventno-5580-phase-1.htm

try a checkdisk on both drives, you don’t fall into last two.

ESENT is a database used by Microsoft search, and indexing. There is very little information on google about these errors, which always helps. Its also used by the apps on the store.

Event 508:

If the event is just one odd occurrence, then it may be just a transient problem. If it happens on regular basis then the specified drive should be checked for problems (run chkdsk, make sure you have enough free space and physical memory — running low on memory may affect all the disk operations).

http://www.eventid.net/display-eventid-508-source-ESENT-eventno-5580-phase-1.htm

try a checkdisk on both drives, you don’t fall into last two.

Nope tried it on both and it says nothing is wrong with both of them

Colif

: Jun 12, 2015

: 61,167

: 5,188

: 166,290

: 10,454

One guy fixed it running this so its worth a try

right click start button
choose command prompt (admin)
type SFC /scannow and press enter

this scans system files and may fix this behaviour

One guy fixed it running this so its worth a try

right click start button
choose command prompt (admin)
type SFC /scannow and press enter

this scans system files and may fix this behaviour

Nope nothing. I did notice my RAM sticks were not in the same color I’m not sure if that could be the cause but so far no freezes in 30min of use

Colif

: Jun 12, 2015

: 61,167

: 5,188

: 166,290

: 10,454

508, on ever search I do comes back as the storage device being the cause. I looked into your ram idea but did not see any results similar. I assume windows is seeing the right amount for you?

533 appears to be a logon failure: Event 533 is logged on the workstation or server where the user failed to logon. https://www.ultimatewindowssecurity.com/securitylog/encyclopedia/event.aspx?eventid=533

I checked around and found a few explanations for the event you listed. The common theme for this event was that it is indicating a faulty drive or controller. Here are some of the explanations for the event 508, I got them from eventid.net you have to be a member to see the results so I will paste some of what I found.

«As per Microsoft: «This Warning event is logged when the Exchange database engine tries to write to the named file and encounters a delayed response from the operating system in performing that write operation. This is a warning, not an error, because the operation eventually finishes, although it is slow. This might indicate a hardware problem, probably with the disk controller, a disk, or other storage component». See MSEX2K3DB for more information about this event»

https://www.experts-exchange.com/questions/23306210/Sporadic-networking-performance-issues-only-event-ID-508-from-ESE-to-suggest-problem.html

i think 533 is a result of 508, you must have been trying to logon to a site online and the ssd was too slow to respond, and the logon timed out in the 30 second freeze time.

All signs point at ssd, you may not believe it but that is what PC is telling you. Only other choice is drivers, I don’t think flashing bios would fix this, and you say you have latest now.

508, on ever search I do comes back as the storage device being the cause. I looked into your ram idea but did not see any results similar. I assume windows is seeing the right amount for you?

I checked around and found a few explanations for the event you listed. The common theme for this event was that it is indicating a faulty drive or controller. Here are some of the explanations for the event 508, I got them from eventid.net you have to be a member to see the results so I will paste some of what I found.

«As per Microsoft: «This Warning event is logged when the Exchange database engine tries to write to the named file and encounters a delayed response from the operating system in performing that write operation. This is a warning, not an error, because the operation eventually finishes, although it is slow. This might indicate a hardware problem, probably with the disk controller, a disk, or other storage component». See MSEX2K3DB for more information about this event»

https://www.experts-exchange.com/questions/23306210/Sporadic-networking-performance-issues-only-event-ID-508-from-ESE-to-suggest-problem.html

i think 533 is a result of 508, you must have been trying to logon to a site online and the ssd was too slow to respond, and the logon timed out in the 30 second freeze time.

All signs point at ssd, you may not believe it but that is what PC is telling you. Only other choice is drivers, I don’t think flashing bios would fix this, and you say you have latest now.

I ran a benchmark test with my SSD and it seems it be really slow with random read and write.

Colif

: Jun 12, 2015

: 61,167

: 5,188

: 166,290

: 10,454

Can you share results and I see if I can confirm your suspicion.

Sequential Read: 2563
Sequential Write: 1140
Random Read: 62282
Random Write: 22469

Colif

: Jun 12, 2015

: 61,167

: 5,188

: 166,290

: 10,454

Can you share results and I see if I can confirm your suspicion.

Sequential Read: 2563
Sequential Write: 1140
Random Read: 62282
Random Write: 22469

are you running rapid through Samsung Magician? I only ask as your sequential is way bigger than mine but I am not running rapid

mine are (we both had same SSD)

SR: 548
SW: 484
RR: 95725
RW: 82982

your random scores are still lower so, especially the Random write

rapid mode is essentially a RAMDISK that the magician software creates in your system for the SSD to use. the memory in SSDs is slower then your ram. but using the ram means your risk of data loss in a power failure should be greater since your SSD is using it as a buffer of sorts.

IF samsung is using the rapid mode test results in their official benchmarks for these drives, what they are doing would be considered a scam because its not testing the drives, its testing a ramdisk.

i have a brand new samsung 850 pro 256GB and i have the same issue. using magician Without rapid mode my scores are.

Sequential read — 547 MB/s (expected 550 but good enough)
Sequential write — 502 MB/s (expected 520 but good enough)

Random read — 61893 IOPs (expected 100,000)
Random write — 50409 IOPs (expected 90,000)

http://www.tomshardware.com/answers/id-2507951/850-evo-low-iops.html

looking through that thread, one possible thing you can do is install latest Intel Raid Storage Technology drivers, it seems it might speed you up, but your random read/write scores are very low. Also seems AMD motherboards supply slower scores than Intel ones.

If you used samsung magician to do benchmarks, it seems it isn’t very accurate. http://www.tomshardware.com/answers/id-2573130/brand-samsung-850-evo-250gb-low-random-read-write-iops.html

try running As SSD benchmark
as a comparison — these are my scores

Can you share results and I see if I can confirm your suspicion.

Sequential Read: 2563
Sequential Write: 1140
Random Read: 62282
Random Write: 22469

are you running rapid through Samsung Magician? I only ask as your sequential is way bigger than mine but I am not running rapid

mine are (we both had same SSD)

SR: 548
SW: 484
RR: 95725
RW: 82982

your random scores are still lower so, especially the Random write

rapid mode is essentially a RAMDISK that the magician software creates in your system for the SSD to use. the memory in SSDs is slower then your ram. but using the ram means your risk of data loss in a power failure should be greater since your SSD is using it as a buffer of sorts.

IF samsung is using the rapid mode test results in their official benchmarks for these drives, what they are doing would be considered a scam because its not testing the drives, its testing a ramdisk.

i have a brand new samsung 850 pro 256GB and i have the same issue. using magician Without rapid mode my scores are.

Sequential read — 547 MB/s (expected 550 but good enough)
Sequential write — 502 MB/s (expected 520 but good enough)

Random read — 61893 IOPs (expected 100,000)
Random write — 50409 IOPs (expected 90,000)

http://www.tomshardware.com/answers/id-2507951/850-evo-low-iops.html

If you used samsung magician to do benchmarks, it seems it isn’t very accurate. http://www.tomshardware.com/answers/id-2573130/brand-samsung-850-evo-250gb-low-random-read-write-iops.html

try running As SSD benchmark

Yes I am running Rapid without it my random stuff are 9000 or lower

Colif

: Jun 12, 2015

: 61,167

: 5,188

: 166,290

: 10,454

samsung ssd have 5 year warranties, you might want to rma yours and ask for a new one. Those scores are a little worrying

I had this same issue and immediately suspected a Trojan. It was Poweliks Trojan. This piece of garbage does not download files but just changes some code and causes your machine to pull in fake ad visits and fake clicks that look like real clicks to the vendors. I removed it with Hitman Pro, but symantek has a free poweliks removal tool.

My machine was freezing for 30 seconds or more at a time and it was maddening. Anyone with these ESENT issues should use a good quality Trojan or rootkit sniffer to see if that’s the issue.

samsung ssd have 5 year warranties, you might want to rma yours and ask for a new one. Those scores are a little worrying

I was hoping you could interpret these numbers for me after running a scan. The last couple days I have been having random freezing, which last for about 15-30 seconds, then returns to normal. I have updated all drivers, checked memory, run disk check, system file checker, etc. with no resolution. During this test I noticed in the upper left hand corner, in German lol, it says PCI IDE controller-bad. Here are the numbers:

292.37 — 163.84
14.36 — 50.72
18.37 — 82.32
0.261 — 0.304
Score 62 — 156

I would appreciate any help you could provide.

Colif

: Jun 12, 2015

: 61,167

: 5,188

: 166,290

: 10,454

what are specs of PC? How old is motherboard? What make ssd?

Advertising
Cookies Policies
Privacy
Term & Conditions
Topics

Источник

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

EVGA GeForce GTX 970 04G-P4-2978-KR 4GB FTW GAMING w/ACX 2.0, Silent Cooling Graphics Card

CORSAIR RMx RM750X 750W ATX12V / EPS12V 80 PLUS GOLD

AMD FX-8350 Black Edition Vishera 8-Core 4.0 GHz (4.2 GHz Turbo) Socket AM3+ 125W FD8350FRHKBOX Desktop Processor

GIGABYTE GA-990FXA-UD5 R5 (rev. 1.0) AM3+ AMD 990FX SATA 6Gb/s USB 3.0 ATX AMD Motherboard

HyperX Fury Black Series 16GB (2 x 8GB) 240-Pin DDR3 SDRAM DDR3 1600

And the event details are:

— <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=»2016-08-18T17:52:12.241672100Z» />
<EventRecordID>382</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-99BECKT</Computer>
<Security />
</System>
— <EventData>
<Data>taskhostw</Data>
<Data>3880</Data>
<Data>WebCacheLocal:</Data>
<Data>C:\Users\Hugo\AppData\Local\Microsoft\Windows\WebCache\V01.log</Data>
<Data>507904 (0x000000000007c000)</Data>
<Data>4096 (0x00001000)</Data>
<Data>36</Data>
</EventD

— <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=»2016-08-18T17:52:12.241672100Z» />
<EventRecordID>383</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-99BECKT</Computer>
<Security />
</System>
— <EventData>
<Data>taskhostw</Data>
<Data>3880</Data>
<Data>WebCacheLocal:</Data>
<Data>C:\Users\Hugo\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat</Data>
<Data>98304 (0x0000000000018000)</Data>
<Data>32768 (0x00008000)</Data>
<Data>36</Data>
</EventData>
</Event>

And the General view:
taskhostw (3880) WebCacheLocal: A request to write to the file «C:\Users\Hugo\AppData\Local\Microsoft\Windows\WebCache\V01.log» at offset 507904 (0x000000000007c000) 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.

: Jun 12, 2015

: 62,823

: 5,625

: 168,090

Esent Event ID 508 and 533 This warning can also be caused by an insufficient (or potentially even just low) amount of unused space on your currently running Operating System’s HDD/SSD

http://answers.microsoft.com/en-us/windows/forum/windows_10-performance/esent-event-id-508510-and-533-warnings-in-event/5f60a4ae-ed72-42e2-932d-5756cacc497f?auth=1

since you didn’t list a hdd, I can only assume you don’t have one
that could be reason but I doubt it. Might want to make more free space

might also want to run HDtune trial and Crystal disk mark on your drives, something slow to respond there.

[quotemsg=18458977,0,2007449]

Esent Event ID 508 and 533 This warning can also be caused by an insufficient (or potentially even just low) amount of unused space on your currently running Operating System’s HDD/SSD

http://answers.microsoft.com/en-us/windows/forum/windows_10-performance/esent-event-id-508510-and-533-warnings-in-event/5f60a4ae-ed72-42e2-932d-5756cacc497f?auth=1

since you didn’t list a hdd, I can only assume you don’t have one
that could be reason but I doubt it. Might want to make more free space

might also want to run HDtune trial and Crystal disk mark on your drives, something slow to respond there.[/quotemsg]

: Jun 12, 2015

: 62,823

: 5,625

: 168,090

ESENT is a database used by Microsoft search, and indexing. There is very little information on google about these errors, which always helps. Its also used by the apps on the store.

Event 508:

If the event is just one odd occurrence, then it may be just a transient problem. If it happens on regular basis then the specified drive should be checked for problems (run chkdsk, make sure you have enough free space and physical memory — running low on memory may affect all the disk operations).

http://www.eventid.net/display-eventid-508-source-ESENT-eventno-5580-phase-1.htm

try a checkdisk on both drives, you don’t fall into last two.

[quotemsg=18461518,0,2007449]ESENT is a database used by Microsoft search, and indexing. There is very little information on google about these errors, which always helps. Its also used by the apps on the store.

Event 508:

If the event is just one odd occurrence, then it may be just a transient problem. If it happens on regular basis then the specified drive should be checked for problems (run chkdsk, make sure you have enough free space and physical memory — running low on memory may affect all the disk operations).

http://www.eventid.net/display-eventid-508-source-ESENT-eventno-5580-phase-1.htm

try a checkdisk on both drives, you don’t fall into last two. [/quotemsg]

Nope tried it on both and it says nothing is wrong with both of them

: Jun 12, 2015

: 62,823

: 5,625

: 168,090

One guy fixed it running this so its worth a try

right click start button
choose command prompt (admin)
type SFC /scannow and press enter

this scans system files and may fix this behaviour

[quotemsg=18464770,0,2007449]One guy fixed it running this so its worth a try

right click start button
choose command prompt (admin)
type SFC /scannow and press enter

this scans system files and may fix this behaviour[/quotemsg]

Nope nothing. I did notice my RAM sticks were not in the same color I’m not sure if that could be the cause but so far no freezes in 30min of use

: Jun 12, 2015

: 62,823

: 5,625

: 168,090

508, on ever search I do comes back as the storage device being the cause. I looked into your ram idea but did not see any results similar. I assume windows is seeing the right amount for you?

I checked around and found a few explanations for the event you listed. The common theme for this event was that it is indicating a faulty drive or controller. Here are some of the explanations for the event 508, I got them from eventid.net you have to be a member to see the results so I will paste some of what I found.

«As per Microsoft: «This Warning event is logged when the Exchange database engine tries to write to the named file and encounters a delayed response from the operating system in performing that write operation. This is a warning, not an error, because the operation eventually finishes, although it is slow. This might indicate a hardware problem, probably with the disk controller, a disk, or other storage component». See MSEX2K3DB for more information about this event»

https://www.experts-exchange.com/questions/23306210/Sporadic-networking-performance-issues-only-event-ID-508-from-ESE-to-suggest-problem.html

i think 533 is a result of 508, you must have been trying to logon to a site online and the ssd was too slow to respond, and the logon timed out in the 30 second freeze time.

All signs point at ssd, you may not believe it but that is what PC is telling you. Only other choice is drivers, I don’t think flashing bios would fix this, and you say you have latest now.

[quotemsg=18471013,0,2007449]508, on ever search I do comes back as the storage device being the cause. I looked into your ram idea but did not see any results similar. I assume windows is seeing the right amount for you?

I checked around and found a few explanations for the event you listed. The common theme for this event was that it is indicating a faulty drive or controller. Here are some of the explanations for the event 508, I got them from eventid.net you have to be a member to see the results so I will paste some of what I found.

«As per Microsoft: «This Warning event is logged when the Exchange database engine tries to write to the named file and encounters a delayed response from the operating system in performing that write operation. This is a warning, not an error, because the operation eventually finishes, although it is slow. This might indicate a hardware problem, probably with the disk controller, a disk, or other storage component». See MSEX2K3DB for more information about this event»

https://www.experts-exchange.com/questions/23306210/Sporadic-networking-performance-issues-only-event-ID-508-from-ESE-to-suggest-problem.html

i think 533 is a result of 508, you must have been trying to logon to a site online and the ssd was too slow to respond, and the logon timed out in the 30 second freeze time.

All signs point at ssd, you may not believe it but that is what PC is telling you. Only other choice is drivers, I don’t think flashing bios would fix this, and you say you have latest now.[/quotemsg]

I ran a benchmark test with my SSD and it seems it be really slow with random read and write.

: Jun 12, 2015

: 62,823

: 5,625

: 168,090

Can you share results and I see if I can confirm your suspicion.

[quotemsg=18476363,0,2007449]Can you share results and I see if I can confirm your suspicion.[/quotemsg]

Sequential Read: 2563
Sequential Write: 1140
Random Read: 62282
Random Write: 22469

: Jun 12, 2015

: 62,823

: 5,625

: 168,090

[quotemsg=18478190,0,2260685][quotemsg=18476363,0,2007449]Can you share results and I see if I can confirm your suspicion.[/quotemsg]

Sequential Read: 2563
Sequential Write: 1140
Random Read: 62282
Random Write: 22469[/quotemsg]

are you running rapid through Samsung Magician? I only ask as your sequential is way bigger than mine but I am not running rapid

mine are (we both had same SSD)

SR: 548
SW: 484
RR: 95725
RW: 82982

your random scores are still lower so, especially the Random write

rapid mode is essentially a RAMDISK that the magician software creates in your system for the SSD to use. the memory in SSDs is slower then your ram. but using the ram means your risk of data loss in a power failure should be greater since your SSD is using it as a buffer of sorts.

IF samsung is using the rapid mode test results in their official benchmarks for these drives, what they are doing would be considered a scam because its not testing the drives, its testing a ramdisk.

i have a brand new samsung 850 pro 256GB and i have the same issue. using magician Without rapid mode my scores are.

Sequential read — 547 MB/s (expected 550 but good enough)
Sequential write — 502 MB/s (expected 520 but good enough)

Random read — 61893 IOPs (expected 100,000)
Random write — 50409 IOPs (expected 90,000)

http://www.tomshardware.com/answers/id-2507951/850-evo-low-iops.html

If you used samsung magician to do benchmarks, it seems it isn’t very accurate. http://www.tomshardware.com/answers/id-2573130/brand-samsung-850-evo-250gb-low-random-read-write-iops.html

try running As SSD benchmark
as a comparison — these are my scores

[quotemsg=18481021,0,2007449][quotemsg=18478190,0,2260685][quotemsg=18476363,0,2007449]Can you share results and I see if I can confirm your suspicion.[/quotemsg]

Sequential Read: 2563
Sequential Write: 1140
Random Read: 62282
Random Write: 22469[/quotemsg]

are you running rapid through Samsung Magician? I only ask as your sequential is way bigger than mine but I am not running rapid

mine are (we both had same SSD)

SR: 548
SW: 484
RR: 95725
RW: 82982

your random scores are still lower so, especially the Random write

rapid mode is essentially a RAMDISK that the magician software creates in your system for the SSD to use. the memory in SSDs is slower then your ram. but using the ram means your risk of data loss in a power failure should be greater since your SSD is using it as a buffer of sorts.

IF samsung is using the rapid mode test results in their official benchmarks for these drives, what they are doing would be considered a scam because its not testing the drives, its testing a ramdisk.

i have a brand new samsung 850 pro 256GB and i have the same issue. using magician Without rapid mode my scores are.

Sequential read — 547 MB/s (expected 550 but good enough)
Sequential write — 502 MB/s (expected 520 but good enough)

Random read — 61893 IOPs (expected 100,000)
Random write — 50409 IOPs (expected 90,000)

http://www.tomshardware.com/answers/id-2507951/850-evo-low-iops.html

If you used samsung magician to do benchmarks, it seems it isn’t very accurate. http://www.tomshardware.com/answers/id-2573130/brand-samsung-850-evo-250gb-low-random-read-write-iops.html

try running As SSD benchmark
[/quotemsg]

Yes I am running Rapid without it my random stuff are 9000 or lower

: Jun 12, 2015

: 62,823

: 5,625

: 168,090

samsung ssd have 5 year warranties, you might want to rma yours and ask for a new one. Those scores are a little worrying

My machine was freezing for 30 seconds or more at a time and it was maddening. Anyone with these ESENT issues should use a good quality Trojan or rootkit sniffer to see if that’s the issue.

[quotemsg=18481405,0,2007449]samsung ssd have 5 year warranties, you might want to rma yours and ask for a new one. Those scores are a little worrying[/quotemsg]

292.37 — 163.84
14.36 — 50.72
18.37 — 82.32
0.261 — 0.304
Score 62 — 156

I would appreciate any help you could provide.

: Jun 12, 2015

: 62,823

: 5,625

: 168,090

what are specs of PC? How old is motherboard? What make ssd?

Similar threads

Advertising
Cookies Policies
Privacy
Term & Conditions

Источник

Question

Answers

Similar threads