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