The client I'm working for recently upgraded all laptops to Microsoft Surface running windows 10 (version 10.0.16299) and Office 2016: Microsoft Excel 2016 MSO (16.0.9126.2295) 64-bit Microsoft Office 365 ProPlus
I'm working on an Excel VBA application that was working fine under the old laptops, but has now started crashing Excel with the following error: An unhandled win32 exception occurred in EXCEL.EXE [14756]
There are different dialog messages that appear as Excel crashes: Microsoft Excel has stopped working Windows Error Reporting has stopped working
Another forum post recommended checking the Windows Event Viewer to obtain log of Error crash report. This gave me the following details:
Faulting application name: EXCEL.EXE, version: 16.0.9126.2295, time stamp: 0x5bafc794 Faulting module name: MSCOMCTL.OCX, version: 0.0.0.0, time stamp: 0x5984a51c Exception code: 0xc0000005 Fault offset: 0x0000000000021f8f Faulting process ID: 0x42c8 Faulting application start time: 0x01d47124a3a41f4c Faulting application path: C:\Program Files\Microsoft Office\Root\Office16\EXCEL.EXE Faulting module path: C:\windows\system32\MSCOMCTL.OCX Report ID: 74d9c093-61f0-4616-b20b-dc7f2acda9a5 Faulting package full name: Faulting package-relative application ID:
I've been searching numerous forums for solutions using the information I've gathered and so far come up empty.
I've isolated the problem to a specific user action, clicking on a ListView control. This control was added to the application to replace the former Listbox control on a form in order to allow the font colour to be set to red where an item had been selected. Since moving to the Surface laptops, this ListView control appears to be causing a conflict which is causing Excel to crash. I can’t be any more sure than that. Disabling the ListView control and setting the application to use the ListBox control appears to have resolved the issue.
I hope this is helpful to others. If anyone can explain why Excel is actually crashing, I'd appreciate it as I only feel I have a workaround, rather than a fix.
I'm wondering if there is a conflict with 64 bit v 32 bit drivers/dll files. The VBA references being used are: VBA References Mark