Random 64-bit Excel 2013 VBA crashes (VBE7.dll errors)

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:

Open in new window


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:

1.

Open a good version of the spreadsheet

2.

Enable Macros

3.

Breathe a sigh of relief

4.

Don't change a thing and Save it

5.

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?
LVL 5
Amfab SteelAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

John TsioumprisSoftware & Systems EngineerCommented:
At these hard cases there is only one way to at least get a clue of what is happening and why...
Get a newly formatted machine...load it with absolutely the bare minimum...if it works then you know that something is responsible for the crash...this could very from a mistaken permission in a registry key to a driver utility ...
If the problem insists even with the bare minimum then the last resort is Process Monitor
Look to the the thousands of entries to try to isolate the problematic ones...anything that doesn't resemble "success" or "found" is probably the offending one....rule out also standard windows processes and again keep everything bare minimum...no antivirus,no extra from the Mainboard CD....just the required drivers and Office...not even your beloved PDF printer (you can't imagine what kind of trouble i faced due to a "problematic" PDF printer....it just "killed" ERP)
0
Amfab SteelAuthor Commented:
Thanks for the comment John. We have reproduced this problem on a fresh install of Windows/Excel. The issue is definitely related to the amount of data in the template as we do not have the problem with smaller data-sets. I have found that a lot of others are having similar issues with 64bit Excel and have tried every solution with no luck. Looks like we will have to open an incident with Microsoft.
0
John TsioumprisSoftware & Systems EngineerCommented:
There is also a good chance that you have some objects that don't release memory properly...
Look in your code for objects that are set but not destroyed after the operations (e.g. recordsets)
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

J2FCommented:
Have you verified the workbook has not picked up some extraneous garbage along the way?
I've noticed an Excel crashes tends to add some extra workbook objects to the book.
A particularly nasty one, in my experience, has been the "Thisworkbook1" object.
Also the Sheetxx objects which have the same icon as the Thisworkbook object.

My problems have been with workbooks which originated in older Excel versions. (some of mine go back to the Windows 95 era) To date I have not had any problems with new workbooks created in my present environment.

Another source of crashes, which started occurring when I started running Excel on a 64bit processor (though not necessarily Excel 64 bit), has been Conditional Formatting rules that are no longer valid, have a #Ref in the refers to address.
0
Amfab SteelAuthor Commented:
So after opening an incident with Microsoft and sending them the spreadsheet in question, they confirmed it is actually a new bug with 64-bit Excel. They gave a timeframe of 3-4 months for a bug fix as they do not have an action plan yet to fix it. Thanks for your input guys.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Martin LissOlder than dirtCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Excel

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.