Faulting module name: VBE7.DLL Crashing Excel

I just noticed a very similar crash. I may have some useful information here:

1. I repeatedly tried the following thing over again:
   I pressed Delete on an empty cell in my Excel work sheet, which has some VBA macro code behind it which I wrote. But it somehow resulted in an error and a question if I wanted to start debugging it. When clicking Yes to start the debugging, Excel immediately closed entirely. Obviously a crash.
2. Eventually, after several attempts, I decided to save my document first, then I reopened it, en the issue was suddenly completely resolved. No exception anymore, no prompt to start debugging, everything was fine again.
3. Then I decided to check the Windows Eventlog, and I discovered the same error information as people reported here, with VBE7.DLL, error code 0xc0000005 (which means Access Violation), often meaning that something goes some direction in memory (wrong pointer in C/C++, out of bounds read, etc.). Whoops.
   Often also a security issue. Maybe a good idea if they research this.

Extra info:

> The Excel document sits on a OneDrive location.

I can confirm it does not. I am on 2402 and still have regular crashes. The code compiles cleanly. I've found it has more to do with userforms/macros than macros.

So far reverting to O365 2310 has resolved all of the instability we were experiencing with macro enabled worksheets.

Microsoft !!!

Will you ever FIX the BUG you have in Excel when a PC uses 2 or more monitors where your code CANNOT handle it with ActiveX controls?

It's been, at least, 6 years since it was first reported and you have done NOTHING !!!!!

NOTHING about it !!!!

What a SHAME !!!

Cheers,

Ed

Hi EOutlook,

Thanks for contacting us and sorry for the inconveniences,

The error message "Faulting module name: VBE7.DLL" means that Excel is crashing due to a problem with the Visual Basic for Applications (VBA) editor.

To fix this error, you can try the following solutions:

• Repair your VBA code or remove any unnecessary or problematic macros. To do this, open your Excel file in safe mode by holding the Ctrl key while launching Excel, then go to Developer > Visual Basic and check your code for errors or warnings. You can also use the Debug > Compile VBA Project command to find and fix any syntax errors. If you have any unused or unwanted macros, you can delete them from the Project Explorer window.
• Change your VBA settings to match your Excel version and system configuration. To do this, open your Excel file in safe mode, then go to Developer > Visual Basic > Tools > VBA Project Properties > General and make sure the Compile On Demand and Background Compile options are unchecked. Then go to Tools > Options > General and make sure the Break on All Errors option is checked.
• Update your VBA libraries or install any missing ones. To do this, open your Excel file in safe mode, then go to Developer > Visual Basic > Tools > References and check if any of the listed references are marked as MISSING or have a different version than your Excel version. If so, you can either uncheck them or browse for the correct or updated version of the library file. You can also use the Tools > Add-Ins command to install any additional libraries that you may need.
• Repair or update your Excel installation. To do this, go to Control Panel > Programs > Programs and Features > select the Office > right-click and select Change > Online repair. You can also check for any available updates for your Office version by going to File > Account > Update Options > Update Now.

Let me know if this helps or if you need further assistance.

Regards, Sola

“Give back to the Community. Help the next person who has this issue by indicating if this reply solved your problem. Click Yes or No below. “

Kindly note that this is a user to user forum, we are users helping other users, we aren't Microsoft employee neither are we Microsoft agents.