Q: Ancient MacBook 2,1

What's a "kernel panic"? (Mac OS X)

Tutorial - Avoiding and eliminating Kernel panic

About "You need to restart your computer" (kernel panic) messages

Technical Note TN2063- Understanding and Debugging Kernel Panics

OS X- About kernel panics

Mac OS X- How to log a kernel panic

Visit The XLab FAQs and read the FAQ on diagnosing kernel panics:

CR0, CR1, CR2, CR3, and CR4 followed by hexadecimal addresses state of the Control Registers in the Xeon processor when each panic occurs.

For example, the CR0 indicates operating mode and states of the processor. CR2 indicates the address that caused a page fault.

 

EAX, EBX, ECX, EDX, EBP, EDI and ESI state each the extended 32-bit registers at the time of a type 14 page-fault exception.

 

"No mapping exists for frame pointer" means that a page invoked by a program code is not mapped in physical memory for the page frame pointer.

 

A kernel trap "type 14=page fault" can be proved that the cause is most likely either of the following scenarios:

 

1. The processor detects that an attempt to execute an instruction at an invalid memory address.

 

2. The processor detects that an instruction by a program [#1] or a computation by you does not have sufficient privilege to access the indicated page. #1: A software attempts to access a kernel memory space that does not have the privilege.

 

3. The processor detects that a program code attempt to write to a read-only page.

 

4. The processor detects an instruction fetch that attempts to a physical address in a memory page cannot be executed due to unable-bit flag.

 

5. I cannot explain you about the last scenario because too complicated.

 

Possible cause: Either incompatible software or bad RAM.

 

Suggested troubleshooting procedure:

 

1. Verify topology such as the power resource and a LAN network.

 

2. Run Apple Hardware Test disc with Extended mode if available. If disc is not available, swapping them to reseat to each restart the computer.

 

3. Troubleshoot incompatible third-party software.

There is some number of Knowledge Base articles for Kernel Panic you may want to refer. It may be a good idea what computation you were doing shortly before the first panic.

You might consider erasing the drive and reinstalling OS X. However, that's about it because you haven't provided enough information: Writing an effective Apple Support Communities question.

Post a recent panic log and we'll take a look Mac OS X: How to log a kernel panic - Apple Support