Skip navigation

i have an issue with my mac book pro, where whenever i run certain programs that uses flash player or run more than one app for a period of time it shuts down and gives me an error report

248 Views 12 Replies Latest reply: Jan 7, 2013 3:52 PM by sdpitbull RSS
tetewilli Calculating status...
Currently Being Moderated
Jan 7, 2013 9:07 AM

is there a way i can submit my crash report here so someone could look at it and let me know what's causing the issue

MacBook Pro (13-inch Mid 2009), OS X Mountain Lion (10.8)
  • Grant Bennet-Alder Level 8 Level 8 (48,145 points)
  • Grant Bennet-Alder Level 8 Level 8 (48,145 points)

    The type of error was a page fault. It occurred deep in subroutines called by the graphics drivers. It does not specifically implicate graphics Hardware, as some of these panic reports do.

     

    Your Mac uses an discrete NVIDIA graphics chip, but shares the screen buffer with main memory:

     

    a NVIDIA GeForce 9400M "graphics processor with 256 MB of DDR3 SDRAM shared with main memory"

    In cases like this there are two tracks to pursue:

     

    1) do you have enough real RAM to do what you are doing without taxing memory so much that the graphics processor runs short of RAM?

     

    2) are you having memory errors, which would show themselves as random kernel panics for seemingly unrelated causes (no trends in previous panics)?

     

    You have no non-Apple kernel extensions, so this is an all Apple problem (no third-party debugging required).

    Mac Pro (Early 2009), Mac OS X (10.6.8), & Server, PPC, & AppleTalk Printers
  • Linc Davis Level 10 Level 10 (107,995 points)

    That panic was not caused by third-party software. If it's happened only once, and is not repeated in at least a few thousand hours of use, a reasonable choice would be to ignore it. Machines don't work perfectly. They never will.

     

    If the problem is recurrent, the possibilities are (1) a damaged OS X installation; (2) a fault in a peripheral device, if any; (3) an internal hardware fault; and (4) an obscure bug in OS X.

     

    You can rule out the first two possibilities by reinstalling the OS and testing with non-essential peripherals disconnected and aftermarket expansion cards removed, if applicable.

     

    If you've recently upgraded the memory, reinstall the original memory and see whether there's any improvement. Be careful not to touch the gold contacts on the memory modules when handling them. If necessary, clean them with a mild solvent such as rubbing alcohol.

     

    The Apple Hardware Test, though generally unreliable, will sometimes detect memory faults. A negative test can't be depended on.

     

    In the category of obscure bugs, reports suggest that FileVault may trigger kernel traps under some unknown conditions. Most, if not all, of these reports seem to involve booting from an aftermarket SSD. If those conditions apply to you, try deactivating FileVault.

     

    Otherwise, make a "Genius" appointment at an Apple Store to have the machine tested. You may have to leave it there for several days. There isn't much point in doing this unless you can reproduce the panic, or if you can't, it happens often enough that it's likely to be repeated at the store. Otherwise you may be told that nothing is wrong.

     

    Print the first page of the panic report and bring it with you.

     

    Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you know how to restore, and you have at least  two independent backups.) Don’t erase the recovery partition, if present.

     

    *An SSD doesn't need to be zeroed.

  • Linc Davis Level 10 Level 10 (107,995 points)

    the only thing that was newly installed was two four gig memory.

     

    Things go a lot more smoothly in these forums when you disclose all the relevant information at the beginning of the thread, rather than at the end.

  • sdpitbull Level 3 Level 3 (965 points)

    Put the original memory back in the machine and see if the problem goes away. That is the only way to find out. I had a similar issue that was narrowed down to a memory stick that went bad in a MBPro 15. I put the original memory back in and had no issues.

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.