Skip navigation

Kernal Error - please help

251 Views 5 Replies Latest reply: Sep 1, 2013 9:38 AM by Linc Davis RSS
declanmcr Calculating status...
Currently Being Moderated
Sep 1, 2013 2:02 AM

Heys guys,


I have a MBP 13 (early 2011), with Mac OS 10.8.4. However in the last day or so my Mac keeps freezing/re-booting itself...


I keep gerting "Kernal Error" reports, similar to this one below: (please help!):



Process:         WebProcess [244]

Path: /System/Library/PrivateFrameworks/WebKit2.framework/ OS/WebProcess


Version:         8536 (8536.30.1)

Build Info:      WebKit2-7536030001000000~9

Code Type:       X86-64 (Native)

Parent Process:  ??? [1]

User ID:         501


Date/Time:       2013-09-01 09:11:07.403 +0100

OS Version:      Mac OS X 10.8.4 (12E55)

Report Version:  10


Interval Since Last Report:          604779 sec

Crashes Since Last Report:           28

Per-App Interval Since Last Report:  13977 sec

Per-App Crashes Since Last Report:   2

Anonymous UUID: E1E8341B-B434-1246-8E51-9142ED12BAFF


Crashed Thread:  6 JavaScriptCore::Marking



Exception Codes: KERN_INVALID_ADDRESS at 0x0000000040000038


External Modification Warnings:

Thread creation by external task.


VM Regions Near 0x40000038:


__TEXT 00000001093f3000-00000001093f4000 [ 4K] r-x/rwx SM=COW /System/Library/PrivateFrameworks/WebKit2.framework/ OS/WebProcess


Application Specific Information:

Bundle controller class:




Thread 0:: Dispatch queue:

MacBook Pro, OS X Mountain Lion (10.8.4)
  • clintonfrombirmingham Level 7 Level 7 (26,850 points)
    Currently Being Moderated
    Sep 1, 2013 2:21 AM (in response to declanmcr)

    Please post the entire kernel panic log -> - in a reply here.



  • Linc Davis Level 10 Level 10 (108,135 points)
    Currently Being Moderated
    Sep 1, 2013 8:10 AM (in response to declanmcr)

    That kind of crash is caused by a hardware fault, in every case I've seen.



    If your model has user-replaceable memory, and you've upgraded the memory modules, reinstall the original memory and see whether there's any improvement. Be careful not to touch the gold contacts. Clean them with a mild solvent such as rubbing alcohol. Aftermarket memory must exactly match the technical specifications for your model. Memory that is either slower or faster than specified may be incompatible.


    The Apple Hardware Test or Apple Diagnostics, though generally unreliable, will sometimes detect a fault. A negative test can't be depended on. Run the extended version of the test.

  • Linc Davis Level 10 Level 10 (108,135 points)
    Currently Being Moderated
    Sep 1, 2013 9:38 AM (in response to declanmcr)

    Posting more crash logs is not going to change anything. You might be able to stop the crashing by removing one of the memory modules. If the crashes continue, put that module back in and remove the other one.


More Like This

  • Retrieving data ...

Bookmarked By (0)


  • 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.