Windows 10: Event viewer spamming Error 537 C:\WINDOWS\system32\SRU\SRUDB.dat

My PC seems to be working fine, i don't notice any problem.However entering to the event viewer i noticed is spamming constantly error 537:svchost 3820,D,22 SRUJet: A request for a node on an empty page Pgno: 12770, Flags: 0xa80a has been made error -351 for a B-Tree ObjectId: 18, PgnoRoot: 95 of database C:\WINDOWS\system32\SRU\SRUDB.dat. This is typically due to a lost I/O from sto

:)

 

Recovering C:/Windows/system32/SRU/SRUDB.dat

The support team of a third party application said that on my PC the following file is damaged or corrupted:

C:/Windows/system32/SRU/SRUDB.dat

They suggested to use the Windows System File Checker ("sfc /scannow") without further information.

I attempted to run it as Administrator either in normal and in safe mode with no success.

I attempted to repair the file by running:

C:\Windows\System32>sfc /scanfile=C:/Windows/system32/SRU/SRUDB.dat

but I got a message saying that Windows protection blocked the required action.

Given that the solution provided by the third party application support team is correct, how can I repair the file witout compromising other installed applications?

Regards

Marius

 

ESENT error, event ID 447, 467, 530, 537, 544

I've been getting the following errors in event viewer constantly every minute for a while. I've tried a couple of solutions throught command prompt, using System File Checker and DISM but neither gave me any results. I'm worried its a hardware issue.

Thanks in advance!

ESENT error 447:

svchost (3444,D,21) SRUJet: A bad page link (error -338) has been detected in a B-Tree (ObjectId: 14, PgnoRoot: 49) of database C:\Windows\system32\SRU\SRUDB.dat (49 => 2658, 14).

ESENT error 467:

svchost (3444,D,23) SRUJet: Database C:\Windows\system32\SRU\SRUDB.dat: Index UserIdTimeStamp of table {5C8CF1C7-7257-4F13-B223-970EF5939312} is corrupted (0).

ESENT error 530:

svchost (3444,D,22) SRUJet: The database page read from the file "C:\Windows\system32\SRU\SRUDB.dat" at offset 2514944 (0x0000000000266000) (database page 613 (0x265)) for 4096 (0x00001000) bytes failed verification due to a lost flush detection timestamp
mismatch. The read operation will fail with error -1119 (0xfffffba1).

The flush state on database page 613 (0x265) was 2 while the flush state on flush map page 0 (0x0) was 1.

If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

ESENT error 537:

svchost (3444,D,22) SRUJet: A request for a node on an empty page (Pgno: 1235) has been made (error -351) for a B-Tree (ObjectId: 18, PgnoRoot: 79) of database C:\Windows\system32\SRU\SRUDB.dat. This is typically due to a lost I/O from storage hardware.
Please check with your hardware vendor for latest firmware revisions, make changes to your controller's caching parameters, use crash consistent hardware with Forced Unit Access support, and/or replace faulty hardware.

ESENT error 544:

svchost (3568,D,22) SRUJet: The database page read from the file "C:\Windows\system32\SRU\SRUDB.dat" at offset 884736 (0x00000000000d8000) (database page 215 (0xD7)) for 4096 (0x00001000) bytes failed verification due to a persisted lost flush detection
timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1).

The flush state on database page 215 (0xD7) was 3 while the flush state on flush map page 0 (0x0) was 2.

If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

 

Error in Event Viewer

Hi,



Thank you for writing to Microsoft Community Forums.



As you have mentioned, you have performed a repair installation on the computer and you see Event 508, 510 and 533 in Event Viewer.



I would like to inform that if you see any critical error in Event Viewer, please share the event logs with us to help you with the appropriate troubleshooting steps. Please follow the steps mentioned below to share the event logs:

1. Press Windows + X from the keyboard, select
   Event Viewer.
   
2. Expand Windows Logs from the left pane and select
   Applications.
   
3. Click Filter Current Log from extreme right pane. Then in the new windows check the box beside
   Error and click OK.
   
4. Now, look for a critical Error in the list and note down the message/information from the
   General Tab in the lower section.
   

Please reply with the status of the issue, we will be glad to help you further.



Regards,

Nikhar Khare

Microsoft Community - Moderator