This discussion is archived
65349 Views 427 Replies Latest reply: Oct 28, 2009 6:35 AM by ampamp19
Currently Being ModeratedJul 27, 2008 11:27 AM (in response to Chris Replogle)My MBP just died yesterday, and guess what it was nVidia 8600M GT that didn't make it. 8 days ego my warranty ended. If they are not going to recall all broken nvidias I'm screwed.Macbook Pro, Mac OS X (10.5.4)
Currently Being ModeratedJul 29, 2008 6:02 AM (in response to Chris Replogle)I'll add one more to the list, mine is Mac Pro tower. As far as I can tell, it was 10.5.4 that hosed me. Same NVChannel error in system.log.
The freezes are annoying as ****, seems totally random. It takes me 3-4 boots just to get up to speed, the first three boots of the morning look like this:
Don't have the time for an Archive & Install, but that appears to be the best solution so far.Mac Pro 2Ghz Dual Core, Mac OS X (10.5.4), 3GB RAM
Currently Being ModeratedJul 29, 2008 6:35 AM (in response to tripleclick)Hmmm... just throwing this out there.
When looking at System Profiler > Software > Extensions as advised in the replacement thread, I noticed something a touch odd. The NVidia drivers haven't been touched in a year:
All with a modification date of 6/21/07, meaning they haven't been modified in the 8 months I have owned this Mac Pro. Does that mean I didn't upgrade to LUG 1.0?
However, I did notice that a ton of files were updated on July 24 – right around the same time I started having these display issues (maybe this was 10.5.4, don't remember). Maybe any of these could be a cause?
Unsupported (***?) 9.4.0
I bolded potential oddballs, just based on my own basic knowledge of the OS underpinnings. I'll leave it to smarter folks to figure out if any of this makes any sense
Message was edited by: tripleclickMac Pro 2Ghz Dual Core, Mac OS X (10.5.4), 3GB RAM
Currently Being ModeratedAug 9, 2008 12:19 PM (in response to GrubInCan)Numbers triggers the freeze easily. So does OmniGraffle 5. So does Excel according to
My own findings (8-way Mac Pro Jan 2008 model with 8800GT and 16GB RAM) is that freezing is solved by removing the second monitor from the computer. Zero freezes after that. I'm half tempted to get an ATI card from OWC. I want my second monitor!Mac Pro 8-way 16GB, Mac OS X (10.5.4)
Currently Being ModeratedAug 9, 2008 3:58 PM (in response to Larry K)Good news from Apple Support: the problem has been identified and is apparently fixed in 10.5.5!! Got email confirmation this afternoon.Macbook Pro 2.4, Mac OS X (10.5.2)
Currently Being ModeratedAug 9, 2008 6:43 PM (in response to aberrant)That's great... when does 10.5.5 come out? =)MacBook Pro 15-inch: 2.4GHz, Mac OS X (10.5.4)
Currently Being ModeratedAug 9, 2008 8:54 PM (in response to aberrant)I have been having troubles like everyone else for a while as well. Last week I took my MBP in to Apple and it crashed right in front of one of their geniuses. They kept it overnight and the GPU seriously overheated. For me, that means replacing the main board under AppleCare.
Hopefully this ends with either the replacement main board or the pending update.MacBook Pro, Mac OS X (10.5.4)
Currently Being ModeratedAug 9, 2008 9:40 PM (in response to Darren Martz1)I've already had my logic board replaced due to failure of the graphics card... problems disappeared for a while but have resurfaced in the last couple of days.
Seems to me like there is a combination of software and hardware issues with the Nvidia cards.
I'm going to think seriously about getting another machine ASAP as my work is really sufferingMacBook Pro 17, Mac OS X (10.5.4), 2.4GHz, 4GB RAM
Currently Being ModeratedAug 10, 2008 6:57 PM (in response to Adrian Smith2)Everyone needs to read this article. There are many more articles like it. Looks like all of us all of us affected MBP users have to wait for Nvidia and Apple to act.
http://www.consumeraffairs.com/news04/2008/08/nvidia.htmlMBP 17" 2.6GHZ 4MB, Mac OS X (10.5.4)
Currently Being ModeratedAug 10, 2008 9:15 PM (in response to Larry K)Good to see the issue getting some more prime exposure..
http://blogs.zdnet.com/Apple/?p=2108MacBook Pro, Mac OS X (10.5.4)
Currently Being ModeratedAug 11, 2008 10:05 AM (in response to Larry K)I think people may be confusing lots of different errors here. The original poster had a Mac Pro (not MacBook Pro). Some of the errors listed are "Fifo: Watchdog Timeout Error", and some are other NVChannel Errors.
My Mac Pro (with NVidia GeForce 7300 GT) started producing exactly the same error as the OP's, i.e. "NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x8 = Fifo: Watchdog Timeout Error". The symptom was even light work (web browsing) would result in a 10 second freeze every couple of minutes. Every freeze was accompanied by the same thing in System.log. There was also a small amount of screen corruption occasionally (small areas being painted in the wrong colours).
I couldn't afford the downtime of sending it to be repaired, so I went and bought another 7300 graphics card. I've now been running it for about 7 hours without a single freeze. I thus think that the cause of my problem was a dead graphics card. Of course this might be same problem as the NVidia chipsets dying on the MacBook Pro, but it is just as likely to be a different problem, given it appears to be different chips.
So fix to the OP's problem: replace dead graphics card.MacPro 2.1 Quad-Core, Mac OS X (10.5.4)
Currently Being ModeratedAug 11, 2008 7:27 PM (in response to Breezemaster)<AOL> Me, too </AOL>
Decided to pick up a new MBP to use while the POS Superdrive in my older one was replaced; was promptly bitten by the 8600 graphics channel exception/graphics channel timeout/IOHIDEventQueueEnqueue exceptions under 10.5.4. "Unimpressed" really doesn't do justice to my feelings regarding having my machine lock up several times daily, usually while blitting crap all over both displays.
I suppose I should be grateful that about 80% of the time the machine only has a stroke and eventually recovered and only requires that I go for the cord about 20% of the time.
I'll be dragging both machines to the "Genius Bar" in a week or so, whereupon I'll try to find words small enough to explain what's going on. The fact that there doesn't seem to be another avenue for hardware support doesn't precisely improve my humor about this either; it's a three hour round trip to the nearest ubertrendy Apple Store.
And people wonder why all of my servers are commodity X86 boxes running Linux.MBP4.1, 2 * MBP2.1, other bits.., Mac OS X (10.5.4)
Currently Being ModeratedSep 1, 2008 12:18 PM (in response to Larry K)As recently as two weeks ago I had been a very happy camper with Panther and Tiger. Little did I anticipate the grief that was with Leopard Family Pack.
I had the Mac retailer Install Leopard, clean install on a clean hard drive, 1.2 gig ram, 1Ghz G4 CPU, GeForce FX Go5200 32MB, 12" PowerBook Aluminum... I had been using the PB12 with a 23" Cinema display with good results for a couple years.
I immediately applied the updates to 10.5.4. It does work reasonably well for non-graphic-intensive apps. Let me qualify that, though.
Preview.app is having very serious troubles, amongst other graphic apps. Simply opening up a folder full of JPEGs, 82 files, each less than 100k in size, in preview.app gives no end of problems. Zooming, resizing window, etc. tends to cause preview.app to go into convulsions. The preview window goes black, or it goes into a rainbow of stripes, or it goes into grey stripes... spinning beachball... occasionally seg faults. Going into slide show mode gives a black screen and spinning beach ball and no satisfaction.
Digging out the console messages, yielded a familiar story it seems:
01/09/08 1:14:10 PM kernel 00000006
01/09/08 1:14:10 PM kernel 00100080 00000039 00004e58 00000800
01/09/08 1:14:10 PM kernel 000052e2 00000328 00000000 00000002
01/09/08 1:14:10 PM kernel 00000000 beef3902 00021001
01/09/08 1:14:25 PM kernel NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0xd = GR: SW Notify Error
I would guess that this might be a gnarly problem, judging by the length of the discussion. Hopefully, we all can find an answer/solution for this soon.PB 12 G4 al, Mac OS X (10.5.4), iMac G5 21" Tiger, Linux
Currently Being ModeratedSep 1, 2008 1:07 PM (in response to ejritz)Append to my previously noted behaviour:
After I reported the above, I switched back to answering e-mails when I noticed that mail.app had stopped placing my sent mail into the sent mail folder for all e-mail sent today. (Grr)
Following a reboot, preview.app behaved slightly better, though still not well ... more interestingly, the above error message was not being generated in the console log this time around.PB 12 G4 al, Mac OS X (10.5.4), iMac G5 21" Tiger, Linux
Currently Being ModeratedSep 2, 2008 9:30 PM (in response to ejritz)I also have this problem on my MPB 2.5Gh. Keep freezing up randomly, and I loose my work, time and concentration.
NV GeForce 8600M GT
Device ID: 0x0407
Revision ID: 0x00a1
ROM Revision: 3212
kernel: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0xd = GR: SW Notify Error
kernel: NVChannel(GL): Graphics channel timeout!
This is not good enough. NVidia and Apple has to step up and fix it!MacBook Pro 2.5GHz, Mac OS X (10.5.4), 2GB memory