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.
Similar Messages
-
Connecting network cable to Thunderbolt display causes MBA to crash
When plugging my MBA into my Thunderbolt screen I noticed that it often causes my MBA to crash - very frustrating! I have since discovered that this only happens when my wired network lead is connected to the Thunderbolt display. Does anyone have any suggestions? I have checked the firmware for the monitor and it is apparently up to date. I would like to be able to use the wired network through the connection on the back of the Thunderbolt screen so it really is quite inconvenient.
Thanks for any help/advice.
MBA (c. late 2012) running under Yosemite, new (late 2014) 27" Thunderbolt display.This is the report that was captured after the most recent crash (it means nothing to me!):
Anonymous UUID: 822F27BF-3E21-E25D-7633-8F8CFFE82DDA
Wed Jan 28 09:10:54 2015
*** Panic Report ***
Machine-check capabilities: 0x0000000000000c07
family: 6 model: 58 stepping: 9 microcode: 21
signature: 0x306a9
Intel(R) Core(TM) i7-3667U CPU @ 2.00GHz
7 error-reporting banks
Processor 0: IA32_MCG_STATUS: 0x0000000000000005
IA32_MC3_STATUS(0x40d): 0xbe00000000800400
IA32_MC3_ADDR(0x40e): 0x00003f7fa326f37c
IA32_MC3_MISC(0x40f): 0x000000000003ffff
Processor 1: IA32_MCG_STATUS: 0x0000000000000004
IA32_MC3_STATUS(0x40d): 0xbe00000000800400
IA32_MC3_ADDR(0x40e): 0x00003f7fa326f37c
IA32_MC3_MISC(0x40f): 0x000000000003ffff
Processor 2: IA32_MCG_STATUS: 0x0000000000000004
IA32_MC3_STATUS(0x40d): 0xbe00000000800400
IA32_MC3_ADDR(0x40e): 0x00003f7fa383cd6d
IA32_MC3_MISC(0x40f): 0x000000000003ffff
Processor 3: IA32_MCG_STATUS: 0x0000000000000005
IA32_MC3_STATUS(0x40d): 0xbe00000000800400
IA32_MC3_ADDR(0x40e): 0x00003f7fa383cd6d
IA32_MC3_MISC(0x40f): 0x000000000003ffff
panic(cpu 1 caller 0xffffff802241f12a): "Machine Check at 0xffffff7fa326f37c, registers:\n" "CR0: 0x000000008001003b, CR2: 0x000000010a35d000, CR3: 0x0000000025272000, CR4: 0x00000000001626e0\n" "RAX: 0xffffff812b25e010, RBX: 0x0000000000000000, RCX: 0x38d4d359698d0037, RDX: 0xffffff81239fc088\n" "RSP: 0xffffff814b943b40, RBP: 0xffffff814b943b80, RSI: 0xffffff81239fc068, RDI: 0x0000000000000000\n" "R8: 0x00000000009891e0, R9: 0xffffff81239fc068, R10: 0x00001821f6529797, R11: 0x00001821f5ba05b7\n" "R12: 0xffffff80f3939000, R13: 0x00000000ffffffff, R14: 0x0000000000000000, R15: 0xffffff8022b0ae74\n" "RFL: 0x0000000000010202, RIP: 0xffffff7fa326f37c, CS: 0x0000000000000008, SS: 0x0000000000000000\n" "Error code: 0x0000000000000000\n"@/SourceCache/xnu/xnu-2782.1.97/osfmk/i386/trap_native.c:1 68
Backtrace (CPU 1), Frame : Return Address
0xffffff8123965e90 : 0xffffff802233a811
0xffffff8123965f10 : 0xffffff802241f12a
0xffffff8123966070 : 0xffffff802243acef
0xffffff814b943b80 : 0xffffff7fa3271a68
0xffffff814b943bb0 : 0xffffff7fa326e261
0xffffff814b943c00 : 0xffffff7fa30ad4b0
0xffffff814b943ce0 : 0xffffff7fa326f830
0xffffff814b943da0 : 0xffffff7fa32719dd
0xffffff814b943e00 : 0xffffff7fa3274973
0xffffff814b943e50 : 0xffffff7fa3274aa6
0xffffff814b943ea0 : 0xffffff80228db3cd
0xffffff814b943f00 : 0xffffff802236be13
0xffffff814b943fb0 : 0xffffff80224192c7
Kernel Extensions in backtrace:
com.apple.iokit.IOUSBFamily(705.4.14)[E15E9DC8-410F-3612-8371-E5FECD939E0D]@0xf fffff7fa30ab000->0xffffff7fa310ffff
dependency: com.apple.iokit.IOPCIFamily(2.9)[766FC23F-452C-3B74-951C-598BB17BCF06]@0xffffff 7fa2b24000
com.apple.driver.AppleUSBEHCI(705.4.14)[8DF38F62-9C2F-3A62-B6AD
Model: MacBookAir5,2, BootROM MBA51.00EF.B02, 2 processors, Intel Core i7, 2 GHz, 8 GB, SMC 2.5f7
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x02FE, -
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x02FE, -
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xE9), Broadcom BCM43xx 1.0 (7.15.124.12.10)
Bluetooth: Version 4.3.1f2 15015, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Network Service: Display Ethernet, Ethernet, en2
PCI Card: Apple 57761-B0, Ethernet Controller, Thunderbolt@191,0,0
PCI Card: pci11c1,5901, IEEE 1394 Open HCI, Thunderbolt@190,0,0
PCI Card: pci12d8,400e, USB Open Host Controller, Thunderbolt@196,0,0
PCI Card: pci12d8,400e, USB Open Host Controller, Thunderbolt@196,0,1
PCI Card: pci12d8,400f, USB Enhanced Host Controller, Thunderbolt@196,0,2
Serial ATA Device: APPLE SSD SM512E, 500.28 GB
USB Device: Hub
USB Device: FaceTime HD Camera (Built-in)
USB Device: Hub
USB Device: Hub
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Hub
USB Device: HP LaserJet 400 color M451dn
USB Device: Apple Thunderbolt Display
USB Device: Display Audio
USB Device: FaceTime HD Camera (Display)
Thunderbolt Bus: MacBook Air, Apple Inc., 23.4
Thunderbolt Device: Thunderbolt Display, Apple Inc., 1, 26.2 -
Using the integrated USB hub on my Thunderbolt Display causes troubles
I just purchased a MacBook Air and a Thunderbolt Display. Unfortunately, when I connect USB plugs to the Displays buildin USB hub, I'm getting severed connections all the time (USB-Connection lost, Firewire-Connection lost, Ethernet-Connection lost...).
I really loved the idea of not having to use external USB-hubs as this only clutters my desk - but the Displays internal hub cannot be used savely (I have a couple of hard drives connected via FW and USB to the Display - this has already resulted in data loss (fortunately I had a backup).
As soon as I'm NOT using the Display's USB ports everything is fine (the Display's FireWire and Ethernet ports do not seem to cause any trouble).
Anyone else seeing this?Plugging an additional USB hub into the integrated USB hub extends the problematic behavior even further.
If I eject a thumb drive from a USB hub that's attached to the Thunderbolt display hub (for example), it will never recognize that thumb drive again, on any of the USB ports on the display or any additional hub connected to the display, until I reboot with no added USB hub, and then reconnect an empty hub, and then add devices one at a time.
I've also noticed that while some devices drop off, some continue to show up in the system report, even when they have been properly ejected or disconnected. Refreshing the system report doesn't update with what's really going on...
Weird... So since mountain lion, I don't disconnect any USB devices from the Thunderbolt display, unless I really, truly must. -
Retina macbook pro with thunderbolt display causes speaker issues
I have a thunderbolt display and used the speakers fine on old macbook pro. I now plug in my new retina macbook pro 15" with mountain lion and the sound plays fine for a while then starts to crackle real bad and then stops all together. If I switch the the laptop speakers then switch back after 30 or so minutes the thunderbolt speakers will work again for a short amount of time then again crackle and stop.
This may be mountain lion related but I have tried another non-retina version macbook pro with mountain lion and did not notice the issue but it was only for an hour or so. So this leads me to belive its the computer.
Any suggestions? its really really anoying and wasting my time trying to fix it.I have the exact same issue. I hauled the TB Display into the Apple Store 3 times and finally they replaced it. Come to find out this new one has the same issue still. So It has to be rMBP related at this point. Unfortunately I don't think I have it under warranty still and the issue is hard to demonstrate. I recorded videos of it but every time I go into the store and plug it is the same as switching the speakers from internal to external and it takes 30-60 mins before it degrates to scratching sounds.
Please let me know if you ever foudn a solution. Im going to try to keep taking it in until I can get this resolved. -
Thunderbolt display update crash
Hello,
During Thunderbolt Display Firmware update 1.2 my computer stuck and turn off. Thunderbolt display stop working, computer shows no thunderbolt devices. I also try connect to MacBook Pro with same result. Is any way how to recover display?
Thank for your help.
Petr
Message was edited by: brhelp_zr
I am sorry i wrote post with same problem like https://discussions.apple.com/thread/6759865..and solved. The secret seemed to be to follow these steps. Have no idea if they are all necessary but it worked for me.
In Display preferences hit gather window to bring the thunderbolt display preferences onto the mac screen
Uncheck Adjust brightness automatically and save
disconnect the display from the mac.
Restart the mac
Power down the display and leave for a few minutes
Power up the display
Reconnect the display to the mac
The screen returned to life. Let's see if it stays that way, I will report if it doesn't. -
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. -
Mac OS X 10.8 crashes after disconnecting the Thunderbolt display
Wondering if anyone can help my Mac OS X 10.8.5 crashes after I disconnect the thunderbolt display.
I normally work in the studio with my macbook connected to an external display.
When I go to use it without the thunderbolt display it crashes - 4 times in one day, which really isn't ideal when your freelancing.
I've checked my log files and I have a list of panic reports. I'm not too sure what I'm supposed to be looking for, but each of the reports refer to the graphics control. I've read online it might have something to do with the display sleep, so I've reset that.
GPU Panic: [<None>] 5 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff808013e000 0x0a5480a2, D0, P3/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.4.5/src/AppleM uxControl/kext/GPUPanic.cpp:127
I'd be very grateful if anyone could help
ChloeHi Chloebat,
I'm sorry to hear you are having issues with your MacBook Pro. If you continue to have intermittent but persistent crashing issues with your Mac, possibly related to the display, you may find the troubleshooting steps outlined in the following article helpful:
OS X: When your computer spontaneously restarts or displays "Your computer restarted because of a problem." - Apple Support
Regards,
- Brenden -
Macbook pro 17 inch primo 2011 and thunderbolt display crashes
I have a Macbook pro 17 inch primo 2011 and thunderbolt display which has recently started to crash.
Only modifications I have doen lately is I swapped the CD/DVD drive for a harddrive and put in 16 GB of ram
but it has been running for more than a month with these hardware additions without problems.
Today my Macbook has started to crash frequently within 10 min to 1 hour after plugging in my thunderbolt display.
I tried to check CPU heat, change RAM but it keps crashing.
When it crashes it either gives me a blue screen, a black screen or a distorts everythings and freeze up.
When rebooting I have to press Command-Option-P-R to clear NVRAM / PRAM.
I found a few support threads from people having similar problems so I started to disconnect the thunderbolt display
and without plugging it in my laptop works fine.
I have done a SMC reset also but that has not resolved my issue.
Below is the crash report and if anybody has any suggestions what to do to resolve this please let me know
My thunderbolt display was purchased in late 2011
If this is not solveable what options do I have ?
Thanks !
Interval Since Last Panic Report: 2527129 sec
Panics Since Last Report: 6
Anonymous UUID: 5309BD58-3CBB-321E-545E-6EE6BED7E0E2
Tue Feb 5 17:02:21 2013
Machine-check capabilities 0x0000000000000c09:
family: 6 model: 42 stepping: 7 microcode: 26
Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz
9 error-reporting banks
threshold-based error status present
extended corrected memory error handling present
Processor 0: machine-check status 0x0000000000000004:
machine-check in progress
MCA error-reporting registers:
IA32_MC0_STATUS(0x401): 0x0000000000000000 invalid
IA32_MC1_STATUS(0x405): 0x0980000000000000 invalid
IA32_MC2_STATUS(0x409): 0x0000000000000000 invalid
IA32_MC3_STATUS(0x40d): 0xbe00000000800400 valid
MCA error code: 0x0400
Model specific error code: 0x0080
Other information: 0x00000000
Threshold-based status: Undefined
Status bits:
Processor context corrupt
ADDR register valid
MISC register valid
Error enabled
Uncorrected error
IA32_MC3_ADDR(0x40e): 0x00003f7f85769a95
IA32_MC3_MISC(0x40f): 0x000000000003ffff
IA32_MC4_STATUS(0x411): 0x0000000000000000 invalid
IA32_MC5_STATUS(0x415): 0x0020000000000000 invalid
IA32_MC6_STATUS(0x419): 0x0020000000000000 invalid
IA32_MC7_STATUS(0x41d): 0x0020000000000000 invalid
IA32_MC8_STATUS(0x421): 0x0020000000000000 invalid
Processor 1: machine-check status 0x0000000000000005:
restart IP valid
machine-check in progress
MCA error-reporting registers:
IA32_MC0_STATUS(0x401): 0x0000000000000000 invalid
IA32_MC1_STATUS(0x405): 0x0980000000000000 invalid
IA32_MC2_STATUS(0x409): 0x0000000000000000 invalid
IA32_MC3_STATUS(0x40d): 0xbe00000000800400 valid
MCA error code: 0x0400
Model specific error code: 0x0080
Other information: 0x00000000
Threshold-based status: Undefined
Status bits:
Processor context corrupt
ADDR register valid
MISC register valid
Error enabled
Uncorrected error
IA32_MC3_ADDR(0x40e): 0x00003f7f85769a95
IA32_MC3_MISC(0x40f): 0x000000000003ffff
IA32_MC4_STATUS(0x411): 0x0000000000000000 invalid
IA32_MC5_STATUS(0x415): 0x0020000000000000 invalid
IA32_MC6_STATUS(0x419): 0x0020000000000000 invalid
IA32_MC7_STATUS(0x41d): 0x0020000000000000 invalid
Package 0 logged:
IA32_MC8_STATUS(0x421): 0x0020000000000000 invalid
Processor 2: no valid machine-check state
Processor 3: no valid machine-check state
Processor 4: machine-check status 0x0000000000000004:
machine-check in progress
MCA error-reporting registers:
IA32_MC0_STATUS(0x401): 0x0000000000000000 invalid
IA32_MC1_STATUS(0x405): 0x0980000000000000 invalid
IA32_MC2_STATUS(0x409): 0x0000000000000000 invalid
IA32_MC3_STATUS(0x40d): 0xbe00000000800400 valid
MCA error code: 0x0400
Model specific error code: 0x0080
Other information: 0x00000000
Threshold-based status: Undefined
Status bits:
Processor context corrupt
ADDR register valid
MISC register valid
Error enabled
Uncorrected error
IA32_MC3_ADDR(0x40e): 0x00003f7f85fa3e1f
IA32_MC3_MISC(0x40f): 0x000000000003ffff
IA32_MC4_STATUS(0x411): 0x0000000000000000 invalid
IA32_MC5_STATUS(0x415): 0x0020000000000000 invalid
IA32_MC6_STATUS(0x419): 0x0020000000000000 invalid
IA32_MC7_STATUS(0x41d): 0x0020000000000000 invalid
IA32_MC8_STATUS(0x421): 0x0020000000000000 invalid
Processor 5: machine-check status 0x0000000000000005:
restart IP valid
machine-check in progress
MCA error-reporting registers:
IA32_MC0_STATUS(0x401): 0x0000000000000000 invalid
IA32_MC1_STATUS(0x405): 0x0980000000000000 invalid
IA32_MC2_STATUS(0x409): 0x0000000000000000 invalid
IA32_MC3_STATUS(0x40d): 0xbe00000000800400 valid
MCA error code: 0x0400
Model specific error code: 0x0080
Other information: 0x00000000
Threshold-based status: Undefined
Status bits:
Processor context corrupt
ADDR register valid
MISC register valid
Error enabled
Uncorrected error
IA32_MC3_ADDR(0x40e): 0x00003f7f85fa3e1f
IA32_MC3_MISC(0x40f): 0x000000000003ffff
IA32_MC4_STATUS(0x411): 0x0000000000000000 invalid
IA32_MC5_STATUS(0x415): 0x0020000000000000 invalid
IA32_MC6_STATUS(0x419): 0x0020000000000000 invalid
IA32_MC7_STATUS(0x41d): 0x0020000000000000 invalid
IA32_MC8_STATUS(0x421): 0x0020000000000000 invalid
Processor 6: no valid machine-check state
Processor 7: no valid machine-check state
panic(cpu 0 caller 0xffffff80048b83c9): "Machine Check at 0xffffff7f85769a95, registers:\n" "CR0: 0x000000008001003b, CR2: 0x000000010cd0e30c, CR3: 0x00000000072b4000, CR4: 0x00000000000606e0\n" "RAX: 0xffffff802516f800, RBX: 0xffffff802516f800, RCX: 0xffffff80253ab800, RDX: 0x0000000000000001\n" "RSP: 0xffffff8207ad3e90, RBP: 0xffffff8207ad3ec0, RSI: 0xffffff8207ad3edf, RDI: 0xffffff802520e000\n" "R8: 0xffffff8004ebec60, R9: 0x7fffffffffffff00, R10: 0xffffff8004ebdc20, R11: 0x0000000000000201\n" "R12: 0xffffff80253ab800, R13: 0xffffff81d60d2000, R14: 0xffffff8207ad3edf, R15: 0xffffff802520e000\n" "RFL: 0x0000000000010282, RIP: 0xffffff7f85769a95, CS: 0x0000000000000008, SS: 0x0000000000000010\n" "Error code: 0x0000000000000000\n"@/SourceCache/xnu/xnu-2050.18.24/osfmk/i386/trap_native.c: 280
Backtrace (CPU 0), Frame : Return Address
0xffffff800470bd20 : 0xffffff800481d626
0xffffff800470bd90 : 0xffffff80048b83c9
0xffffff800470bf00 : 0xffffff80048cedbf
0xffffff8207ad3ec0 : 0xffffff7f856d75b4
0xffffff8207ad3ef0 : 0xffffff8004c472a8
0xffffff8207ad3f30 : 0xffffff8004c45daa
0xffffff8207ad3f80 : 0xffffff8004c45ed9
0xffffff8207ad3fb0 : 0xffffff80048b26b7
Kernel Extensions in backtrace:
com.apple.driver.AirPort.Brcm4331(602.15.22)[5BDCA43F-AD42-3F05-BCCF-BC364D17E1 5F]@0xffffff7f856ca000->0xffffff7f858bbfff
dependency: com.apple.iokit.IOPCIFamily(2.7.2)[B1B77B26-7984-302F-BA8E-544DD3D75E73]@0xffff ff7f84e72000
dependency: com.apple.iokit.IO80211Family(500.15)[4282DF5A-86B9-3213-B9B1-675FAD842A94]@0xf fffff7f8565e000
dependency: com.apple.iokit.IONetworkingFamily(3.0)[28575328-A798-34B3-BD84-D708138EBD17]@0 xffffff7f85015000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
12C60
Kernel version:
Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
Kernel UUID: 69A5853F-375A-3EF4-9247-478FD0247333
Kernel slide: 0x0000000004600000
Kernel text base: 0xffffff8004800000
System model name: MacBookPro8,3 (Mac-942459F5819B171B)
System uptime in nanoseconds: 6197670207287
last loaded kext at 6133447331639: com.apple.driver.AppleUSBCDC 4.1.22 (addr 0xffffff7f86cb5000, size 16384)
last unloaded kext at 5379727445407: com.apple.driver.AppleUSBCDC 4.1.22 (addr 0xffffff7f86cb2000, size 12288)
loaded kexts:
com.apple.driver.AppleUSBCDC 4.1.22
com.apple.iokit.SCSITaskUserClient 3.5.1
com.apple.filesystems.smbfs 1.8
com.apple.filesystems.afpfs 10.0
com.apple.nke.asp_tcp 7.0.0
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.filesystems.autofs 3.0
com.apple.filesystems.ntfs 3.10
com.apple.iokit.IOBluetoothSerialManager 4.0.9f33
com.apple.driver.AGPM 100.12.69
com.apple.driver.AppleMikeyHIDDriver 122
com.apple.driver.AppleHDA 2.3.1f2
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.ApplePolicyControl 3.2.11
com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport 4.0.9f33
com.apple.driver.AppleUpstreamUserClient 3.5.10
com.apple.driver.AppleIntelHD3000Graphics 8.0.0
com.apple.driver.AppleMCCSControl 1.0.33
com.apple.kext.AMDFramebuffer 8.0.0
com.apple.driver.SMCMotionSensor 3.0.2d6
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleMikeyDriver 2.3.1f2
com.apple.driver.AppleLPC 1.6.0
com.apple.driver.AppleSMCLMU 2.0.2d0
com.apple.AMDRadeonAccelerator 1.0.0
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.driver.AppleMuxControl 3.2.11
com.apple.driver.AppleIntelSNBGraphicsFB 8.0.0
com.apple.driver.AppleUSBTCButtons 235.4
com.apple.driver.AppleUSBTCKeyboard 235.4
com.apple.driver.AppleIRController 320.15
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 34
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.2.2
com.apple.driver.AppleUSBHub 5.2.5
com.apple.iokit.AppleBCM5701Ethernet 3.2.5b3
com.apple.driver.AirPort.Brcm4331 602.15.22
com.apple.driver.AppleFWOHCI 4.9.6
com.apple.driver.AppleAHCIPort 2.4.1
com.apple.driver.AppleUSBEHCI 5.4.0
com.apple.driver.AppleEFINVRAM 1.6.1
com.apple.driver.AppleIntelCPUPowerManagementClient 196.0.0
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleACPIButtons 1.6
com.apple.driver.AppleRTC 1.5
com.apple.driver.AppleHPET 1.7
com.apple.driver.AppleSMBIOS 1.9
com.apple.driver.AppleACPIEC 1.6
com.apple.driver.AppleAPIC 1.6
com.apple.nke.applicationfirewall 4.0.39
com.apple.security.quarantine 2
com.apple.driver.AppleIntelCPUPowerManagement 196.0.0
com.apple.iokit.IOSCSIBlockCommandsDevice 3.5.1
com.apple.iokit.IOFireWireSerialBusProtocolTransport 2.1.1
com.apple.iokit.IOFireWireSBP2 4.2.0
com.apple.security.SecureRemotePassword 1.0
com.apple.kext.triggers 1.0
com.apple.iokit.IOSCSIArchitectureModelFamily 3.5.1
com.apple.iokit.IOSerialFamily 10.0.6
com.apple.driver.DspFuncLib 2.3.1f2
com.apple.iokit.IOAudioFamily 1.8.9fc10
com.apple.kext.OSvKernDSPLib 1.6
com.apple.iokit.IOSurface 86.0.3
com.apple.iokit.IOBluetoothFamily 4.0.9f33
com.apple.iokit.AppleBluetoothHCIControllerUSBTransport 4.0.9f33
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.AppleSMBusController 1.0.10d0
com.apple.driver.AppleSMBusPCI 1.0.10d0
com.apple.driver.AppleSMC 3.1.4d2
com.apple.iokit.IOAcceleratorFamily 19.0.26
com.apple.kext.AMD6000Controller 8.0.0
com.apple.kext.AMDSupport 8.0.0
com.apple.driver.AppleHDAController 2.3.1f2
com.apple.iokit.IOHDAFamily 2.3.1f2
com.apple.driver.IOPlatformPluginFamily 5.2.0d16
com.apple.driver.AppleGraphicsControl 3.2.11
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.iokit.IONDRVSupport 2.3.5
com.apple.iokit.IOGraphicsFamily 2.3.5
com.apple.iokit.IOFireWireIP 2.2.5
com.apple.driver.AppleThunderboltDPInAdapter 1.8.5
com.apple.driver.AppleThunderboltDPAdapterFamily 1.8.5
com.apple.driver.AppleThunderboltPCIDownAdapter 1.2.5
com.apple.driver.AppleUSBMultitouch 235.7
com.apple.iokit.IOUSBHIDDriver 5.2.5
com.apple.driver.AppleUSBMergeNub 5.2.5
com.apple.driver.AppleUSBComposite 5.2.5
com.apple.driver.CoreStorage 274.7
com.apple.driver.AppleThunderboltNHI 1.6.0
com.apple.iokit.IOThunderboltFamily 2.1.1
com.apple.iokit.IOUSBUserClient 5.2.5
com.apple.iokit.IOEthernetAVBController 1.0.2b1
com.apple.iokit.IO80211Family 500.15
com.apple.iokit.I
Model: MacBookPro8,3, BootROM MBP81.0047.B27, 4 processors, Intel Core i7, 2.2 GHz, 16 GB, SMC 1.70f5
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 512 MB
Graphics: AMD Radeon HD 6750M, AMD Radeon HD 6750M, PCIe, 1024 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1333 MHz, 0x029E, 0x434D534F384758334D314131333333433920
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1333 MHz, 0x029E, 0x434D534F384758334D314131333333433920
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.81.22)
Bluetooth: Version 4.0.9f33 10885, 2 service, 11 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: APPLE SSD TS256C, 251 GB
Serial ATA Device: ST750LX003-1AC154, 750,16 GB
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfa100000 / 3
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0246, 0xfa120000 / 5
USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821a, 0xfa113000 / 6
USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0xfa200000 / 2
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfd100000 / 2
USB Device: USB Receiver, 0x046d (Logitech Inc.), 0xc51b, 0xfd130000 / 5
USB Device: iPhone, apple_vendor_id, 0x12a0, 0xfd120000 / 4
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3
FireWire Device: My Book 111D, WD, 800mbit_speedThe other day I got the blue screen, the fan going on high, and then when I disconnect my thunderbolt connection from my macbook pro - i get a shutdown.
Today I got flickering followed by the fan on high and then again I disconneced my thunderbolt cable and after a minute or two a shudown.
This never happened before. Actually I was suprised to hear about a firmware update for flickering since that's never happened to me but since updating I now get the flicker.
Any ideas?? Any help would be greatly appreciated as this is my work labtop. -
Why is my 15" rMPB crashing when using 2 Thunderbolt Displays?
Over the last few days my 2012 15" rMBP has been crashing periodically.
Today it continued to crash every few minutes, I tried resetting PRAM and SMC - didn't seem to help. After reading somewhere (not here) people having issues with Multiple external Displays, I onlly plugged in one of my 2 Thunderbolt Displays and it seems to be stable.
In my normal set up I use 2 - 27" TBD's and a 55" Sanyo TV via HDMI - it has worked great for over a year but now I am experiencing continued crashing when I have everything plugged in.
Is this a known issue?
I think this may be an issue with the last update - which was installed on my rMBP on the 9th or Jan (only 9 days ago)... that is about when I first started noticing an issue.
Is there anything I can do?Welcome to Apple Support Communities
Note that your MacBook Pro is using the dedicated GPU and you have got two GPUs. The dedicated GPU generates more heat, and even more if you are using the GPU to display image in three displays (including your built-in display). I would not be worried if fans are working correctly -
Macbook Pro Retina crashes with thunderbolt display
Whenver I plug the thunderbolt display into my macbook pro retina both displays black out and the computer becomes semi-unrespsonsive (ie I can hear the volume controls however that is all. I need to force shutdown.
I've noticed this problem happening since I installed xQuark (X11) a week ago, I have since removed it and any traces of it but the problem seems to have become worse.
Below was taken from /Library/Logs/DiagnosticReports/Kernel_2014-05-15-110032_Erics-MacBook-Pro.pani c
Anonymous UUID: 19585CF3-FBBE-A563-492E-2409319F5C2A
Thu May 15 11:00:32 2014
panic(cpu 0 caller 0xffffff7f88774fb0): "GPU Panic: [<None>] 5 0 a0 d9 9 8 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0x102c00000 0xffffff80fdc15000 0x0e7150a2, D0, P1/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.4.35/src/Apple MuxControl/kext/GPUPanic.cpp:127
Backtrace (CPU 0), Frame : Return Address
0xffffff80f9cdb320 : 0xffffff8006422fa9
0xffffff80f9cdb3a0 : 0xffffff7f88774fb0
0xffffff80f9cdb470 : 0xffffff7f86dfa22c
0xffffff80f9cdb530 : 0xffffff7f86ec4106
0xffffff80f9cdb570 : 0xffffff7f86ec4176
0xffffff80f9cdb5e0 : 0xffffff7f870e99de
0xffffff80f9cdb650 : 0xffffff7f86ee6c2d
0xffffff80f9cdb670 : 0xffffff7f86e00c75
0xffffff80f9cdb720 : 0xffffff7f86dfe780
0xffffff80f9cdb920 : 0xffffff7f86e000cf
0xffffff80f9cdb9f0 : 0xffffff7f87d0007b
0xffffff80f9cdbac0 : 0xffffff7f87c91c0b
0xffffff80f9cdbaf0 : 0xffffff7f87c903f4
0xffffff80f9cdbb70 : 0xffffff80068cd2aa
0xffffff80f9cdbb90 : 0xffffff80068cde0e
0xffffff80f9cdbbf0 : 0xffffff80068cb85f
0xffffff80f9cdbd40 : 0xffffff80064b65a8
0xffffff80f9cdbe50 : 0xffffff8006426bf1
0xffffff80f9cdbe80 : 0xffffff80064139f5
0xffffff80f9cdbef0 : 0xffffff800641e043
0xffffff80f9cdbf70 : 0xffffff80064c97bd
0xffffff80f9cdbfb0 : 0xffffff80064f3b96
Kernel Extensions in backtrace:
com.apple.driver.AppleMuxControl(3.4.35)[1BFF66C1-65E4-3BB3-9DEE-B61C3137019B]@ 0xffffff7f88767000->0xffffff7f88779fff
dependency: com.apple.driver.AppleGraphicsControl(3.4.35)[09897896-ACBD-36B5-B1D4-0CCC4000E 3B3]@0xffffff7f8875f000
dependency: com.apple.iokit.IOACPIFamily(1.4)[045D5D6F-AD1E-36DB-A249-A346E2B48E54]@0xfffff f7f876d7000
dependency: com.apple.iokit.IOPCIFamily(2.9)[EDA75271-4E9D-34E7-A2C5-14F0C8817D37]@0xffffff 7f86aba000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[4421462D-2B1F-3540-8EEA-9DFCB0565E39]@0 xffffff7f86d57000
dependency: com.apple.driver.AppleBacklightExpert(1.0.4)[E04639C5-D734-3AB3-A682-FE66694C66 53]@0xffffff7f88762000
com.apple.nvidia.driver.NVDAResman(8.2.4)[3D591202-DD24-3441-925A-F6808ABDF185] @0xffffff7f86daa000->0xffffff7f8700efff
dependency: com.apple.iokit.IOPCIFamily(2.9)[EDA75271-4E9D-34E7-A2C5-14F0C8817D37]@0xffffff 7f86aba000
dependency: com.apple.iokit.IONDRVSupport(2.4.1)[999E29DA-D513-3544-89D1-9885B728A098]@0xff ffff7f86d9a000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[4421462D-2B1F-3540-8EEA-9DFCB0565E39]@0 xffffff7f86d57000
com.apple.nvidia.driver.NVDAGK100Hal(8.2.4)[ACFCEA0C-4C80-36C0-8636-D10EE7D2DE1 7]@0xffffff7f87019000->0xffffff7f871c5fff
dependency: com.apple.nvidia.driver.NVDAResman(8.2.4)[3D591202-DD24-3441-925A-F6808ABDF185] @0xffffff7f86daa000
dependency: com.apple.iokit.IOPCIFamily(2.9)[EDA75271-4E9D-34E7-A2C5-14F0C8817D37]@0xffffff 7f86aba000
com.apple.iokit.IOAcceleratorFamily(98.14)[E354596B-CE66-31A7-B0DC-834008B85FCA ]@0xffffff7f87c7a000->0xffffff7f87cd2fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[EDA75271-4E9D-34E7-A2C5-14F0C8817D37]@0xffffff 7f86aba000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[4421462D-2B1F-3540-8EEA-9DFCB0565E39]@0 xffffff7f86d57000
com.apple.GeForce(8.2.4)[401BA8AE-CD52-3810-A066-4C648B3FC46D]@0xffffff7f87cdf0 00->0xffffff7f87d6dfff
dependency: com.apple.iokit.IOAcceleratorFamily(98.14)[E354596B-CE66-31A7-B0DC-834008B85FCA ]@0xffffff7f87c7a000
dependency: com.apple.iokit.IOPCIFamily(2.9)[EDA75271-4E9D-34E7-A2C5-14F0C8817D37]@0xffffff 7f86aba000
dependency: com.apple.iokit.IONDRVSupport(2.4.1)[999E29DA-D513-3544-89D1-9885B728A098]@0xff ffff7f86d9a000
dependency: com.apple.nvidia.driver.NVDAResman(8.2.4)[3D591202-DD24-3441-925A-F6808ABDF185] @0xffffff7f86daa000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[4421462D-2B1F-3540-8EEA-9DFCB0565E39]@0 xffffff7f86d57000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
13C1021
Kernel version:
Darwin Kernel Version 13.1.0: Wed Apr 2 23:52:02 PDT 2014; root:xnu-2422.92.1~2/RELEASE_X86_64
Kernel UUID: E9CF78E2-1E9F-3B6F-81A4-FEE6C6D0E4D5
Kernel slide: 0x0000000006200000
Kernel text base: 0xffffff8006400000
System model name: MacBookPro10,1 (Mac-C3EC7CD22292981F)
System uptime in nanoseconds: 90093108152
last loaded kext at 84805683382: com.apple.driver.AppleUSBDisplays 360.8.14 (addr 0xffffff7f88070000, size 20480)
loaded kexts:
com.apple.driver.AppleUSBDisplays 360.8.14
com.apple.driver.AppleUSBCDC 4.2.1b5
com.apple.driver.AppleUSBOHCI 656.4.1
com.apple.driver.AppleFWOHCI 4.9.9
com.apple.driver.AppleBluetoothMultitouch 80.14
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.filesystems.autofs 3.0
com.apple.iokit.IOBluetoothSerialManager 4.2.3f10
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AppleMikeyDriver 2.6.0f1
com.apple.driver.AGPM 100.14.15
com.apple.driver.X86PlatformShim 1.0.0
com.apple.driver.ApplePlatformEnabler 2.0.9d1
com.apple.driver.AppleHDAHardwareConfigDriver 2.6.0f1
com.apple.driver.AppleUpstreamUserClient 3.5.13
com.apple.driver.AppleHDA 2.6.0f1
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.GeForce 8.2.4
com.apple.iokit.IOBluetoothUSBDFU 4.2.3f10
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.2.3f10
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleIntelHD4000Graphics 8.2.4
com.apple.driver.AppleThunderboltIP 1.1.2
com.apple.nvidia.NVDAStartup 8.2.4
com.apple.driver.AppleIntelMCEReporter 104
com.apple.driver.AppleSMCLMU 2.0.4d1
com.apple.driver.AppleLPC 1.7.0
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.driver.AppleIntelFramebufferCapri 8.2.4
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleMuxControl 3.4.35
com.apple.driver.AppleBacklight 170.3.5
com.apple.driver.AppleMCCSControl 1.1.12
com.apple.driver.AppleUSBTCButtons 240.2
com.apple.driver.AppleUSBTCKeyEventDriver 240.2
com.apple.driver.AppleUSBTCKeyboard 240.2
com.apple.driver.AppleFileSystemDriver 3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.driver.XsanFilter 404
com.apple.driver.AppleUSBHub 666.4.0
com.apple.driver.AppleSDXC 1.5.2
com.apple.iokit.IOAHCIBlockStorage 2.5.1
com.apple.iokit.AppleBCM5701Ethernet 3.8.1b2
com.apple.driver.AirPort.Brcm4331 700.20.22
com.apple.driver.AppleAHCIPort 3.0.0
com.apple.driver.AppleUSBEHCI 660.4.0
com.apple.driver.AppleUSBXHCI 670.4.0
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleACPIButtons 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.driver.AppleIntelCPUPowerManagementClient 216.0.0
com.apple.nke.applicationfirewall 153
com.apple.security.quarantine 3
com.apple.driver.AppleIntelCPUPowerManagement 216.0.0
com.apple.driver.AppleUSBAudio 2.9.5f4
com.apple.iokit.IOFireWireIP 2.2.6
com.apple.iokit.IOFireWireFamily 4.5.5
com.apple.driver.AppleThunderboltPCIUpAdapter 1.4.5
com.apple.driver.AppleBluetoothHIDKeyboard 170.15
com.apple.driver.AppleHIDKeyboard 170.15
com.apple.driver.IOBluetoothHIDDriver 4.2.3f10
com.apple.driver.AppleMultitouchDriver 245.13
com.apple.kext.triggers 1.0
com.apple.iokit.IOSerialFamily 10.0.7
com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.6
com.apple.driver.DspFuncLib 2.6.0f1
com.apple.vecLib.kext 1.0.0
com.apple.iokit.IOAudioFamily 1.9.5fc2
com.apple.kext.OSvKernDSPLib 1.14
com.apple.iokit.IOAcceleratorFamily 98.14
com.apple.nvidia.driver.NVDAGK100Hal 8.2.4
com.apple.nvidia.driver.NVDAResman 8.2.4
com.apple.iokit.IOBluetoothFamily 4.2.3f10
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.2.3f10
com.apple.iokit.IOSurface 91
com.apple.driver.AppleThunderboltEDMSink 2.1.3
com.apple.driver.AppleThunderboltDPOutAdapter 3.1.7
com.apple.driver.AppleHDAController 2.6.0f1
com.apple.iokit.IOHDAFamily 2.6.0f1
com.apple.driver.AppleSMBusPCI 1.0.12d1
com.apple.iokit.IOAcceleratorFamily2 98.14
com.apple.AppleGraphicsDeviceControl 3.4.35
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.X86PlatformPlugin 1.0.0
com.apple.driver.AppleSMC 3.1.8
com.apple.driver.IOPlatformPluginFamily 5.7.0d10
com.apple.driver.AppleGraphicsControl 3.4.35
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.IOUSBHIDDriver 660.4.0
com.apple.driver.AppleThunderboltDPInAdapter 3.1.7
com.apple.driver.AppleThunderboltDPAdapterFamily 3.1.7
com.apple.driver.AppleThunderboltPCIDownAdapter 1.4.5
com.apple.driver.AppleUSBMergeNub 650.4.0
com.apple.driver.AppleUSBComposite 656.4.1
com.apple.driver.AppleThunderboltNHI 2.0.1
com.apple.iokit.IOThunderboltFamily 3.2.7
com.apple.iokit.IOEthernetAVBController 1.0.3b4
com.apple.driver.mDNSOffloadUserClient 1.0.1b5
com.apple.iokit.IOUSBUserClient 660.4.2
com.apple.iokit.IO80211Family 630.35
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOAHCIFamily 2.6.5
com.apple.iokit.IOUSBFamily 675.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 1Hi there ericdi,
It looks like you are experiencing persistent kernel panics. You may find the troubleshooting steps toward the bottom of the article below helpful. Please keep in mind, diagnosing a recurring kernel panic can be difficult. If you would like to avoid this process, or do not know how to perform any of the following steps, consider bringing the Mac to a Genius at an Apple Store or an Apple Authorized Service Provider for assistance. Be sure to ask that, if the drive needs reformatting or replacing, they contact you about escalating your case to a special data recovery service. If you plan to visit an Apple Retail store, make a reservation at the Genius Bar using http://www.apple.com/retail/geniusbar/ (available in some countries only).
OS X: About kernel panics
http://support.apple.com/kb/ts3742
-Griff W. -
Thunderbolt display update 1.2 causes unresponsive display
After running the thunderbolt display update 1.2 my display now displays the very thing the update was designed was supposed to correct - a black unresponsive screen (which I have ironically never suffered fro at all ever - grrrr).
I cannot get the thunderbolt display to come back to life although the mac can see it and thinks it is there and is extending the desktop to it.
Anyone else have this issue or ideas to solve?..and solved. The secret seemed to be to follow these steps. Have no idea if they are all necessary but it worked for me.
In Display preferences hit gather window to bring the thunderbolt display preferences onto the mac screen
Uncheck Adjust brightness automatically and save
disconnect the display from the mac.
Restart the mac
Power down the display and leave for a few minutes
Power up the display
Reconnect the display to the mac
The screen returned to life. Let's see if it stays that way, I will report if it doesn't. -
GPU Panic with Thunderbolt Display after upgrading to 10.9.3
Hi everybody! I have a MacBook Pro Retina Mid 2012 and use it with a Thunderbolt Display 27". After upgrading to 10.9.3, a GPU Panic error started annoying me. All displays (thunderbolt and mac) go black and I have to hold down the power button to force the shutdown and then power on.
Sometimes, I connect the display and it works for some days. Sometimes, it crashes just when I connect the thunderbolt display. It's just not what we expect from such premium product.
I've read the posts similar to this, did a PRAM reset, etc, but none of this worked for me. Any ideas?
This is the last crash log I had today. Please anybody help me! Thanks.
Anonymous UUID: D1494D64-F53F-A329-4592-C68AA7584D9C
Sat May 31 19:20:13 2014
panic(cpu 4 caller 0xffffff7fac421f7c): "GPU Panic: [<None>] 4 0 a0 d9 9 8 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0x112c00000 0xffffff814c058000 0x0e7150a2, D0, P1/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.5.26/src/Apple MuxControl/kext/GPUPanic.cpp:127
Backtrace (CPU 4), Frame : Return Address
0xffffff8135a1b530 : 0xffffff802a622fa9
0xffffff8135a1b5b0 : 0xffffff7fac421f7c
0xffffff8135a1b680 : 0xffffff7fac577bf4
0xffffff8135a1b740 : 0xffffff7fac641eaa
0xffffff8135a1b780 : 0xffffff7fac641f1a
0xffffff8135a1b7f0 : 0xffffff7fac86a9e2
0xffffff8135a1b860 : 0xffffff7fac664985
0xffffff8135a1b880 : 0xffffff7fac57e6ad
0xffffff8135a1b930 : 0xffffff7fac57c1b8
0xffffff8135a1bb30 : 0xffffff7fac57d258
0xffffff8135a1bc10 : 0xffffff7fac52b601
0xffffff8135a1bdb0 : 0xffffff7fac52a26a
0xffffff8135a1bdd0 : 0xffffff7fac3f3812
0xffffff8135a1beb0 : 0xffffff7fac3f36ee
0xffffff8135a1bf00 : 0xffffff7fac3f255e
0xffffff8135a1bf20 : 0xffffff802a64a23a
0xffffff8135a1bfb0 : 0xffffff802a6d7127
Kernel Extensions in backtrace:
com.apple.driver.AppleMuxControl(3.5.26)[B67CD59F-1344-37BC-8A9A-46D6D3DCA13D]@ 0xffffff7fac413000->0xffffff7fac426fff
dependency: com.apple.driver.AppleGraphicsControl(3.5.26)[C0F9A79F-167E-3A68-873C-5CE17B97F B11]@0xffffff7fac40b000
dependency: com.apple.iokit.IOACPIFamily(1.4)[045D5D6F-AD1E-36DB-A249-A346E2B48E54]@0xfffff f7fab45b000
dependency: com.apple.iokit.IOPCIFamily(2.9)[244D4E48-78E6-3369-8D76-285C66EF9BF4]@0xffffff 7faacbe000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[B889D3AB-CCC0-3FCD-A83E-D2E3E4CB537B]@0 xffffff7fab514000
dependency: com.apple.driver.AppleBacklightExpert(1.0.4)[E04639C5-D734-3AB3-A682-FE66694C66 53]@0xffffff7fac40e000
com.apple.driver.AGPM(100.14.15)[BD884E30-94CF-3D5B-9A31-6C2F694CD5C4]@0xffffff 7fac3f1000->0xffffff7fac402fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[244D4E48-78E6-3369-8D76-285C66EF9BF4]@0xffffff 7faacbe000
dependency: com.apple.driver.IOPlatformPluginFamily(5.7.0d11)[F6325632-ED32-3679-9DB4-C5BD0 9717674]@0xffffff7fab464000
dependency: com.apple.iokit.IONDRVSupport(2.4.1)[B93BBFC9-9ED5-3DDD-8CED-5EDA081BB997]@0xff ffff7fab557000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[B889D3AB-CCC0-3FCD-A83E-D2E3E4CB537B]@0 xffffff7fab514000
dependency: com.apple.AppleGraphicsDeviceControl(3.5.26)[E971FED4-805F-3462-9D93-1919EBE3DC 82]@0xffffff7fac0d5000
com.apple.nvidia.driver.NVDAResman(8.2.6)[DB59C243-61DE-3B0C-86C3-6D89446F6F14] @0xffffff7fac527000->0xffffff7fac799fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[244D4E48-78E6-3369-8D76-285C66EF9BF4]@0xffffff 7faacbe000
dependency: com.apple.iokit.IONDRVSupport(2.4.1)[B93BBFC9-9ED5-3DDD-8CED-5EDA081BB997]@0xff ffff7fab557000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[B889D3AB-CCC0-3FCD-A83E-D2E3E4CB537B]@0 xffffff7fab514000
dependency: com.apple.AppleGraphicsDeviceControl(3.5.26)[E971FED4-805F-3462-9D93-1919EBE3DC 82]@0xffffff7fac0d5000
com.apple.nvidia.driver.NVDAGK100Hal(8.2.6)[AE5D65B5-1E26-3509-97B9-C68D97C2114 3]@0xffffff7fac79a000->0xffffff7fac946fff
dependency: com.apple.nvidia.driver.NVDAResman(8.2.6)[DB59C243-61DE-3B0C-86C3-6D89446F6F14] @0xffffff7fac527000
dependency: com.apple.iokit.IOPCIFamily(2.9)[244D4E48-78E6-3369-8D76-285C66EF9BF4]@0xffffff 7faacbe000
BSD process name corresponding to current thread: kernel_task
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: 0x000000002a400000
Kernel text base: 0xffffff802a600000
System model name: MacBookPro10,1 (Mac-C3EC7CD22292981F)
System uptime in nanoseconds: 21441224134
last loaded kext at 16902757158: com.apple.driver.AppleBluetoothMultitouch 80.14 (addr 0xffffff7fac44d000, size 77824)
loaded kexts:
com.InnovationTechnology.driver.ComputerAudio 1.01
com.apple.driver.AppleBluetoothMultitouch 80.14
com.apple.driver.AppleGraphicsDevicePolicy 3.5.26
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.filesystems.autofs 3.0
com.apple.GeForce 8.2.6
com.apple.iokit.IOBluetoothSerialManager 4.2.4f1
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AGPM 100.14.15
com.apple.driver.ApplePlatformEnabler 2.0.9d1
com.apple.driver.X86PlatformShim 1.0.0
com.apple.driver.AppleUpstreamUserClient 3.5.13
com.apple.nvidia.NVDAStartup 8.2.6
com.apple.driver.AppleHDAHardwareConfigDriver 2.6.1f2
com.apple.driver.AppleHDA 2.6.1f2
com.apple.driver.AppleMikeyDriver 2.6.1f2
com.apple.driver.AudioAUUC 1.60
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.iokit.IOBluetoothUSBDFU 4.2.4f1
com.apple.driver.AppleIntelHD4000Graphics 8.2.6
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.2.4f1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleIntelFramebufferCapri 8.2.6
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.driver.AppleSMCLMU 2.0.4d1
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleIntelMCEReporter 104
com.apple.driver.AppleLPC 1.7.0
com.apple.driver.AppleMuxControl 3.5.26
com.apple.driver.AppleBacklight 170.3.5
com.apple.driver.AppleMCCSControl 1.1.12
com.apple.driver.AppleThunderboltIP 1.1.2
com.apple.driver.AppleUSBTCButtons 240.2
com.apple.driver.AppleUSBTCKeyEventDriver 240.2
com.apple.driver.AppleUSBTCKeyboard 240.2
com.apple.driver.AppleFileSystemDriver 3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.5.1
com.apple.driver.AppleSDXC 1.5.2
com.apple.iokit.AppleBCM5701Ethernet 3.8.1b2
com.apple.driver.AppleUSBHub 666.4.0
com.apple.driver.AirPort.Brcm4331 700.20.22
com.apple.driver.AppleAHCIPort 3.0.0
com.apple.driver.AppleUSBEHCI 660.4.0
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.driver.AppleIntelCPUPowerManagementClient 217.92.1
com.apple.nke.applicationfirewall 153
com.apple.security.quarantine 3
com.apple.driver.AppleIntelCPUPowerManagement 217.92.1
com.apple.driver.AppleMultitouchDriver 245.13
com.apple.driver.AppleBluetoothHIDKeyboard 170.15
com.apple.driver.IOBluetoothHIDDriver 4.2.4f1
com.apple.driver.AppleHIDKeyboard 170.15
com.apple.kext.triggers 1.0
com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.6
com.apple.iokit.IOAcceleratorFamily 98.20
com.apple.nvidia.driver.NVDAGK100Hal 8.2.6
com.apple.nvidia.driver.NVDAResman 8.2.6
com.apple.iokit.IOSerialFamily 10.0.7
com.apple.driver.DspFuncLib 2.6.1f2
com.apple.vecLib.kext 1.0.0
com.apple.iokit.IOSurface 91.1
com.apple.iokit.IOBluetoothFamily 4.2.4f1
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.2.4f1
com.apple.driver.X86PlatformPlugin 1.0.0
com.apple.iokit.IOAcceleratorFamily2 98.20
com.apple.AppleGraphicsDeviceControl 3.5.26
com.apple.driver.AppleHDAController 2.6.1f2
com.apple.iokit.IOHDAFamily 2.6.1f2
com.apple.driver.AppleSMC 3.1.8
com.apple.iokit.IOAudioFamily 1.9.7fc2
com.apple.kext.OSvKernDSPLib 1.14
com.apple.driver.IOPlatformPluginFamily 5.7.0d11
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.AppleSMBusPCI 1.0.12d1
com.apple.driver.AppleThunderboltEDMSink 2.1.3
com.apple.driver.AppleThunderboltDPOutAdapter 3.1.7
com.apple.driver.AppleUSBMultitouch 240.9
com.apple.iokit.IOUSBHIDDriver 660.4.0
com.apple.driver.AppleUSBMergeNub 650.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.AppleThunderboltPCIUpAdapter 1.4.5
com.apple.driver.AppleThunderboltPCIDownAdapter 1.4.5
com.apple.driver.AppleThunderboltNHI 2.0.1
com.apple.iokit.IOThunderboltFamily 3.2.7
com.apple.iokit.IOEthernetAVBController 1.0.3b4
com.apple.driver.mDNSOffloadUserClient 1.0.1b5
com.apple.iokit.IO80211Family 630.35
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOUSBUserClient 660.4.2
com.apple.iokit.IOAHCIFamily 2.6.5
com.apple.iokit.IOUSBFamily 677.4.0
com.apple.driver.AppleEFINVRAM 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.driver.AppleEFIRuntime 2.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: MacBookPro10,1, BootROM MBP101.00EE.B02, 4 processors, Intel Core i7, 2.6 GHz, 8 GB, SMC 2.3f36
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In
Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533642465238432D50422020
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533642465238432D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xEF), Broadcom BCM43xx 1.0 (5.106.98.100.22)
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 SM512E, 500,28 GB
USB Device: Hub
USB Device: FaceTime HD Camera (Built-in)
USB Device: Hub
USB Device: Hub
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Apple Internal Keyboard / Trackpad
Thunderbolt Bus: MacBook Pro, Apple Inc., 23.4Third party software / hardware is often the cause of kernel panics.
com.InnovationTechnology.driver.ComputerAudio < from your report
Visit the the website for uninstall instructions. It may not be compatible with 10.9.3. -
Driver for Facetime Camera on Thunderbolt Display - Win 7 in Bootcamp
I have a Thunderbolt display working just fine on a Windows 7 installation using bootcamp on my Mid 2012 Macbook Pro Retina - except the driver for the facetime camera on the display is not installed. The facetime camera on the Macbook Pro did install. The bootcamp driver folder on my USB stick created for the install does not seem to include a driver for this. I have already done a bootcamp driver package reinstall to no avail. Has anyone gotten this working? Can you give me the driver details and how you did it if so?
Thanks.
gregNow it has gotten worse. I wish I had documented what I had done, but I think it was after I ran some addtional updates. Can't remember if it was the Office updates or the addtional Win7 updates.
But now besides the error message when I try to open my virtual machine in Parallels (which I got both before & after running Bootcamp updates), now 2x at least it did not boot into bootcamp but instead showed that there were problems & the fix screen came up. Again.
I did manage to run the Windows backup on my new WD Passport partitioned back up drive w about 50 GB formatted for Windows & the rest of it for Mac so I can use it w Time Machine.
It backed up files in libaries & personal folders for all users 1.86 GB
But I'm hesitant to go ahead & upgrade Parallels 5 to 8 w the purchased update to download & run as well as doing the upgrade Mountain Lion. It does not seem wise to install new or additional software on top of an unstable Windows/Bootcamp set up.
So wondering my options. I'm guessing that the solution to an unstable Windows OS would be to reinstall it as a clean install. But then the normal thing to do would be to run the updates which took a long time the other day & then messed things up so the track pad wasn't tracking well. Before later causing it to crash.
Just got word from Parallels suggesting a claen install into Bootcamp.
But also considering just installing it as a new virtual machine in Parallels & dispensing w Bootcamp.
I hope this makes some sense. I'm very tired but want to put these questions out there so when I get back to it, hopefully there will be some suggestions/recommendations.
Thanks. -
Thunderbolt display: devices not discovered after using Mini DisplayPort–to–VGA adapter
I have an interested problem related to using my MacBook Air in clamshell (closed) mode, connected to a Thunderbolt display. The problem appears to be related to moving my MacBook air between my office and my home.
At the office, I use the MacBook Air with an external VGA display, connected via the Mini DisplayPort–to–VGA adapter. At home, I use the MacBook Air together with a Thunderbolt display. An Apple USB keyboard is also connected to the display.
Mini DisplayPort–to–VGA adapter implicated
The following sequence of events causes the problem to occur:
Use the MacBook air (open) together with a VGA display, connected via a Mini DisplayPort–to–VGA adapter (depicted at right);
Put the MacBook Air to sleep by closing the lid, and disconnect the Mini DisplayPort–to–VGA adapter (I am not sure if the order of these two steps is significant—I usually perform them almost simultaneously when packing up my MacBook Air and getting ready to leave the office); and
With the MacBook Air still closed, connect it to a Thunderbolt display with a connected USB keyboard.
At this point, I would expect to be able to wake up the MacBook Air by tapping on the space bar of the keyboard. However, what I have observed is that this does not wake the MacBook Air.
I can wake the MacBook however by moving or clicking a Bluetooth mouse that is paired with the MacBook Air.
At this point, although the MacBook Air is awake, and the display is working, the USB keyboard connected to the display still does not work. This is the problem, in a nutshell.
Unplugging the USB keyboard from the display, and plugging it back in causes the MacBook Air properly to identify the keyboard.
I used Apple System Profiler to save a list of identified devices at two points in time:
Immediately after waking the MacBook Air by moving the Bluetooth mouse (at which point the USB keyboard was not working); and
After unplugging and plugging in again the USB keyboard (at which point the USB keyboard worked fine).
Many devices are enumerated in the second list that are missing from the first. For example:
Keyboard Hub@fe110000 <class IOUSBHubDevice, id 0x1000378ef, !registered, !matched, inactive, busy 3 (37993 ms), retain 6>
AppleUSBHub <class AppleUSBHub, id 0x1000378f2, !registered, !matched, inactive, busy 1 (37987 ms), retain 6>
IOUSBInterface@0 <class IOUSBInterface, id 0x1000378f4, !registered, !matched, inactive, busy 1 (37986 ms), retain 6>
Keyboard Hub@fe110000 <class IOUSBHubDevice, id 0x1000378f6, registered, matched, active, busy 0 (7 ms), retain 10>
AppleUSBHub <class AppleUSBHub, id 0x1000378f9, registered, matched, active, busy 0 (1 ms), retain 9>
IOUSBInterface@0 <class IOUSBInterface, id 0x1000378fb, !registered, !matched, active, busy 0, retain 7>
Apple Keyboard@fe112000 <class IOUSBDevice, id 0x1000378fd, registered, matched, active, busy 0 (112 ms), retain 11>
and many child devices…
Using the Mini DisplayPort–to–VGA adapter appears to be a necessary step to causing this problem to occur. If I merely disconnect the MacBook Air from the display, let it go to sleep, and then reconnect it again, the USB keyboard will work immediately and can be used to wake the computer from sleep.
Some devices are discovered even when the computer is in sleep mode. This is how it should work.
The problem appears to be that when a Mini DisplayPort–to–VGA adapter has been used since the last time the computer was connected to a Thunderbolt display, the MacBook air does not discover devices completely when it is again connected to the Thunderbolt display while in sleep mode.
Can anyone else reproduce this problem?Hi glraczon.support,
It sounds like the external display you are using (projector) operates at a smaller resolution than your MacBook Pro. You may want to configure the display preferences in System Preferences for the external projector.
Here is an article that may help you with that process:
OS X Mountain Lion: About the Display pane of System Preferences
http://support.apple.com/kb/HT5369
Thanks,
Matt M. -
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?
Maybe you are looking for
-
hi just bought my first Mac Mini, and am considering getting an Apple monitor. I see Apple has a Thunderbolt Display and an LED Cinema Display, they cost the same, and I'm wondering which would be a better bet for the Mini. I do have a non-Apple moni
-
Transfer of Outlook express address book to PC
I have a new computer and want to transfer the addresses stored in my blackberry to my computer... Can someone walk me through the process?
-
Unplugged iPhone5 and MacBook Pro won't turn on
Downloading Indesign using hotspot from my iPhone 5 unplugged it and the computer shut off shortly after, plugged in power no response. Note I was at 74% my phone was at 16% all I did was unplug my phone and black it goes. It say 2010 on the back tri
-
hello I would like to change my type of subscription (adobe reader) to improve to get a higher level. Should I cancel the first one and then take another one ? thks cecile
-
I want the user to view all other schema
hi all i have a project with 5 modules(GL, AP, AR, OM, PO) and each module has its own schema (tables,pkgs,views,.................) and i want to create a new user(test) that don't have any objects , i create it only to connect on forms by it and i w