I did some google searching and for lr 5 there was a comment about deleting the preference file. I tried that, no luck, same behavior.
And I also deleted the default catalog and lock files that the program creates - same error.
this morning i un-installed, re-insalled, re-downloaded, reinstalled, re-installed patch - same error.
Does Adobe Support follow this forum?
From the windows event log
Faulting application name: lightroom.exe, version: 188.8.131.52, time stamp: 0x5523190c
Faulting module name: ig7icd64.dll, version: 10.18.10.3910, time stamp: 0x53e8f299
Exception code: 0xc0000005
Fault offset: 0x0000000000039894
Faulting process id: 0x120c
Faulting application start time: 0x01d09a22597fb2eb
Faulting application path: C:\Program Files\Adobe\Adobe Lightroom\lightroom.exe
Faulting module path: C:\Windows\SYSTEM32\ig7icd64.dll
Report Id: 996a5e19-0615-11e5-8260-7824afca232c
Faulting package full name:
Faulting package-relative application ID:- <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="2015-05-29T15:15:55.000000000Z" /><EventRecordID>1284</EventRecordID><Channel>Application</Channel><Computer>b-tab</Computer><Security />
</System>- <EventData><Data>lightroom.exe</Data><Data>184.108.40.206</Data><Data>5523190c</Data><Data>ig7icd64.dll</Data><Data>10.18.10.3910</Data><Data>53e8f299</Data><Data>c0000005</Data><Data>0000000000039894</Data><Data>120c</Data><Data>01d09a22597fb2eb</Data><Data>C:\Program Files\Adobe\Adobe Lightroom\lightroom.exe</Data><Data>C:\Windows\SYSTEM32\ig7icd64.dll</Data><Data>996a5e19-0615-11e5-8260-7824afca232c</Data><Data /><Data />
There are two other reports that I found involving this intel graphics driver dll for adobe products. I have asked Asus for any input before i attempt to install the generic intel graphic drivers.
There is a SOCPackage patch from Asus that they suggest would fix the problem. Running it did not fix the problem - however, taking the dll from the unpacked patch and manually coping it into windows/system32 DID fix the problem.
I do not know why their patch failed to update the dll when it ran,