Sign up ×
Ask Different is a question and answer site for power users of Apple hardware and software. It's 100% free, no registration required.

I have an early 2010 MacBook Pro. I just upgraded the RAM to 8GB because I was constantly using more than 4GB. I have upgraded to flash storage as well so I didn't want my system constantly using swap. My MacBook keeps crashing constantly. Here is my error log:

Interval Since Last Panic Report:  26019 sec
Panics Since Last Report:          1
Anonymous UUID:                    372A45EB-F401-8CF5-4375-11E86EC6A531

Sun Sep  1 16:57:38 2013
panic(cpu 2 caller 0xffffff80244b8655): Kernel trap at 0xffffff8024487ca3, type 13=general protection, registers:
CR0: 0x000000008001003b, CR2: 0x00007fa3e6003000, CR3: 0x000000000ba5f05f, CR4: 0x00000000000606e0
RAX: 0x0e5000ffffff805a, RBX: 0xffffff8028da83a0, RCX: 0x0e5000ffffff805a, RDX: 0xffffff8024abdac0
RSP: 0xffffff8114be3ce0, RBP: 0xffffff8114be3d00, RSI: 0x000000002231db52, RDI: 0xffffff8027b4ea20
R8:  0xfffffffffffff000, R9:  0xffffff8039395580, R10: 0x0000000103b04000, R11: 0x0000000000000200
R12: 0x0000000000019440, R13: 0xffffff8028dbd958, R14: 0xffffff8027b4ea20, R15: 0xffffff8026b42000
RFL: 0x0000000000010207, RIP: 0xffffff8024487ca3, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x00007fa3e6003000, Error code: 0x0000000000000000, Fault CPU: 0x2

Backtrace (CPU 2), Frame : Return Address
0xffffff8114be3980 : 0xffffff802441d626 
0xffffff8114be39f0 : 0xffffff80244b8655 
0xffffff8114be3bc0 : 0xffffff80244ce17d 
0xffffff8114be3be0 : 0xffffff8024487ca3 
0xffffff8114be3d00 : 0xffffff80244893a8 
0xffffff8114be3d20 : 0xffffff80244894e8 
0xffffff8114be3d60 : 0xffffff802447c637 
0xffffff8114be3d90 : 0xffffff8024476524 
0xffffff8114be3dc0 : 0xffffff80244759b0 
0xffffff8114be3e00 : 0xffffff802446737c 
0xffffff8114be3ef0 : 0xffffff802446b0e0 
0xffffff8114be3f20 : 0xffffff80247b8c66 
0xffffff8114be3f50 : 0xffffff80247e16aa 
0xffffff8114be3fb0 : 0xffffff80244ce9c3 

BSD process name corresponding to current thread: AppleIDAuthAgent

Mac OS version:

Kernel version:
Darwin Kernel Version 12.4.0: Wed May  1 17:57:12 PDT 2013; root:xnu-2050.24.15~1/RELEASE_X86_64
Kernel UUID: 896CB1E3-AB79-3DF1-B595-549DFFDF3D36
Kernel slide:     0x0000000024200000
Kernel text base: 0xffffff8024400000
System model name: MacBookPro8,1 (Mac-94245B3640C91C81)

System uptime in nanoseconds: 16155595033
last loaded kext at 5864370255:    1.60 (addr 0xffffff7fa56f1000, size 32768)
loaded kexts:    1.60    1.9.5d0    3.0    4.1.4f2    100.12.87    1.0.2d2    122    2.3.7fc4    2.3.7fc4    1.0.0    1.0.0d1    7.0.0    3.4.5    2.3.7fc4    3.5.10    8.1.2    2.0.3d0    1.0.0    4.1.4f2    4.1.4f2    3.4.5    170.2.5    1.6.0    1.1.11    8.1.2    3.0.3d1    237.1    237.1    237.1    320.15    3.0.1    1.0.0d1    1.0.0d1    34    3.5.5    404    1.4.2    615.20.17    5.5.5    2.3.1    4.9.6    3.6.1b4    2.5.2    5.2.5    5.5.0    1.7    161.0.0    1.7    1.5    1.8    1.9    1.7    1.6    196.0.0    4.0.39    2.1    196.0.0    1.0    10.0.6    2.3.7fc4    1.8.9fc11    1.6    86.0.4    4.1.4f2    1.0.11d0    1.1.8    1.1.8    1.8.9    1.0.0    4.1.4f2    2.2.5    3.4.5    1.0.4    2.3.7fc4    2.3.7fc4    5.3.0d51    1.0.11d0    2.3.7    2.3.7    3.1.4d2    1.8.9    1.8.9    1.2.6    237.3    5.2.5    5.5.5    5.2.5    3.5.5    1.7    1.7.1    1.7.1    1.7.8    2.4.0    2.5.1    3.5.5    530.4    5.5.5    4.5.5    1.0.2b1    3.0    2.3.1    5.6.0    1.7    1.8.1    1.1    220.3    1.0.0d1    7    345    1.8    28.21    1.7    2.7.3    1.4    1.0
Model: MacBookPro8,1, BootROM MBP81.0047.B27, 2 processors, Intel Core i5, 2.3 GHz, 8 GB, SMC 1.68f99
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 512 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1333 MHz, 0x01BA, 0x202020202020202020202020202020202020
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1333 MHz, 0x01BA, 0x202020202020202020202020202020202020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (
Bluetooth: Version 4.1.4f2 12041, 2 service, 11 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: INTEL SSDSC2CW180A3, 180.05 GB
Serial ATA Device: MATSHITADVD-R   UJ-8A8
USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0xfa200000 / 3
USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0xfa100000 / 2
USB Device: BRCM2070 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0xfa110000 / 5
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821a, 0xfa113000 / 8
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0252, 0xfa120000 / 4
USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0xfd100000 / 2
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3

Is my RAM defective? Should I just revert back to the original 4GB RAM?


I tested the RAM several times and I couldn't find the problem. I think that the RAM must have been bad near the beginning of the sequence so it was hard to find, but I'm not really sure. I just went to the store and bought new RAM and now my Mac never crashes. Thank you everyone for all of the help.

If you are having the same problem that I was having, just get new RAM, it is a lot less trouble and it will save you hours of testing your RAM (which is not fun).

share|improve this question
Your RAM is fine, it is showing up correctly. –  Buscar웃 Sep 1 '13 at 22:31
Just because the ram shows up correctly, doesn't mean the ram isn't bad! Run a memory test to know for sure. –  spuder Sep 1 '13 at 22:45
That is a useful test for those who can get they computer operational at all. –  Buscar웃 Sep 1 '13 at 22:59
So is the RAM test a good idea? –  John Sep 1 '13 at 23:43
Wasting your time testing the new RAM. Simplest way is to reinsert the old RAM. If the machines runs fine, then you have ruled out that the new memory is faulty. It could be that your Mac doesn't like it (some models are notoriously finicky about memory) or that it is indeed just a bad stick(s). In any case, it isn't working for you so I'm not sure there is much of a point trying to isolate exactly why. A hardware fault can't be "fixed." –  user10355 Sep 3 '13 at 4:38

2 Answers 2

Your system identifies the RAM correctly:

Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1333 MHz, 0x01BA, 0x202020202020202020202020202020202020 Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1333 MHz, 0x01BA, 0x202020202020202020202020202020202020

However, there is another problem with your


Try fixing it with this:

  1. Restart system in safe mode.

  2. If that does not work restart in repair mode + R.

share|improve this answer
Once I have it in safe mode, then what do I do? –  John Sep 1 '13 at 23:43
I think Buscar meant that just starting up in Safe Mode and then rebooting normally fixes the problem. However, Buscar should clarify. –  sameetandpotatoes Sep 2 '13 at 0:22
I rebooted in safe mode and it was super slow, it took about 2 mins to boot when it usually only takes about 7 seconds. I logged in and waited a while and then rebooted. It hasn't crashed yet, I will accept this answer if it doesn't crash by tomorrow. –  John Sep 2 '13 at 1:43
Restarting in Safe mode allows os to get sorted out in the start up sequence (on the shutdown). Yours got stuck on the AppleIDAuthAgent (a keychain passwords -reason unknown). As for the RAM test, now you can actually do that since your computer is up and running. :) Enjoy your 8 gig. –  Buscar웃 Sep 2 '13 at 7:29
It crashed again today, i will try the RAM test. –  John Sep 2 '13 at 17:48

There are many reasons your Mac could crash.

To rule out memory, try running a memory test:

Additionally, you should double check that the ram you purchased runs at a supported latency. Use MacTracker or go to the website of the ram manufacture for a list of tested computers.

If you put the old ram back and the crashing stops, then that is as close to a smoking gun as you will find.

If the Memory test passes and putting the old memory back in don't fix it, the next place to look would be a corrupted OS


  • Repair permissions, verify disk
  • Boot into safemode (hold shift key while booting up your mac)
  • Disable all startup items and enable them a few at a time until the crashing returns
  • Create a new user account
  • If you have a spare hard drive, install a clean OS to it and boot from it temporarily.
share|improve this answer
I ran the RAM tester, it always says that my RAM is good but I don't think so. I think that there is a bad register somewhere near the beginning of the sequence, is there any way to use the RAM checker to check all of the RAM, not just the available RAM? –  John Sep 3 '13 at 16:39

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.