Faulting module name: VBE7.DLL Crashing Excel

Microsoft is aware of the issue please be patient and roll back to 2310 this is a better thread below documenting the issue please do not flood it. We are still waiting to get on the meeting with them as our IT team went on vacation. but as of now it's not fixed in the current release.

Issues with VBA after upgrating to Version 2311 (Build 17029.20108) - Microsoft Community

How to revert to an earlier version of Office - Microsoft Support

It would be a surprise if there was only 1 EXCEL CRASH on a Saturday so here is the second !!!

Faulting application name: EXCEL.EXE, version: 16.0.17231.20218, time stamp: 0x65c2ea6c

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

Exception code: 0xc0000005

Fault offset: 0x00000000000ec984

Faulting process id: 0x1bac

Faulting application start time: 0x01da5c588d53100d

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: 628b64b7-e845-4f28-b094-7637dbcb76fa

Faulting package full name: 

Faulting package-relative application ID: 

Saturday could not be the exception..... ANOTHER EXCEL CRASH !!!

Faulting application name: EXCEL.EXE, version: 16.0.17231.20218, time stamp: 0x65c2ea6c

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

Exception code: 0xc0000005

Fault offset: 0x00000000000f32af

Faulting process id: 0x384c

Faulting application start time: 0x01da5c52705c6212

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: 82a7fd86-bf16-48c7-b057-2f776c21822a

Faulting package full name: 

Faulting package-relative application ID: 

Hello again !!!

Before I start doing all the checking, I would like to add the following.

a) This is NOT a permanent problem. This is NOT a problem that, as of now, can be replicated.

b) This problem is intermittent. I have not been able to find a pattern that causes the problem.

I have not one workbook with VBA code but about 10+ workbooks that have VBA code, each one performs different tasks, for example, add a customer, add a product, add a vendor, change customer info, change product info, change vendor info, etc....

The problem has been occurring randomly on any of the 10+ workbooks. I have followed, I guess, the best coding practices in terms of releasing each and every object variable, setting them to Nothing, before executing, Application.Quit. Every other workbook that is opened to accomplish a given task is properly closed with savechanges=:False before continuing with other statements.

I wish it was a permanent problem that could be replicated again, and again, and again, etc. But this is not the case.

Will come back later after checking all points suggested. Thanks,

Ed

Here is ANOTHER !!!!

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: 0x3640

Faulting application start time: 0x01da3f2ddb52d611

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: ec64381b-0f54-4cb9-bd70-82562affef9c

Faulting package full name: 

Faulting package-relative application