none
Windows 7 - Word 2003 and Visio 2003 keep crashing

    Question

  • I have a Latitude E6510 (Intel i7 Q720 and 8GB) running Windows 7 Pro x64, this is a brand new laptop from Dell and about 2 weeks old. I installed MS Office 2003 and Visio 2003 on it and started having problems with both Word and Visio crashing. I thought maybe there is a bad Windows install so I went ahead and reinstalled Windows 7 Pro x64 and reinstalled MS Office Pro 2003 and Visio on it and had the same problems with both Word and Visio crashing again. I uninstalled and reinstalled both Visio and Word and continue to have crashes.

    Do I need to reinstall Windows and if yes should I only use Windows 7 Pro 32 bit version? When I had a laptop with Windows XP and same application I never ran into any problems.

    I Checked the logs and in Applications I found the following errors (listed by date - oldest to recent).

    Source: SidebySide

    Activation context generation failed for "c:\Windows\winsxs\amd64_microsoft-windows-m..corruptedfilerepair_31bf3856ad364e35_6.1.7600.16385_none_5cd4e58f34e57306\MsiCofire.dll".Error in manifest or policy file "c:\Windows\winsxs\amd64_microsoft-windows-m..corruptedfilerepair_31bf3856ad364e35_6.1.7600.16385_none_5cd4e58f34e57306\MsiCofire.dll" on line 2. Invalid Xml syntax.

    --------------------------------------------------------------------------------------------

    Source: Application Error

    Faulting application name: WINWORD.EXE, version: 11.0.5604.0, time stamp: 0x3f314a2f

    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

    Exception code: 0xc0000005

    Fault offset: 0x00000000

    Faulting process id: 0x1ec

    Faulting application start time: 0x01cbb108902f7ea1

    Faulting application path: C:\Program Files (x86)\Microsoft Office\OFFICE11\WINWORD.EXE

    Faulting module path: unknown

    Report Id: bf9c1a96-1cfe-11e0-a573-c0cb38cbd09d

    ------------------------------------------

    Source: Application Error

     

    Faulting application name: WINWORD.EXE, version: 11.0.5604.0, time stamp: 0x3f314a2f

    Faulting module name: mso.dll, version: 11.0.5606.0, time stamp: 0x3f334cce

    Exception code: 0xc0000005

    Fault offset: 0x0001f01b

    Faulting process id: 0x13d0

    Faulting application start time: 0x01cbb1133074f78b

    Faulting application path: C:\Program Files (x86)\Microsoft Office\OFFICE11\WINWORD.EXE

    Faulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\office11\mso.dll

    Report Id: 7147ea99-1d06-11e0-a3d5-c0cb38cbd09d

    ---------------------------------------------------------

    Source: Application Error

    Faulting application name: WINWORD.EXE, version: 11.0.5604.0, time stamp: 0x3f314a2f

    Faulting module name: mso.dll, version: 11.0.5606.0, time stamp: 0x3f334cce

    Exception code: 0xc0000005

    Fault offset: 0x0001f442

    Faulting process id: 0x6c8

    Faulting application start time: 0x01cbb1134fddc821

    Faulting application path: C:\Program Files (x86)\Microsoft Office\OFFICE11\WINWORD.EXE

    Faulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\office11\mso.dll

    Report Id: 92ceab69-1d06-11e0-a3d5-c0cb38cbd09d

     

    -----------------------------------------

    Source: Application Error

    Faulting application name: VISIO.EXE, version: 11.0.3216.0, time stamp: 0x3f3df10d

    Faulting module name: OLEAUT32.dll, version: 6.1.7600.16567, time stamp: 0x4bbc2f3d

    Exception code: 0xc0000005

    Fault offset: 0x0001290f

    Faulting process id: 0x8b0

    Faulting application start time: 0x01cbb1e0b1936d17

    Faulting application path: C:\Program Files (x86)\Microsoft Office\Visio11\VISIO.EXE

    Faulting module path: C:\Windows\syswow64\OLEAUT32.dll

    Report Id: ff454977-1dd3-11e0-b60d-c0cb38cbd09d

     

    -----------------------------------------------------

     

    Source; Application Hang

    The program WINWORD.EXE version 11.0.5604.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.

     Process ID: 1130

     Start Time: 01cbb26b650aca77

     Termination Time: 13

     Application Path: C:\Program Files (x86)\Microsoft Office\OFFICE11\WINWORD.EXE

     Report Id: b89d015c-1e8f-11e0-a78d-c0cb38cbd09d

     

    ------------------------------------------

     

    Source: SidebySide

    Activation context generation failed for "c:\Windows\winsxs\amd64_microsoft-windows-m..corruptedfilerepair_31bf3856ad364e35_6.1.7600.16385_none_5cd4e58f34e57306\MsiCofire.dll".Error in manifest or policy file "c:\Windows\winsxs\amd64_microsoft-windows-m..corruptedfilerepair_31bf3856ad364e35_6.1.7600.16385_none_5cd4e58f34e57306\MsiCofire.dll" on line 2. Invalid Xml syntax.

    -----------------------------------------------

     

    Source: Application Error

    Faulting application name: VISIO.EXE, version: 11.0.8161.0, time stamp: 0x4678ecae

    Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b29c

    Exception code: 0xc0000005

    Fault offset: 0x0002e1fe

    Faulting process id: 0x1680

    Faulting application start time: 0x01cbb37c982e8494

    Faulting application path: C:\Program Files (x86)\Microsoft Office\Visio11\VISIO.EXE

    Faulting module path: C:\Windows\SysWOW64\ntdll.dll

    Report Id: a22b61b4-1f70-11e0-8341-c0cb38cbd09d

     

    ---------------------------------------------

     

    Source: Application Error

    Faulting application name: WINWORD.EXE, version: 11.0.8328.0, time stamp: 0x4c717ed1

    Faulting module name: MSCTF.dll, version: 6.1.7600.16385, time stamp: 0x4a5bda69

    Exception code: 0xc0000005

    Fault offset: 0x000136d4

    Faulting process id: 0x17a0

    Faulting application start time: 0x01cbb380f24b57c1

    Faulting application path: C:\Program Files (x86)\Microsoft Office\OFFICE11\WINWORD.EXE

    Faulting module path: C:\Windows\syswow64\MSCTF.dll

    Report Id: abc9132e-1f74-11e0-8341-c0cb38cbd09d

     

    ---------------------------

     

    Source: SideBySide

    Activation context generation failed for "c:\Windows\winsxs\amd64_microsoft-windows-m..corruptedfilerepair_31bf3856ad364e35_6.1.7600.16385_none_5cd4e58f34e57306\MsiCofire.dll".Error in manifest or policy file "c:\Windows\winsxs\amd64_microsoft-windows-m..corruptedfilerepair_31bf3856ad364e35_6.1.7600.16385_none_5cd4e58f34e57306\MsiCofire.dll" on line 2. Invalid Xml syntax.

     

    -------------------------------------------------

     

     

     

    Friday, January 14, 2011 11:19 PM

All replies

  • It looks like some Windows DLLs in the WinSxS folder are damaged.
    Please start the command prompt (cmd.exe) with admin rights [1] and run sfc [2]:

    sfc.exe /scannow

    Is it able to find and repair broken files?

    best regards
    André

    [1] http://windows.microsoft.com/en-US/windows7/How-do-I-run-an-application-once-with-a-full-administrator-access-token
    [2] http://support.microsoft.com/kb/929833
    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Saturday, January 15, 2011 12:16 AM
  • I already ran the command and no corruption was found. Should I reinstall Windows 7 and MS products and see if I can continue to have crash problems?
    Monday, January 17, 2011 3:55 AM
  • I reinstalled Windows 7 Pro X64 again and ran into the same problem. 

    Faulting application name: VISIO.EXE, version: 11.0.3216.0, time stamp: 0x3f3df10d

    Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b29c

    Exception code: 0xc0000005

    Fault offset: 0x00033539

    Faulting process id: 0x117c

    Faulting application start time: 0x01cbb69a218d7c7e

    Faulting application path: C:\Program Files (x86)\Microsoft Office\Visio11\VISIO.EXE

    Faulting module path: C:\Windows\SysWOW64\ntdll.dll

    Report Id: 6c54260f-228d-11e0-83be-c0cb38cbd09d

    -------------------------------------------

    Could there be a problem with laptop hardware such as memory, processor that is causing the problem. Because I have other users with Latitude E6510 laptops and none are having this type of problem with Visio and Office crashing.

    Monday, January 17, 2011 11:05 PM
  • Please temporary disable antivirus。

    If the issue persists, try to troubleshoot in Clean Boot Mode.

    How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    Tuesday, January 18, 2011 6:19 AM
    Moderator
  • I disabled the symantec endpoint protection and still had problem with visio and word 2003 crashing.

    I followed the steps for troubleshooting using clean boot and could not come to conclusion. Sometime I can copy and paste from Visio to Work with no probelms and others both application crash.  A user has created a Word file for manual and trying to copy Visio drawing into the manual. Is it possible that the Word file is corrupted and causing the crash? I tried working with new word file but Word and Visio continued to crash, for example I tried creating word file 6 times and twice I ran into crashes.

    I am not sure what options are available for me at this point? Should I Install Windows 7 Pro x32 instead of Windows 7 Pro x64?

    Thanks...B

    Tuesday, January 18, 2011 10:51 PM
  • We can't debug this. Contact the Microsoft support directly.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Wednesday, January 19, 2011 2:53 PM
  • I think I need to contact Microsoft. I tried from different laptops and all tests resulted in crash. I think there issues with Visio 2003, Word 2003 and Windows 7 Pro.  I have Windows XP machines that are not having any of the issues I described.
    Wednesday, January 19, 2011 4:26 PM
  • I went ahead and logged the ticket with support.  Will just have to wait and see if $259 will do the magic.

    Wednesday, January 19, 2011 4:32 PM
  • If you have not already had Microsoft Support help you with this (or if the problem persists), can you check to see if it is related to either a roaming profile or permissions on the machine?  That could explain why even after a reinstall of both Windows & Office/Visio the same problem exists.  We have a user who is having the same problem and when someone else logs into their machine, there is no problem.  In our case the other user has lesser permissions so we have concluded that it is something related to the user's profile.

     

    We are now in the process of cutting down his roaming profile to enable use to pinpoint where the problem is located.

    Thursday, January 20, 2011 7:31 PM
  • I don't think it is related to profile or permissions since all user have Admin rights on the machines and happened to more than user but not with others based on my testing today.  I performed tests as follow:

    1)      Desktop - Dell Optiplex 380 – Windows 7 Pro 32 bit – 4 GB of Memory - I tried copying diagrams from Visio to Word and I had no crashes with Word or Visio

    2)      Desktop - Dell Precision T7500 – Windows 7 Pro x64 bit – 12 GB of Memory - I tried copying diagrams from Visio to Word and I had no crashes with Word or Visio

    3)      Laptop – Dell Vostro 1000 – Windows 7 Pro x32bit – 2 GB or Memory - I tried copying diagrams from Visio to Word and I had no crashes with Word or Visio

    The user that is having crashed with Visio and Word is using Dell Latitude E6510 with 12 GB of Memory and Win 7 Pro x64. Also, I tried 3 other Latitude E6510 or E6500 all with Win 7 Pro x64 (4 GB of memory) and had crashes with Visio and Word.

     

    Friday, January 21, 2011 9:28 PM
  • I know exactly what you mean, because I have exactly the same problem.
    I have a Latitude E6410 with Office 2003 en Visio 2003. The problem must be office 2003 in conjunction with Dell because I never had this problem before on other systems.

    If you found the solution, please let me know.

    Wednesday, January 26, 2011 10:01 AM
  • Microsoft has indicated that the problem seemed to be related to OLE32.dll. They send me instructions on how test and collect crash dump data to forward to them. I will update later..

    Wednesday, February 2, 2011 12:20 AM
  • I know this makes no sense at all, but after a lot of digging, I found that if you uninstall the 'Widcomm Bluetooth driver' that comes on Dell laptops, this will resolve the Office 2k3 problem. I uninstalled it, then downloaded the latest from Dell's site, and my Office 2k3 is working fine now.

    I have a Dell e6410.

    • Proposed as answer by dallasfan61 Wednesday, February 2, 2011 4:13 PM
    Wednesday, February 2, 2011 4:13 PM
  • I had the exact same issues with my Dell Lattitude E6510 and Office 2K7.  Downloaded the Widcomm Bluetooth driver updates from Dell like dallasfan61, and it resolved the issues with Word and Visio crashing.  I noticed an odd situation though, when the update restarted Windows and I logged back in, Windows stated that the profile I logged into could not be used, to log out and back in.  Once I logged out and back in, everything was back to normal, including Office 2K7.  Wonder if the profile was corrupt after installing Visio?
    Friday, February 4, 2011 12:34 PM
  • The E6510 has the Dell Wireless 375 Module and it is latest version.
    Friday, February 4, 2011 5:25 PM
  • Microsoft is still looking into this issue, but I am starting to think the problem might be related to either a Windows Update or there is a problem with Latitude E6510. I have few others users with E6510 that are reporting problems with Project, Excel, Word, Visio crashing and all there laptops are brand new.  Even I installed Office 2010 on an E6510 laptop and he is having issues per error below.

    Faulting application name: WINWORD.EXE, version: 14.0.4762.1000, time stamp: 0x4bae25b7

    Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b29c

    Exception code: 0xc0000374

    Fault offset: 0x000cdc9b

    Faulting process id: 0x1830

    Faulting application start time: 0x01cbc89c74850b41

    Faulting application path: C:\Program Files (x86)\Microsoft Office\Office14\WINWORD.EXE

    Faulting module path: C:\Windows\SysWOW64\ntdll.dll

    Report Id: 5382a116-3490-11e0-b8ee-c0cb38a8784b

    I will wait to see what Microsoft says and go from there. In the meantime I have installing office 2010 on few machines so my users can test before a full deployment.

    Thursday, February 10, 2011 3:17 PM
  • Hello Bluem1,

    I've the same problem with Visio crashing Windows 7/64. I also think that it is caused by one of the recent Windows Updates, because I'm quite sure that that is the only thing I've changed in the recent weeks and I'm actually not using that machine at the moment. (execption: a driver and software belonging to a Brother MFC-6890CDW and cleanups with ccleaner).

    Another bug is that Windows restarts automatically  if I've started it up and do nothing with it.

    (I have a recente clean install of windows 7 64 bit  running as a virtual machine in Virtual Box on a Macbook Pro. Visio 2003 prof and Office 2007).

     

     

     

     

     

    Tuesday, February 15, 2011 3:45 PM
  • Same problem.  2 different brand new E6510's.  How did you remove the Widcomm Driver - can't find it.

    Wednesday, February 16, 2011 3:56 AM
  • Where did you find the Widcomm driver to uninstall.  I can't find it.

    I'm having same problem on 2 brand new E6510's.

    Wednesday, February 16, 2011 3:57 AM
  • Hello Bluem1,

    I've the same problem with Visio crashing Windows 7/64. I also think that it is caused by one of the recent Windows Updates, because I'm quite sure that that is the only thing I've changed in the recent weeks and I'm actually not using that machine at the moment. (execption: a driver and software belonging to a Brother MFC-6890CDW and cleanups with ccleaner).

    Another bug is that Windows restarts automatically  if I've started it up and do nothing with it.

    (I have a recente clean install of windows 7 64 bit  running as a virtual machine in Virtual Box on a Macbook Pro. Visio 2003 prof and Office 2007).

     

     

     

     

     


    A few days later, I think I've found the answer in this article:

    http://knightfoo.wordpress.com/2010/06/14/visio-2007-and-2010-crashing/



    It relates also to earlier suggested solutions that see the bluetooth driver as the cause.

    A more general workaround is thougt to disable the 'COM Add-ons'  in Visio (and Word?).

    In Visio 2003 via:tools->options->tab security-> disable: 'Enable COM add-ins'.



    Hope this helps!
    • Proposed as answer by MRR2011 Friday, February 18, 2011 12:28 PM
    Friday, February 18, 2011 12:27 PM
  • Hi All,

    I found that if you disable the Bluetooth Add-in (Com add-in) in Visio 2010, Visio doesn't crash any more. Remenber, start Visio "as administrator" and then remove the Bluethooth add-in. BTW do the same with all Office products.

    Running Windows 7 SP1, 64-bit. Office 2010 Professional (32-bit). Dell Precision m4500.

    So, I can confirm that the bluetooth package is causing the crashes and therefor the hardware depency is explained.

     

    Regards from NL.

    Monday, March 14, 2011 1:36 PM
  • Disabled Widcomm Bluetooth software Office add-in's to fix this issue on Windows 7 32bit with Office 2003 SP3.

    See: http://community.spiceworks.com/topic/113324-office-2003-crashes-when-trying-to-copy-paste-or-save-with-windows-7-pro

    Wednesday, April 18, 2012 1:04 PM
  • I have a Latitud E6400 using Windows 7 and had the problem with Visio 2003.  I do the change in Tols-> options -> security and disable the option indicated and it works.

    Thank you

    Thursday, May 10, 2012 4:06 PM
  • I can confirm that this is still and issue (Visio Standard 2003 crashes during cut-and-paste) with Windows 7 64-bit Professional, the Bluetooth driver seems to be the issue.

    Disabled Widcomm Bluetooth software and the problem disappears.

    My Dell Lattitude E6420 is brand new in 05/2012. 8 GB RAM. Core i7. Win 7 Professional 64-bit.

    Saturday, May 12, 2012 1:24 AM