PS6 suddenly quit with this message:
This is the firest time I have ever encountered the Compatibility message. It seems Windows sees the program as being an old one.
Here's the Events Report.
Log Name: Application
Source: Application Error
Date: 5/30/2012 3:16:17 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Hudechrome-PC
Description:
Faulting application name: Photoshop.exe, version: 13.0.0.0, time stamp: 0x4f61c045
Faulting module name: atio6axx.dll, version: 6.14.10.11631, time stamp: 0x4f7e509e
Exception code: 0xc000041d
Fault offset: 0x0000000000a57064
Faulting process id: 0x121c
Faulting application start time: 0x01cd3e89703738e1
Faulting application path: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Photoshop.exe
Faulting module path: C:\Windows\system32\atio6axx.dll
Report Id: 1302feba-aaa5-11e1-88d0-002618e82977
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="2012-05-30T22:16:17.000000000Z" />
<EventRecordID>12107</EventRecordID>
<Channel>Application</Channel>
<Computer>Hudechrome-PC</Computer>
<Security />
</System>
<EventData>
<Data>Photoshop.exe</Data>
<Data>13.0.0.0</Data>
<Data>4f61c045</Data>
<Data>atio6axx.dll</Data>
<Data>6.14.10.11631</Data>
<Data>4f7e509e</Data>
<Data>c000041d</Data>
<Data>0000000000a57064</Data>
<Data>121c</Data>
<Data>01cd3e89703738e1</Data>
<Data>C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Photoshop.exe</Data>
<Data>C:\Windows\system32\atio6axx.dll</Data>
<Data>1302feba-aaa5-11e1-88d0-002618e82977</Data>
</EventData>
I'm running CS6 on Win7.
I see the old bugaboo ati is indicated, and is most likely the cause, yet the appearance of the compatibility report is new.
Earlier, I had a problem using the Quick Selection Tool. The screen went black instead of showing the cursor. I had to quit CS6 and restart to fix it. An hour or 2 later, this crash.
I expected that. Unfortunately, I have another program that reqires OpenCL to operate at a reasonable speed, which I use for batch processing of certain data. 12.2 runs as a slug with that program. 24+sec per image vs 7 sec with 12.4.
Rock and a hard place. Maybe 12.5 will fix things.
Chris, what did Windows actually do with respect to a compatibility fix?
North America
Europe, Middle East and Africa
Asia Pacific