Log Name:      Application
Source:        Application Error
Date:          1/5/2025 1:46:50 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Private
Description:
Faulting application name: DllHost.exe, version: 10.0.19041.3636, time stamp: 0x6d07b58e
Faulting module name: kpm_integration.dll, version: 21.19.13.549, time stamp: 0x6737728e
Exception code: 0xc0000005
Fault offset: 0x00016676
Faulting process id: 0x7a80
Faulting application start time: 0x01db5ef22947be9a
Faulting application path: C:\Windows\SysWOW64\DllHost.exe
Faulting module path: C:\Program Files (x86)\Kaspersky Lab\Kaspersky 21.19\kpm_integration.dll
Report Id: a095813e-0a9d-4f98-b941-decdc9eb68df
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2025-01-04T21:46:50.6189778Z" />
    <EventRecordID>2253</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>Private</Computer>
    <Security />
  </System>
  <EventData>
    <Data>DllHost.exe</Data>
    <Data>10.0.19041.3636</Data>
    <Data>6d07b58e</Data>
    <Data>kpm_integration.dll</Data>
    <Data>21.19.13.549</Data>
    <Data>6737728e</Data>
    <Data>c0000005</Data>
    <Data>00016676</Data>
    <Data>7a80</Data>
    <Data>01db5ef22947be9a</Data>
    <Data>C:\Windows\SysWOW64\DllHost.exe</Data>
    <Data>C:\Program Files (x86)\Kaspersky Lab\Kaspersky 21.19\kpm_integration.dll</Data>
    <Data>a095813e-0a9d-4f98-b941-decdc9eb68df</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

 

 

How to fix this ?

I already checked the windows done SFC scan and System Restore 

Hello @AlRashed,

Unfortunately, you are experiencing a known error.
It will only be fixed with the upcoming MR20 version.
According to some reports from beta testers, the solution has been found.