2nd display causes crash

New to Macs here so be gentle
Just got my new iMac core duo 17" and decided to try and hook up my 19" Princeton LCD190 monitor to it. I am using the dvi port on the monitir using the mini-dvi adaptor hooked to the dvi cable that came with the monitor.
Every time I plug the cable into the iMac, it crashes telling me I need to reboot the computer holding the on/off button. The same thing happens after the reboot. The only way to get the iMac to boot is to unplug the cable from it.
Anyone have any ideas why this is happening? TIA!

Every time I plug the cable into the iMac, it crashes
telling me I need to reboot the computer holding the
on/off button.
Hi HobbyTalk - When it tells you to reboot, does it say that in several languages, including Japanese? If so, you are experiencing a kernel panic.
http://docs.info.apple.com/article.html?artnum=106227
Kernel panics are extremely rare; the leading cause of a kernel panic is dodgy peripherals. There is probably nothing wrong with your Mac if it only panics when you plug in the monitor.
Troubleshooting:
If you can, test your Mac with a different monitor, different cable, and different Mini-DVI adaptor. If that works without a panic, then you can be fairly sure its the monitor, monitor cable, or the Mini-DVI connector that's causing the panic. Then you can fine tune your testing to identify which of the 3 bits of kit could be dodgy.
Troubleshooting tip: approach it like a science experiment, testing the various elements with a goal to logically ruling out suspects. Jot down a testing strategy, and make notes.
I know you probably don't have alternative Macs, monitors, or cables, to test with, which probably means having to buy replacements just to test, so the easiest and most hopeful test would be replacing the monitor cable. If you got a bad cable, a simple replacement would get everything working without too much hassle.

Similar Messages

Thunderbolt Displays Cause Crash

Hi,
I have a macbook pro retina and two of the external thunderbolt displays (daisy chained).
Every time that I plug my MBP into the thunderbolt displays while it is asleep and try to wake the computer, it crashes. It sometimes reboots on its own, but usually I have to open the lid and hold the power button down.
This is a huge issue for me -- has anyone else had a similar problem? Can anyone offer any advice?

Hey Chett,
I know this is a few years old now, but I have the same issue, but no advice.
Currently looking into this.

2nd HDD causes Qosmio G40 to crash

My C drive is fine and everything ok split into 2 partitions running Vista Premium.
2nd HDD causes the computer to crash with the following error message:
0X00008086
0X00000100
0X000002B4
0X00000001
0X00000000
I have reinstalled everything wiped the disks and now the drive wont format
I have read that it could be a SATA problem but in the BIOS the ability to change the settings are not accessible.
My warranty ran out days before this failed so I cant get it done on it.
Before it went I used to be able to use it for a while and then something would trigger the blue screen, sometimes the laptop doesnt even see its there.
Can anyone throw any light on the problem?

How do you know the 2nd HDD is causing the crash?
If you remove the HDD, does it still crash?
Have you tried repairing the file systems on the 2nd HDD?
In a command prompt, run CHKDSK x: /F (where x; is the drive letter, such as D: )
Also test the HDD for bad sectors. DFT is a bootable CD with a HDD test. Boot from the CD and run the Advanced test
DFT Download: http://www.hitachigst.com/hdd/support/download.htm#DFT

MSI 660 TI PE Display Driver crashes

First, here is my system.
i5-2500k Processor (http://www.newegg.com/Product/Product.aspx?Item=N82E16819115072) (Processor is overclocked to 4.3ghz, temp on it never goes over 45-50°C though)
MSI Geforce GTX 660TI PE Video card (http://www.newegg.com/Product/Product.aspx?Item=N82E16814127696)
Asus P8Z68-V Pro\Gen 3 Motherboard (http://www.newegg.com/Product/Product.aspx?Item=N82E16813131790)
Corsair HX series HX650 Power Supply (http://www.newegg.com/Product/Product.aspx?Item=N82E16817139012)
4x4GB of G.Skill Ram (http://www.newegg.com/Product/Product.aspx?Item=N82E16820231314)
When my old MSI P67A-GD55 Motherboard bricked a month ago, instead of waiting on RMA I went ahead and got the Asus board, at the same time I went ahead and upgraded my old Asus GTX 560TI card to the MSI GTX 660TI card. Since the upgrade, I am constantly getting display driver crashes "Display driver nvlddmkm stopped responding and has successfully recovered." when playing games. Guild Wars 2 and Starcraft 2 are the only ones I've had time to try, but both consistently give driver crashes after awhile (sometimes as soon as 15-20 mins, sometimes takes several hours of gameplay).
Here is the list of things I've already tried:
-First, I tried the most recent Nvidia drivers. Still crashes.
-Second, I tried running driver sweeper, removing all old drivers and reinstalling. Still crashes.
-Third, I tried disabling TDR in the Win7 registry. Still crashes.
-Fourth, I really ramped up the auto fan speeds. So far it hasn't crashed while doing this, but I can't do it for too long because the fans get so loud that it annoys me greatly.
-Fifth, I thought it might be an old Motherboard driver conflict of some sort, so I completely formated my OS hard drive and reinstalled Windows 7. Still getting crashes.
-Sixth, I used driver sweeper again and rolled back to the last official MSI drivers (the ones from October). Still getting crashes.
I really don't think the card is overheating. The most recent crash happened tonight after playing Starcraft 2 for about 20 minutes, and the temperature of the card never got over 60°C. That's why even with the extremely ramped up fan speeds I tried, I think if I used them long enough, the driver would still crash.
The power supply is the same as what I used with the 560TI and it didn't have these issues. And from my understanding, the 560TI consumed more power than the 660TI.
At this point, I'm at my wits end. The only thing else I know to try is swapping out the old 560TI in with the new motherboard or waiting for my old motherboard to come back from RMA and trying the 660TI in it. Though that means rebuilding the case, uninstalling the new mobo drivers and installing the old mobo drivers and authenticating Windows. Doing all of that is going to kill most of a day and I really only want to do that if I absolutely have to.
I've had such limited time for troubleshooting the card, that I'm regrettably past the 30day limit on RMA replacements to Newegg. So unfortunately that means I'm looking at an RMA directly to MSI and that takes about a month. Before I do that, does anyone have any advice on something to try that might be the cuplrit or can help determine the culprit? I can't find any details in the Event Viewer as to what caused the driver crash. Just that it has stopped responding and has recovered. I wish it could tell me if there was a loss of power, or anything. Power Management Mode is set to prefer maximum performance btw.
Btw, as a brief description of what happens. The screen goes black, and then comes back and the game is running very slowly. There will also usually be a popup above the taskbar saying that the driver had crashed. I keep the MSI Afterburner info window open in my second monitor and Power usage never goes over 80%, GPU Usage is usually around 95-99%. Core Clock and Memory clock drop to about 324mhz (which is what it idles at) temporarily during the crash. GPU Usage of course dips to very low levels while the driver is crashing, as well.
Oh and in an added twist, I've run Kombuster several times. Burn-in test DirectX 11 1920x1600 8xMSAA as long as five hours, and the display driver has never crashed. I'll probably turn it on, and disable the computer's sleep and display off tonight and let it run for about 8-9 hours and see what happens. That's one thing that throws me off, if it's a hardware defect, wouldn't Kombuster cause it to crash?
edit-Here is a screenshot of the Afterburner monitor during a crash while playing Starcraft 2. The huge dip in the bars that I have the cursor over is when the crash occured.

Well with the Power% limited to 75%, I just had another crash in Starcraft 2. Temp was only at 56°C just before the crash.
Here is a shot of the Afterburner Hardware Monitor when it crashed:
Unfortunately I do not have another PC to test the card in. And I don't know anyone around here with a system that the card could work in.
If I swapped out the 660TI with my old 560TI and I do not get any crashes, wouldn't that indicate it's the 660TI's fault and I'd need to RMA since the 560TI is a more power hungry card?

Display Blank - Crash? - Something

I have been having some problems with my Archlinux install that I have been using for years. I may just do a reinstall soon. The system is a IBM T61 Laptop. I just do not know wtf is going on.
Every now and then the screen will go completely black but the system stays running. No back light, nothing. The external monitor shuts off also. I think the display is crashing.
One of the reasons I know the system is running still is because synergy still works. That is, I can use the mouse to use the other systems that synergy is connected to. This means networking up, mouse up, etc. SSH sessions to other boxes are still open.
I cannot switch to an other ttys or anything. I mean, I can switch to them, but they do not come up on the display. I can restart the system with shortcut keys.
$ lsmod | grep intel
kvm_intel 129393 0
kvm 379223 1 kvm_intel
snd_hda_intel 36520 2
snd_hda_codec 148129 2 snd_hda_intel,snd_hda_codec_analog
snd_pcm 77765 2 snd_hda_codec,snd_hda_intel
snd_page_alloc 7234 2 snd_pcm,snd_hda_intel
snd 59141 11 snd_hwdep,snd_timer,snd_pcm,snd_hda_codec,snd_hda_intel,thinkpad_acpi,snd_hda_codec_analog
intel_agp 10872 1 i915
intel_gtt 12664 3 i915,intel_agp
$ uname -a
Linux matrix 3.11.4-1-ARCH #1 SMP PREEMPT Sat Oct 5 21:22:51 CEST 2013 x86_64 GNU/Linux
Something from xorg.1.log
[ 485.118] (II) LoadModule: "intel"
[ 485.118] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 485.119] (II) Module intel: vendor="X.Org Foundation"
[ 485.119] compiled for 1.12.4, module version = 2.20.9
[ 485.119] Module class: X.Org Video Driver
[ 485.119] ABI class: X.Org Video Driver, version 12.1
More from Xorg.0.log
[1305732.004] (II) intel(0): switch to mode [email protected] on pipe 1 using VGA1, position (1280, 0), rotation normal
(EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f67d]
(EE) 1: /usr/bin/X (mieqEnqueue+0x22b) [0x5615bb]
(EE) 2: /usr/bin/X (QueuePointerEvents+0x52) [0x44da82]
(EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7ff0087ce000+0x580d) [0x7ff0087d380d]
(EE) 4: /usr/bin/X (0x400000+0x73da8) [0x473da8]
(EE) 5: /usr/bin/X (0x400000+0x9c330) [0x49c330]
(EE) 6: /usr/lib/libpthread.so.0 (0x7ff00cef6000+0xf870) [0x7ff00cf05870]
(EE) 7: /usr/lib/libc.so.6 (ioctl+0x7) [0x7ff00c035f17]
(EE) 8: /usr/lib/libdrm.so.2 (drmIoctl+0x50) [0x7ff00db905c0]
(EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x27c19) [0x7ff00a8acc19]
(EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36311) [0x7ff00a8bb311]
(EE) 11: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36a2e) [0x7ff00a8bba2e]
(EE) 12: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36abc) [0x7ff00a8bbabc]
(EE) 13: /usr/bin/X (0x400000+0xc0e51) [0x4c0e51]
(EE) 14: /usr/bin/X (ChangeWindowAttributes+0x115) [0x463895]
(EE) 15: /usr/bin/X (0x400000+0x32154) [0x432154]
(EE) 16: /usr/bin/X (0x400000+0x373be) [0x4373be]
(EE) 17: /usr/bin/X (0x400000+0x2693a) [0x42693a]
(EE) 18: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7ff00bf79bc5]
(EE) 19: /usr/bin/X (0x400000+0x26c81) [0x426c81]
(EE)
(EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.
(EE) [mi] mieq is *NOT* the cause. It is a victim.
(EE) [mi] EQ overflow continuing. 100 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f67d]
(EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x44da82]
(EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7ff0087ce000+0x580d) [0x7ff0087d380d]
(EE) 3: /usr/bin/X (0x400000+0x73da8) [0x473da8]
(EE) 4: /usr/bin/X (0x400000+0x9c330) [0x49c330]
(EE) 5: /usr/lib/libpthread.so.0 (0x7ff00cef6000+0xf870) [0x7ff00cf05870]
(EE) 6: /usr/lib/libc.so.6 (ioctl+0x7) [0x7ff00c035f17]
(EE) 7: /usr/lib/libdrm.so.2 (drmIoctl+0x50) [0x7ff00db905c0]
(EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x27c19) [0x7ff00a8acc19]
(EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36311) [0x7ff00a8bb311]
(EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36a2e) [0x7ff00a8bba2e]
(EE) 11: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36abc) [0x7ff00a8bbabc]
(EE) 12: /usr/bin/X (0x400000+0xc0e51) [0x4c0e51]
(EE) 13: /usr/bin/X (ChangeWindowAttributes+0x115) [0x463895]
(EE) 14: /usr/bin/X (0x400000+0x32154) [0x432154]
(EE) 15: /usr/bin/X (0x400000+0x373be) [0x4373be]
(EE) 16: /usr/bin/X (0x400000+0x2693a) [0x42693a]
(EE) 17: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7ff00bf79bc5]
(EE) 18: /usr/bin/X (0x400000+0x26c81) [0x426c81]
(EE)
(EE) [mi] EQ overflow continuing. 200 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f67d]
(EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x44da82]
(EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7ff0087ce000+0x580d) [0x7ff0087d380d]
(EE) 3: /usr/bin/X (0x400000+0x73da8) [0x473da8]
(EE) 4: /usr/bin/X (0x400000+0x9c330) [0x49c330]
(EE) 5: /usr/lib/libpthread.so.0 (0x7ff00cef6000+0xf870) [0x7ff00cf05870]
(EE) 6: /usr/lib/libc.so.6 (ioctl+0x7) [0x7ff00c035f17]
(EE) 7: /usr/lib/libdrm.so.2 (drmIoctl+0x50) [0x7ff00db905c0]
(EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x27c19) [0x7ff00a8acc19]
(EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36311) [0x7ff00a8bb311]
(EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36a2e) [0x7ff00a8bba2e]
(EE) 11: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36abc) [0x7ff00a8bbabc]
(EE) 12: /usr/bin/X (0x400000+0xc0e51) [0x4c0e51]
(EE) 13: /usr/bin/X (ChangeWindowAttributes+0x115) [0x463895]
(EE) 14: /usr/bin/X (0x400000+0x32154) [0x432154]
(EE) 15: /usr/bin/X (0x400000+0x373be) [0x4373be]
(EE) 16: /usr/bin/X (0x400000+0x2693a) [0x42693a]
(EE) 17: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7ff00bf79bc5]
(EE) 18: /usr/bin/X (0x400000+0x26c81) [0x426c81]
(EE)
(EE) [mi] EQ overflow continuing. 300 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f67d]
(EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x44da82]
(EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7ff0087ce000+0x580d) [0x7ff0087d380d]
(EE) 3: /usr/bin/X (0x400000+0x73da8) [0x473da8]
(EE) 4: /usr/bin/X (0x400000+0x9c330) [0x49c330]
(EE) 5: /usr/lib/libpthread.so.0 (0x7ff00cef6000+0xf870) [0x7ff00cf05870]
(EE) 6: /usr/lib/libc.so.6 (ioctl+0x7) [0x7ff00c035f17]
(EE) 7: /usr/lib/libdrm.so.2 (drmIoctl+0x50) [0x7ff00db905c0]
(EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x27c19) [0x7ff00a8acc19]
(EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36311) [0x7ff00a8bb311]
(EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36a2e) [0x7ff00a8bba2e]
(EE) 11: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36abc) [0x7ff00a8bbabc]
(EE) 12: /usr/bin/X (0x400000+0xc0e51) [0x4c0e51]
(EE) 13: /usr/bin/X (ChangeWindowAttributes+0x115) [0x463895]
(EE) 14: /usr/bin/X (0x400000+0x32154) [0x432154]
(EE) 15: /usr/bin/X (0x400000+0x373be) [0x4373be]
(EE) 16: /usr/bin/X (0x400000+0x2693a) [0x42693a]
(EE) 17: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7ff00bf79bc5]
(EE) 18: /usr/bin/X (0x400000+0x26c81) [0x426c81]
(EE)
(EE) [mi] EQ overflow continuing. 400 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f67d]
(EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x44da82]
(EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7ff0087ce000+0x580d) [0x7ff0087d380d]
(EE) 3: /usr/bin/X (0x400000+0x73da8) [0x473da8]
(EE) 4: /usr/bin/X (0x400000+0x9c330) [0x49c330]
(EE) 5: /usr/lib/libpthread.so.0 (0x7ff00cef6000+0xf870) [0x7ff00cf05870]
(EE) 6: /usr/lib/libc.so.6 (ioctl+0x7) [0x7ff00c035f17]
(EE) 7: /usr/lib/libdrm.so.2 (drmIoctl+0x50) [0x7ff00db905c0]
(EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x27c19) [0x7ff00a8acc19]
(EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36311) [0x7ff00a8bb311]
(EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36a2e) [0x7ff00a8bba2e]
(EE) 11: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36abc) [0x7ff00a8bbabc]
(EE) 12: /usr/bin/X (0x400000+0xc0e51) [0x4c0e51]
(EE) 13: /usr/bin/X (ChangeWindowAttributes+0x115) [0x463895]
(EE) 14: /usr/bin/X (0x400000+0x32154) [0x432154]
(EE) 15: /usr/bin/X (0x400000+0x373be) [0x4373be]
(EE) 16: /usr/bin/X (0x400000+0x2693a) [0x42693a]
(EE) 17: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7ff00bf79bc5]
(EE) 18: /usr/bin/X (0x400000+0x26c81) [0x426c81]
(EE)
(EE) [mi] EQ overflow continuing. 500 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f67d]
(EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x44da82]
(EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7ff0087ce000+0x580d) [0x7ff0087d380d]
(EE) 3: /usr/bin/X (0x400000+0x73da8) [0x473da8]
(EE) 4: /usr/bin/X (0x400000+0x9c330) [0x49c330]
(EE) 5: /usr/lib/libpthread.so.0 (0x7ff00cef6000+0xf870) [0x7ff00cf05870]
(EE) 6: /usr/lib/libc.so.6 (ioctl+0x7) [0x7ff00c035f17]
(EE) 7: /usr/lib/libdrm.so.2 (drmIoctl+0x50) [0x7ff00db905c0]
(EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x27c19) [0x7ff00a8acc19]
(EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36311) [0x7ff00a8bb311]
(EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36a2e) [0x7ff00a8bba2e]
(EE) 11: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36abc) [0x7ff00a8bbabc]
(EE) 12: /usr/bin/X (0x400000+0xc0e51) [0x4c0e51]
(EE) 13: /usr/bin/X (ChangeWindowAttributes+0x115) [0x463895]
(EE) 14: /usr/bin/X (0x400000+0x32154) [0x432154]
(EE) 15: /usr/bin/X (0x400000+0x373be) [0x4373be]
(EE) 16: /usr/bin/X (0x400000+0x2693a) [0x42693a]
(EE) 17: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7ff00bf79bc5]
(EE) 18: /usr/bin/X (0x400000+0x26c81) [0x426c81]
(EE)
(EE) [mi] EQ overflow continuing. 600 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f67d]
(EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x44da82]
(EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7ff0087ce000+0x580d) [0x7ff0087d380d]
(EE) 3: /usr/bin/X (0x400000+0x73da8) [0x473da8]
(EE) 4: /usr/bin/X (0x400000+0x9c330) [0x49c330]
(EE) 5: /usr/lib/libpthread.so.0 (0x7ff00cef6000+0xf870) [0x7ff00cf05870]
(EE) 6: /usr/lib/libc.so.6 (ioctl+0x7) [0x7ff00c035f17]
(EE) 7: /usr/lib/libdrm.so.2 (drmIoctl+0x50) [0x7ff00db905c0]
(EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x27c19) [0x7ff00a8acc19]
(EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36311) [0x7ff00a8bb311]
(EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36a2e) [0x7ff00a8bba2e]
(EE) 11: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36abc) [0x7ff00a8bbabc]
(EE) 12: /usr/bin/X (0x400000+0xc0e51) [0x4c0e51]
(EE) 13: /usr/bin/X (ChangeWindowAttributes+0x115) [0x463895]
(EE) 14: /usr/bin/X (0x400000+0x32154) [0x432154]
(EE) 15: /usr/bin/X (0x400000+0x373be) [0x4373be]
(EE) 16: /usr/bin/X (0x400000+0x2693a) [0x42693a]
(EE) 17: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7ff00bf79bc5]
(EE) 18: /usr/bin/X (0x400000+0x26c81) [0x426c81]
(EE)
(EE) [mi] EQ overflow continuing. 700 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f67d]
(EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x44da82]
(EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7ff0087ce000+0x580d) [0x7ff0087d380d]
(EE) 3: /usr/bin/X (0x400000+0x73da8) [0x473da8]
(EE) 4: /usr/bin/X (0x400000+0x9c330) [0x49c330]
(EE) 5: /usr/lib/libpthread.so.0 (0x7ff00cef6000+0xf870) [0x7ff00cf05870]
(EE) 6: /usr/lib/libc.so.6 (ioctl+0x7) [0x7ff00c035f17]
(EE) 7: /usr/lib/libdrm.so.2 (drmIoctl+0x50) [0x7ff00db905c0]
(EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x27c19) [0x7ff00a8acc19]
(EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36311) [0x7ff00a8bb311]
(EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36a2e) [0x7ff00a8bba2e]
(EE) 11: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36abc) [0x7ff00a8bbabc]
(EE) 12: /usr/bin/X (0x400000+0xc0e51) [0x4c0e51]
(EE) 13: /usr/bin/X (ChangeWindowAttributes+0x115) [0x463895]
(EE) 14: /usr/bin/X (0x400000+0x32154) [0x432154]
(EE) 15: /usr/bin/X (0x400000+0x373be) [0x4373be]
(EE) 16: /usr/bin/X (0x400000+0x2693a) [0x42693a]
(EE) 17: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7ff00bf79bc5]
(EE) 18: /usr/bin/X (0x400000+0x26c81) [0x426c81]
(EE)
(EE) [mi] EQ overflow continuing. 800 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f67d]
(EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x44da82]
(EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7ff0087ce000+0x580d) [0x7ff0087d380d]
(EE) 3: /usr/bin/X (0x400000+0x73da8) [0x473da8]
(EE) 4: /usr/bin/X (0x400000+0x9c330) [0x49c330]
(EE) 5: /usr/lib/libpthread.so.0 (0x7ff00cef6000+0xf870) [0x7ff00cf05870]
(EE) 6: /usr/lib/libc.so.6 (ioctl+0x7) [0x7ff00c035f17]
(EE) 7: /usr/lib/libdrm.so.2 (drmIoctl+0x50) [0x7ff00db905c0]
(EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x27c19) [0x7ff00a8acc19]
(EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36311) [0x7ff00a8bb311]
(EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36a2e) [0x7ff00a8bba2e]
(EE) 11: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36abc) [0x7ff00a8bbabc]
(EE) 12: /usr/bin/X (0x400000+0xc0e51) [0x4c0e51]
(EE) 13: /usr/bin/X (ChangeWindowAttributes+0x115) [0x463895]
(EE) 14: /usr/bin/X (0x400000+0x32154) [0x432154]
(EE) 15: /usr/bin/X (0x400000+0x373be) [0x4373be]
(EE) 16: /usr/bin/X (0x400000+0x2693a) [0x42693a]
(EE) 17: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7ff00bf79bc5]
(EE) 18: /usr/bin/X (0x400000+0x26c81) [0x426c81]
(EE)
(EE) [mi] EQ overflow continuing. 900 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f67d]
(EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x44da82]
(EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7ff0087ce000+0x580d) [0x7ff0087d380d]
(EE) 3: /usr/bin/X (0x400000+0x73da8) [0x473da8]
(EE) 4: /usr/bin/X (0x400000+0x9c330) [0x49c330]
(EE) 5: /usr/lib/libpthread.so.0 (0x7ff00cef6000+0xf870) [0x7ff00cf05870]
(EE) 6: /usr/lib/libc.so.6 (ioctl+0x7) [0x7ff00c035f17]
(EE) 7: /usr/lib/libdrm.so.2 (drmIoctl+0x50) [0x7ff00db905c0]
(EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x27c19) [0x7ff00a8acc19]
(EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36311) [0x7ff00a8bb311]
(EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36a2e) [0x7ff00a8bba2e]
(EE) 11: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff00a885000+0x36abc) [0x7ff00a8bbabc]
(EE) 12: /usr/bin/X (0x400000+0xc0e51) [0x4c0e51]
(EE) 13: /usr/bin/X (ChangeWindowAttributes+0x115) [0x463895]
(EE) 14: /usr/bin/X (0x400000+0x32154) [0x432154]
(EE) 15: /usr/bin/X (0x400000+0x373be) [0x4373be]
(EE) 16: /usr/bin/X (0x400000+0x2693a) [0x42693a]
(EE) 17: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7ff00bf79bc5]
(EE) 18: /usr/bin/X (0x400000+0x26c81) [0x426c81]
(EE)
[1318137.711] [mi] Increasing EQ size to 512 to prevent dropped events.
[1318137.712] [mi] EQ processing has resumed after 981 dropped events.
[1318137.712] [mi] This may be caused my a misbehaving driver monopolizing the server's resources.
[1318137.715] (EE) intel(0): Detected a hung GPU, disabling acceleration.
[1318152.048] (II) AIGLX: Suspending AIGLX clients for VT switch
[1318152.962] (II) AIGLX: Resuming AIGLX clients after VT switch
[1318152.962] (II) intel(0): switch to mode [email protected] on pipe 0 using LVDS1, position (0, 0), rotation normal
[1318153.021] (II) intel(0): switch to mode [email protected] on pipe 1 using VGA1, position (1280, 0), rotation normal
[1318153.207] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[1318153.208] setversion 1.4 failed
[1318177.918] (II) AIGLX: Suspending AIGLX clients for VT switch
[1318181.633] (II) AIGLX: Resuming AIGLX clients after VT switch
[1318181.633] (II) intel(0): switch to mode [email protected] on pipe 0 using LVDS1, position (0, 0), rotation normal
[1318181.691] (II) intel(0): switch to mode [email protected] on pipe 1 using VGA1, position (1280, 0), rotation normal
[1318181.882] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[1318281.915] (II) AIGLX: Suspending AIGLX clients for VT switch
[1318285.985] (II) AIGLX: Resuming AIGLX clients after VT switch
[1318285.985] (II) intel(0): switch to mode [email protected] on pipe 0 using LVDS1, position (0, 0), rotation normal
[1318286.041] (II) intel(0): switch to mode [email protected] on pipe 1 using VGA1, position (1280, 0), rotation normal
[1318286.232] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[1318397.073] (II) intel(0): switch to mode [email protected] on pipe 0 using LVDS1, position (0, 0), rotation normal
[1318398.272] (II) intel(0): switch to mode [email protected] on pipe 1 using VGA1, position (1280, 0), rotation normal
[1318848.591] (II) AIGLX: Suspending AIGLX clients for VT switch
[1318850.428] (II) AIGLX: Resuming AIGLX clients after VT switch
[1318850.428] (II) intel(0): switch to mode [email protected] on pipe 0 using LVDS1, position (0, 0), rotation normal
[1318850.488] (II) intel(0): switch to mode [email protected] on pipe 1 using VGA1, position (1280, 0), rotation normal
[1318850.671] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[1318956.173] (II) intel(0): switch to mode [email protected] on pipe 0 using LVDS1, position (0, 0), rotation normal
[1318957.332] (II) intel(0): switch to mode [email protected] on pipe 1 using VGA1, position (1280, 0), rotation normal
[1319022.909] (II) evdev: Logitech Unifying Device. Wireless PID:101b: Close
[1319022.909] (II) UnloadModule: "evdev"
[1319022.909] (II) evdev: HID 0a5c:4503: Close
[1319022.909] (II) UnloadModule: "evdev"
[1319022.909] (II) evdev: HID 0a5c:4502: Close
[1319022.909] (II) UnloadModule: "evdev"
[1319022.909] (II) evdev: ThinkPad Extra Buttons: Close
[1319022.909] (II) UnloadModule: "evdev"
[1319022.909] (II) evdev: TPPS/2 IBM TrackPoint: Close
[1319022.909] (II) UnloadModule: "evdev"
[1319022.909] (II) UnloadModule: "synaptics"
[1319022.909] (II) evdev: AT Translated Set 2 keyboard: Close
[1319022.909] (II) UnloadModule: "evdev"
[1319022.909] (II) evdev: Sleep Button: Close
[1319022.909] (II) UnloadModule: "evdev"
[1319022.909] (II) evdev: Video Bus: Close
[1319022.909] (II) UnloadModule: "evdev"
[1319022.909] (II) evdev: Power Button: Close
[1319022.909] (II) UnloadModule: "evdev"
[1319023.028] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
[1319023.028] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
[1319023.028] (EE)
Fatal server error:
[1319023.028] (EE) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
[1319023.028] (EE)
[1319023.028] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
more
lspci | grep -i Display
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 0c)

Your xorg.0.log wrote:<snip>
[1318137.715] (EE) intel(0): Detected a hung GPU, disabling acceleration.
<snip>
I have to imagine that this is not a good thing...
Does switching kernels help? Maybe you could try to linux-lts kernel. It is now the 3.10LTS, so hopefully your system hasn't been doing this since then. Otherwise, you might have to go dig up an even older kernel to make sure it is not a bug there.

2nd Display has fast motion jitters . . .

I have a Dual 3.2GHz Quad-Core Mac Pro with 8GB RAM. I had the NVIDIA GeForce 8800 GT now have the NVIDIA Quadro FX 5600 and am getting the same issue with both. I have dual 30" displays setup as extended desktop. The primary display works fine but if I move a window on the 2nd display, it's really jerky, almost like the card is having a difficult time keeping up but that can't be it. Any thoughts?

Went to the genius bar in london and they weren't sure about why this was happening. They suspected it was caused by a software update to OS10.4, and recommended rolling it back by reinstalling the original OS from disc. (Perhaps someone sitting in America was unaware of Europe's PAL tv refresh rate...) Unfortunately my discs are currently in a port in Brasil waiting to be shipped home with all my other stuff, so I'll have a wait a month or so to try. If anyone at Apple is reading, can you check this out?

Have iMac mid 2007 using Mavericks . . . will not function with new 2nd display?

Sys Prefs setup with 2nd display using Mavericks . . . the new functions of Mav won't come in with LG display even though same display works with my other Macs. Any like experiences or advise would be more than appreciated? bumdiago

Shawn:
One thing that caused the refresh to stop working is when you have error or bad settings in your report. Expand your upper right control panel or EVDRE area and see if everything is good. For instance, an EVDRE usually gives an error message rather than displaying (EVDRE OK) at upper right.
Also, did your input template refresh the data properly every time after you sent your data? If so, you may convert your input template to a report, and see if that will solve your problem.
Hope my 2 cents helps...
Brian

LR 2.2 on OS X 10.5.6 - Cannot reject multiple images on 2nd display Grid

Hi there,
For some reason, if I select multiple images on Grid View on my 2nd display and click 'X' to apply the Reject Flag, only the first image selected will get the X Flag. However, if I do the same exact with the Grid on my primary display, all images selected will get the X Flag.
Any ideas on what could be causing this? Is this a feature that I am missing an understanding of?
TIA!
Brian

Hmmmm... thanks for the confirmation. It just seems so odd that Adobe would feel the need to 'classify' the 2nd display as a second-class citizen. Would it really be that much more resource-intensive to allow me to take action on multiple photos on the 2nd display?
Oh well, perhaps in a future build.

MacBook 2nd display (mini-DVI-DVI (D)- VGA)?

I am trying to hook up a second display to my MacBook. The problem is that I don't have a mini-DVI to VGA adapter, but I have a mini-DVI to DVI, and a DVI to VGA adapters. So I connected my Apple mini-DVI to DVI, to my DVI to VGA, and then to my 2nd display (NEC LCD1560NX). The notebook's image flips as i normally connect a second display, it auto-detects the 2nd screen and displays its correct name, but I do not get an image on my second display. It set to the right resolution and frequency.
Any suggestions?

go to system preferences -> display-> and mirror the displays, it should work on the second display, but the cons on the macbook is to work on the first display, the built in card may not support the second one, if thats the case i'm sorry i can't help it. you can also try to get a DVI/VGA splitter and see if that work, it works on standard integrated intel VGA models. good luck!

I can't seem to turn off my 2nd display (with no adapter plugged in)

Been looking on the internets for ages about this and not got anywhere, so did a completely fresh install last night.
The problem is that the DVI (2nd display connection) thinks that I have a VGA display connected (i.e. the 2nd display) when I plug in the DVI-VGA adapter to use with a TV that works fine. The 2nd display resets to align itself to the TV connected.
When I disconnect the adapter the Mac resets it display. Back to having this phantom display connected.
I've plugged in the DVI-VGA adapter as well and then carefully removed that and sameroblem.
Having done a fresh install that would mean it's not a software issue, so it has to be a hardware one? Something with the actual connection? Does anyone know of any potential problems as to why this would happen?
I've tried some compressed air. (I've lost the straw so it was straight from the can, spray paint style)
Please help.
Thanks.

Anyone?

Ipad mini retina display safari crashed with ios 8.0.2

After updating my daughters iPad Mini retina display, safari crashes as soon as anything is entered in the search box. This started after IOS 8.0.2 update.
I have rebooted and reset the iPad. I have cleared the history and website data, but nothing has helped.

Try some basic troubleshooting:
(A) Try reset iPad
Hold down the Sleep/Wake button and the Home button at the same time for at least ten seconds, until the Apple logo appears
(B) Try reset all settings
Settings>General>Reset>Reset All Settings
(C) Setup as new (data will be lost if you do not have backup)
Settings>General>Reset>Erase all content and settings

2nd Display & iMac w/ 2 Different Sets of Content from Same iMac

Can I do this? (How can I do this?) I'd like to connect a second display to my iMac and use the iMac to generate content (like live feeds or video content from CNN.com) to play on the second display while I "work" on the iMac and its screen. Thus, each display have its own content--but the content is generated by the one iMac. Could I use a HD tv as the second display?
Thanks for your guidance.
Bill

Depends on the iMac, but some of them do support this.
Look yours up at http://www.everymac.com/systems/apple/imac/index-imac.html and look for the section about displays and 2nd display support under your model.
With the second display connected to the appropriate port, you use your Displays System Preferences to configure them. If you choose "mirror" both displays show the same thing. If you choose to not mirror, you can have an "extended desktop where you can place different windows on different monitors and do exactly what you want to do. AN HD TV might be usable but you have to look up what your iMac can handle in terms of pixels and resolution and compare that to your HD TV specs. You can certainly buy inexpensive monitors to use if your HD TV is compatible.

Photoshop CS4 and graphic cards. Can cause crashing?

Since upgrading to CS4 I seem to have increased crashing.
Here are my system specs.
Mac 2 x 2.66 GHz Dual-Core Intel Xeon
9 GB of Ram
250 GB internal dedicated scratch disc
NVDIA GeForce 7300 GT with 256 VRAM
After having endless techs look at my machine and upgrading everything. I am beginning to suspect the graphics card.
With OpenGL can a underperforming video card cause crashing in photoshop especially with massive file sizes ( multilayered CMYK poster sized files the can exceed 7 GB)?

Did you install the 11.0.1 update?
Is your OS up to date with patches?
Have you tried disabling OpenGL in preferences to avoid using the GPU/Graphics card?

Connecting a 2nd display

HI,
I have a Mac Pro, circa Dec 07 (therefore no mini display port) and currently use a 23" cinema display. I want to attach another identical display and assume I can do this via the other (spare) DVI port at the back of the Mac?
However, my main monitor has the firewire and USB cables plugged into the tower which come cabled along with the DVI cable, but when connecting the 2nd display can I just connect the DVI cable into the Mac Pro and not bother with the firewire and USB cable which are bound with it?
Obviously I understand that using the firewire and USB cable from the first display increases my available ports (at the rear of the first display)... but do I really need to connect those with the 2nd display, because I'm running out of ports at the back of the Mac!
Hope that makes sense...
Thanks,
Mark

One thing that's occured to me, somebody might know...
I calibrate my main monitor, so when the second display is either being mirrored, or just an extension of the desktop, I guess the existing calibration is sufficient as the main display calls the shots?
Or am I wrong, should both be calibrated as separate displays prior to using them together?
Thanks to anybody who can help...
Mark

2nd display disappears on switching focus to another application

Hi,
I'm running LR5 on Windows. I've got the grid view on my primary display and a second display showing the loupe view.
If the focus moves to another application (i.e. a small notepad window on the primary display) then I can still see LR with its grid view in the background behind notepad on the primary display however the loupe view on the second display disappears and I can see the desktop.
Is it possible to configure LR not to automatically hide the 2nd display when the input foucs moves to a different wiindow? I'd like to be able to continue displaying the image on the 2nd display while I'm doing something else on the primary display.
I've not been able to check but I've a feeling this is new behaviour in 5, I don't think 3 or 4 did this.
Many thanks in advance for your time/help! :-)

No, sorry. I've just checked LR3 for you, and the behaviour's the same.

2nd display causes crash

Similar Messages

Maybe you are looking for