In fact it is probably an Add In that caused Excel to crash the first time ‘round. The second potential problem can be an Add In. However I also have my own personal.xlsb workbook that contains lots of VBA that I use on a regular basis, and this workbook can also become a problem. If the workbook has its own VBA code, then this can cause the problem. The first (the one that happens to me most) is that some VBA code in one of your workbooks becomes corrupt. Well there are 2 main causes for this problem. It then “pretends” to be looking for a solution prior to telling you that it can’t fix it and you have to close the program.Īnd if your experience is anything like mine, once this starts to happen with a workbook, it keeps on happening over and over with seemingly no way out. You are inside your workbook doing something important (it always happens when you are doing something important), and then the screen background greys out, and you get a message saying Microsoft Excel has stopped working. If this happens to you then you will already be aware of this scenario. It used to happen to me a lot more in the past, but after I discovered what was causing the repeat behaviour I have been able to greatly reduce how often this occurs. I use Excel 2013 64 bit and sometimes Excel just keeps crashing on me. Relationships in Power BI and Power Pivot.Who Needs Power Pivot, Power Query and Power BI Anyway?.The Best Way to Install Power BI Desktop.30 Reasons You Should Be Considering Power BI.Dimensional Modeling (Excel and Power BI).Foundations of Power BI – Data to Dashboard.Module 1: Foundations of Power BI – Data to Dashboard.Every run of the macro, it performs the same operations on different data. It opens existing excel files and does a lot of numeric data manipulation (copy, select, delete, pivot, formulas, mail sending, etc). The macro contains a lot of code (25 modules).

Need to say that the macro still works OK in the majority of runs, but once in a while it gets stuck (around 5% of the runs during the day). Then, after some more time, the behavior was such that the macro got terminated without any popups, and the excel file was closed and opened in a recovered version, while the macro was not running anymore. When I clicked on the debug option and let it continue with F5, the macro kept going without problems.Īfter some time, I only got generic automation errors popups without a debug option. The macro stopped running properly also when only upgrading the Office 2010 to 2016 in a Windows 7 desktop.Īt first, I got a lot of runtime errors ‘1004’ with debug (Select methods, PasteSpecial methods, etc). Recently, we upgraded our desktops to Windows 10 Enterprise and Office 2016, and the macro stopped running properly. The macro was initially written in an Office 2010 file in Windows 7 Enterprise, and worked flawlessly for two years. I have a VBA macro that runs every ten minutes, all day (using Application.onTime).

Excel macros stopped working