Windows 10: ESENT errors on event viewer before a critical shutdown and Out of Memory exceptions

Hi all,Machine details: Windows 10Antivirus: McAfee solidcoreRAM: 4GBAttached is the event viewer logs of application which on 30th May we have 30th May 2022 shows a ton of ESENT errors event ID 454, 482, 419.454: svchost 3744,R,98 SRUJet: Database recovery/restore failed with unexpected error -1069., 482: svchost 3744,U,98 SRUJet: An attempt to write to the file "C:\WINDOWS\system32\SRU\SRUDB.dat" at offset 98172928 0x0000000005da0000 for 0 0x00000000

:)

 

ESENT errors in Event Viewer


Not sure if this is the right place, so please move it/me if I'm misplaced.

I recently re-installed W10, and used Kari's tutorial to help me move the Users folder to a partition on another disk, using the sysprep routine.

This is a list of W10s Environment variables that apply to my account (MS/user/admin):






Those that relate to my account all seem to be pointing to the right location (H:\Users).

However, until I turned off 'Sync my settings', the event viewer was littered with errors regarding ESENT--Extensible Storage (database) Engine, recorded multiple times per minute in an infinitely repetitive sequence: Events 494, 454, 488 & 413. The 494 event is the trigger:

SettingSyncHost (2876) {068B89D8-0F81-40D5-A335-0959E66CAECB}: Database recovery failed with error -1216 because it encountered references to a database, 'C:\Users\omnes\AppData\Local\Microsoft\Windows\SettingSync\metastore\meta.edb', which is no longer present. The database was not brought to a Clean Shutdown state before it was removed (or possibly moved or renamed). The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, procedures for recovering from this error are available in the Microsoft Knowledge Base or by following the "more information" link at the bottom of this message.

Can anyone suggest a way of directing the SettingSyncHost process to the right location? The drive/partition label (C should be H:, but otherwise the path is correct, and the db file (which is a hidden, system file) exists in that location.

It's not a problem for at present, as I don't have any devices that use that account, and have turned off 'Sync my settings' via Account settings; but it may be in the future, and may also be an issue for those who have moved the Users folder and have devices that give them that syncing feeling.

Incidentally, virtually all references in the MKB describe permissions rather than location problems, and the "more information" link in Event Viewer (Event Log Online Help) provides no information (Page Not Found).

 

Critical error messages in event viewer after each shutdown

I'm getting a trio of critical error messages in event viewer after each shutdown:

- "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

- "Windows failed fast startup with error status 0xC00000D4."

- "The previous system shutdown was unexpected."

The PC starts up fine and seems to shut down very fast - within 10-12 seconds, and there seems to be no issues with startup or shutdown. But when I stumbled onto these critical messages in event viewer I got concerned. What could be triggering this? How do I troubleshoot this? They are logged in event viewer after each shutdown/reboot.

 

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