Answered by:
Lync 2013 Client crashes

Question
-
Eventlog message:
Faulting application name: lync.exe, version: 15.0.4420.1017, time stamp: 0x5067326f
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1116
Exception code: 0xc0000017
Fault offset: 0x0000c41f
Faulting process id: 0x2918
Faulting application start time: 0x01cecb1ab5a8cccf
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 5806ca39-372c-11e3-af61-002618927526We are having this on a few lync clients. The crashes are at random, a few times per day. Generally happens when the client is idle. Windows 7 systems, with the latest version of the client. (15.0.4517.1504)Any ideas?
Thursday, October 17, 2013 8:21 PM
Answers
-
Okay, it took awhile to confirm, but problem is fixed. Reinstallation did not help, nor was it a Bluetooth related issue.
We had, in all cases, several duplicate copies of some lync updates. Removed the dupes, restarted, problem did not recur.
- Marked as answer by Everett.Chris Friday, November 1, 2013 4:23 PM
Friday, November 1, 2013 4:22 PM
All replies
-
did you try to uninstall and re-install it?
Thanks -WS SharePoint administrator, MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog *Please remember to mark your question as answered & Vote helpful,if this solves/helps your problem.*
Thursday, October 17, 2013 10:37 PM -
Hi Everett.Chris,
Did you solve the issue with the suggestion Waqas105 provided?
Did you install Bluetooth on your computer? If yes, please remove it and test the issue again.
Please also make sure you remove all instances of the Lync 2013 Security Update KB2817465.
If the issue persists, please past the entire log or message when Lync client crashes so that we know which file cause the issue.
Best Regards,
Eason Huang
- Marked as answer by Kent-Huang Sunday, October 27, 2013 4:19 AM
- Unmarked as answer by Everett.Chris Friday, November 1, 2013 4:23 PM
Friday, October 18, 2013 9:18 AM -
Okay, it took awhile to confirm, but problem is fixed. Reinstallation did not help, nor was it a Bluetooth related issue.
We had, in all cases, several duplicate copies of some lync updates. Removed the dupes, restarted, problem did not recur.
- Marked as answer by Everett.Chris Friday, November 1, 2013 4:23 PM
Friday, November 1, 2013 4:22 PM -
Hi - I am having the same issue. Can you be a little more specific on what you did in terms of removing these duplicate copies and where I would find them.
Thanks
Dennis
Monday, November 11, 2013 10:49 AM -
Hi Dennis,
You will find any Lync 2013 client associated updates in 'Programs and Features ' > 'view installed updates'
Lync 2013 client updates are listed under the Microsoft Office heading, and you can remove them from here.
Incidentally I notice that I have 3 instances of KB2825630 - but my Lync client is behaving correctly.
Kind regards
BenMonday, November 11, 2013 11:25 AM -
Thanks Ben
Hmmm, ok I have done that. No change
Ran Office repair - no change
Removed ALL Lync updates - no change
Ran Windows update to reapply all Lync updates - no change
So I still have this issue, if I run the Lync client it immediately crashes with unhandled exception.
Any ideas welcome
Regards
Dennis
Wednesday, November 13, 2013 10:31 PM -
My issue was not an immediate crash on starting lync, it happened after lync was running for some time (random).Wednesday, November 13, 2013 11:04 PM
-
Hi Dennis,
You will find any Lync 2013 client associated updates in 'Programs and Features ' > 'view installed updates'
Lync 2013 client updates are listed under the Microsoft Office heading, and you can remove them from here.
Incidentally I notice that I have 3 instances of KB2825630 - but my Lync client is behaving correctly.
Kind regards
BenWednesday, November 13, 2013 11:04 PM -
what are the errors you are getting when it crashed?
did you try with different user on the same machine, if it is specific to one machine?
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog
Thursday, November 14, 2013 4:31 AM -
I am having the same problem as Dennis.... any solutions?Tuesday, April 8, 2014 8:07 PM
-
Solution:
Rename your SIP folder here:
1. Navigate to the directory - C:\Users\username\appdata\local\microsoft\office\15.0\lync
2. Rename your sip_name@domain.com folder to sip_name@domain.old
3. Launch Lync, it will take a few seconds to launch as it creates your new sip directory.
4. Resolved.
- Proposed as answer by ryanwhitaker Friday, June 27, 2014 5:18 PM
Friday, June 27, 2014 5:17 PM -
Ran into this for a user today. I noticed that the system was using lots of generic drivers for different devices (e.g. video card, monitor, etc..) I installed the latest Chipset for the motherboard, Video drivers and after a reboot Lync started perfectly.Wednesday, November 19, 2014 12:25 AM
-
Thank you soo much..
It is working.. :-)Monday, March 23, 2015 11:40 AM -
it worked. thanks !Friday, June 10, 2016 12:49 PM
-
Instead of renaming the SIP Folder I just deleted it, seems to have resolved this issue for me.
Robert "Ben" Stewart BS, GIS, MCITP, MCSE, MCSA: Messaging
Thursday, June 23, 2016 3:40 PM -
Tried this solution. It didnt even recreate sip folder
Unsure why Skyp for Business as provided by my company would suddenly stop working.
Thanks for this option though
I will try anything
Saturday, October 29, 2016 9:40 AM -
How many Lync.exe programs do you see running in the task manager, if you see multiple end them and start the appplication again. Do you want to try clean boot , which can stop all third party application and then test the behavior
https://support.microsoft.com/en-us/kb/929135
Linus || Please mark posts as answers/helpful if it answers your question.
Wednesday, November 2, 2016 3:05 AM -
Thanks,
this option is work for me.
but my contact is not showing after rename SIP folder.
not issue thanks.
Monday, September 24, 2018 5:13 AM