- Remove From My Forums
-
Question
-
In the last 3 weeks we have started to see the following errors
Event ESENT 510
svchost (2136) A request to write to the file «C:\Windows\system32\LogFiles\Sum\Current.mdb» at offset 4096 (0x0000000000001000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (20 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 95 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further
assistance diagnosing the problem.Event ESENT 507
svchost (2136) A request to read from the file «C:\Windows\system32\LogFiles\Sum\Current.mdb» at offset 147456 (0x0000000000024000) 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 ESENT 532
svchost (2136) A request to read from the file «C:\Windows\system32\LogFiles\Sum\Current.mdb» at offset 147456 (0x0000000000024000) 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.Running VM server 2012 R2
Доброго времени суток. Сегодня решили кратко рассказать, что делать, если у вас при активации ESET NOD32 появляется ошибка ACT 0.
Почему появляется ошибка ACT 0?
Последнее время все чаще начинаем обращать внимание на то, что появляется подобная ошибка при активации с помощью ключа на ESET NOD32 на 2 месяца. И наблюдяется данная проблема при активации в регионе Россия. А происходит это по той причине, что компания ESET ушла с нашего рынка и сейчас старается всячески усложнить активацию. Другими словами – блокировка активации в регионе Россия.
Как исправить ошибку ACT 0?
Так как мы понимаем, почему происходит данная ошибка, то исправить её становиться очень просто. Нужно использовать VPN при активации программы.
Просто используйте любой другой регион, где нод официально еще остался и никаких проблем в активации связанных с ошибкой ACT 0 не будет!
VPN
Это программа, которая меняет регион вашего компьютера при использовании сети интернет. Меняет Ваш IP адрес.
Как альтернативный способ активации – можете воспользоваться другим антивирусом, при активации которого – никаких проблем не будет
-
Распродажа!
-
Распродажа!
-
- Remove From My Forums
-
Question
-
In the last 3 weeks we have started to see the following errors
Event ESENT 510
svchost (2136) A request to write to the file «C:\Windows\system32\LogFiles\Sum\Current.mdb» at offset 4096 (0x0000000000001000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (20 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 95 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further
assistance diagnosing the problem.Event ESENT 507
svchost (2136) A request to read from the file «C:\Windows\system32\LogFiles\Sum\Current.mdb» at offset 147456 (0x0000000000024000) 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 ESENT 532
svchost (2136) A request to read from the file «C:\Windows\system32\LogFiles\Sum\Current.mdb» at offset 147456 (0x0000000000024000) 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.Running VM server 2012 R2
Event 508
wuaueng.dll (620) SUS20ClientDataStore: A request to write to the file «C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log» at offset 401408 (0x0000000000062000) 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 510
wuaueng.dll (620) SUS20ClientDataStore: A request to write to the file «C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log» at offset 401408 (0x0000000000062000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (22 seconds) to be serviced by the OS. In addition, 1 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 229 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Event 533
wuaueng.dll (620) SUS20ClientDataStore: A request to write to the file «C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log» at offset 401408 (0x0000000000062000) 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.
What would caused this to appear and how do stop them?
Any help would be appreciated.
Go to techsupport
r/techsupport
Stumped on a tech problem? Ask the community and try to help others with their problems as well.
Note: Reddit is dying due to terrible leadership from CEO /u/spez. Please use our Discord server instead of supporting a company that acts against its users and unpaid moderators.
Members
Online
•
A week ago, I was able to determine through the event log that Esent 508 and 510 errors were occurring. I have run every disk check program I can think of. All drives report %100 health. I’m stumped. ANy ideas?