mattgrimley Posted December 15, 2015 Posted December 15, 2015 Ahh, a different process. i have just confirmed (via rebuilding again) that a clean built machine with all non Office updates assigned works fine. Time to start installing office updates one by one.... 1
danielvw Posted December 16, 2015 Posted December 16, 2015 I have crash too in Word, Excel, PP, Outlook in some Desktops/Notebooks. Win7-64bit Office2013. Format Notebook and new Installation. Disabled Hardware Accel, uninstall Abbyy Finereader, uninstall/disabled add-in etc in IE and Office, change Printer default, Nvidia/Intel Driver Update. https://support.microsoft.com/en-us/kb/2975838 . Now it is better, before many crash, now 1 to 4 crash everyday. I have newer seen before this problem. What can we do? Faulting application name: EXCEL.EXE, version: 15.0.4779.1001, time stamp: 0x564c261b Faulting module name: ntdll.dll, version: 6.1.7601.19045, time stamp: 0x56258e62 Exception code: 0xc0000005 Fault offset: 0x0002e3c6 Faulting process id: 0x18b0 Faulting application start time: 0x01d137e03013f870 Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\EXCEL.EXE Faulting module path: C:\windows\SysWOW64\ntdll.dll Report Id: 48ddbc83-a3d4-11e5-81c0-00b56d0607b7 Faulting application name: WINWORD.EXE, version: 15.0.4779.1001, time stamp: 0x564c2980 Faulting module name: ntdll.dll, version: 6.1.7601.19045, time stamp: 0x56258e62 Exception code: 0xc0000005 Fault offset: 0x0002e423 Faulting process id: 0x2e60 Faulting application start time: 0x01d1375c923cc709 Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\WINWORD.EXE Faulting module path: C:\windows\SysWOW64\ntdll.dll Report Id: d57db453-a34f-11e5-81e7-0050b675f57b Faulting application name: OUTLOOK.EXE, version: 15.0.4779.1001, time stamp: 0x564c29f2 Faulting module name: EMSMDB32.DLL, version: 15.0.4779.1001, time stamp: 0x564c2964 Exception code: 0xc0000005 Fault offset: 0x001b621f Faulting process id: 0x1a24 Faulting application start time: 0x01d1370b6002adde Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\OUTLOOK.EXE Faulting module path: C:\Program Files (x86)\Microsoft Office\Office15\EMSMDB32.DLL Report Id: ac58f627-a34c-11e5-81e7-0050b675f57b Faulting application name: EXCEL.EXE, version: 15.0.4779.1001, time stamp: 0x564c261b Faulting module name: EXCEL.EXE, version: 15.0.4779.1001, time stamp: 0x564c261b Exception code: 0xc0000005 Fault offset: 0x0039cbfd Faulting process id: 0x226c Faulting application start time: 0x01d1371f35fae9fe Faulting application path: C:\PROGRA~2\MICROS~1\Office15\EXCEL.EXE Faulting module path: C:\PROGRA~2\MICROS~1\Office15\EXCEL.EXE Report Id: b5e5d1c6-a330-11e5-81e7-0050b675f57b 1
mattgrimley Posted December 16, 2015 Posted December 16, 2015 Well, i got nowhere testing individual updates.. I also tried disabling hardware acceleration, but that had no effect. Finally, i'm in the process of trying video driver updates. That seems more positive. I tried one machine which had a consistent crash. Upon updating the graphics driver (intel) and rebooting, i wouldnt crash. I've updated the driver in WDS and send a command for 10 machines to rebuild. Thanks for for the input @danielvw and i'll post back with findings! Matt
LeMarchand Posted December 16, 2015 Posted December 16, 2015 Finally, i'm in the process of trying video driver updates. Mine had the latest I could locate. Have given up and I'm now updating to 2016 - all the affected machines are in a suite and don't need SIMS.
mattgrimley Posted December 18, 2015 Posted December 18, 2015 Mine had the latest I could locate. Have given up and I'm now updating to 2016 - all the affected machines are in a suite and don't need SIMS. Well, so far every machine type that i've updated the graphics drivers on has worked consistently afterwards. Christmas break now, but i'm hoping to have left this behind and to get back to a planned roll-out of Office 2016 and Windows 10! Thanks for the advice and merry christmas, one and all!
stgoodyeara Posted December 18, 2015 Posted December 18, 2015 ive installed Office 2016 in 2 suites today and they have worked beautifully afterwards. Just got some policies to sort to re-suppress the first runs, disable addon etc as it appears the office 2013 adm doesn't work with 2016. But that a small price to pay for stability with the few weeks we've had with office.
burgemaster Posted December 18, 2015 Author Posted December 18, 2015 ive installed Office 2016 in 2 suites today and they have worked beautifully afterwards. Just got some policies to sort to re-suppress the first runs, disable addon etc as it appears the office 2013 adm doesn't work with 2016. But that a small price to pay for stability with the few weeks we've had with office. Import the new 2016 ADMs mate
danielvw Posted January 5, 2016 Posted January 5, 2016 After uninstall and install Office 2013 the crashs are stopping, yeah. Perhaps after a new Windows Install with Drivers and Softwares (Acrobat etc.), install the Office 2013 as last is the better option?
mattgrimley Posted January 5, 2016 Posted January 5, 2016 After uninstall and install Office 2013 the crashs are stopping, yeah. Perhaps after a new Windows Install with Drivers and Softwares (Acrobat etc.), install the Office 2013 as last is the better option? Are you sure it doesn't come back as soon as you put the updates back on? It does for us consistently. The issue certainly seems to be an incompatibility with video drivers. Some machines have newer ones available and appear to work after a full clean install. Others not so. Capita are apparently saying Autumn for support of Office 2016 (though why it should take them a year all of sudden, who knows), but we appear have no choice unless an MS fix or a raft of updated video drivers suddenly arrive.
gshaw Posted February 16, 2016 Posted February 16, 2016 Anyone had any joy with this? The crashes went quiet for a while but have started again with a vengeance Tried different versions of graphics drivers but no joy. Looks like Office 2016 is going to be the way we'll have to go...
LeMarchand Posted February 16, 2016 Posted February 16, 2016 Anyone had any joy with this? The crashes went quiet for a while but have started again with a vengeance Tried different versions of graphics drivers but no joy. Looks like Office 2016 is going to be the way we'll have to go... I started to get something similar, but with a different faulting module on my machine (O2016/W10). May be unconnected as no-one else has complained yet...
Michael Posted February 16, 2016 Posted February 16, 2016 It's interesting that ntdll.dll is causing issues - different versions of it exist in Windows as follows: Windows 7 = 6.1.7601.18229 Windows 8 = ? Windows 10, Build 10240 = 10.0.10240.16430 Windows 10, Build 10586 = 10.0.10586.0 The only applications I've seen do this on Windows 10 are Facility CMIS, Adsum4Dinners and Adsum4Trips. I haven't seen Office 2016 create such error. I'm speculating the bug is related to the different ntdll.dll versions - it would be interesting to see for example, whether installing Office 2013 (fully updated) on Windows 10 whether the issue is still there. Reading this discussion, it seems many are still using Windows 7 and Office 2013 fully updated and that's when the problem occurs.
StaffsPaul Posted February 16, 2016 Posted February 16, 2016 Fingers crossed, this problem seems to have gone away for us. None of our student machines have this error in the event log after 1st Feb. We were having the problem on Windows 8.1 pcs, with Office 2013. I am wondering if this January Office update fixed it: https://support.microsoft.com/en-us/kb/3114486 "After you install the November 10, 2015 update for Office 2013 (KB3101360) or the December 8, 2015 update for Office 2013 (KB3114333), Office applications may hang or crash. This can affect one or more Office applications, such as Outlook 2013, Word 2013, Excel 2013, OneNote 2013, and PowerPoint 2013." Our ntdll.dll version is 6.3.9600.18202. It has a modified date of 19/01/2016 so this might also be what fixed it for us. I don't think that was included in the above Office update - possibly in a Feb 9th windows security update.
gshaw Posted February 16, 2016 Posted February 16, 2016 (edited) Being student machines I'm guessing no Outlook users on there? That seems to be the most crashy app, followed by Word Edit: just checked, one of our affected machines has the January update installed. That said the exact KB3114486 isn't present WSUS lists it as Installed, plus running the manual updater also says product is already installed; can only assume there's been some newer updates since that also encompass it. Either way, back to the drawing board... Edited February 16, 2016 by gshaw
RLR Posted February 17, 2016 Posted February 17, 2016 Not read the whole thread but this might help: Office 2013 patch KB 3114717 freezes 32-bit Word 2013 on Win 7, 8.1, 10 | InfoWorld 1
gshaw Posted February 18, 2016 Posted February 18, 2016 @RLR that does seem to have done the trick and backed up by the findings in http://www.edugeek.net/forums/office-software/166126-office-2013-32-bit-applications-running-slow.html
maxrebo Posted March 9, 2016 Posted March 9, 2016 Not read the whole thread but this might help: Office 2013 patch KB 3114717 freezes 32-bit Word 2013 on Win 7, 8.1, 10 | InfoWorld I to was having issues with this, removed KB3114717 and now seems to be ok (tested in two IT suites), Removed this through WSUS, what has everyone done with the "unapproved" KB3114717? Its currently sat in my WSUS console (Failed and needed updates) as "unapproved".
gshaw Posted March 9, 2016 Posted March 9, 2016 I to was having issues with this, removed KB3114717 and now seems to be ok (tested in two IT suites), Removed this through WSUS, what has everyone done with the "unapproved" KB3114717? Its currently sat in my WSUS console (Failed and needed updates) as "unapproved". How did you do the removal? Script or via WSUS?
maxrebo Posted March 9, 2016 Posted March 9, 2016 How did you do the removal? Script or via WSUS? uninstalled on WSUS 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now