Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: Wockeez
Wockeez Author
User level: Level 1
0 points

Macbook Pro Slow and shut's down, Memory or HDD or Motherboard?

The last few months my Macbook Pro medio 2012 is starting to get slow. I was thinking of a reinstall but didn't have the time yet.

The last month it got really slow started to freeze and instantly shuts down. He restarts and then I get a light grey screen saying with the Icon (a map with a questionmark inside it) that he can't find the bootdisk/drive. I shut it down again with the button and restart, he then starts up normally. This would have me believe it has something to do with my HDD or with the motherboard but then again i'm not a tech guy so i'm just guessing really. Then I got the idea of doing a hardware test, with this error as outcome: 4MEM/62/40000000: 0x81d97590


After searching the web, this would mean my memory would be bad/broken. I read in another post to download an app called 'Remember' Which tests your RAM. I tried it yesterday and it worked fine, nothing was wrong. But today I did it again when my Macbook was running slow again and went to do some other stuff. When I came back my Macbook had a black screen saying something about insert a bootdisk. I just shut it down and restarted it again and started normally. He is somewhat slow at the light grey screen with the apple logo.


So my question is, does anyone know where the problem lies, the RAM, HDD or the motherboard? Will a reinstall also help? Should I check if my RAM is still placed correctly or maybe is dirty? I do use a app called Memory Monitor to clean the working memory from time to time. I didn't update to El Captain yet, wanted to do that instantly when I would do a clean install of my mac, but I think I'm gonna wait with that until I know where the problem lies.


Really hope someone can help me!


Kind regards,

Mike


This was the report about the shut down:


crash report


Anonymous UUID: 2DD0FAD1-4D38-B739-F019-9F395B5DB6AD


Sat Nov 28 17:54:55 2015


*** Panic Report ***

panic(cpu 0 caller 0xffffff80037c127e): "launchd died\nState at Last Exception:\n\n"@/SourceCache/xnu/xnu-2782.50.1/bsd/kern/kern_exit.c:363


uuid info:

0x7fff61d7e000 uuid = <b1b370a5-479f-3533-8ad7-97b687d4f989>

0x108fa1000 uuid = <c0446878-e8d0-3461-a226-91ff1c2b2da6>

0x108ff1000 uuid = <4396b358-725e-3ec0-bcbb-e4bf75fe1fb0>


RAX: 0x0000000002000001, RBX: 0x0000000000000006, RCX: 0x000000010a2800e8, RDX: 0x0000000000000000

RSP: 0x000000010a2800e8, RBP: 0x000000010a280190, RSI: 0x000000010a27ff40, RDI: 0x0000000000000001

R8: 0x0000000000000000, R9: 0x0000000108fe09f0, R10: 0x00007fff91399b02, R11: 0x0000000000000206

R12: 0x0000000000000000, R13: 0x00007fff9688d7e0, R14: 0x000000010a2805d0, R15: 0x000000010a280790

RFL: 0x0000000000000206, RIP: 0x00007fff9139795a, CS: 0x0000000000000007, SS: 0x0000000000000023


Thread 0xffffff8021e8a970

0x00007fff9768fdab

0x00007fff9768fec8

0x00007fff976893b4

0x00007fff9c109a6c

0x0000000108fcf907

0x00007fff96a7de73

0x00007fff96a80dc7

0x00007fff96a80a1c

0x00007fff942c5a9d

0x00007fff942c33dd

0x0000000000000000


Thread 0xffffff80220c1798

0x0000000108fb8c91

0x00007fff96a7de73

0x00007fff96a815cd

0x00007fff96a81030

0x00007fff96a80bef

0x00007fff96a80a1c

0x00007fff942c5a9d

0x00007fff942c33dd

0x0000000000000000


Thread 0xffffff8021e8a000

0x00007fff96a8226e

0x0000000000000000


Thread 0xffffff8021fb15c0

0x00007fff96a81925

0x0000000000000000


Thread 0xffffff803a4bd000

0x00007fff96a8a4e6

0x00007fff96a8293b

0x00007fff96a813bc

0x00007fff96a81030

0x00007fff96a80bef

0x00007fff96a821a3

0x00007fff942c605a

0x00007fff942c5fd7

0x00007fff942c33ed

0x0000000000000000


Thread 0xffffff8037edb2e0

0x00007fff8fbeaf1a

0x0000000000000001

0x00007fff61d8a475

0x00007fff907537b5

0x00007fff9765e648

0x00007fff9688d7e0

0x00007fff9688fddf

0x00007fff96a7de73

0x00007fff96a7e8ca

0x00007fff9688e0a7

0x0000000108fcc393

0x00007fff96a7de73

0x00007fff96a815cd

0x00007fff96a81030

0x00007fff96a813bc

0x00007fff96a81030

0x00007fff96a80bef

0x00007fff96a80a1c

0x00007fff942c5a9d

0x00007fff942c33dd

0x0000000000000000


Thread 0xffffff8025fd2e28

0x00007fff942c33dd

0x0000000000000000


Mac OS version: 14F1021

Kernel version: Darwin Kernel Version 14.5.0: Tue Sep 1 21:23:09 PDT 2015; root:xnu-2782.50.1~1/RELEASE_X86_64

Kernel UUID: 06D286E3-A8A1-3BE7-A7EB-EAC6E0C69758

System model name: MacBookPro9,1 (Mac-4B7AC7E43945597E)

MacBook Pro (15-inch Mid 2012), OS X Yosemite (10.10.5)

Posted on Nov 28, 2015 11:01 AM

Reply
Question marked as Best reply
User profile for user: Grant Bennet-Alder
Grant Bennet-Alder
User level: Level 10
127,195 points

Posted on Nov 28, 2015 2:13 PM

an app called 'Remember' Which tests your RAM. I tried it yesterday and it worked fine, nothing was wrong.


That is not the right way to think about memory problems. When ANY RAM test says there is a problem, it is telling you the truth. RAM problems are very hard to isolate, and if a diagnostic runs, but does not find the problem, that is NOT "nothing was wrong" that is "it could not find the problem right away."


This is not mystery. The component most likely to fail is the RAM DIMMs, not anything else. So you could try running Rember all night, you could try removing one of your DIMMs and see if the failures stop, you could try getting some new DIMMs and seeing if they work better.

View in context
2 replies
Question marked as Best reply
User profile for user: Grant Bennet-Alder
Grant Bennet-Alder
User level: Level 10
127,195 points

Nov 28, 2015 2:13 PM in response to Wockeez

an app called 'Remember' Which tests your RAM. I tried it yesterday and it worked fine, nothing was wrong.


That is not the right way to think about memory problems. When ANY RAM test says there is a problem, it is telling you the truth. RAM problems are very hard to isolate, and if a diagnostic runs, but does not find the problem, that is NOT "nothing was wrong" that is "it could not find the problem right away."


This is not mystery. The component most likely to fail is the RAM DIMMs, not anything else. So you could try running Rember all night, you could try removing one of your DIMMs and see if the failures stop, you could try getting some new DIMMs and seeing if they work better.

Reply
User profile for user: Wockeez
Wockeez Author
User level: Level 1
0 points

Nov 28, 2015 2:21 PM in response to Grant Bennet-Alder

Hey, thanks you for the response!

With the last crash, I was running 'Rember' in a loop. I'm gonna try to remove 1 of the SODIMM RAM and see if that works. If not I probably need to buy a new pair of RAM like this one: http://www.amazon.com/Crucial-DDR3L-1600-PC3-12800-CT2K8G3S160BM-CT2C8G3S160BM/d p/B008LTBJFW right?

I don't mind buying a new pair of RAM, but I want to minimize the chances that something else could be the problem. Because if it turns out to be the for instance the motherboard then it would be like flushing €90 through the toilet.


Thanks for your answer I'm gonna try it and let you know.


Kind regards,

Mike

Reply

Macbook Pro Slow and shut's down, Memory or HDD or Motherboard?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.
Learn more Sign up