Event ID 474

Hello all

I Hope you are Well.

I receive this Error occasionally, always Overnight.

Log Name: Application
Source: ESENT
Date: 31/08/2025 00:22:48
Event ID: 474
Task Category: (2)
Level: Error
Keywords: Classic
User: N/A
Computer: KNC-HTPC
Description:
wuaueng.dll (6848,D,29,0) SUS20ClientDataStore: The database page read from the file "C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.edb" at offset 15106048 (0x0000000000e68000) (database page 921 (0x399)) for 16384 (0x00004000) bytes failed verification due to a page checksum mismatch. The stored checksum was [6e0d11f2d06acb89:158a158a8cdcaacf:25ca5a35e89b7147:6d836d8386fe9e2f] and the computed checksum was [6e0d11f2d06acb89:158a158a8cdcaacf:27f0580f368b926f:6d836d8386fe9e2f]. The read operation will fail with error -1018 (0xfffffc06). If this condition persists then please 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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="ESENT" />
<EventID Qualifiers="0">474</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2025-08-30T23:22:48.4517858Z" />
<EventRecordID>4671</EventRecordID>
<Correlation />
<Execution ProcessID="6848" ThreadID="0" />
<Channel>Application</Channel>
<Computer>KNC-HTPC</Computer>
<Security />
</System>
<EventData>
<Data>wuaueng.dll</Data>
<Data>6848,D,29,0</Data>
<Data>SUS20ClientDataStore: </Data>
<Data>C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.edb</Data>
<Data>15106048 (0x0000000000e68000)</Data>
<Data>16384 (0x00004000)</Data>
<Data>-1018 (0xfffffc06)</Data>
<Data>[6e0d11f2d06acb89:158a158a8cdcaacf:25ca5a35e89b7147:6d836d8386fe9e2f]</Data>
<Data>[6e0d11f2d06acb89:158a158a8cdcaacf:27f0580f368b926f:6d836d8386fe9e2f]</Data>
<Data>921 (0x399)</Data>
</EventData>
</Event>

It says that the cause is 'Likely Faulty Hardware' but everything in Device Manager shows as Working.

Any suggestions?

Thanks in advance

Kevin

This is what I found regarding that event:

This error indicates a checksum mismatch in the DataStore.edb file used by Windows Update. ESENT (Extensible Storage Engine) is flagging corruption in a database page, which usually points to:

• Disk I/O issues (bad sectors, failing SSD/HDD)
• Memory instability (especially during idle/overnight cycles)
• Power state transitions (sleep/hibernate/resume anomalies)
• Antivirus or backup software interference during update scans

In a command prompt as admin:

Run chkdsk /f /r on the system drive.
This tells Windows to scan the drive for errors, fix file system problems, and also check the physical disk surface for bad sectors.

Also:

In a command prompt as admin:


Renames the DataStore.edb database file (where Windows keeps the update history and cached update metadata). By renaming it, Windows will generate a new one the next time the update service runs.

Personally, I don’t think I have ever checked the event viewer. It just gives people something to worry about generally when there’s nothing to worry about.

Hello @antspants

Thanks for the Reply.

The Disc Scan returned No Errors so that is Good.

I have also Renamed the DataStore.edb so I will see how it goes.

The only reason I have been keeping an eye on the Event Viewer is because of the Explorer Crashes Overnight which seem to have eased, at the moment at least.

You are Right though, I should only really look at Event Viewer when there is a Problem

Thanks

Kevin

if you do get errors again it maybe worthwhile checking the reliability monitor and then problem devices.

reliability monitor
control panel > security & maintenance > maintenance > reliability monitor

problem devices
start > windows tools > system information > components > problem devices

it may help in any future error messages.
best of luck, Steve ..

Hello @XxXxX

Thanks for the Reply.

I did check the Reliability Monitor and there were No Issues.

I was not aware of the Windows Tools so Thanks for that Tip.

Kevin

kncowans said:

Hello @antspants

Thanks for the Reply.

The Disc Scan returned No Errors so that is Good.

I have also Renamed the DataStore.edb so I will see how it goes.

The only reason I have been keeping an eye on the Event Viewer is because of the Explorer Crashes Overnight which seem to have eased, at the moment at least.

You are Right though, I should only really look at Event Viewer when there is a Problem

Thanks

Kevin

Click to expand...

I do remember the Plex issues you were having and event ID’s running rampant

Hello @antspants

Yes, I felt like a Headless Chicken chasing Crashes

I ended up doing a Clean Install of WIndows 11 so I could eliminate any accumulated Junk.

Things seem to be Better, for the most part.

I have had to Return my New Fractal Designs Ridge Case though as the Front USB-C was causing Over Current Errors.

According to the RMA Tracker, the Case has been Tested and has been shown to be Faulty so I will be receiving a Replacement Next Week.

All Fun

Kevin

kncowans said:

According to the RMA Tracker, the Case has been Tested and has been shown to be Faulty so I will be receiving a Replacement Next Week

Click to expand...

Best outcome. I love when it’s easy(ish)

kncowans said:

According to the RMA Tracker, the Case has been Tested and has been shown to be Faulty so I will be receiving a Replacement Next Week.

All Fun

Click to expand...

Hmmm.. hard to believe that is the case with the case. Not ruling it out though.

Since memory instability is also one of the potential factors on the list perhaps a scan might be in order?

I find MemTest 86 to be fairly reliable. Have used it for years.

Recently had to return two different sets of brand new Crucial RAM before I could get this reading.