Switch from "Dynamic" to "Discrete". If that doesn't work, switch to "Integrated". See if that helps...
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Lion randomly crashing..?
- Thread starter garry12
- Start date
- Sort by reaction score
Switch from "Dynamic" to "Discrete". If that doesn't work, switch to "Integrated". See if that helps...
I wish that was the case, mine is clearly failing due to Time Machine (mainly spotlight running in that bundle). I really need to verify if it is stemming from the network issues folks are talking about or not.
For those having the black screen crashes--you are not alone:
https://discussions.apple.com/message/15677101#15677101
https://discussions.apple.com/message/15677101#15677101
I'm currently at 1 days uptime, i have installed Fan Control which is possibly helping albeit its strange to have the fan spinning up so much when all its running is Safari. Tend to think its possibly hardware related which has been exposed by the Lion install.
Started in SL
The scary thing is that my problems started happening during Snow Leopard (10.6.8? or whatever the latest one was). I really hope it's not a hardware issue or else my Macbook Pro is an oversized and overweight Macbook Air. Staying with the Intel chip seems to help.
The scary thing is that my problems started happening during Snow Leopard (10.6.8? or whatever the latest one was). I really hope it's not a hardware issue or else my Macbook Pro is an oversized and overweight Macbook Air. Staying with the Intel chip seems to help.
So I went to the Apple Store and long story short, they replaced my logic board and erased the hard drive (which was unexpected) and installed SL 10.6.8 on it. They claimed it was good and ready and ran with no problems. Brought it home and ran a bunch of stuff on it, reinstalled Lion and it seemed ok for a while. UNTIL I installed Dropbox and The Hit List. It crashed with the black screen problem two times in a row! I'm completely at a loss as to what is happening. I do have 8 gigs of ram running that I purchased from a third party vendor. I am wondering if that is contributing to the problem. Seems to me that the crashes might be happening under heavy video load. BTW, before replacing the logic board, I tried limiting the video to the intel chip vs the nvidia chip and it made no difference.
Last edited:
Yeah mine is definitely an issue with Time Machine. No clue why though.
Code:
Sat Jul 30 06:39:22 2011
panic(cpu 1 caller 0xffffff80004dbfae): "hfs_vnop_reclaim: vp points to wrong cnode (vp=0xffffff8018d68ba0 cp->c_vp=0xffffff8018d683a0 cp->c_rsrc_vp=0)\n"@/SourceCache/xnu/xnu-1699.22.73/bsd/hfs/hfs_cnode.c:739
Backtrace (CPU 1), Frame : Return Address
0xffffff80f394b660 : 0xffffff8000220702
0xffffff80f394b6e0 : 0xffffff80004dbfae
0xffffff80f394b720 : 0xffffff8000316bfc
0xffffff80f394b750 : 0xffffff80002fd31d
0xffffff80f394b7a0 : 0xffffff80002fce9e
0xffffff80f394b7e0 : 0xffffff80002ff296
0xffffff80f394b870 : 0xffffff80004db54c
0xffffff80f394b960 : 0xffffff80004ef75d
0xffffff80f394bb20 : 0xffffff80005018bb
0xffffff80f394bb50 : 0xffffff80004d233f
0xffffff80f394bc00 : 0xffffff80004d158a
0xffffff80f394be10 : 0xffffff8000316b83
0xffffff80f394be70 : 0xffffff8000303a2c
0xffffff80f394bf50 : 0xffffff80005ca7cb
0xffffff80f394bfb0 : 0xffffff80002d8383
BSD process name corresponding to current thread: backupd
Mac OS version:
11A511
Kernel version:
Darwin Kernel Version 11.0.0: Sat Jun 18 12:56:35 PDT 2011; root:xnu-1699.22.73~1/RELEASE_X86_64
Kernel UUID: 24CC17EB-30B0-3F6C-907F-1A9B2057AF78
System model name: MacBookPro6,2 (Mac-F22586C8)
System uptime in nanoseconds: 6483252949930
last loaded kext at 4970987851576: com.apple.iokit.IOAVBFamily 1.0.0d22 (addr 0xffffff7f8078d000, size 36864)
last unloaded kext at 5030994983776: com.apple.iokit.IOAVBFamily 1.0.0d22 (addr 0xffffff7f8078d000, size 36864)
loaded kexts:
com.apple.filesystems.afpfs 9.8
com.apple.nke.asp_tcp 6.0.1
com.apple.driver.Oxford_Semi 3.0.0
com.apple.driver.AppleHWSensor 1.9.4d0
com.apple.filesystems.autofs 3.0
com.apple.driver.AppleMikeyHIDDriver 122
com.apple.driver.AppleSMCLMU 2.0.1d2
com.apple.driver.AppleMikeyDriver 2.1.1f11
com.apple.driver.AGPM 100.12.40
com.apple.driver.AppleHDA 2.1.1f11
com.apple.driver.AudioAUUC 1.59
com.apple.driver.AppleUpstreamUserClient 3.5.9
com.apple.driver.AppleMCCSControl 1.0.24
com.apple.driver.AppleIntelHDGraphics 7.0.2
com.apple.driver.AppleIntelHDGraphicsFB 7.0.2
com.apple.driver.SMCMotionSensor 3.0.1d2
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AudioIPCDriver 1.2.0
com.apple.driver.ACPI_SMC_PlatformPlugin 4.7.0b2
com.apple.driver.AppleMuxControl 3.0.8
com.apple.driver.AppleLPC 1.5.1
com.apple.GeForce 7.0.2
com.apple.driver.AppleUSBTCButtons 220.8
com.apple.driver.AppleIRController 309
com.apple.driver.AppleUSBCardReader 3.0.0
com.apple.driver.AppleUSBTCKeyboard 220.8
com.apple.iokit.SCSITaskUserClient 3.0.0
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 32
com.apple.driver.AirPort.Brcm4331 500.20.6
com.apple.iokit.IOAHCIBlockStorage 2.0.0
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleUSBHub 4.4.0
com.apple.driver.AppleFWOHCI 4.8.6
com.apple.iokit.AppleBCM5701Ethernet 3.0.6b9
com.apple.driver.AppleEFINVRAM 1.5.0
com.apple.driver.AppleUSBEHCI 4.4.0
com.apple.driver.AppleACPIButtons 1.4
com.apple.driver.AppleAHCIPort 2.1.8
com.apple.driver.AppleRTC 1.4
com.apple.driver.AppleHPET 1.6
com.apple.driver.AppleSMBIOS 1.7
com.apple.driver.AppleACPIEC 1.4
com.apple.driver.AppleAPIC 1.5
com.apple.driver.AppleIntelCPUPowerManagementClient 166.0.0
com.apple.nke.applicationfirewall 3.0.30
com.apple.security.quarantine 1
com.apple.driver.AppleIntelCPUPowerManagement 166.0.0
com.apple.security.SecureRemotePassword 1.0
com.apple.iokit.IOFireWireSerialBusProtocolTransport 2.1.0
com.apple.iokit.IOFireWireSBP2 4.2.0
com.apple.kext.triggers 1.0
com.apple.driver.DspFuncLib 2.1.1f11
com.apple.driver.AppleSMBusController 1.0.10d0
com.apple.iokit.IOSurface 80.0
com.apple.iokit.IOBluetoothSerialManager 2.5f17
com.apple.iokit.IOSerialFamily 10.0.5
com.apple.iokit.IOFireWireIP 2.2.3
com.apple.iokit.IOAudioFamily 1.8.3fc11
com.apple.kext.OSvKernDSPLib 1.3
com.apple.driver.AppleHDAController 2.1.1f11
com.apple.iokit.IOHDAFamily 2.1.1f11
com.apple.driver.AppleSMC 3.1.1d2
com.apple.driver.IOPlatformPluginFamily 4.7.0b2
com.apple.driver.AppleGraphicsControl 3.0.8
com.apple.driver.AppleSMBusPCI 1.0.10d0
com.apple.driver.AppleBacklightExpert 1.0.3
com.apple.nvidia.nv50hal 7.0.2
com.apple.NVDAResman 7.0.2
com.apple.iokit.IONDRVSupport 2.3
com.apple.iokit.IOGraphicsFamily 2.3
com.apple.driver.BroadcomUSBBluetoothHCIController 2.5f17
com.apple.driver.AppleUSBBluetoothHCIController 2.5f17
com.apple.iokit.IOBluetoothFamily 2.5f17
com.apple.iokit.IOSCSIBlockCommandsDevice 3.0.0
com.apple.iokit.IOUSBMassStorageClass 3.0.0
com.apple.driver.AppleUSBMultitouch 220.23
com.apple.iokit.IOUSBHIDDriver 4.4.0
com.apple.driver.AppleUSBMergeNub 4.4.0
com.apple.driver.AppleUSBComposite 3.9.0
com.apple.driver.CoreStorage 180
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.0.0
com.apple.iokit.IOBDStorageFamily 1.6
com.apple.iokit.IODVDStorageFamily 1.6
com.apple.iokit.IOCDStorageFamily 1.7
com.apple.iokit.IO80211Family 400.40
com.apple.driver.XsanFilter 403
com.apple.iokit.IOAHCISerialATAPI 2.0.0
com.apple.iokit.IOSCSIArchitectureModelFamily 3.0.0
com.apple.iokit.IOUSBUserClient 4.4.0
com.apple.iokit.IOFireWireFamily 4.4.3
com.apple.iokit.IOEthernetAVBController 1.0.0d5
com.apple.iokit.IONetworkingFamily 2.0
com.apple.driver.AppleEFIRuntime 1.5.0
com.apple.iokit.IOHIDFamily 1.7.0
com.apple.iokit.IOAHCIFamily 2.0.6
com.apple.iokit.IOUSBFamily 4.4.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 165
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.DiskImages 326
com.apple.iokit.IOStorageFamily 1.7
com.apple.driver.AppleKeyStore 28.18
com.apple.driver.AppleACPIPlatform 1.4
com.apple.iokit.IOPCIFamily 2.6.5
com.apple.iokit.IOACPIFamily 1.4Clean Install Helped?
Well last Friday i wiped out my MacHD partition which had an upgrade from SL 10.6.8 and installed a clean copy of Lion in its place.
So far not one black screen and temps appear to be much reduced, still testing though but it seems promising!
Well last Friday i wiped out my MacHD partition which had an upgrade from SL 10.6.8 and installed a clean copy of Lion in its place.
So far not one black screen and temps appear to be much reduced, still testing though but it seems promising!
You've hit the nail on the head here. I started having Kernel Panic and random reboots after updating Snow Leopard from 10.6.7 to 10.6.8 and even on a fresh install of Lion I'm getting the same kernel panics. If I roll back to 10.6.7 (using TimeMachine or fresh install of 10.6 and then download and install the 10.6.7 combo updater) then it's back to normal and stable, as soon as I put 10.6.8 or Lion over the top it's back to regular Kernel Panics.
I've opened a case with http://bugreport.apple.com and they asked for my KP logs and System Profile and then I've heard nothing. I hoped that the latest Lion update would fix it but that didn't.
Note - this is on my MacPro 1,1 which I have upgraded to 2xquad core E5345 XEONs. I thought it might be my Nvidia 7300GT GPU so I took that out and bought a new ATI 5770 but it still happens. I think it's either RAID related or just a stupid bug.
Some people have suggested it's to do with the the CPUs overheating but if i monitor the CORE temps and then stress test the CPUs then all 8 cores will max out and the temps never go above 70ºC which is very safe for the E5345. Funny thing is, I can boot into Lion, stress test the CPUs all at 100% for 5 hours and not have a kernel panic, then I can fresh boot, only open safari and have kernel panic in 2 minutes.
As a side note, others have reported a program called Little Snitch can cause kernel panics and crashing in Lion and there was a new version released this week to fix this, but I've never installed little snitch and a fresh untouched Lion install crashes.
You can see my Kernel Panic logs and more info/updates here
http://blog.scoopz.com/2011/08/04/a...d-lion-10-7-cause-kernel-panics-on-macpro-11/
I am suffering from the same issue as everyone else. I installed the gfx utility to control the mode my graphics card was in, but it didn't solve it, just reduced the freezes/restarts to a few times a day.
I called Apple Express Lane and they had me reset the system controller, zap the pram, verify and repair the disk and disk permissions, and finally, reinstall lion. The issue persisted.
I took it into the Apple store today and they offered to take it in and replace the logic board after some testing. "Some testing" was an unknown amount of time.
They were not willing to consider this forum or the apple forum as a source of information into the problem, but they felt that it was in fact a hardware issue and not software (but they did say they still needed to test it).
I intended to talk my way into a new laptop due to me having purchased AppleCare as well as having purchased $50,000+ worth of hardware (for work) through that very store. They were unwilling to do that.
They did, however, give me a credit for the value of the repair (Which was ~$530) toward the purchase of a new Macbook Air. I went with this option. The good news is that they let me keep the old laptop.
I think it's clear to everyone that this is in fact a hardware issue. It is something that can be corrected in software, by simply finding a way to not call whatever kernel function that is responsible for the kernel panic. It might not be the most effecient workaround but I'd personally rather have a slower render (temporarily) than a freeze/restart that results in data loss.
Everyone who is reading this and is experiencing this problem should write a reply so that Apple works through this issue. They can fix it or they can work with the vendor (nvidia) to work through it.
I called Apple Express Lane and they had me reset the system controller, zap the pram, verify and repair the disk and disk permissions, and finally, reinstall lion. The issue persisted.
I took it into the Apple store today and they offered to take it in and replace the logic board after some testing. "Some testing" was an unknown amount of time.
They were not willing to consider this forum or the apple forum as a source of information into the problem, but they felt that it was in fact a hardware issue and not software (but they did say they still needed to test it).
I intended to talk my way into a new laptop due to me having purchased AppleCare as well as having purchased $50,000+ worth of hardware (for work) through that very store. They were unwilling to do that.
They did, however, give me a credit for the value of the repair (Which was ~$530) toward the purchase of a new Macbook Air. I went with this option. The good news is that they let me keep the old laptop.
I think it's clear to everyone that this is in fact a hardware issue. It is something that can be corrected in software, by simply finding a way to not call whatever kernel function that is responsible for the kernel panic. It might not be the most effecient workaround but I'd personally rather have a slower render (temporarily) than a freeze/restart that results in data loss.
Everyone who is reading this and is experiencing this problem should write a reply so that Apple works through this issue. They can fix it or they can work with the vendor (nvidia) to work through it.
Someone please try to answer my simple question without all of the distracting side comments that are likely to come despite my plea...
How in the world can this be a "hardware" issue when the problem comes up only after upgrading to Lion (a software change), and reverting to Snow Leopard eliminates the problem??
Someone please try to answer my simple question without all of the distracting side comments that are likely to come despite my plea...
How in the world can this be a "hardware" issue when the problem comes up only after upgrading to Lion (a software change), and reverting to Snow Leopard eliminates the problem??
The short answer to this question is that Apple introduced new functionality in the 10.7 kernel and the function calls that the drivers are making are being handled by this new functionality. The code they introduced in 10.7 probably exposes previously unused functionality in the hardware that is now being called, thus triggering the kernel panic (which is fatal and tells the system to halt). This problem could be solved by nVidia by simply updating their drivers not to call into the function(s) that trigger the panic, or by Apple to handle the call nVidia is making in a different manner.
The key thing everyone should be doing is sending the problem reports to Apple. They see the information that tells them what triggered the event. When they start to see a pattern, they'll re-act accordingly (hopefully).
In the Apple Discussion, linked previously in this thread, there's a link to a new article that references nVidia publicly stating that they had a QC problem during the timeframe our GPUs were made.
Sorry for the distraction, but all of this information is already in the thread if you take the time to dig deep enough and actually read the posts.
No, no. I read the whole thread, including all that you just said. (but thanks for the concise repeat)
Maybe we are speaking different languages here ... but everything you just said tells me it is a software problem. Namely, the software is improperly calling out some hardware function.
You even suggested this when you were describing what needs to be done to fix it. If it was a hardware problem, then the proper fix would be to replace the hardware, not update drivers or change the way the OS interacts with the GPU.
Last edited:
The fixes I mentioned are just approaches to working around the problem. The calls that the drivers are making to the kernel are good calls; And the calls the kernel is making to the hardware are also good calls. The hardware is faulty and whatever functionality the kernel is asking it to perform is bad. The response the kernel gets from the HW is what triggers the panic.
By not making the calls, they don't trigger the panic. This is what happened between 10.6 and 10.7; 10.6 wasn't making those calls and 10.7 is. Whatever functionality the GPU offers that is not working _should_ be working.
Oh, Ok. I get what you are saying.
I suppose that my thoughts are from the perspective of the average user, not the OS engineer. If it works with Snow Leopard, but not with Lion, it seems obvious that the problem is software. And also (again from the "average user's" point of view), if it can be "fixed" with a driver update or OS update, this again seems to indicate a software problem.
But I do see what you are saying that the engineers have written good code that the GPU should be able to handle, but can't.
Either way, if Apple doesn't provide a software fix, I have a computer that is unreliable ... which defeats the purpose of me being an Apple customer in the first place.
Same problem
I have the same problem with a Mac Book Pro 2010 i7 8 GB
I keep it "alive" by using gfxCardStatus to stop the switch over the nvida graphics which directly results in a black screen of death
There is a long thread on https://discussions.apple.com/message/15665312#15665312 but so far no solution only ways to prevent it to happen
I was very happy when Lion was released but this problem is a bit sad
I have the same problem with a Mac Book Pro 2010 i7 8 GB
I keep it "alive" by using gfxCardStatus to stop the switch over the nvida graphics which directly results in a black screen of death
There is a long thread on https://discussions.apple.com/message/15665312#15665312 but so far no solution only ways to prevent it to happen
I was very happy when Lion was released but this problem is a bit sad
Lion freeze on MBP 2010
have you guys tried this...
This is a common problem on mid 2010 MacBook Pros. Its a problem with the graphics chips switching causing the freeze esp on login. The fix or workaround (for the moment) is to switch off "automatic graphics switching" (AGS) in the energy saver pref pane, and enable auto login to bypass the login freeze. your machine will be much more stable after that, but battery life will suffer. Hope 10.7.2 fixes this.
see this thread...
https://discussions.apple.com/thread...art=0&tstart=0
have you guys tried this...
This is a common problem on mid 2010 MacBook Pros. Its a problem with the graphics chips switching causing the freeze esp on login. The fix or workaround (for the moment) is to switch off "automatic graphics switching" (AGS) in the energy saver pref pane, and enable auto login to bypass the login freeze. your machine will be much more stable after that, but battery life will suffer. Hope 10.7.2 fixes this.
see this thread...
https://discussions.apple.com/thread...art=0&tstart=0
Crashing happens with 2011 MBP too
Hi all,
Reading through the postings, I figured you might be interested to know in my personal experience with this problem.
I have a MacBook Pro 13 inch, early 2011 model. Unlike previous users, I have only noticed the crash while using Flash player with an external monitor. I normally connect the computer to one of two external monitors -- one at work and one at home. The one at home is a 20" Acer with max res of 1600x900. The one at home is a 23" ASUS monitor with 1920x1080. So far my computer has crashed only while using the ASUS monitor at home, but I watch more streaming content at home than at work so it could just be that. In any case I get the same thing -- external monitor screen goes totally black and when I disconnect it, the laptop screen is black and the computer cannot be awoken. Hard shutdown and restart necessary.
I had the ASUS before I upgraded to Lion, and did not notice a single crash while running Snow Leopard. So I am inclined to believe this is a software problem.
Many of you mentioned that the gfx thing worked ok, but here's the thing: my newer Mac does not have an NVIDIA graphics card. It has the Intel HD integrated graphics. This fact makes it even more convincing to me that this is an Apple software issue, not a hardware or 3rd party software issue.
This seems like a problem with how Lion handles high quality streaming content from Flash and its own integrated video hardware at high resolution. Another interesting side note: my computer has never crashed while using Netflix's online streaming, even in HD. So at least for me it looks like a Flash-Lion integration issue.
I am not a developer or computer scientist, so let me know if anything I said is blatantly false.
Thanks!
-Kevin
Hi all,
Reading through the postings, I figured you might be interested to know in my personal experience with this problem.
I have a MacBook Pro 13 inch, early 2011 model. Unlike previous users, I have only noticed the crash while using Flash player with an external monitor. I normally connect the computer to one of two external monitors -- one at work and one at home. The one at home is a 20" Acer with max res of 1600x900. The one at home is a 23" ASUS monitor with 1920x1080. So far my computer has crashed only while using the ASUS monitor at home, but I watch more streaming content at home than at work so it could just be that. In any case I get the same thing -- external monitor screen goes totally black and when I disconnect it, the laptop screen is black and the computer cannot be awoken. Hard shutdown and restart necessary.
I had the ASUS before I upgraded to Lion, and did not notice a single crash while running Snow Leopard. So I am inclined to believe this is a software problem.
Many of you mentioned that the gfx thing worked ok, but here's the thing: my newer Mac does not have an NVIDIA graphics card. It has the Intel HD integrated graphics. This fact makes it even more convincing to me that this is an Apple software issue, not a hardware or 3rd party software issue.
This seems like a problem with how Lion handles high quality streaming content from Flash and its own integrated video hardware at high resolution. Another interesting side note: my computer has never crashed while using Netflix's online streaming, even in HD. So at least for me it looks like a Flash-Lion integration issue.
I am not a developer or computer scientist, so let me know if anything I said is blatantly false.
Thanks!
-Kevin
Kevin, if it only happens with FLASH then it's Adobes fault, not Apples. Have you upgraded to FLASH 11 yet? If not get FLASH 11 and see if you have the same problem. FLASH always suck on Macs, just one of many reasons SJ doesn't like FLASH.
Hugh
I'm sorry if posting so much later has resurrected this thread unnecessarily, but I am also running a MBP Mid-2010 15" with the NVidia GeForce GT 330M 512 MB. I upgraded the ram to 8BG this weekend only to have the crashes occur as normal. This happens to me frequently if I am on Second Life, making any kinds of edits within Adobe Photoshop, or enabling a Skype video call. (edit: Oh yes, this also happens almost EVERY time I use Quicktime to play a video. I have to use VLC exclusively now.)
I took my machine into a local Apple Store and the genius told me that he could submit this as the TS4088 error, even though it didn't seem to be, which meant they would replace the entire logic board for ~$300 instead of ~$600. I'm still upset that I have to pay to fix something that has been caused by upgrading operating systems...
At any rate, looks likeI'll be without my machine for a week.
I took my machine into a local Apple Store and the genius told me that he could submit this as the TS4088 error, even though it didn't seem to be, which meant they would replace the entire logic board for ~$300 instead of ~$600. I'm still upset that I have to pay to fix something that has been caused by upgrading operating systems...
At any rate, looks likeI'll be without my machine for a week.
Last edited: