When I looked up the MEARWService.exe, it turns out to be part of ManageEngine Agent. This is since the latest update...
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: MEARWService.exe
P2: 0.0.0.0
P3: 00000000
P4: StackHash_0000
P5: 0.0.0.0
P6: 00000000
P7: 00000000
P8: PCH_84
P9:
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f5f3d593-0a98-49b6-a06d-6070db5b74db.tmp.WERInternalMetadata.xml
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_MEARWService.exe_fc7f4c8abf645e3c6d7b4b614c25a23544a29_79d673ab_726e2491-a348-4cf0-988e-387746ab6b55
Analysis symbol:
Rechecking for solution: 0
Report Id: 53268c68-4b8e-4138-a28b-2df4ec04bd08
Report Status: 100
Hashed bucket:
Cab Guid: 0
Second error, all part of same issue:
Faulting application name: MEARWService.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x00000000
Fault offset: 0x0000000000000000
Faulting process id: 0x24DC
Faulting application start time: 0x1DB6CD55B8A6E5A
Faulting application path: C:\Program Files (x86)\ManageEngine\UEMS_Agent\EDR\Anti-Ransomware\Public\Bin\EXE\MEARWService.exe
Faulting module path: unknown
Report Id: f70102ad-696a-4d35-bbbf-56723cfb130a
Faulting package full name:
Faulting package-relative application ID: