SR MBP WoW lockups

Discussion in 'Mac and PC Games' started by kinetik, Jun 20, 2007.

  1. kinetik macrumors newbie

    Joined:
    Jun 8, 2007
    #1
    Bought the base model santa rosa Mac Book Pro a few weeks back (2.2ghz, 2gb RAM, 128mb VRAM), and am having issues with random lockups in World of Warcraft...

    I thought it was heat-related, so I installed SMCFanControl (4000rpm) and added a Targus ChillPad, but it still happens on occasion. Basically the UI freezes, but the soundtrack still plays, and sometimes to mouse continues to work (haphazardly, jumping all over the screen), but mostly the mouse/keyboard is dead too. If I wait several minutes I get booted back to the login screen with a "disconnected from server" message.

    Anyone else experience this? Could it be bad RAM? (suggestions for eliminating possible culprits?)

    P.S.: am usually running in closed-lid mode (although yes tried open lid mode too) with an external 22" monitor running at 1680.
     
  2. kinetik thread starter macrumors newbie

    Joined:
    Jun 8, 2007
    #2
    Followup: played for several hours last night with just the MBP and an external mouse (no external monitor) and experienced NO lockups. The machine got fairly hot - 160 degrees F, but I think that's to be expected. Looks like my lockups may have had something to do with the external monitor setup? (video card has to work harder/hotter to run @ 1680)
     
  3. senc01a macrumors regular

    Joined:
    May 31, 2007
    #3
    It has happened to me twice on OSX too.
    No external monitor, just a usb mice.

    Both of the times i had Adium launched, i think that it was just because someone from my contact list logged in, and the popup message made something to the fullscreen 3d, that for some reason made it freeze even tough the mouse kept moving ocasionally, and the soundtrack still went on.
     
  4. kinetik thread starter macrumors newbie

    Joined:
    Jun 8, 2007
    #4
    Update: got a locked-up screen again last night when using built-in display and usb keyboard/mouse. The issue may not be related to using an external monitor afterall...
     
  5. djinn macrumors 68000

    djinn

    Joined:
    Oct 4, 2003
    #5
    I smell a driver problem with Nvidia and OS X. Try it in Bootcamp XP and see if you get the same problem.
     
  6. Sbrocket macrumors 65816

    Sbrocket

    Joined:
    Jun 3, 2007
    Location:
    /dev/null
    #6
    There is a reported driver issue with the 8600M GT cards and anti-aliasing support. Try turning off anti-aliasing in WoW and see if the freeze-ups come back. If it does lock up again try pushing Command-Option-Esc or wait for a couple minutes, sometimes (if it really is this issue) the graphics card can recover. Please post any of your findings here so I can add observations to the currently maintained bug report.

    Also, it would really help if you can open up Console (Applications->Utilities->Console) and search through system.log for a message similar to this:
    Jun 24 19:36:27 ******** kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0xd = GR: SW Notify Error
    Jun 24 19:36:27 ******** kernel[0]: 0000000c
    Jun 24 19:36:27 ******** kernel[0]: 00200000 00005097 0000047c 00000000
    Jun 24 19:36:27 ******** kernel[0]: 00000486 00000f10 00000000 00000003
    Jun 24 19:36:27 ******** kernel[0]: 00000000 00000000 00000002
     
  7. pieman02 macrumors regular

    Joined:
    Apr 27, 2007
    #7
    The last two times I have run FEAR on my 2.4 MBP it has frozen screen and sound still keeps playing...so not just related to OS X, but I am in search of better drivers (Vista...wish me luck :( )

    Didn't even seem to be hot or anything like that and the system did not recover either time at all...

    Anyone else?
     
  8. theguy macrumors newbie

    Joined:
    Jul 11, 2007
    #8
    Me too

    Mine locks up...a lot. Really pissing me off.

    It looks like this:
    Code:
    Jul 11 22:14:10 theguys-computer kernel[0]: NVChannel(GL): Graphics channel timeout!
    Jul 11 22:14:11 theguys-computer DirectoryService[64]: CNodeRegister:RegisterLocalNetInfoHierarchy::Call to netinfo_domainname for local domain name lasted 10 seconds.
    Jul 11 22:14:11 theguys-computer DirectoryService[64]: CNodeRegister:RegisterLocalNetInfoHierarchy::Call to netinfo_domainname returned domain name: /.
    Jul 11 22:14:22 theguys-computer kernel[0]: NVChannel(GL): Graphics channel timeout!
    Jul 11 22:14:34 theguys-computer kernel[0]: NVChannel(GL): Graphics channel timeout!
    Jul 11 22:14:36 theguys-computer kernel[0]: nfs server automount -nsl [187]: not responding
    Jul 11 22:14:36 theguys-computer KernelEventAgent[51]: tid 00000000 received VQ_NOTRESP event (1)
    Jul 11 22:14:36 theguys-computer KernelEventAgent[51]: tid 00000000 type 'nfs', mounted on '/Network', from 'automount -nsl [187]', not responding
    Jul 11 22:14:36 theguys-computer KernelEventAgent[51]: tid 00000000 type 'smbfs', mounted on '/Volumes/linksys', from '//WORKGROUP;guest@LINKSYSWRT350N/ALL_PARTITIONS', not responding
    Jul 11 22:14:36 theguys-computer KernelEventAgent[51]: tid 00000000 found 1 filesystem(s) with problem(s)
    Jul 11 22:14:46 theguys-computer kernel[0]: NVChannel(GL): Graphics channel timeout!
    Jul 11 22:14:58 theguys-computer kernel[0]: NVChannel(GL): Graphics channel timeout!
    Jul 11 22:15:10 theguys-computer kernel[0]: NVChannel(GL): Graphics channel timeout!
    Jul 11 22:15:22 theguys-computer kernel[0]: NVChannel(GL): Graphics channel timeout!
    Jul 11 22:15:34 theguys-computer kernel[0]: NVChannel(GL): Graphics channel timeout!
    Jul 11 22:15:47 theguys-computer kernel[0]: NVChannel(GL): Graphics channel timeout!
    Jul 11 22:16:04 theguys-computer lookupd[1559]: NetInfo connection failed for server 127.0.0.1/local
    Jul 11 22:16:04 theguys-computer lookupd[1559]: ni_statistics: Communication failure
    Jul 11 22:16:18 theguys-computer kernel[0]: NVChannel(GL): Graphics channel timeout!
    Jul 11 22:16:30 theguys-computer kernel[0]: NVChannel(GL): Graphics channel timeout!
    Jul 11 22:16:42 theguys-computer kernel[0]: NVChannel(GL): Graphics channel timeout!
    Jul 11 22:16:55 theguys-computer kernel[0]: NVChannel(GL): Graphics channel timeout!
    Jul 11 22:17:07 theguys-computer kernel[0]: NVChannel(GL): Graphics channel timeout!
    Jul 11 22:17:19 theguys-computer kernel[0]: NVChannel(GL): Graphics channel timeout!
    Jul 11 22:17:31 theguys-computer kernel[0]: NVChannel(GL): Graphics channel timeout!
    
     
  9. theguy macrumors newbie

    Joined:
    Jul 11, 2007
    #9
    Could you point us to the bug report or provide a bug number? I'd like to track the status of this bug and help any way I can with solving it. Thanks!
     
  10. Sbrocket macrumors 65816

    Sbrocket

    Joined:
    Jun 3, 2007
    Location:
    /dev/null
    #10
    Even if I gave you my bug number, you wouldn't be able to track it without access to Apple's internal network and a copy of Radar.
     
  11. danny.gasperini macrumors newbie

    Joined:
    Jul 27, 2007
    #11
    I just got a cursor lock up for about 8 seconds and then everything came back to normal. I was doing nothing more than browsing the Finder and viewing a .mov from a window using the pane view. I have had this happen a few times in World of Warcraft, and assumed that it was WoW that was triggering the freeze. At the time the GPU/CPU were at no more than 45/55 degrees celcius respectively. From the system log:

    Jul 27 20:34:30 dannys-computer kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0xd = GR: SW Notify Error
    Jul 27 20:34:31 dannys-computer kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0xd = GR: SW Notify Error
    Jul 27 20:34:44 dannys-computer kernel[0]: 0000000c
    Jul 27 20:34:44 dannys-computer kernel[0]: 00200000 00005097 0000047c 00000000
    Jul 27 20:34:44 dannys-computer kernel[0]: 00000486 000015e0 00000000 00000003
    Jul 27 20:34:44 dannys-computer kernel[0]: 00000000 00000000 00000000
    Jul 27 20:34:44 dannys-computer kernel[0]: 0000000c
    Jul 27 20:34:44 dannys-computer kernel[0]: 00200000 00005097 0000047c 00000000
    Jul 27 20:34:44 dannys-computer kernel[0]: 00000486 000015e0 00000000 00000003
    Jul 27 20:34:44 dannys-computer kernel[0]: 00000000 00000000 00000000
    Jul 27 20:34:44 dannys-computer kernel[0]: 0000000c
    Jul 27 20:34:44 dannys-computer kernel[0]: 00200000 00005097 0000047c 00000000
    Jul 27 20:34:44 dannys-computer kernel[0]: 00000486 000015e0 00000000 00000003
    Jul 27 20:34:44 dannys-computer kernel[0]: 00000000 00000000 00000000
     
  12. mysticalos macrumors member

    Joined:
    May 8, 2007
    #12
    I'm getting this problem during wow now with nvidia card and Leopard. game locked up with log showing

    1/22/08 9:00:03 PM kernel NVChannel(GL): Graphics channel timeout!
    1/22/08 8:59:47 PM [0x0-0x18018].com.glu.WeatherPop[214] Connection Failure!
    1/22/08 9:00:14 PM loginwindow[40] Application hardKill returned -600
    1/22/08 9:00:12 PM com.apple.launchd[181] ([0x0-0x1a01a].com.blizzard.worldofwarcraft[216]) Exited: Terminated
    1/22/08 9:01:36 PM kernel FirmtekCtrllr::HotPlugHandler: unit zero hotplug condition on chnannel = 1, removal = 1
    1/22/08 9:01:37 PM kernel FirmtekCtrllr::HotPlugHandler: unit zero hotplug condition on chnannel = 1, removal = 0
    1/22/08 9:01:37 PM kernel disk0s10: media is not present.
    1/22/08 9:01:37 PM kernel live.0.indexHead] [FSLogMsgID 680707529] [FSLogMsgOrder Last]
    1/22/08 9:01:37 PM mds[39] (/Volumes/Alpha/.Spotlight-V100/Store-V1/Stores/3AC9D67C-2C94-4FEF-8B03-2D3D96D2185F)(Error) IndexStore in SIStoreDirytySDBChunks:Error storing dirty sdb pages: 22
    1/22/08 9:01:37 PM kernel disk0s10: media is not present.
    1/22/08 9:01:37 PM mds[39] (/Volumes/Alpha/.Spotlight-V100/Store-V1/Stores/3AC9D67C-2C94-4FEF-8B03-2D3D96D2185F)(Error) IndexCI in CIMetaInfoSync:sync err: 22
    1/22/08 9:01:37 PM kernel disk0s10: media is not present.
    1/22/08 9:01:37 PM kernel disk0s10: media is not present.
    1/22/08 9:01:37 PM kernel jnl: disk0s10: close: journal 0x27dce08, is invalid. aborting outstanding transactions
     

Share This Page