Photoshop 2014 crashing unless external display is present
Hello -
Running Photoshop CC 2014 on a 2013 Macbook Pro Retina Display. 16 gb ram, OS X 10.9.5 with all software updates installed as of Nov 1 2014. Recently, I've discovered that Photoshop crashes on startup if my Macbook Pro is not connected to an external display. *any* external display connected remedies the problem if it's set at the primary display, and Photoshop starts up just fine. Photoshop is the only CC 2014 app giving me this issue. Photoshop CC doesn't - it launches fine without an external display connected.
I have tried a complete uninstall of Photoshop CC 2014 and reinstall, even used Adobe's clean uninstall tool. Have tried removing Photoshop preferences. Have disabled 3rd party plugins. Have started in "safe mode." Have turned off Extensis Suitcase's auto-activation plugin. Have tried without Suitcase open at all. Nothing has remedied the problem except for having ANY external display connected and designated as the primary display.
Will post my error log - wondered if anyone else has experienced this?
Error report from when this happens is below. Hoping something stands out to someone here for a remedy?
Process: Adobe Photoshop CC 2014 [536]
Path: /Applications/Adobe Photoshop CC 2014/Adobe Photoshop CC 2014.app/Contents/MacOS/Adobe Photoshop CC 2014
Identifier: com.adobe.Photoshop
Version: 15.2.1 (15.2.1.257)
Code Type: X86-64 (Native)
Parent Process: launchd [153]
Responsible: Adobe Photoshop CC 2014 [536]
User ID: 502
Date/Time: 2014-11-01 22:12:06.764 -0500
OS Version: Mac OS X 10.9.5 (13F34)
Report Version: 11
Anonymous UUID: E5B6AC5D-74CE-231A-3696-6D8742E43C11
Crashed Thread: 0 Main Thread Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000050
VM Regions Near 0x50:
-->
__TEXT 000000010c67e000-0000000110f59000 [ 72.9M] r-x/rwx SM=COW /Applications/Adobe Photoshop CC 2014/Adobe Photoshop CC 2014.app/Contents/MacOS/Adobe Photoshop CC 2014
Thread 0 Crashed:: Main Thread Dispatch queue: com.apple.main-thread
0 com.extensis.AutoActivationPlugin.PS15 0x00000001bccf5bb8 CTFontDescriptorCopyAttributeOverride(__CTFontDescriptor const*, __CFString const*) + 44
1 com.apple.CoreText 0x00007fff923e031c TFont::InitMatrix(CGAffineTransform const*, __CTFontDescriptor const*) + 112
2 com.apple.CoreText 0x00007fff923dff80 TFont::TFont(__CTFontDescriptor const*, double, CGAffineTransform const*, __CTFontDescriptor const*) + 70
3 com.apple.CoreText 0x00007fff923dce8e CTFontCreateWithFontDescriptor + 114
4 com.apple.AppKit 0x00007fff924ea6ed -[__NSSharedFontInstanceInfo _platformFont] + 573
5 com.apple.AppKit 0x00007fff924ea195 -[__NSSharedFontInstanceInfo _textTransform] + 33
6 com.apple.AppKit 0x00007fff924ea163 -[__NSSharedFontInstanceInfo _matrix] + 22
7 com.apple.AppKit 0x00007fff924ea0b9 -[NSFont initWithInstanceInfo:renderingMode:] + 105
8 com.apple.AppKit 0x00007fff924e9dea -[__NSSharedFontInstanceInfo fontInstanceForRenderingMode:] + 383
9 com.apple.AppKit 0x00007fff924e9ae9 -[__NSFontTypefaceInfo fontInstanceForFontDescriptor:size:affineTransform:renderingMode:] + 671
10 com.apple.AppKit 0x00007fff9251a346 -[NSFont initWithCoder:] + 1731
11 com.apple.Foundation 0x00007fff950e1522 _decodeObjectBinary + 2534
12 com.apple.Foundation 0x00007fff950e09dd _decodeObject + 288
13 com.apple.AppKit 0x00007fff92541489 -[NSButtonCell initWithCoder:] + 224
14 com.apple.Foundation 0x00007fff950e1522 _decodeObjectBinary + 2534
15 com.apple.Foundation 0x00007fff950e09dd _decodeObject + 288
16 com.apple.AppKit 0x00007fff92516e26 -[NSControl initWithCoder:] + 265
17 com.apple.AppKit 0x00007fff92539ca2 -[NSButton initWithCoder:] + 44
18 com.apple.Foundation 0x00007fff950e1522 _decodeObjectBinary + 2534
19 com.apple.Foundation 0x00007fff950e262f -[NSKeyedUnarchiver _decodeArrayOfObjectsForKey:] + 1774
20 com.apple.Foundation 0x00007fff950e282b -[NSArray(NSArray) initWithCoder:] + 202
21 com.apple.Foundation 0x00007fff950e1522 _decodeObjectBinary + 2534
22 com.apple.Foundation 0x00007fff950e09dd _decodeObject + 288
23 com.apple.AppKit 0x00007fff924d05ac -[NSView initWithCoder:] + 1949
24 com.apple.AppKit 0x00007fff924d2294 -[NSClassSwapper initWithCoder:] + 528
25 com.apple.Foundation 0x00007fff950e1522 _decodeObjectBinary + 2534
26 com.apple.Foundation 0x00007fff950e09dd _decodeObject + 288
27 com.apple.AppKit 0x00007fff924d1cb8 -[NSResponder initWithCoder:] + 63
28 com.apple.AppKit 0x00007fff924cfe6f -[NSView initWithCoder:] + 96
29 com.apple.AppKit 0x00007fff92516d50 -[NSControl initWithCoder:] + 51
30 com.apple.AppKit 0x00007fff92539ca2 -[NSButton initWithCoder:] + 44
31 com.apple.Foundation 0x00007fff950e1522 _decodeObjectBinary + 2534
32 com.apple.Foundation 0x00007fff950e09dd _decodeObject + 288
33 com.apple.AppKit 0x00007fff924a9ccd -[NSNibConnector initWithCoder:] + 106
34 com.apple.AppKit 0x00007fff924a9b4e -[NSNibOutletConnector initWithCoder:] + 73
35 com.apple.Foundation 0x00007fff950e1522 _decodeObjectBinary + 2534
36 com.apple.Foundation 0x00007fff950e262f -[NSKeyedUnarchiver _decodeArrayOfObjectsForKey:] + 1774
37 com.apple.Foundation 0x00007fff950e282b -[NSArray(NSArray) initWithCoder:] + 202
38 com.apple.Foundation 0x00007fff950e1522 _decodeObjectBinary + 2534
39 com.apple.Foundation 0x00007fff950e09dd _decodeObject + 288
40 com.apple.AppKit 0x00007fff924a8782 -[NSIBObjectData initWithCoder:] + 205
41 com.apple.Foundation 0x00007fff950e1522 _decodeObjectBinary + 2534
42 com.apple.Foundation 0x00007fff950e09dd _decodeObject + 288
43 com.apple.AppKit 0x00007fff924a856f loadNib + 232
44 com.apple.AppKit 0x00007fff924a7b6c +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 288
45 com.apple.AppKit 0x00007fff9273c4d2 +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] + 140
46 com.apple.AppKit 0x00007fff92813e3c _NXLoadNib + 193
47 com.apple.AppKit 0x00007fff9281384f -[NSAlert init] + 95
48 com.adobe.Photoshop 0x000000010c71472c 0x10c67e000 + 616236
49 com.adobe.Photoshop 0x000000010c7145b8 0x10c67e000 + 615864
50 com.adobe.Photoshop 0x000000010c77da13 0x10c67e000 + 1047059
51 com.adobe.Photoshop 0x000000010c77e68a 0x10c67e000 + 1050250
52 com.adobe.Photoshop 0x000000010c71b088 0x10c67e000 + 643208
53 com.adobe.Photoshop 0x000000010c9bd67b 0x10c67e000 + 3405435
54 com.adobe.Photoshop 0x000000010c9bd829 0x10c67e000 + 3405865
55 com.adobe.Photoshop 0x000000010c680d34 0x10c67e000 + 11572
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff8d589662 kevent64 + 10
1 libdispatch.dylib 0x00007fff8b6af421 _dispatch_mgr_invoke + 239
2 libdispatch.dylib 0x00007fff8b6af136 _dispatch_mgr_thread + 52
Thread 2:
0 libsystem_kernel.dylib 0x00007fff8d588e6a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8daf9f08 _pthread_wqthread + 330
2 libsystem_pthread.dylib 0x00007fff8dafcfb9 start_wqthread + 13
Thread 3:
0 libsystem_kernel.dylib 0x00007fff8d588e6a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8daf9f08 _pthread_wqthread + 330
2 libsystem_pthread.dylib 0x00007fff8dafcfb9 start_wqthread + 13
Thread 4:
0 libsystem_kernel.dylib 0x00007fff8d588e6a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8daf9f08 _pthread_wqthread + 330
2 libsystem_pthread.dylib 0x00007fff8dafcfb9 start_wqthread + 13
Thread 5:
0 libsystem_kernel.dylib 0x00007fff8d588e6a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8daf9f08 _pthread_wqthread + 330
2 libsystem_pthread.dylib 0x00007fff8dafcfb9 start_wqthread + 13
Thread 6:
0 libsystem_kernel.dylib 0x00007fff8d588e6a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8daf9f08 _pthread_wqthread + 330
2 libsystem_pthread.dylib 0x00007fff8dafcfb9 start_wqthread + 13
Thread 7:
0 libsystem_kernel.dylib 0x00007fff8d588e6a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8daf9f08 _pthread_wqthread + 330
2 libsystem_pthread.dylib 0x00007fff8dafcfb9 start_wqthread + 13
Thread 8:
0 libsystem_kernel.dylib 0x00007fff8d588e6a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8daf9f08 _pthread_wqthread + 330
2 libsystem_pthread.dylib 0x00007fff8dafcfb9 start_wqthread + 13
Thread 9:
0 libsystem_kernel.dylib 0x00007fff8d584a56 semaphore_wait_trap + 10
1 libtbb.dylib 0x0000000111c60550 tbb::internal::rml::private_worker::thread_routine(void*) + 480
2 libsystem_pthread.dylib 0x00007fff8daf8899 _pthread_body + 138
3 libsystem_pthread.dylib 0x00007fff8daf872a _pthread_start + 137
4 libsystem_pthread.dylib 0x00007fff8dafcfc9 thread_start + 13
Thread 10:
0 libsystem_kernel.dylib 0x00007fff8d584a56 semaphore_wait_trap + 10
1 libtbb.dylib 0x0000000111c60550 tbb::internal::rml::private_worker::thread_routine(void*) + 480
2 libsystem_pthread.dylib 0x00007fff8daf8899 _pthread_body + 138
3 libsystem_pthread.dylib 0x00007fff8daf872a _pthread_start + 137
4 libsystem_pthread.dylib 0x00007fff8dafcfc9 thread_start + 13
Thread 11:
0 libsystem_kernel.dylib 0x00007fff8d584a56 semaphore_wait_trap + 10
1 libtbb.dylib 0x0000000111c60550 tbb::internal::rml::private_worker::thread_routine(void*) + 480
2 libsystem_pthread.dylib 0x00007fff8daf8899 _pthread_body + 138
3 libsystem_pthread.dylib 0x00007fff8daf872a _pthread_start + 137
4 libsystem_pthread.dylib 0x00007fff8dafcfc9 thread_start + 13
Thread 12:
0 libsystem_kernel.dylib 0x00007fff8d584a56 semaphore_wait_trap + 10
1 libtbb.dylib 0x0000000111c60550 tbb::internal::rml::private_worker::thread_routine(void*) + 480
2 libsystem_pthread.dylib 0x00007fff8daf8899 _pthread_body + 138
3 libsystem_pthread.dylib 0x00007fff8daf872a _pthread_start + 137
4 libsystem_pthread.dylib 0x00007fff8dafcfc9 thread_start + 13
Thread 13:
0 libsystem_kernel.dylib 0x00007fff8d584a56 semaphore_wait_trap + 10
1 libtbb.dylib 0x0000000111c60550 tbb::internal::rml::private_worker::thread_routine(void*) + 480
2 libsystem_pthread.dylib 0x00007fff8daf8899 _pthread_body + 138
3 libsystem_pthread.dylib 0x00007fff8daf872a _pthread_start + 137
4 libsystem_pthread.dylib 0x00007fff8dafcfc9 thread_start + 13
Thread 14:
0 libsystem_kernel.dylib 0x00007fff8d584a56 semaphore_wait_trap + 10
1 libtbb.dylib 0x0000000111c60550 tbb::internal::rml::private_worker::thread_routine(void*) + 480
2 libsystem_pthread.dylib 0x00007fff8daf8899 _pthread_body + 138
3 libsystem_pthread.dylib 0x00007fff8daf872a _pthread_start + 137
4 libsystem_pthread.dylib 0x00007fff8dafcfc9 thread_start + 13
Thread 15:
0 libsystem_kernel.dylib 0x00007fff8d584a56 semaphore_wait_trap + 10
1 libtbb.dylib 0x0000000111c60550 tbb::internal::rml::private_worker::thread_routine(void*) + 480
2 libsystem_pthread.dylib 0x00007fff8daf8899 _pthread_body + 138
3 libsystem_pthread.dylib 0x00007fff8daf872a _pthread_start + 137
4 libsystem_pthread.dylib 0x00007fff8dafcfc9 thread_start + 13
Thread 16:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x00007fff8d5889aa __select + 10
1 com.apple.CoreFoundation 0x00007fff8f408a03 __CFSocketManager + 867
2 libsystem_pthread.dylib 0x00007fff8daf8899 _pthread_body + 138
3 libsystem_pthread.dylib 0x00007fff8daf872a _pthread_start + 137
4 libsystem_pthread.dylib 0x00007fff8dafcfc9 thread_start + 13
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x00007fff7c688680 rcx: 0x0000000000010f80 rdx: 0x0000610000086180
rdi: 0x0000610000086180 rsi: 0x00007fff7c688680 rbp: 0x00007fff5357e2e0 rsp: 0x00007fff5357e2c0
r8: 0x00007fff9249331e r9: 0x0000000000000032 r10: 0x00007fff92493306 r11: 0x00007fff9249331e
r12: 0x0000000000000000 r13: 0x0000610000086180 r14: 0x0000610000086180 r15: 0x0000000000000000
rip: 0x00000001bccf5bb8 rfl: 0x0000000000010202 cr2: 0x0000000000000050
Logical CPU: 0
Error Code: 0x00000004
Trap Number: 14
Similar Messages
-
Macbook crashes with external displays, Macbook crashes with external displays
Dear Community,
I have a problem with my new (Dec. 2013) Macbook Pro. Everything worked fine until two weeks ago. Then, I connected my Macbook via VGA-adapter (original) with an LCD Monitor at home (I had done this before without any problems). My Mac froze and nothing happened, so I had to reboot it manually (press the on/off button 5 seconds). The Macbook would show a grey display und would not reboot, no matter what I tried. The secure boot program did not work, either. I could start it with disk utility and load my last time machine backup.
After I did this, everything worked fine again. Last week I tried to connect my Mac with another LCD display at work (which had also worked fine before). Same error! Mac froze and nothing worked and I had to load a backup again.
I brought my Mac to the next Apple store, where a hardware check revealed no defects.
Nonetheless, they exchanged the logic board and told me everything was fine, again.
Today, I have worked the whole day using my external display at work. Everything was ok, but I could only use the external display and not the Notebook display. When I tried to sync the two monitors to work with the Mac and the external display together – same error!
I have called the Apple store, but they had no idea and just told me that the Apple warranty does not cover third-party displays. The Apple hotline suggested looking for a driver for the external displays, but there are none. And again: Until two weeks ago, everything worked without problems.
Has anybody an idea what to do with this?
JuliaI was searching and found that the Matrox DualHead2Go maybe work. Any idea?
Thanks -
Use external display to present iphone screen for training
I have to teach newbies in my company how to use both the iPhone 4 and the iPad.
I was hoping, that there was a way to display the iPhone screen (exactly like we all see in the keynotes) so I can navigate around and they can see what's happening on an external display - instead of gathering over my shoulder.
There just has to be something - I see all the iphone costumes people use and I can't imagine there isn't a way for me to utilize it for training...
Thanks...The only way I could think to do that would be to take screenshots of the iPhone showing the things you want to teach them, and then you could buy the iPad VGA Adapter, which works with photo slideshows and movies. You might be better off taking screenshots on the iPhone and iPad and putting together a Powerpoint to demonstrate.
I guess in the Keynotes, Apple has their own custom setup that allows them to show a live feed of the iPhone screen. I hope this is helpful, sorry if it's not exactly what you were looking for.
http://store.apple.com/us/product/MC552ZM/A
Best of luck. -
How to detect if external display is present
I need my code to evaluate whether an external display is connected via a mini-display port.
Ideally, I'd like to do this by having a bash command that determines a boolean True/False value for the presence of a file. I'm just not sure what file I should be looking for, presumably something in /dev/
Any suggestions what it should be, or suggestions of a better way to make the determination (anything in applescript, bash, objective-c, or plain-old c will do)?
TIAThis seems to cover the same issue:
http://macscripter.net/viewtopic.php?id=28627
From what I can tell at the moment, a full answer is going to have to be done in Obj-C, but a short Applescript like this will at least get the number of displays connected:
tell application "Image Events"
launch
get properties of every display
quit
end tell -
Random fatal crash with external display
I have an iMac 9,1 (Intel c2d @ 2.93GHz) running OSX 10.6.1
I have my Sony Bravia KDL-46W4500 hooked up to it through display-port -> hdmi adapter -> hdmi cable. 9 out of 10 times, this works great. But occasionally, when I turn on my tv (my iMac is always on before I turn on my tv), I can see the screen being detected, followed by a complete crash/freeze of my iMac. Not even a "you have to restart" screen. It just fails, epic. I think I have seen this problem also a few times with OSX 10.5.x, so it is not something new to Snow.
Anyone care to have a guess as to what is causing it?Hi alcohol
20 or 24" iMac?
Which graphic's chip does it have?
How much RAM does it have?
Some models have a graphic's chip that shares RAM with the main memory.
Dennis -
Softproof in Lightroom and Photoshop on external display not matching
Hi,
When I soft proof an image in Lightroom (5) and in Photoshop (CS6) on my external display there is a noticeable difference between the two proofs.
This is the case both with "simulate paper & ink" on and off (with matching settings in both applications) and with a variety of different profiles being used. On my laptop screen the proofs always match (between Photoshop and Lightroom).
On the external display with soft proofing off there is an exact match between images in LR and PS. With soft proofing on saturated areas of images (particularly reds, greens and yellows) become noticeably less saturated and blocked up in LR as compared to PS. Subdued colours appear to match. It's almost like they are both using the same profile but Lightroom is squashing it into a smaller gamut. I'm fairly sure PS is correct and LR is the one with something going wrong.
I'd like to sort it as I'd prefer to soft proof in Lightroom as that's where I print from. I've read up a lot on colour management and can't find a solution.
Can anyone help?
Thanks,
Tom
(I'm on a Macbook pro running 10.8.4 and the external display is an NEC Spectraview 271 (euro version of PA271W), the display is calibrated and profiled with Spectraview 5, with an i1 Display Pro. Working space in PS is Prophoto RGB and it's set to preserve embedded profiles. I've checked with various test images but mostly been using Bill Atkinon's printer test image. I set up the image in LR and PS to match on screen position and with the same colour (white) background, I can then flick back and forth and there should be no change but there is and it's very obvious.)I'm having trouble with Lightroom 5 soft proofing with reds too. To rid my propossed print of a gamut warning I must totally desaturate or change my paper profile to glossy (or both). This is odd because my monitor is calibrated, I'm using the correct paper profiles etc and when I ignore the gamut warning my prints are looking good. This isn't helpful to you but at least your not alone....
-
Macbook Pro Retina 15" External Display
I have a Macbook Pro Retina 15" that I want to connect to a projector via HDMI connection. How do I turn on the External Display to present a Keynote Presentation? I have not tried it yet, will the Mackbook automatically connect to the projector when I connect the HDMI Cable. Also is there a screen resolution setting in the Macbook? The Projector Manual states that there is one by openning the apple in the upper left hand corner. I have tried that and I don't find any settings for resolution under it or in the Hardware section.
Analog VGA is obsolete. It is not surprising it is not well supported on newer Hardware.
Computer-makers want to transition to DisplayPort/ Mini DisplayPort, because the "heartbeat" of repainting the screen every 1/60th to 1/100th second is no longer needed. But that means Display-Makers need to have a screen buffer.
The Icon on the MenuBar only shows the last three resolutions, not all available. -
I got the following message after the crash, it happens a few times a day, my system is the base with 16gb ram late 2013 15" macbook pro retina. it only happens when i am connected to an external display, I do have a converter from vga to displayport. also, i run 4 different browsers in incognito mode as i do web testing and also have about 30 tabs open and excel and a few other apps open, not sure if this is what makes it happen or if it is the external display? it is under warranty, so if you see anything below that may relate to the hardware i can bring it in and get it fixed.
Anonymous UUID: AA4AEC5A-B8ED-31D9-CF66-7F2AC3593105
Wed May 28 09:37:14 2014
panic(cpu 4 caller 0xffffff800acdbf5e): Kernel trap at 0xffffff800ac93f39, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x0000000000000030, CR3: 0x0000000007f08013, CR4: 0x00000000001606e0
RAX: 0x0000000000000000, RBX: 0x0000000000000000, RCX: 0x0000000000023000, RDX: 0x0000000000000023
RSP: 0xffffff81f8fe39d0, RBP: 0xffffff81f8fe3a10, RSI: 0x0000000000000040, RDI: 0x0000000000146d55
R8: 0xffffff81f8fe3a68, R9: 0x0000000000000000, R10: 0x0000000000000000, R11: 0x0000000000000206
R12: 0xffffff8030309920, R13: 0x0000000000000003, R14: 0x0000000000000000, R15: 0x0000000000000004
RFL: 0x0000000000010282, RIP: 0xffffff800ac93f39, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000000030, Error code: 0x0000000000000000, Fault CPU: 0x4
Backtrace (CPU 4), Frame : Return Address
0xffffff81f8fe3660 : 0xffffff800ac22fa9
0xffffff81f8fe36e0 : 0xffffff800acdbf5e
0xffffff81f8fe38b0 : 0xffffff800acf3456
0xffffff81f8fe38d0 : 0xffffff800ac93f39
0xffffff81f8fe3a10 : 0xffffff800acafdfe
0xffffff81f8fe3a50 : 0xffffff800b0bb851
0xffffff81f8fe3a90 : 0xffffff7f8c6e608d
0xffffff81f8fe3af0 : 0xffffff7f8c70e24c
0xffffff81f8fe3b30 : 0xffffff7f8c715fb2
0xffffff81f8fe3b70 : 0xffffff7f8c715ddc
0xffffff81f8fe3b90 : 0xffffff800b0cff0d
0xffffff81f8fe3bf0 : 0xffffff800b0cdabf
0xffffff81f8fe3d40 : 0xffffff800acb66a8
0xffffff81f8fe3e50 : 0xffffff800ac26bf1
0xffffff81f8fe3e80 : 0xffffff800ac139f5
0xffffff81f8fe3ef0 : 0xffffff800ac1e043
0xffffff81f8fe3f70 : 0xffffff800acc989d
0xffffff81f8fe3fb0 : 0xffffff800acf3c76
Kernel Extensions in backtrace:
com.apple.iokit.IOAcceleratorFamily2(98.20)[990E3F01-63C7-301C-83B2-40F786CA8F2 6]@0xffffff7f8c6e4000->0xffffff7f8c748fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[244D4E48-78E6-3369-8D76-285C66EF9BF4]@0xffffff 7f8b2be000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[B889D3AB-CCC0-3FCD-A83E-D2E3E4CB537B]@0 xffffff7f8bac1000
BSD process name corresponding to current thread: UserEventAgent
Mac OS version:
13D65
Kernel version:
Darwin Kernel Version 13.2.0: Thu Apr 17 23:03:13 PDT 2014; root:xnu-2422.100.13~1/RELEASE_X86_64
Kernel UUID: ADD73AE6-88B0-32FB-A8BB-4F7C8BE4092E
Kernel slide: 0x000000000aa00000
Kernel text base: 0xffffff800ac00000
System model name: MacBookPro11,2 (Mac-3CBD00234E554E41)
System uptime in nanoseconds: 603272572446
last loaded kext at 245583784123: com.apple.filesystems.msdosfs 1.9 (addr 0xffffff7f8cc49000, size 65536)
last unloaded kext at 427763147270: com.apple.filesystems.msdosfs 1.9 (addr 0xffffff7f8cc49000, size 57344)
loaded kexts:
com.apple.filesystems.autofs 3.0
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AppleUpstreamUserClient 3.5.13
com.apple.driver.AppleGraphicsDevicePolicy 3.5.26
com.apple.driver.AppleHDA 2.6.1f2
com.apple.iokit.IOBluetoothSerialManager 4.2.4f1
com.apple.driver.AGPM 100.14.15
com.apple.driver.ApplePlatformEnabler 2.0.9d1
com.apple.driver.X86PlatformShim 1.0.0
com.apple.driver.AppleIntelHD5000Graphics 8.2.6
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.driver.AppleSMCLMU 2.0.4d1
com.apple.driver.AppleThunderboltIP 1.1.2
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.2.4f1
com.apple.driver.AppleLPC 1.7.0
com.apple.driver.AppleCameraInterface 4.26.0
com.apple.driver.AppleIntelFramebufferAzul 8.2.6
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleBacklight 170.3.5
com.apple.driver.AppleMCCSControl 1.1.12
com.apple.driver.AppleUSBTCButtons 240.2
com.apple.driver.AppleUSBTCKeyboard 240.2
com.apple.driver.AppleUSBCardReader 3.4.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.driver.AppleUSBHub 666.4.0
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.5.1
com.apple.driver.AppleAHCIPort 3.0.0
com.apple.driver.AirPort.Brcm4360 831.21.63
com.apple.driver.AppleUSBXHCI 677.4.0
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleACPIButtons 2.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 2.0
com.apple.driver.AppleAPIC 1.7
com.apple.nke.applicationfirewall 153
com.apple.security.quarantine 3
com.apple.kext.triggers 1.0
com.apple.driver.DspFuncLib 2.6.1f2
com.apple.vecLib.kext 1.0.0
com.apple.iokit.IOAudioFamily 1.9.7fc2
com.apple.kext.OSvKernDSPLib 1.14
com.apple.iokit.IOSerialFamily 10.0.7
com.apple.iokit.IOSurface 91.1
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.2.4f1
com.apple.driver.X86PlatformPlugin 1.0.0
com.apple.driver.IOPlatformPluginFamily 5.7.0d11
com.apple.AppleGraphicsDeviceControl 3.5.26
com.apple.iokit.IOAcceleratorFamily2 98.20
com.apple.driver.AppleHDAController 2.6.1f2
com.apple.iokit.IOHDAFamily 2.6.1f2
com.apple.iokit.IOBluetoothFamily 4.2.4f1
com.apple.driver.AppleSMC 3.1.8
com.apple.driver.AppleGraphicsControl 3.5.26
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.driver.AppleSMBusController 1.0.11d1
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.driver.AppleUSBMultitouch 240.9
com.apple.iokit.IOSCSIBlockCommandsDevice 3.6.6
com.apple.iokit.IOUSBMassStorageClass 3.6.0
com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.6
com.apple.driver.AppleUSBMergeNub 650.4.0
com.apple.iokit.IOUSBHIDDriver 660.4.0
com.apple.driver.AppleUSBComposite 656.4.1
com.apple.driver.AppleThunderboltDPInAdapter 3.1.7
com.apple.driver.AppleThunderboltDPAdapterFamily 3.1.7
com.apple.driver.AppleThunderboltPCIDownAdapter 1.4.5
com.apple.iokit.IOUSBUserClient 660.4.2
com.apple.iokit.IOAHCIFamily 2.6.5
com.apple.driver.AppleThunderboltNHI 2.0.1
com.apple.iokit.IOThunderboltFamily 3.2.7
com.apple.iokit.IO80211Family 630.35
com.apple.driver.mDNSOffloadUserClient 1.0.1b5
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOUSBFamily 677.4.0
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 278.11
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.AppleKeyStore 2
com.apple.driver.DiskImages 371.1
com.apple.iokit.IOStorageFamily 1.9
com.apple.iokit.IOReportFamily 23
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 2.0
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0
com.apple.kec.pthread 1
Model: MacBookPro11,2, BootROM MBP112.0138.B07, 4 processors, Intel Core i7, 2 GHz, 16 GB, SMC 2.18f10
Graphics: Intel Iris Pro, Intel Iris Pro, Built-In
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x134), Broadcom BCM43xx 1.0 (6.30.223.154.63)
Bluetooth: Version 4.2.4f1 13674, 3 services, 23 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM0256F, 251 GB
USB Device: Internal Memory Card Reader
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB Receiver
Thunderbolt Bus: MacBook Pro, Apple Inc., 17.1Hey SreeHarsha Vardhan,
Thanks for using Apple Support Communities.
Sounds like you are having trouble with the screen on your Macbook. If you are not getting anything on the screen, take a look at this article.
Apple computers: Troubleshooting issues with video on internal or external displays
http://support.apple.com/kb/HT1573
Have a nice day,
Mario -
Photoshop CC 2014 crash when opening or creating new files when running with Cintiq 13HD.
I have a problem where Photoshop CC 2014 crashes when trying to open or create a new file while the Photoshop window is being displayed on my Cintiq 13HD.
When Photoshop is being displayed on my main monitor it doesn't crash.
I'm running Windows 7 (64 bit) and have updated my graphics and wacom drivers to their latest versions and Photoshop is completely up to date. (I'm running the 30-day free trial)
Here's the event log of the crash:
Faulting application name: Photoshop.exe, version: 15.2.1.257, time stamp: 0x543dbc5e
Faulting module name: atig6txx.dll, version: 8.14.1.6398, time stamp: 0x54176130
Exception code: 0xc0000005
Fault offset: 0x00000000000122b7
Faulting process id: 0x23dc
Faulting application start time: 0x01d0030b1092334e
Faulting application path: D:\Program Files (x86)\Adobe\Adobe Photoshop CC 2014\Photoshop.exe
Faulting module path: C:\Windows\system32\atig6txx.dll
Report Id: 61680f48-6efe-11e4-aeeb-bc5ff45851eaAs you can already see, your ATI/AMD video card drriver is crashing.
Update the driver from AMD's website to pick up all the bug fixes you are missing. -
Here in France, it's getting late, 9.45 PM, that is 12 hours after the first crash of Photoshop CC 2014 on my Mac OS 10.9.4.
Nothing changed on my computer, excepted the PhCC14 update.
Then I launched the app and it crashed right after displaying the workframe.
I tried and tried so many things :
Ashutosh.Nigam suggested me in this forum to change the permissions to SLStore & SLCache Folder, but it did not work.
Ali from french Adobe support told me to delete my Settings files, but it was not enough.
A girl with no name from the same team told me to update my graphics card driver, but, you know, I run the latest Mac OS X version and everything is updated, mademoiselle.
Stephane sent me a link to a huge page of things to do :
- Troubleshoot account-specific fonts, but there wasn't any corrupted font
- Delete account-specific Adobe cache files but... guess what...
- Troubleshoot account-specific login items but... yes, that's it, I can see you understand me
- Reset the access settings on the user account's Library folder... oh god, that was fun, I used the Terminal and sudo commands
- I checked the disk and repaired all permissions...
I did all of these things because when I tried to open PhCC in an other admin session, it worked. So it could be an incompatibility between my session and PhCC. But, but, but, when I tried again to lauch the app in the second session, it worked fine but refused to quit. Ha ha ha.
Last call to the french support : "Désolé Monsieur, you didn't spend 2000 € for a specific help, but because you have lost a whole day of work, we will pay you back 2€. And no, Photoshop won't work anymore on your session. You have to move all your files to a new session."
It's unfair ! The software was running gently on my session, Adobe change things and I have to break everything on my computer, move every config from one session to another with absolutely no warranty that it won't crash again.
It's NOT what I pay Adobe CC each month for.
Very disappointed Jean-LucAnyone know how to read a crash report?
I can print with Lightroom, there is nothing wrong with the printer, or the file. But I want to print with Photoshop without a crash. Besides, Lightroom doesn't give me access to all of my print settings.
Hoping someone can help, I"m exasperated..... -
Photoshop CC 2014 crashes on creating 3D objects
Hello, I need help with this problem of Photoshop in this computer.
Photoshop CC 2014 crashes when choosing 3D > New 3D Extrusion From Selected Path and the rest of operations from this menu.
It can show the 3D Workspace, but creating 3D objects causes the program to crash. The GPU enhanced feature Perspective Warp works.
In Preferences > Performance Photoshop detects the graphics card as NVIDIA Corporation GeForce GT 610/PCIe/SSE2, and changing the Advanced Settings Mode to Basic does not solve the problem. Total VRAM says 2019 MB.
I've already installed 4GB more of RAM and a different graphics card (NVIDIA) apart of the integrated graphic card (AMD) trying to fix this problem, but it remains the same.
Drivers are updated and working (old uninstalled).
Resetting Preferences and using another Administrator account also does not work.
This is annoying, I need to do the work in 3D using computers from others and I don't understand why only this feature fails and causes such bad behavior.
Your help would be appreciated. Thank you.
Information extracted from dxdiag:
Operating System: Windows 8.1 64-bit
Memory: 8192MB RAM
DirectX Version: DirectX 11
Processor: AMD E1-2500 APU with Radeon(TM) HD Graphics (2 CPUs), ~1.4GHz
Card name: NVIDIA GeForce GT 610
Current mode: 1280 x 1024 (32 bit) (60Hz)
Display Memory: 4042 MB
Dedicated Memory: 1994 MB
Shared Memory: 2047 MBThanks for your response. Our mandatory profiles and regular local profiles are all generated from the same default user profiles, so the app data is the same. We have system restrictions set by GPO's, so perhaps it's something related to group policy?
Here is the first part of the crash log, the system's not letting me post the whole thing:
Version=1
EventType=APPCRASH
EventTime=130676361272269133
ReportType=2
Consent=1
ReportIdentifier=8b941ca2-ad68-11e4-8267-001b217dec70
IntegratorReportIdentifier=8b941ca1-ad68-11e4-8267-001b217dec70
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Photoshop.exe
Sig[1].Name=Application Version
Sig[1].Value=15.2.2.310
Sig[2].Name=Application Timestamp
Sig[2].Value=5480338c
Sig[3].Name=Fault Module Name
Sig[3].Value=MSVCR110.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=11.0.51106.1
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5098826e
Sig[6].Name=Exception Code
Sig[6].Value=c00000fd
Sig[7].Name=Exception Offset
Sig[7].Value=00000000000536cd
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.4
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=e9f5
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=e9f5c8c33e4791a059633dbdb8508411
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=6ad1
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=6ad1e4ea6e8492e201dad09da2580b61 -
2014 Macbook Pro Retina crashes when extending display to Apple TV 3rd Gen
2014 Macbook Pro Retina running Mavericks 10.9.5 crashes and restarts every time I Extend Desktop in Airplay to new Apple TV 3rd Gen running latest update.
What can I do to avoid this?
Thanks
JonHello Freytag,
I would be concerned too if my MacBook Pro was getting recurring kernel panics when using an external display.
First, I recommend troubleshooting the connection with the external display. This article is for internal and external displays, so you can skip any steps referring to the internal display. I recommend reviewing the section titled "No video or no signal, image distortion, 'snow,' or flickering" in the article below. I recommend reviewing the full article, but the following steps specifically stands out to me for the situation you are experiencing:
Reset the system
You can reset the Mac's parameter RAM and SMC.
You can find the full article here:
Apple computers: Troubleshooting issues with video on internal or external displays
http://support.apple.com/kb/ht1573
If you continue expereince kernel panics, I recommend following the steps in the section titled "Troubleshooting a recurring kernel panic" in the article below to help isolate and troubleshoot this issue:
OS X: When your computer spontaneously restarts or displays "Your computer restarted because of a problem."
http://support.apple.com/kb/TS4636
Thank you for using Apple Support Communities.
Best,
Sheila M. -
Photoshop CC 2014 crashes in OSX 10.9.4
I am using a MacBook Pro mid 2010 with OSX 10.9.4 and Photoshop CC 2014 crashes on opening with a message "Could not initialise Photoshop because of a program error."
I also have the previous version Photoshop CC and it runs fine. Anyone experiencing the same?
Thanks, Chris"Could not initialize Photoshop because of a program error" is a generic error and means something unanticipated.
Lets optimize PS for best performance and then check. http://helpx.adobe.com/photoshop/kb/optimize-performance-photoshop-cs4-cs5.html#main_Set_P erformance_preferences
You can also check http://blogs.adobe.com/crawlspace/2012/07/photoshop-basic-troubleshooting-steps-to-fix-mos t-issues.html
~ Arpit -
How do I put an external display to sleep when I am using my MacBook Air for presentation?
How do I put an external display to sleep when I am using my MacBook Air for presentation? I do not want to go to the projector just to turn it off and turn on again after a while? Is there a keyboard shortcut for that?
I want to be able to sleep the external display and at the same time do things in the MacBook.( This feature is useful for me so that I can prepare some things and so that my audience will not see what I am about to show them.)
Is there a feature for Mountain Lion? -
Ongoing fatal crash and security bug related to connecting external display
The infrastructures in OS X to resume from sleep, to authenticate, and to change displays is fundamentally not working.
The security bug I have encountered has to do with connecting a cinema display exclusively to a MacBook Pro. This is a specific situation, but please note that I have experienced the same problem on no fewer than three independent laptop. Plus, the Genius in the Apple Retail Store was convinced of the general instability of this infrastructure. The security problem is that hot corners no longer function if I transition between two states in the same reboot. The first state is where I have the laptop powered on and using its own internal display exclusively (when I'm on the road). The second state is when I have the laptop displaying its output exclusively on an external display (when I'm at home). What happens is that an attempt to use hot corners fails. There is no response. I even added configuration on all four corners (whereas I originally had settings only for the rightmost corners), and even then, the hot corner action (of sleeping the display or entering locked screen saver mode) does not commence. This prevents the user from being able to secure the display on demand using standard methods that are supposed to work.
The instability level related to connecting the external display exclusively is high. Again, I've experienced this on no fewer than three independent laptops, and the Apple Genius at the Retail Store confirmed that this aspect of OS X did not work consistently. When I want to connect the cinema display to the laptop in such a way that the laptop's own display is not part of the active screen, the process I use succeeds about half the time. Supposing I have been on the road, where I am using the laptop display exclusively. I then put the laptop to sleep. When I return home with the lid open, I connect first the USB (power) from the cinema display to the laptop, and then I connect the Mini DisplayPort. When that step works, what happens is that the login screen shows on the cinema display despite the fact that my laptop lid is closed. This is good, and is what I want. At that point, I open the laptop lid and quickly log in.
With Apple being a mobile device company, I rely on the laptop for tasks that one traditionally may use a desktop for. This simply points to the versatility of the laptop. But I'd like the bugs resolved, so that I do not have to hesitate to make use of the inherent flexibility possible with the MacBook Pro.
Here's what happens when the process (of connecting the external display in a way that establishes itself as the only screen in use by OS X) fails. Firstly, when I connect the external display via Mini DisplayPort, the laptop doesn't even respond. Instead, it remains asleep. So to work around it I have to repeatedly disconnect and reconnect the Mini DisplayPort so that the asleep MacBook Pro will see that there is a display connected to it. Also, sometimes that isn't even enough and I have to open the laptop lid, and put it to sleep again so as to trigger whatever actions are necessary to recognise the external display (presumably by having the laptop recently awake). Around half the time, I have to play this game of disconnecting and reconnecting until it actually works. This high level of reproducibility (confirmed by the Apple Genius representative's confidence that this part of the system doesn't actually work) should make it easy for an engineer to look into the problem.
Fatally, and recently, OS X has completely crashed when I have attempted to connect the external display. The external display has gone completely blue, and after a half a minute, it blanked out and my entire laptop became unresponsive. I called Apple Support and was given a case number. I also took the laptop into the retail store to see if I could recover my current session without rebooting. There was no process suggested to make that happen and I was told to reboot the machine. I've had this happen before on other laptops, and it is frustrating that the kernel reaches such a state that it cannot be used. As I see it, this problem is not too unrelated to the way that I need to play a game in order to get the external display connected exclusively. Here are some workarounds that could be added:
Firstly, whenever I connect an external display, I'd like the laptop to see that this has happened, and to take action accordingly (such as resuming from sleep). Secondly, If I connect an external keyboard, and press a key on it, I'd like this to wake the laptop too (in the event that the first method fails for some unforeseen reason). I'd also like the connection of the cinema display's USB power not to cause the laptop to enter into a confused state between asleep and awake. Sometimes I need to disconnect and reconnect USB power in order to trigger the laptop into waking, but that's only because it's not doing it on its own properly. On the other hand, I also ensure that the laptop doesn't have the Mini DisplayPort connected without also having the cinema display USB power connected, because that also is an unsupported configuration.
I've also gotten the laptop to become confused about whether it is asleep or awake. When I open the lid, it seems to enter into sleep mode, but closing it seems to bring it into an active state.
Also, I've successfully logged on and authenticated with the screen showing exclusively on the external display. But just ten seconds after I start using the system, the laptop falls asleep--with the lid open! Whatever triggers that action doesn't seem to be on track. The laptop is open, there are incoming events such as mouse movements and key presses, and the external display is on and is in use. And then the laptop falls asleep! This has happened numerous times. Not only should this not happen; the instances where it does happen can cause further instability and put my system at risk of fatally crashing.
Also, the authentication system itself is highly buggy--far more than it should be. At times I have opened the laptop lid and caught a glimpse of a window before I have begun the login process. Also, an external authentication application that asks for Kerberos/AFS login credentials has been able to overlay itself on top of the primary authentication (whereas I should only see a single login dialog when I need to authenticate to the system). Also, I've had several of these authentication screens overlay on top of one another, although it's been months since I've experienced that one (so it may have been fixed). Also, around a third of the time, the window that authenticates me (on the black background) somehow transfers itself into the background (even though there's only one window!). What that means is what I begin to type my password, and now the laptop starts beeping at me and I need to manually click on the password field and begin entering my password again. This really shouldn't happen, and indicates too much complexity in this authentication process (such as, more OS X code is involved than is strictly necessary, which is likely to make the authentication system more difficult to test). Also, at times, I have been using too much CPU, such that the authentication screen takes too long to emerge. That also means that I'm not able to logon until I uncleanly shutdown the laptop. If the laptop has been asleep, and is revived in preparation for login, then that login screen should be given highest priority, even if there are other heavy CPU or I/O intensive tasks running in the background. And maybe the login dialog shouldn't disappear when the user is legitimately attempting to log in. So even if there is a possibility that the system is under heavy resource use (or there is a stall or minor deadlock), it shouldn't prevent the user from logging in altogether.
At the moment, the very fact that the system shut down uncleanly means that the full disk encryption suite that I used has entered into an undetermined state, suggesting I may lose access to all my data. It's my hope that I can rely on Apple's products to interoperate in a way that won't cause me to be fearful and restrictive in my use, so that I can freely connect an external display at times, and at other times carry the laptop on the road.Ive got the same problem with Samsung UE225010 monitor too, its full hd but it looks terrible, could it be Displayport adapter issue, because couple month ago Ive tryed with some IPS display, and it looked same bad.
Maybe you are looking for
-
Does anyone know how to remove an unfinished movie download from an ipod touch
I need some help with my ipod touch 4 I download the movie but it showed that i dont have enough space and it wont let me to remove or delete the movie. I tried everything but no luck. I dont want to see unfinished movie download stuck in my download
-
Hi, The PDK has a number of preview articles that describe the Oracle9iAS Portal V2 features. As a Developer Services member, you can access these from: http://portalstudio.oracle.com/servlet/page?_pageid=2384&_dad=ops&_schema=OPSTUDIO If you have an
-
Quick time is not loading mp3 in PC IE only...
The deal is, this is an issue only shows in Windows Internet Explorer. The code I put in is as follows. <embed src="http://www.newstribune.com/weather_feed/images/tribune.mp3" width="135" height="32" autostart="False" type="audio/mpeg" volume="50"> <
-
Get query name by program name
Hi experts, Someone built a query A, and generated it to program B. Now I need update query A, but I only know program B. How to get the query name by program name? Many thanks.
-
My error problem is with my profile. A new profile fixed this problem. I cant move to a new profile, it's just too much work to set. I just want to know what is wrong this this one. Video didn't work in safe mode so i can say none of addons is confli