Kernel Protection Failure errors?

Discussion in 'macOS' started by rdf8585, Nov 8, 2006.

  1. rdf8585 macrumors regular

    Joined:
    Feb 15, 2006
    #1
    What causes these Kernel Protection Failure errors? I've been getting them today when Safari has crashed.
     
  2. gr8tfly macrumors 603

    gr8tfly

    Joined:
    Oct 29, 2006
    Location:
    ~119W 34N
    #2
    Kernel Panic? (the dimmed screen, with the multi-lingual, and restart)

    Which version OS-X are you on?

    Without looking at the Safari crash log, and/or others, it'd be just a wild guess as to cause. It's something pretty seriously corrupted, or worse a hardware problem (RAM?).

    It's worth doing "Safari->Empty Cache..." and see if it helps.

    Otherwise, verify disk (Disk Utility - First Aid). If the verify fails, reboot on your restore CD (or OS-X install) and run Disk Utility from there to perform the repair. Once you have the disk verified, do a repair permissions.

    If that doesn't help, next I'd re-install the latest OS-X update, using the OS-X combo updater for the version you are running (like 10.4.8, hopefully).

    Hope one of these more generic techniques help.
     
  3. knome macrumors 6502

    knome

    Joined:
    Sep 7, 2006
    #3
    no he is not saying kernel panic. He is saying the reason safari crashes. Usually it is due to the website your a navigating to. Also empty your cashe, and cookies.
     
  4. rdf8585 thread starter macrumors regular

    Joined:
    Feb 15, 2006
    #4
    maps.yahoo.com, nbc.com and myspace.com caused crashes / kernel protection failures. Yeah, obviously its something related to a site... but what exactly needs to happen to create a kernal protection failure?
     
  5. gr8tfly macrumors 603

    gr8tfly

    Joined:
    Oct 29, 2006
    Location:
    ~119W 34N
    #5
    This is probably too specfic, but:


    file: kern_return.h

    #define KERN_PROTECTION_FAILURE 2
    /* Specified memory is valid, but does not permit the
    * required forms of access.
    */


    To find out specifically what caused it, you'd have to look at the safari crash log, and/or other logs (system, console)
     

Share This Page