Hello,

Like this poster, I also have users (3 so far, out of a pool of several hundreds) who have experienced the Lync 2013 crashes. with the "Faulting module name: igd10umd32.dll, version: 8.15.10.2342" reference. The DLL version is different in my case.

We deployed the client to all our users last week. 2 out of the 3 can restart Lync 2013 and keep using it until the next crash occurs. The last 

Aside from the usual uninstall / reinstall (via SCCM and manually) of the client, I've also tried repairing Office 2010 - which apparently worked on one of the 3 problem computers (repair was done yesterday afternoon so still under monitoring).

On another machine, I updated BIOS and graphics drivers (inspired by the IGD10UMD32.DLL reference) and the situation went from bad to worse. He can no longer start Lync 2013 at all, when the initial issue was occasional crashes. I hesitate to update anything on the other 2 machines until I'm convinced this is the way to go.

Thanks for any help you can offer.

Hi,

I think this problem is related with the igd10umd32.dll.

Please try the solutions in the following link to repair the igd10umd32.dll File.

http://www.pcmaxutilities.com/wikidllfiles/igd10umd32-dll-error-fix-guide.html

Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

Thanks for the reply Lisa.

I had tried updating the entire Intel driver set already, but I will try this and get back to you here.

___________________________________________

EDIT: OK, maybe not. There seems to be a string of malware infections reported along with that file, and the page linked refers to removing the DLL from the registry, should one want to attempt a manual fix. 

"

Three - Delete or reinstall the file on your computer

Delete the file on your computer system

If the file is not indispensable on for your computer, you can disable or delete the file on your computer.

• Start Registry Editor by clicking the Start button, typing regedit in the Search box, and pressing Enter.
• Open the HKEY_LOCAL_MACHINE folder ==> "Software" folder ==> "Microsoft" folder==> "Windows" folder ==> "Currentversion" folder.
• Click on the Run folder ==> Click on the igd10umd32.dll file.
• Delete the file by pressing Delete igd10umd32.dll key

"

Sketchy.

I'll remove the drivers manually instead and reinstall them again from scratch, instead of going the update route like I did last time.

• Edited by sboisvert Monday, February 04, 2013 5:06 PM potentially unsafe app

Thanks for the reply Lisa.

I had tried updating the entire Intel driver set already, but I will try this and get back to you here.

___________________________________________

EDIT: OK, maybe not. There seems to be a string of malware infections reported along with that file, and the page linked refers to removing the DLL from the registry, should one want to attempt a manual fix. 

"

Three - Delete or reinstall the file on your computer

Delete the file on your computer system

If the file is not indispensable on for your computer, you can disable or delete the file on your computer.

• Start Registry Editor by clicking the Start button, typing regedit in the Search box, and pressing Enter.
• Open the HKEY_LOCAL_MACHINE folder ==> "Software" folder ==> "Microsoft" folder==> "Windows" folder ==> "Currentversion" folder.
• Click on the Run folder ==> Click on the igd10umd32.dll file.
• Delete the file by pressing Delete igd10umd32.dll key

"

Sketchy.

I'll remove the drivers manually instead and reinstall them again from scratch, instead of going the update route like I did last time.

• Edited by sboisvert Monday, February 04, 2013 5:06 PM potentially unsafe app

Update:

We have tried 3 different driver versions for the Intel HD 3000 chipset (the 3 latest) and yet the problem persists for some, and not others (new cases have been discovered) - even whilst set up with identical driver versions.

Here is a complete AppCrash report:

Error	2/13/2013 1:03:52 PM	Application Error	1000	(100)

Log Name:      Application
Source:        Application Error
Date:          2/13/2013 1:03:52 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      WST25254.domain
Description:
Faulting application name: lync.exe, version: 15.0.4454.1506, time stamp: 0x50d185e0
Faulting module name: igd10umd32.dll, version: 8.15.10.2342, time stamp: 0x4d8d3b0c
Exception code: 0xc0000005
Fault offset: 0x000e33c1
Faulting process id: 0x14d4
Faulting application start time: 0x01ce0a13b4882869
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
Faulting module path: C:\WINDOWS\system32\igd10umd32.dll
Report Id: b90e27fb-7607-11e2-83a2-402cf461baa4
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="2013-02-13T18:03:52.000000000Z" />
    <EventRecordID>72342</EventRecordID>
    <Channel>Application</Channel>
    <Computer>WST25254.domain</Computer>
    <Security />
  </System>
  <EventData>
    <Data>lync.exe</Data>
    <Data>15.0.4454.1506</Data>
    <Data>50d185e0</Data>
    <Data>igd10umd32.dll</Data>
    <Data>8.15.10.2342</Data>
    <Data>4d8d3b0c</Data>
    <Data>c0000005</Data>
    <Data>000e33c1</Data>
    <Data>14d4</Data>
    <Data>01ce0a13b4882869</Data>
    <Data>C:\Program Files (x86)\Microsoft Office\Office15\lync.exe</Data>
    <Data>C:\WINDOWS\system32\igd10umd32.dll</Data>
    <Data>b90e27fb-7607-11e2-83a2-402cf461baa4</Data>
  </EventData>
</Event>

Note that these are all Windows 7 builds. The only common point is that they are all laptops. Other points of reference such as registered Office DLL versions, graphics driver versions, and the like do not allow us to filter down and find anything specific yet.

Here is a rundown of what we've done so far:

1. Repaired Office 2010

   Mixed results: some setups still crash, while others are now functioning properly.

2. Repaired Office 2010, and reinstalled Lync 2013.

   Mixed results: some setups still crash, while others - which had not been fixed by an Office 2010 repair alone - are now functioning properly.

3. Reimaged a computer from scratch (with Office 2010 and Lync 2013 included in this Win7 image).

   The Lync 2013 crashes started happening again after about 6 hour's use.

4. Our desktop management and deployment team has also pushed out the KB2760512 update.

   No apparent effect. Even on a freshly imaged computer, the Lync 2013 crash still occurs.

   

• Edited by sboisvert Wednesday, February 13, 2013 7:40 PM

Update:

We have tried 3 different driver versions for the Intel HD 3000 chipset (the 3 latest) and yet the problem persists for some, and not others (new cases have been discovered) - even whilst set up with identical driver versions.

Here is a complete AppCrash report:

Error	2/13/2013 1:03:52 PM	Application Error	1000	(100)

Log Name:      Application
Source:        Application Error
Date:          2/13/2013 1:03:52 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      WST25254.domain
Description:
Faulting application name: lync.exe, version: 15.0.4454.1506, time stamp: 0x50d185e0
Faulting module name: igd10umd32.dll, version: 8.15.10.2342, time stamp: 0x4d8d3b0c
Exception code: 0xc0000005
Fault offset: 0x000e33c1
Faulting process id: 0x14d4
Faulting application start time: 0x01ce0a13b4882869
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
Faulting module path: C:\WINDOWS\system32\igd10umd32.dll
Report Id: b90e27fb-7607-11e2-83a2-402cf461baa4
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="2013-02-13T18:03:52.000000000Z" />
    <EventRecordID>72342</EventRecordID>
    <Channel>Application</Channel>
    <Computer>WST25254.domain</Computer>
    <Security />
  </System>
  <EventData>
    <Data>lync.exe</Data>
    <Data>15.0.4454.1506</Data>
    <Data>50d185e0</Data>
    <Data>igd10umd32.dll</Data>
    <Data>8.15.10.2342</Data>
    <Data>4d8d3b0c</Data>
    <Data>c0000005</Data>
    <Data>000e33c1</Data>
    <Data>14d4</Data>
    <Data>01ce0a13b4882869</Data>
    <Data>C:\Program Files (x86)\Microsoft Office\Office15\lync.exe</Data>
    <Data>C:\WINDOWS\system32\igd10umd32.dll</Data>
    <Data>b90e27fb-7607-11e2-83a2-402cf461baa4</Data>
  </EventData>
</Event>

Note that these are all Windows 7 builds. The only common point is that they are all laptops. Other points of reference such as registered Office DLL versions, graphics driver versions, and the like do not allow us to filter down and find anything specific yet.

Here is a rundown of what we've done so far:

1. Repaired Office 2010

   Mixed results: some setups still crash, while others are now functioning properly.

2. Repaired Office 2010, and reinstalled Lync 2013.

   Mixed results: some setups still crash, while others - which had not been fixed by an Office 2010 repair alone - are now functioning properly.

3. Reimaged a computer from scratch (with Office 2010 and Lync 2013 included in this Win7 image).

   The Lync 2013 crashes started happening again after about 6 hour's use.

4. Our desktop management and deployment team has also pushed out the KB2760512 update.

   No apparent effect. Even on a freshly imaged computer, the Lync 2013 crash still occurs.

   

• Edited by sboisvert Wednesday, February 13, 2013 7:40 PM

Hi, did you manage to solve this after all?

I have the same issue with Windows 7 x64, Office 2013 x64 on a Latitude E6420 with a double monitor configuration.