Left4Dead 2 wont run on Core i5 MBP?

Discussion in 'MacBook Pro' started by Maximus434, Apr 26, 2010.

  1. Maximus434 macrumors regular

    Joined:
    Jan 11, 2006
    #1
    Can anyone help here?

    Everytime I run left4dead 2 on my new Core i5 2.4Ghz MBP (bootcamp with Win7 64bit) It gets to the main screen, I click quick match and it begins to load, however once it's finished loading the game crashes to desktop. This has been happening since Valve updated it with the new "mutations" game.

    Has anyone else experienced this? I'm extremely frustrated since I love playing this game and valve don't support bootcamp on mac computers.

    Anyone?!
     
  2. ozreth macrumors 65816

    ozreth

    Joined:
    Nov 5, 2009
    #2
    Works on my mid 09 MBP, so I doubt its your hardware.
     
  3. Maximus434 thread starter macrumors regular

    Joined:
    Jan 11, 2006
    #3
    I figured it out. It was crashing after the loading screen with the following error.

    Problem signature:
    Problem Event Name: APPCRASH
    Application Name: left4dead2.exe
    Application Version: 0.0.0.0
    Application Timestamp: 4bcfba0e
    Fault Module Name: d3d9.dll
    Fault Module Version: 6.1.7600.16385
    Fault Module Timestamp: 4a5bd9a9
    Exception Code: c0000005
    Exception Offset: 00046aaa
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 6153
    Additional Information 1: 0a9e
    Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
    Additional Information 3: 0a9e
    Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

    Read our privacy statement online:
    http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt


    Turns out it's a shader problem. I changed the shader detail from Very high to medium and now it runs without problem.

    Makes no sense though because it ran at very high before this latest update!!
     
  4. Fasailmac macrumors member

    Joined:
    Jun 20, 2009
    #4
    its a nvidia issue, it happened on my m11x too, which has the 335m
     

Share This Page