locked
Lync Crashes at start up unable to get running RRS feed

  • Question

  • I am having an issue with Lync where at start up it will crash and outlook works without issue, errors are below however i have already tried the following : 

    reinstalled office and lync, renamed tracing folder, ran as admin, logged in as different user (same issue), SFC scan, disabled Bluetooth, checked for windows updates, recreated my profile, logged onto another machine (works fine) 

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

    Pop up error : 

    Microsoft Lync has stopped working. 

    A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. 

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

    Error in Eventvwr: 

    Log Name:      Application
    Source:        Application Error
    Date:          21/11/2018 16:43:34
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      **********
    Description:
    Faulting application name: lync.exe, version: 15.0.4675.1000, time stamp: 0x54629b57
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x14a86978
    Faulting process id: 0x26f0
    Faulting application start time: 0x01d481b9550a09ab
    Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
    Faulting module path: unknown
    Report Id: c24c51d4-0c77-4f16-a3cd-2bed941b6637
    Faulting package full name: 
    Faulting package-relative application ID: 
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2018-11-21T16:43:34.009750400Z" />
        <EventRecordID>67128</EventRecordID>
        <Channel>Application</Channel>
        <Computer>********</Computer>
        <Security />
      </System>
      <EventData>
        <Data>lync.exe</Data>
        <Data>15.0.4675.1000</Data>
        <Data>54629b57</Data>
        <Data>unknown</Data>
        <Data>0.0.0.0</Data>
        <Data>00000000</Data>
        <Data>c0000005</Data>
        <Data>14a86978</Data>
        <Data>26f0</Data>
        <Data>01d481b9550a09ab</Data>
        <Data>C:\Program Files (x86)\Microsoft Office\Office15\lync.exe</Data>
        <Data>unknown</Data>
        <Data>c24c51d4-0c77-4f16-a3cd-2bed941b6637</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Wednesday, November 21, 2018 4:57 PM

All replies

  • Hi Daniel_Davies,

    Based on my research, after you install either the April 2016 or May 2016 updates for Microsoft Office 2016 or Office 2013, you may face the crashes of Lync 2013/Skype for Business 2016, and you may find the Event ID 1000 in the affected computer. To fix this, we suggest you could try to update you Lync/SFB client to the latest version. Details about this issue, you could refer to Lync, Skype for Business, or Outlook 2016 or 2013 Crash. You could download the latest version of SFB from the following document: Skype for Business downloads and updates

    In addition, we suggest you could try to delete the caches in the affected computer:
    1. SFB client cache file: %Userprofile%\AppData\Local\Microsoft\Office\16.0\Lync\sip_XXXXX
    2. SFB Registry: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Lync\sip_XXXXX

    Best Regards,
    Evan Jiang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Proposed as answer by woshixiaobai Friday, November 23, 2018 9:29 AM
    Thursday, November 22, 2018 3:11 AM
  • Hi Daniel_Davies,

    Is there any update for this issue, if the reply is helpful to you, please try to mark it as an answer, it will help others who have the similar issue.

    Best Regards,
    Evan Jiang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, November 26, 2018 6:40 AM