Skip navigation
This discussion is archived

Display freezing - NVChannel(GL): Graphics channel exception

65342 Views 427 Replies Latest reply: Oct 28, 2009 6:35 AM by ampamp19 RSS
  • ch-vox Calculating status...
    Michael Diehr wrote:
    I'm still having the problem, though less frequently, in 10.5.3.
    10.5.4 is out today, anyone able to test using that?


    unfortunately, even after updating to 10.5.4 I still have NVChannel exception :

    +Jul 1 08:46:34 MacBook-Pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0xd = GR: SW Notify Error+
    +Jul 1 08:46:34 MacBook-Pro kernel[0]: 0000000c+
    +Jul 1 08:46:34 MacBook-Pro kernel[0]: 00200000 00008297 0000047c 00000000+
    +Jul 1 08:46:34 MacBook-Pro kernel[0]: 00000486 00001224 00000001 00000003+
    +Jul 1 08:46:34 MacBook-Pro kernel[0]: 00000000 00000000 01bfe003+
    +Jul 1 08:46:34 MacBook-Pro kernel[0]: 0000000c+
    +Jul 1 08:46:34 MacBook-Pro kernel[0]: 00200000 00008297 0000047c 00000000+
    +Jul 1 08:46:34 MacBook-Pro kernel[0]: 00000486 00001224 00000001 00000003+
    +Jul 1 08:46:34 MacBook-Pro kernel[0]: 00000000 00000000 00000002+
    +Jul 1 08:46:47 MacBook-Pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0xd = GR: SW Notify Error+
    +Jul 1 08:46:47 MacBook-Pro kernel[0]: 0000000c+
    +Jul 1 08:46:47 MacBook-Pro kernel[0]: 00200000 00008297 0000047c 00000000+
    +Jul 1 08:46:47 MacBook-Pro kernel[0]: 00000486 00001224 00000001 00000003+
    +Jul 1 08:46:47 MacBook-Pro kernel[0]: 00000000 00000000 01bfe003+
    +Jul 1 08:46:47 MacBook-Pro kernel[0]: 0000000c+
    +Jul 1 08:46:47 MacBook-Pro kernel[0]: 00200000 00008297 0000047c 00000000+
    +Jul 1 08:46:47 MacBook-Pro kernel[0]: 00000486 00001224 00000001 00000003+
    +Jul 1 08:46:47 MacBook-Pro kernel[0]: 00000000 00000000 00000002+
    +Jul 1 08:46:59 MacBook-Pro kernel[0]: NVChannel(GL): Graphics channel timeout!+
    +Jul 1 08:47:29: --- last message repeated 2 times ---+
    +Jul 1 08:47:35 MacBook-Pro kernel[0]: NVChannel(GL): Graphics channel timeout!+
    +Jul 1 08:48:05: --- last message repeated 2 times ---+
    +Jul 1 08:48:12 MacBook-Pro kernel[0]: NVChannel(GL): Graphics channel timeout!+
    +Jul 1 08:48:35: --- last message repeated 2 times ---+
    +Jul 1 08:48:35 MacBook-Pro /usr/sbin/spindump[256]: process 151 is being monitored+
    +Jul 1 08:48:35 MacBook-Pro /usr/sbin/spindump[256]: process 151 is being no longer being monitored+
    +Jul 1 08:48:49 MacBook-Pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0xd = GR: SW Notify Error+
    +Jul 1 08:48:49 MacBook-Pro kernel[0]: 0000000c+
    +Jul 1 08:48:49 MacBook-Pro kernel[0]: 00200000 00008297 0000047c 00000000+
    +Jul 1 08:48:49 MacBook-Pro kernel[0]: 00000486 00001224 00000001 00000003+
    +Jul 1 08:48:49 MacBook-Pro kernel[0]: 00000000 00000000 00000002+
    +Jul 1 08:48:49 MacBook-Pro kernel[0]: 0000000c+
    +Jul 1 08:48:49 MacBook-Pro kernel[0]: 00200000 00008297 0000047c 00000000+
    +Jul 1 08:48:49 MacBook-Pro kernel[0]: 00000486 00001224 00000001 00000003+
    +Jul 1 08:48:49 MacBook-Pro kernel[0]: 00000000 00000000 00000002+
    +Jul 1 08:49:38 localhost kernel[0]: npvhash=4095+
    Macbook Pro 2,4 GHz, OS X 10.5.4
  • Martin Bergstrom Level 2 Level 2 (475 points)
    Is this when doing th Index Sheet in Quick Look?
    MacBook Pro 2,5 GHz (work) — G4 Quicksilver 867 MHz, Mac OS X (10.5.3)
  • ch-vox Level 1 Level 1 (0 points)
    Martin Bergstrom wrote:
    Is this when doing th Index Sheet in Quick Look?


    Quick Look is working. When I select every pictures (and movies) of a single folder, I can see picture one after the other, but when trying to see the Index Sheet, my Macbook Pro crashes immediately.

    I wonder if in my case this is not the mix of pictures and movies that is problematic.
    I'll try to separate different kind of files later to investigate.
    Macbook Pro 2,4 GHz, MacOS X 10.5.4
  • Darren 2007 Level 1 Level 1 (0 points)
    My wife hits this issue while editing photos in iPhoto. The same log everyone has been reporting shows up in console. It showed up with the same OSX update everyone else has been reporting.

    Jul 2 21:20:47 Our-Computer /usr/sbin/ocspd[565]: starting
    Jul 2 21:35:25 Our-Computer kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0xd = GR: SW Notify Error
    Jul 2 21:35:25 Our-Computer kernel[0]: 0000000c
    Jul 2 21:35:25 Our-Computer kernel[0]: 00200000 00005039 00000474 00000000
    Jul 2 21:35:25 Our-Computer kernel[0]: 00000484 00000100 00000000 00000003
    Jul 2 21:35:25 Our-Computer kernel[0]: 00000000 00000000 00000043
    Jul 2 21:35:25 Our-Computer kernel[0]: 0000000c
    Jul 2 21:35:25 Our-Computer kernel[0]: 00200000 00005039 00000474 00000000
    Jul 2 21:35:25 Our-Computer kernel[0]: 00000484 00000100 00000000 00000003
    Jul 2 21:35:25 Our-Computer kernel[0]: 00000000 00000000 00000043
     MBP, G4, Nano, ATV, TC, AX , Mac OS X (10.5.2)
  • Michael Diehr Level 1 Level 1 (65 points)
    NVidia has admitted hardware problems -- could this be what's going on?
    http://www.macrumors.com/2008/07/03/nvidia-reports-gpu-failures-in-significant-q uantities-of-laptops/
    MBP 15 C2D 2.2 (Santa Rosa), Mac OS X (10.5.3)
  • aberrant Level 1 Level 1 (10 points)
    I am so frustrated right now, I could scream. My bug report was closed as duplicate, reopened with a request for more information, and then reclosed as a duplicate. I asked for details on the original bug, and they got back to me 2 weeks later saying they couldn't release details because I didn't open the bug!

    Anyway, I'm in a bad catch-22 situation. 10.5.2 doesn't have the graphics problem for me, but it DOES have a bug with the way Safari handles client certificates that makes it unusable at work where I have multiple certs. This is fixed in 10.5.4.

    So - do I risk updating to 10.5.4 and reintroducing the graphics problem, or do I stick with 10.5.2 with no graphics issues but a broken Safari?

    Message was edited by: aberrant
    Macbook Pro 2.6, Mac OS X (10.5.2)
  • Sentient Sprocket Calculating status...
    This news is blowing up around the web.

    http://blogs.zdnet.com/hardware/?p=2172
    http://blogs.zdnet.com/BTL/?p=9244
    http://news.cnet.com/8301-13579_3-9983247-37.html
    http://www.crunchgear.com/2008/07/03/nvidias-faulty-laptop-gpus-cause-all-sorts- of-headaches/

    Can anyone speculate what this might mean for those of us here?

    I've yet to see direct acknowledgment that the Macbook Pro is affected.. but of course its just a case of connecting the dots huh..
    MacBook Pro, Mac OS X (10.5.2)
  • ch-vox Level 1 Level 1 (0 points)
    SentientSprocket wrote:
    This news is blowing up around the web.

    http://blogs.zdnet.com/hardware/?p=2172
    http://blogs.zdnet.com/BTL/?p=9244
    http://news.cnet.com/8301-13579_3-9983247-37.html
    http://www.crunchgear.com/2008/07/03/nvidias-faulty-laptop-gpus-cause-all-sorts- of-headaches/

    Can anyone speculate what this might mean for those of us here?

    I've yet to see direct acknowledgment that the Macbook Pro is affected.. but of course its just a case of connecting the dots huh..


    I personaly don't think so. If our Macbook Pro were affected by this hardware issue, they would be affected through 10.5.2 too. But they don't under 10.5.2, so IMHO the problem is purely linked to the software, especially the last Nvidia drivers update.
    Macbook Pro 2,4 GHz, Mac OS X (10.5.4)
  • slexus Calculating status...
    i am... surprised. have you even bothered to read through the whole thread? the same problem exists with every single OS X release. would you please make the effort to know whats going on, before posting inaccurate theories in the future?
    MBP 2.4, Mac OS X (10.5.1)
  • ch-vox Level 1 Level 1 (0 points)
    slexus wrote:
    i am... surprised. have you even bothered to read through the whole thread? the same problem exists with every single OS X release. would you please make the effort to know whats going on, before posting inaccurate theories in the future?


    Sorry, I must have misunderstood something. I've read people writing here that under 10.5.0 till 10.5.2 the bug wasn't there :

    aberrant wrote:

    Anyway, I'm in a bad catch-22 situation. 10.5.2 doesn't have the graphics problem for me, but it DOES have a bug with the way Safari handles client certificates that makes it unusable at work where I have multiple certs. This is fixed in 10.5.4.

    So - do I risk updating to 10.5.4 and reintroducing the graphics problem, or do I stick with 10.5.2 with no graphics issues but a broken Safari?


    So I haven't gone back to 10.5.2 yet, I'll try it next week if I can. And to reply your question : yes I've read the whole thread.

    Regards.
    Macbook Pro 2,4 GHz, Mac OS X (10.5.4), 4 GB RAM, 160 GB HD (5400 rpm), NVidia 8600m GT 256 MB
  • aberrant Level 1 Level 1 (10 points)
    Actually, ch-vox is right, at least for some of us. In my case, the problem was introduced (or at least exacerbated) by the Leopard Graphics Update 1.0, which came out after 10.5.2. The problem is that new Leopard DVDs and (according to others here) 10.5.3 and 10.5.4 now include LGU1.0, so those of us who rolled back to 10.5.2 and did not install LGU1.0 in order to preserve system stability cannot upgrade.

    In any event, no post here warrants impoliteness, impatience (at anyone other than Apple) or disrespect. We're all trying to figure this one out.
    Macbook Pro 2.6, Mac OS X (10.5.2)
  • dombessi Calculating status...
    for anyone interested I finally updated to 10.5.4 about 3 weeks ago and have not had the crash yet.

    my history is in this thread and I had this freeze/crash issue as bad as anyone here with 10.5.2 and LGU installed, 3-5 times a day it would freeze on me.
    macbook pro, Mac OS X (10.5.4)
  • kamilion Calculating status...
    i did not know that 10.5.4 is out for 3 weeks now!? also 10.5.4 changes nothing to this problem because its the same nvidia driver kext file.
    in view of the nvchannel exception 10.5.4 changes nothing for no one. all my friends which have this problem tell me that nothing is changed.
    the problem come with the leopard grafik update 1.0. i hope it will go with a leopard grafik update 2.0 ^^
    MacBook Pro 2,4 Ghz Core 2 Duo 2 GB RAM, Mac OS X (10.5.4)
  • ch-vox Level 1 Level 1 (0 points)
    kamilion wrote:
    the problem come with the leopard grafik update 1.0. i hope it will go with a leopard grafik update 2.0 ^^


    exactly : so do I !
    I cross my fingers...

    Edit :

    I've just read an article on Digitimes about Nvidia defective chips. It says that only 8500M chipsets are affected by the hardware issue, so Apple may not be affected by that problem.
    http://www.digitimes.com/bits_chips/a20080704PD210.html

    Message was edited by: ch-vox
    Macbook Pro 2,4 GHz, Mac OS X (10.5.4), 4 GB RAM, 160 GB HD (5400 rpm), NVidia 8600m GT 256 MB
  • aberrant Level 1 Level 1 (10 points)
    I tested 10.5.4 combo over the weekend and was able to reproduce the issue 100% of the time. To reproduce, invoke quicklook on a series of photographs and go to thumbnail view. Quit quicklook, move the finder window to an external display, and repeat. The system will freeze trying to render the thumbnails on the external display. I just reinstalled 10.5.2.
    Macbook Pro 2.4, Mac OS X (10.5.2)
1 ... 20 21 22 23 24 ... 29 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.