Forum Discussion

vitalus's avatar
vitalus
Copper Contributor
Apr 21, 2026

Crash of Excel

Faulting application name: EXCEL.EXE, version: 16.0.19822.20150, time stamp: 0x69cd5771
Faulting module name: EXCEL.EXE, version: 16.0.19822.20150, time stamp: 0x69cd5771
Exception code: 0xc0000005
Fault offset: 0x000000000004879a
Faulting process id: 0xC24C
Faulting application start time: 0x1DCD1000E36A5B4
Faulting application path: C:\Program Files\Microsoft Office\root\Office16\EXCEL.EXE
Faulting module path: C:\Program Files\Microsoft Office\root\Office16\EXCEL.EXE
Report Id: 0fb8fffd-6a61-48fa-b50b-79d49dc71e0e
Faulting package full name: 
Faulting package-relative application ID: 

 

Occurs every 2-3rd day..  Kutools extension is used and  crash always occurs when Grid Focus feature of Kutools is enabled.

excel
office 365

1 Reply

  • NikolinoDE's avatar
    NikolinoDE
    Platinum Contributor
    Apr 21, 2026

    The error information you provided points to a very specific, known conflict between the Grid Focus feature of Kutools and certain security software, rather than a general issue with Excel or Kutools itself .

    Analysis of the Crash

    The crash is consistent and predictable:

    • Exception Code 0xc0000005: This is a memory access violation, meaning the application tried to use memory it wasn't allowed to . In this specific scenario, it's triggered by security software intervening in Excel's processes.
    • The Culprit: Cisco Secure Endpoint: The crash pattern you described is a documented issue. Cisco has confirmed that the Exploit Prevention engine in Cisco Secure Endpoint (formerly AMP for Endpoints) can mistakenly identify Kutools' Grid Focus feature as a threat, causing Excel to crash .

    How to Resolve the Conflict

    You will need administrative assistance to apply the following fix within the Cisco Secure Endpoint policy. Since it involves security software, you likely cannot do this yourself.

    1. Verify the Diagnosis: The Cisco support documentation provides a specific workaround: modifying the policy to exclude a Windows system file used by Kutools. This confirms the conflict .
    2. Apply the Policy Fix: An IT administrator needs to edit the Secure Endpoint policy XML for your machine or organization to exclude the wbemdisp.dll file from monitoring for EXCEL.EXE .
    3. Alternative Workaround: If the policy cannot be changed immediately, disabling the "Grid Focus" feature in Kutools should prevent the crashes, as you've already identified. This remains the most effective short-term solution.

    Additional General Troubleshooting Steps

    While the conflict is the primary cause, ensuring your software is up-to-date is always good practice:

    • Update Kutools: Make sure you have the latest version of the Kutools add-in, as vendors sometimes release updates to improve compatibility .
    • Update Microsoft 365: Your version of Excel (16.0.19822.20150) is a Monthly Enterprise Channel release from early 2025. Running the latest Office updates can provide fixes and general stability improvements .

    I hope this information helps you and resolve the issue quickly.