Looks like no one’s replied in a while. To start the conversation again, simply
ask a new question.
Apple hardware test — error 4MEM/9/40000000: 0x84cdd498
My Macbook Pro early 2011 15″ model randomly shutdown the other day and since then has been in a reboot loop.
I am on OSX Yosemite.
I have already tried the following steps which haven’t worked:
— Reset PRAM
— Reset SMC
— Couldn’t go to recovery mode or safe mode
— Tried internet recovery mode
I have now just done an apple hardware test and it has detected this error:
4MEM/9/40000000: 0x84cdd498
Please can someone inform me of what the hardware error is.
Thanks
MacBook
Pro,
null
Posted on Apr 10, 2018 4:50 AM
Similar questions
-
MacBook Pro 17″ crashing and restarting
My Early 2011 17″ MacBook Pro, 2.3GHz Intel Core i7, 1TB SSD, 8GB DDR3, OS High Sierra 10.13.5, has started to crash and restart continuously and spontaneously. The screen image can fragment on start up and turns blue and/or grey but can recover to a normal state . I ran the extended Apple Hardware Test and it twice came up with Error Code 4MEM/66/40000000:0x84cfa818.It then says I should contact Apple Support but Apple do not support my Mac model as they regard it as redundant.Does anyone know what the error refers to?I would like to have some idea before I attempt to get it repaired.Thanks, Brian154
2
-
MacBook Pro crash
I recently bought my new Mac and I’m having trouble, it restarts for no reason …panic(cpu 8 caller 0xffffff800b58f8aa): «DSB0(MacBookPro16,1): thunderbolt power on failed 0xffffffff\n»@/System/Volumes/Data/SWE/macOS/BuildRoots/d7e177bcf5/Library/Caches/com.apple.xbs/Sources/IOPCIFamily/IOPCIFamily-428.120.4/IOPCIBridge.cpp:1433
822
5
-
macbook keeps restarting with an error
I have a 2017 MacBook 13 «256 ssd and I ran into this error.panic(cpu 2 caller 0xffffff7f8483e231): nvme: «Fatal error occurred. ID=0x843 ARG1=0xcc2d ARG2=0xe2 ARG3=0xe3 EDD0=0x10600000 EDD1=0x100000 EDD2=0x0 EDD3=0x1d400000 EDD4=0x0 EDD5=0x0 EDD6=0x0 EDD7=0x0 NANDV=0x2, DRAMV=0x2, SSDC=256GB. FW Revision=16.14.01\n»@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-470.100.17/IONVMeController.cpp:5320
Backtrace (CPU 2), Frame : Return AddressAttached a file with an error. Who knows, please help!
447
5
1 reply
Question marked as
★
Helpful
Apr 11, 2018 7:07 AM in response to epdcampbell
That’s a memory error. The cause could be anything from a bad socket, bad trace, or failing memory. Failing memory is the most likely. You can find instructions on how to access the memory here:
MacBook Pro: How to remove or install memory — Apple Support
I’d suggest trying out a single memory at a time to isolate which module or socket may be the issue. It should boot on a single module, although it’s not ideal. It’s kind of a logic problem isolating the issue.
3 replies
Apr 11, 2018 5:38 AM in response to epdcampbell
Hi there, epdcampbell!
Thanks for reaching out to the Apple Support Communities! It sounds like you are having an issue with an error code when you run the Apple Hardware Test and I am happy to assist. Based on the error message you are seeing, I recommend you check out this link to
Contact Support
. This will get you in touch with Apple and they will be happy to proceed with further steps.
Take care!
Apr 11, 2018 5:39 AM in response to epdcampbell
Using Apple Hardware Test https://support.apple.com/HT201257 — «Apple Hardware Test (AHT) contains a suite of diagnostics that will test the hardware of your computer. It’s a great way to rule out a hardware issue when troubleshooting your computer.» «Important: If your Mac was released after June 2013, you will use Apple Diagnostics rather than Apple Hardware Test (AHT). See Using Apple Diagnostics for instructions — http://support.apple.com/kb/HT5781«
Question marked as
★
Helpful
Apr 11, 2018 7:07 AM in response to epdcampbell
That’s a memory error. The cause could be anything from a bad socket, bad trace, or failing memory. Failing memory is the most likely. You can find instructions on how to access the memory here:
MacBook Pro: How to remove or install memory — Apple Support
I’d suggest trying out a single memory at a time to isolate which module or socket may be the issue. It should boot on a single module, although it’s not ideal. It’s kind of a logic problem isolating the issue.
Apple hardware test — error 4MEM/9/40000000: 0x84cdd498
| Текущее время: 21 сен 2023, 10:10 |
Сообщения без ответов | Активные темы
| Страница 1 из 1 [ Сообщений: 17 ] |
 |
 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Показать сообщения за: Поле сортировки
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
 |
Добавлено: 20 окт 2016, 13:55 
тем более, что это не так уж и сложно.
| Страница 1 из 1 [ Сообщений: 17 ] |
|
|
|||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||
|
|
| Вы не можете начинать темы Вы не можете отвечать на сообщения Вы не можете редактировать свои сообщения Вы не можете удалять свои сообщения Вы не можете добавлять вложения |
-
#1
Client’s Macbook Pro (Late 2012, A1425) won’t boot. Shows the splash screen, shows a status bar that gets to the end but as soon as it gets to the end the computer turns off.
Running diagnostics returns:
4mem/9/40000000
I’m assuming this is an issue with the memory that is soldered to the logic board. Is there anything I can do other than replace the logic board?
Thanks!
Brian
-
#2
Yeah it’s RAM. Nothing you can do to fix the issue other than replacing the MLB, I’m afraid.
-
#3
That is indeed a memory diagnostics issue return code. Might be worth to check the memory
-
#4
keysofanxiety: Thank you. I am sure you are right, but I want to get a few more people’s opinions before I order a board. I agree with you though.
Floris: What? What do you mean check the memory?
-
#5
keysofanxiety: Thank you. I am sure you are right, but I want to get a few more people’s opinions before I order a board. I agree with you though.
Floris: What? What do you mean check the memory?
Try to see if you can do a memory test? Or ask Apple what your options are about swapping the memory?
-
#6
Try to see if you can do a memory test? Or ask Apple what your options are about swapping the memory?
The system’s a 13″ rMBP unfortunately, can’t just swap the memory as it’s all soldered. New memory would mean new Logic Board
OP, you could try MemTest x86 to be doubly sure – if you make a bootable USB on FAT32, it does run on Macs when holding ‘Alt’ on startup.
-
#7
The system’s a 13″ rMBP unfortunately, can’t just swap the memory as it’s all soldered. New memory would mean new Logic Board
![:(]( "Frown :(")
I see, yeah, you can ask Apple to confirm the issue and request them the price on having them swapping it.
-
#8
My bad, I thought I had explained that. Yea, the memory is soldered to the board. Can’t change it out. Testing it at this point is futile since that code I got was from the MBP’s onboard diagnostic.
-
#9
New Motherboard didn’t fix the issue.
-
#10
Actually.. The issue I described where it wouldn’t boot was due to an OS corruption, reinstalling OS fixed that. But there was also a motherboard issue with the RAM, and thats what the diagnostics was picking up. After the OS reinstallation, it would kernal panic and reboot.
So we’re good! Now the battery doesn’t detect though.
Hope my experience with the Apple Hardware Test Error Code 4MEM/9/40000000: 0x82d09d18 helps you fix your Mac issue.
Background: I have a late 2011 15″ Macbook Pro. I saw graphic anomalies over the last few years, but didn’t think much of it. Saw a few articles on the problems associated with the late 2011 Macbooks, but didn’t think much of it until I saw that Apple was owning up to the issue and offering warranty work for free even if your Macbook Pro was out of warranty. So a few months ago, I brought the computer in, and they replaced the Logic Board free of charge, but noted an error associated with my third party ram.
As soon as I took it home, I immediately noted that the graphics fan was spinning up for no good reason. And after a few months the graphic anomalies started reappearing. So a couple days ago I brought the Laptop in again to the Apple Store to have it checked out. I was assuming the Logic Board would be the issue again (and still do eventually), but the only issue that they could find was that the “third party ram failed”.
Further Testing and Conclusion: That didn’t make sense to me, so when I brought the Notebook home, I proceeded to perform tests by clicking the option d keys at startup. I first did the quick tests with just one stick of ram at a time as I wanted to figure out which ram was “corrupted”. The simple tests brought back no errors. So I performed the extended tests on each stick of ram, which takes about an hour, and again both sticks of ram came back without errors. So I tried Apple Hardware Test with both sticks of ram, a total of 16GB, and within a few minutes it came back with the Mac error code 4MEM/9/40000000: 0x82d09d18. At this point I remembered reading the other day when I was checking on my Macbook Order from back in 2011 before bringing back to the Apple Store for testing, that the Macbook Pro Model Number FC721LL/A lists the Maximum Ram allowed as being 8GB. Conclusion then for this error, is that the error is solely the result of having more ram installed than what the Laptop is listed as allowing. I have since removed one of the 8GB sticks of Ram and have yet to see any graphic anomalies or had the graphic fan spin up for no reason. I’d be amazed if removing a stick of ram is going to solve the graphic anomalies that looked exactly that same as the ones that required my MacBook Logic Board replacement, but I’d be more than happy if it did.
Additional Update December 8th/2015: It’s been 2 months since I removed the extra ram for my Macbook Pro, and so far there have been no additional visual abnormalities or odd graphics showing up on the screen. All is good.
Another Update September 26th/2017: It’s been almost 2 years since I removed the extra stick of ram from my Macbook Pro, and no additional visual abnormalities or odd graphics have returned, glad I was wrong thinking they would return.
[Sidenote] A few months ago I was having some problems with my Macbook, a lot of spinning color wheel, graphics card spinning up, and screen freezing…turns out it was Firefox that was causing the problems after they updated the underlying code of their browser, since then I’ve switched to Chrome and Safari and those problems have stopped.
Do you have an experience with this or a similar Mac hardware error, let me know how you solved the error.
My MacMini, which I bought new around Thanksgiving 2010 from Amazon, has been having quite a few kernel panics. They aren’t consistent in any way, but they have become more frequent and now many apps seem to be crashing more as well and I have also noticed Spotlight and Alfred have become painfully slow.
I was about to reinstall Snow Leopard and start from scratch after making a SuperDuper clone on an external for backup when I read on the Apple CD that you can run an «Apple Hardware Test» by holding «D» during startup.
I figured it was worth checking out. Especially since my memory is non-original. I had put 2x 4GB Corsair sticks in it right away that I also got from Amazon a few months before then which I had used in my previous early-2009 MacMini. The memory seemed to have worked fine in both computers. All 8 GB were being recognized. These kernel panics only started happening a few months ago.
Now the Apple Hardware tests, which I tried in every conceivable configuration; swapping slots, removing one then the other etc., did in fact show errors. I wrote down two of the error codes. I believe there were only two unique codes; I suppose the different stick arrangements I used is cause for the variances, but it’s possible there were more, but I know for a fact they all started out with the same characters, 4MEM/9/40000000: .
4MEM/9/40000000: 0xa90c1418 & 4MEM/9/40000000: 0xa95de698
However, the strange thing is the Apple Hardware Test only showed this error when I had BOTH sticks installed; either stick in either slot on it’s own showed no error. As I mentioned earlier, I tested all possible configurations because I had read that sometimes it could be a faulty slot.
So, with that information, does anyone have an idea how to fix my Mac. Do I need to replace one or both sticks? Is it something else? Is there an app I can use to help diagnose the issue?
As I’m writing, I realized I can still try using both the original sticks that came with the Mac at the same time, but I need to find them. I may wait until tomorrow to try that.