Lync 2013 Client crashes
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-002618927526
We 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?
October 17th, 2013 4:25pm
did you try to uninstall and re-install it?
October 17th, 2013 6:42pm
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
October 18th, 2013 5:22am
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
18 hours 26 minutes ago
November 1st, 2013 12:24pm
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 01, 2013 4:23 PM
November 1st, 2013 4:22pm
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 01, 2013 4:23 PM
November 1st, 2013 4:22pm
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 01, 2013 4:23 PM
November 1st, 2013 7:22pm
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 01, 2013 4:23 PM
November 1st, 2013 7:22pm
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 01, 2013 4:23 PM
November 1st, 2013 7:22pm
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 01, 2013 4:23 PM
November 1st, 2013 7:22pm
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 01, 2013 4:23 PM
November 1st, 2013 7:22pm
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
November 11th, 2013 5:51am
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
Ben
November 11th, 2013 6:27am
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
November 13th, 2013 5:34pm
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
Ben
We saw the same thing. Duplicate updates do not always cause problems.
November 13th, 2013 6:07pm
My issue was not an immediate crash on starting lync, it happened after lync was running for some time (random).
November 13th, 2013 6:07pm
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?
November 13th, 2013 11:34pm
I am having the same problem as Dennis.... any solutions?
April 8th, 2014 4:11pm
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
17 hours 33 minutes ago
June 27th, 2014 1:21pm
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
June 27th, 2014 5:17pm
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
June 27th, 2014 5:17pm
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
June 27th, 2014 8:17pm
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
June 27th, 2014 8:17pm
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.
November 19th, 2014 12:25am
Thank you soo much..
It is working.. :-)
March 23rd, 2015 7:40am