Faulting module name: VBE7.DLL Crashing Excel

Anonymous
2024-01-04T17:06:22+00:00

This has been happening over and over again.... causing a considerable waste of valuable time:

Faulting application name: EXCEL.EXE, version: 16.0.17029.20108, time stamp: 0x657123fc

Faulting module name: VBE7.DLL, version: 0.0.0.0, time stamp: 0x649f24f9

Exception code: 0xc0000005

Fault offset: 0x00000000000f1a68

Faulting process id: 0x18fc

Faulting application start time: 0x01da3f2dcece709a

Faulting application path: C:\Program Files\Microsoft Office\Root\Office16\EXCEL.EXE

Faulting module path: C:\Program Files\Common Files\Microsoft Shared\VBA\VBA7.1\VBE7.DLL

Report Id: 363bb56e-f4df-4eb0-9249-64123963d735

Faulting package full name: 

Faulting package-relative application ID: 

Will Microsoft EVER fix this ?

Cheers,

Ed

Microsoft 365 and Office | Excel | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

44 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2024-02-04T23:00:01+00:00

    While we do not use tables in our files it seems to be an issue with the VBA compiler we are able to repair the file and it will open again but even basic code that is maybe 20 lines long will still crash when there is clearly no errors in it. Our organization will be meeting with Microsoft as we are a fairly large customer to see if we can get a resolution.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-02-04T22:49:23+00:00

    Please read my latest reply and let us know if it relates to your problem.

    Cheers,

    Ed

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-02-04T22:47:42+00:00

    Hello !!!

    No, I have not been able to determine the exact point/case that causes Excel to crash.

    Things I have "related" to the crash are the following:

    1. The Apps I am developing use Excel Tables.
    2. If for some reason a Table is empty and only contains the headers and I try to execute the following line of code:

    TABLEXYZ.DataBodyRange.Delete

    An error is raised, which is normal and acceptable. Since I have "Stop on All Errors" enabled, execution stops even if you have:

    On Error Resume Next

    TABLEXYZ.DataBodyRange.Delete

    On Error GoTo 0

    Once execution stops, the next thing I do is save the workbook and exit from Excel.

    The next time I try to open the workbook in "safe mode", Excel "tries" to open the workbook but does not complete opening it. It just "returns" to Windows Explorer and when this happens, I open the Event Viewer and I find the Application Error event which is the Excel crash.

    Please let me know if the above relates to your problem.

    Cheers,

    Ed

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-01-30T15:04:44+00:00

    We are experiencing the same issue it happens randomly and crashes excel immediately.

    Same here...At least I am not alone :)

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-01-30T00:50:19+00:00

    We are experiencing the same issue it happens randomly and crashes excel immediately.

    Was this answer helpful?

    0 comments