Excel crashes when entering numbers and formulas into cells

[AAinSB]

Version: 2008 Operating System: Mac OS X 10.6 (Snow Leopard) Processor: Intel This only happens with one file...I have tried switching users, bringing it over to Sun Office and then bringing it back, bringing it to 2004 and back, reinstalling 2008, etc. It works fine with Windows 2003.

I have also copied and moved tabs to a new spreadsheet and the problem still occurs after a few hours of productivity.

I think the file is corrupted as other spreadsheets work fine. Any thoughts on how to fix?

Thanks much! Andy

P.S. Here are the gory details:

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2010-05-26 10:20:31 -0700
Application Name: Microsoft Excel
Application Bundle ID: com.microsoft.Excel
Application Signature: XCEL
Application Version: 12.2.4.100205
Crashed Module Name: Microsoft Excel
Crashed Module Version: 12.2.4.100205
Crashed Module Offset: 0x00162cf8
Blame Module Name: Microsoft Excel
Blame Module Version: 12.2.4.100205
Blame Module Offset: 0x00162cf8
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x00163cf8 in __mh_execute_header + 0x00162CF8 (Microsoft Excel + 0x00162cf8)
# 2 0x0016c16a in __mh_execute_header + 0x0016B16A (Microsoft Excel + 0x0016b16a)
# 3 0x002e7305 in __mh_execute_header + 0x002E6305 (Microsoft Excel + 0x002e6305)
# 4 0x002e79ec in __mh_execute_header + 0x002E69EC (Microsoft Excel + 0x002e69ec)
# 5 0x002e7b3f in __mh_execute_header + 0x002E6B3F (Microsoft Excel + 0x002e6b3f)
# 6 0x002d2e2e in __mh_execute_header + 0x002D1E2E (Microsoft Excel + 0x002d1e2e)
# 7 0x002d5e3f in __mh_execute_header + 0x002D4E3F (Microsoft Excel + 0x002d4e3f)
# 8 0x0017f854 in __mh_execute_header + 0x0017E854 (Microsoft Excel + 0x0017e854)
# 9 0x000ac9c6 in __mh_execute_header + 0x000AB9C6 (Microsoft Excel + 0x000ab9c6)
# 10 0x000ae3dc in __mh_execute_header + 0x000AD3DC (Microsoft Excel + 0x000ad3dc)
# 11 0x001879a2 in __mh_execute_header + 0x001869A2 (Microsoft Excel + 0x001869a2)
# 12 0x00876b24 in __mh_execute_header + 0x00875B24 (Microsoft Excel + 0x00875b24)
# 13 0x00a3b3d2 in __mh_execute_header + 0x00A3A3D2 (Microsoft Excel + 0x00a3a3d2)
# 14 0x01504339 in MHIView::HandleEvent(OpaqueEventHandlerCallRef*, MEvent&amp + 0x00000541 (MicrosoftComponentPlugin + 0x000a5339)
# 15 0x00a3b2a2 in __mh_execute_header + 0x00A3A2A2 (Microsoft Excel + 0x00a3a2a2)
# 16 0x01503308 in MHIView::GetMHIView(OpaqueControlRef*) + 0x000000F0 (MicrosoftComponentPlugin + 0x000a4308)
# 17 0x014fb134 in MEventHandler::FRemoveHandler(unsigned long, unsigned long) + 0x000001DE (MicrosoftComponentPlugin + 0x0009c134)
# 18 0x992ac0a9 in .objc_class_name_IMKInkInputSession + 0x98F66751 (HIToolbox + 0x000080a9)
# 19 0x992ab370 in .objc_class_name_IMKInkInputSession + 0x98F65A18 (HIToolbox + 0x00007370)
# 20 0x992cdb55 in .objc_class_name_IMKInkInputSession + 0x98F881FD (HIToolbox + 0x00029b55)
# 21 0x9931be46 in .objc_class_name_IMKInkInputSession + 0x98FD64EE (HIToolbox + 0x00077e46)
# 22 0x9931bc13 in .objc_class_name_IMKInkInputSession + 0x98FD62BB (HIToolbox + 0x00077c13)
# 23 0x9931a4f0 in .objc_class_name_IMKInkInputSession + 0x98FD4B98 (HIToolbox + 0x000764f0)
# 24 0x99319ff3 in .objc_class_name_IMKInkInputSession + 0x98FD469B (HIToolbox + 0x00075ff3)
# 25 0x993198fe in .objc_class_name_IMKInkInputSession + 0x98FD3FA6 (HIToolbox + 0x000758fe)
# 26 0x992ac0a9 in .objc_class_name_IMKInkInputSession + 0x98F66751 (HIToolbox + 0x000080a9)
# 27 0x992ab370 in .objc_class_name_IMKInkInputSession + 0x98F65A18 (HIToolbox + 0x00007370)
# 28 0x992cdb55 in .objc_class_name_IMKInkInputSession + 0x98F881FD (HIToolbox + 0x00029b55)
# 29 0x992df63b in .objc_class_name_IMKInkInputSession + 0x98F99CE3 (HIToolbox + 0x0003b63b)
# 30 0x992ac4fa in .objc_class_name_IMKInkInputSession + 0x98F66BA2 (HIToolbox + 0x000084fa)
# 31 0x992ab370 in .objc_class_name_IMKInkInputSession + 0x98F65A18 (HIToolbox + 0x00007370)
# 32 0x992cdb55 in .objc_class_name_

 

[XinXin]

Hi Andy, this is a known issue we are investigating. If you can send me ([email protected]) your workbook, probably I can find a workaround or help repair it.

Thanks,
XinXin Liu
Test Lead, Macintosh Business Unit, Microsoft