Where do I begin... At work we use a pretty complex macro-enabled spreadsheet to do estimates using imported data. Recently the data for these jobs has become large enough to require 64-bit Excel. This is when we started having issues. We're using the same exact template of the spreadsheet as we did with 32-bit Excel, where it worked fine. The error that appears in the Application Event log always involves VBE7.dll:
Faulting application name: EXCEL.EXE, version: 15.0.4737.1000, time stamp: 0x558018bb
Faulting module name: VBE7.DLL, version: 0.0.0.0, time stamp: 0x54d13f31
Exception code: 0xc0000005
Fault offset: 0x00000000000ee686
Faulting process id: 0x12e4
Faulting application start time: 0x01d0ca20bac9fb9f
Faulting application path: C:\Program Files\Microsoft Office 15\Root\Office15\EXCEL.EXE
Faulting module path: C:\Program Files\Common Files\Microsoft Shared\VBA\VBA7.1\VBE7.DLL
Report Id: 703aa081-3628-11e5-82e4-3417ebb6749a
Faulting package full name:
Faulting package-relative application ID:
It occurs upon enabling macros, even if the spreadsheet was working fine before the previous save. Once the crash occurs, it will crash every time macros are enabled on any PC. The only way to "fix" it is to open it without macros and re-compile the VB code (via Developer tab > Visual Basic > Debug > Compile) and re-save. The data in the spreadsheet seems to be unaffected by the corruption, only the VB portion is somehow is affected.
After several weeks of testing we can reproduce it on several machines running 64-bit Excel by simply doing the following:
Open a good version of the spreadsheet
Breathe a sigh of relief
Don't change a thing
and Save it
Repeat until crash occurs (usually 3-4 times)
It seems to happen regardless of whether the file is local or on a network drive. Excel is completely closed (as verified by task manager) between each open / close cycle. As I said, once the crash / corruption occurs, it crashes every single time macros get enabled until we re-compile. The PC's we've reproduced it on all have plenty of resources to spare when it occurs.
We've tried full online repairs of Office... fresh installs on a fresh system (no plugins)... Any ideas?