Error 0x80000000000003 cannot load efi drivers test support efi ошибка

MacBook Pro 2013 — cannot load Apple Hardware Test

MacBook Pro 15″,

macOS 10.12

Posted on May 17, 2019 3:59 PM

Error: 0x8000000000000003, Cannot Load ‘EFI/Drivers/TestSupport.efi’ encountered while trying to run diagnostics

What is the meaning of this error and how can it be resolved?

Posted on Aug 2, 2022 4:15 AM

Similar questions

Loading page content

Page content loaded

Unless you can upgrade macOS to a newer version, then there is nothing you can do about this error when trying to run the Apple Diagnostics. A system firmware update to your Mac has rendered the system firmware and the diagnostic boot files located on the Apple server to be incompatible. Apple would need to either update the system firmware or update the diagnostic boot files on their server. This issue has existed for many years now, so I would not expect it to be fixed by Apple after all this time.

If you are having problems with your Mac, then there are other ways we can help you to diagnose the problem. You will need to provide the exact model of the Mac and version of macOS used as well as some background of the problem and the symptoms. If the Mac can boot, then running EtreCheck and posting the report here using the «Additional Text» icon will help us assess your computer. If necessary we may also be able to provide other methods of checking some of the hardware depending on the problem and the exact model of Mac. If you cannot boot normally, then try booting into Safe Mode.

Here is another Apple article for troubleshooting various startup issues (Apple assumes everything is a software issue unless all steps fail to resolve the issue or a clean install fails):

Источник

testsupport.efi error after new installs

ok so, i have a mbp 9.2 mid 2012 that i tried to reset completely to get usernames etc sorted properly, how ever after i do the reset process using d at power on, i run in to a error saying

Error: 0x8000000000000003, Cannot Load ‘EFI/Drivers/TestSupport.efi’

this was after i had wiped my disk drive with the disk utility

to remedy this i had to make a usb thumbdrive with the sierra installer

mentioned for this error plenty of times in this community.

now even after installing sierra from this method i am unable to use the actual web recovery from power on + D

returning again with the error from above.

i am trying to settle this error so i can actually recover my mbp in case of future mishaps from the online recovery platform, so all help would be appreciated.

Posted on May 27, 2019 8:30 PM

Your Mac is too old to use the Apple Diagnostics loaded over Internet Recovery.

You need Apple Hardware Test. That can be problematic. It is on the disk when shipped by Apple, and is on your original release DVD set (if so supplied). But there is no software that makes certain it is RE-Installed if you replace or erase your drive.

A User has put together a whole lot of versions of Apple Hardware Test and a procedure for making a bootable USB-stick:

Posted on May 27, 2019 10:51 PM

Similar questions

Loading page content

Page content loaded

Your Mac is too old to use the Apple Diagnostics loaded over Internet Recovery.

You need Apple Hardware Test. That can be problematic. It is on the disk when shipped by Apple, and is on your original release DVD set (if so supplied). But there is no software that makes certain it is RE-Installed if you replace or erase your drive.

A User has put together a whole lot of versions of Apple Hardware Test and a procedure for making a bootable USB-stick:

Источник

Mac keeps crashing — error 0x8000000000000003 cannot load EFI/Drivers/TestSupport.efi

I was using my Mac to copy my WhatsApp account from an iPhone to an Android phone, but it «crashed in the middle». after some struggle I managed to finish the operation and switch of WhatsApp data.

ever since my Mac keeps crashing very often and won’t open my mail application.

apparently something went wrong in the process and I am not sure about how bad it is and more importantly how to fix.

I am enclosing copies of the various error messages I got.

any help would be highly appreciated.

MacBook Air 13″, macOS 10.15

Posted on Dec 10, 2020 6:55 AM

Similar questions

Loading page content

Page content loaded

I don’t know anything about transferring accounts between an iPhone and Android. I’m not sure it is possible using the method you were using.

As for the pictures of the two errors:

1) That is a common error when trying to boot the Apple Diagnostics. Apple broke this feature several years for some systems.

2) That screen with the different languages is a Kernel Panic. Without a copy of the Kernel Panic log we cannot tell what the problem may be.

3) You have APFS file system issues that First Aid is unable to repair. This means you need to make sure to have a good backup or clone. Then erase the whole physical drive before restoring from a backup or clone.

thank you for taking the time to respond.

1) anything I can or should do ?

2) can I find the log somewhere on my Mac and if so, share it with you and/or anyone who can work something out of it ?

3) shall I do a full back-up or only what I want to keep ? isn’t the risk that when I restore, the bad documents or what was the source of the issue, gets restored as well ?

thank you for taking the time to respond.

1) anything I can or should do ?

Not unless your Mac can run a newer version of macOS which may install a newer system firmware update that may resolve the issue. Part of the issue may be on Apple’s remote servers as well.

2) can I find the log somewhere on my Mac and if so, share it with you and/or anyone who can work something out of it ?

You can try looking in «/Library/Logs/DiagnosticReports» for a file beginning with «kernel» and ending in «.panic». The date & time of the file is found in between those parts of the file name. Post several Kernel Panic reports if you have them. Post the report(s) here using the «Additional Text» icon which looks like a piece of paper.

To look for possible software issues run EtreCheck and post the report here using the «Additional Text» icon which looks like a piece of paper. It is possible the file system issues are the source of the problems.

3) shall I do a full back-up or only what I want to keep ? isn’t the risk that when I restore, the bad documents or what was the source of the issue, gets restored as well ?

When you restore from a backup or «clone» the files are copied over to your drive which will have a fresh clean file system if it was erased. The «cloning» utilities for macOS such as Carbon Copy Cloner do not perform an identical clone at the block level so CCC just ends up «copying» the files from the clone (image or drive). I don’t use Time Machine, but I think if you have a Time Machine backup you will first need to re-install macOS and migrate your data from the backup since I’ve heard TM only recovers the main volume and not the hidden recovery partition. Here is how you erase the whole drive:

Источник

MacBook Pro 2013 — cannot load Apple Hardware Test

MacBook Pro (Retina, 15-inch, Early 2013): When I try to load Apple Hardware Test from the Internet (startup with D key), it doesn’t start, but shows a message:

Error: 8000000000000003, Cannot load ‘EFI/Drivers/TestSupport.efi’

Which sits there for about five minutes, then it restarts into MacOS.

Same result when I try to run AHT from a USB stick, except this time it shows the above message twice – flashing by so quickly I had to get a video of it to see what it said – then immediately restarts into MacOS.

The OS version of Apple Service Diagnostic works okay (it has an OS on it, and shows in the Startup Disk preference Pane), but the EFI version gives the same result as above.

I’ve reset the SMC and NVRAM, and reinstalled the OS (Sierra) numerous times, to no avail.

I ran both AHT (Internet & USB) and ASD/EFI successfully a couple times only a few months ago; something’s changed, but I can’t figure out what.

However, MemTest86 (which also starts up from an EFI driver from a USB stick) still works fine with the MacBook Pro. So it seems this MBP is now somehow allergic to Apple’s own EFI driver?

The same hardware (USB stick for AHT, external HD or USB stick for ASD) works fine with four other Mac portables, and two of them can access Apple Diagnostic (the 2014 & later version of AHT) from the Internet as they’re supposed to (the others are too old to do so). So the problem is definitely something in this MacBook Pro.

The MBP was showing other problems as well; I sent it to a repair service, who said the GPU needed fixing (apparently common in this model), which they did, and said the logic board now tested all good. But it still «Cannot load ‘EFI/Drivers/TestSupport.efi’».

I spoke with somebody at Apple Support, who was mystified, suggested maybe it had something to do with the SSD? The SSD seems to work fine otherwise, starts up okay etc., and DriveDx (which gives detailed readout of SMART parameters) says it is good.

Anybody have any idea what the problem might be? I plan to sell this MBP, but can’t do so in good conscience as it is, even if it seems to be working okay otherwise.

Источник

cannot load efi/drivers/testsupport.efi — iMac 21.5″ late 2012

My wife’s computer has been extremely slow for the past year. She opens an application and she gets the spinning wheel, app opens. Eventually. And if she tries to open another app, same thing happens. Opening new tabs in a web browser is equally frustrating.

I tried to run a hardware test by holding D at startup and a little earth sphere showed up followed by:

Error: 0x8000000000000003, Cannot load efi/drivers/testsupport.efi

In looking around this seems to be a common issue. Taking it to an Apple store isn’t an option for us.

running Catalina 10.15.7

Posted on Feb 19, 2021 5:01 PM

Similar questions

We understand you’re not getting the performance you’d expect on your iMac and we’ll do all we can to help out.

Sounds like you attempted to run Apple Diagnostics on this iMac, but it failed to run. As suggested under the ‘Learn more’ section in the following article Use Apple Diagnostics to test your Mac,

«On an Intel-based Mac, if you can’t start Apple Diagnostics with the D key, try these solutions:

• Press and hold Option-D at startup to use Apple Diagnostics over the internet.
• Make sure that your Mac isn’t using a firmware password.»

If the report comes back with no issues found, we would suggest focusing on this article If your Mac runs slowly, which can help resolve performance issues on Mac. When you open this link, be sure to choose your macOS version under the ‘Select Version’ drop-down menu at the top of the article.

We hope this information helps out.

Thanks for the update. If you’re unable to complete a diagnostics to isolate the issue further, it would be best to get in contact with Apple Support from here. They can be reached using this link: Get Support

Loading page content

Page content loaded

We understand you’re not getting the performance you’d expect on your iMac and we’ll do all we can to help out.

Sounds like you attempted to run Apple Diagnostics on this iMac, but it failed to run. As suggested under the ‘Learn more’ section in the following article Use Apple Diagnostics to test your Mac,

«On an Intel-based Mac, if you can’t start Apple Diagnostics with the D key, try these solutions:

• Press and hold Option-D at startup to use Apple Diagnostics over the internet.
• Make sure that your Mac isn’t using a firmware password.»

If the report comes back with no issues found, we would suggest focusing on this article If your Mac runs slowly, which can help resolve performance issues on Mac. When you open this link, be sure to choose your macOS version under the ‘Select Version’ drop-down menu at the top of the article.

We hope this information helps out.

I confirmed that the iMac in question is NOT using a firmware password. And I also tried the Option-D at startup and I’m still getting the same error as before and unable to run Apple Diagnostics.

Error: 0x8000000000000003, Cannot load efi/drivers/testsupport.efi

Thanks for the update. If you’re unable to complete a diagnostics to isolate the issue further, it would be best to get in contact with Apple Support from here. They can be reached using this link: Get Support

Thank you again. I got the ole’ «obsolete technology» response. They couldn’t help troubleshoot my original problem of not being able to run Apple Diagnostics (hardware test).

Take it to an independent AASP, they may be able to help you out. If you don’t know of any in your area please use the following link to find one.

She told me since my machine was obsolete technology, they wouldn’t have the parts to fix it.

Unfortunately with some system firmware revisions the online Apple Diagnostics are broken. Perhaps upgrading macOS will provide an updated firmware that works with the online diagnostics.

The two most common problems for a slow iMac is a software issue or more likely a failing hard drive. Run EtreCheck and DriveDx and post the reports here using the «Additional Text» icon which looks like a piece of paper.

Assuming your Mac has the standard configuration, it means that you have a super slow 5400 rpm spinning drive which does everything at a snail’s speed. There is nothing one can do about that except get an external SSD, clone your system to it and use that as your main boot drive. That is, unless your hard drive is failing — in which case an authorized service provider may replace the old spinning drive with an SSD.

Here are install videos for a late 2012 21.5″ iMac:

Running an etrecheck report first would be helpful.

Looking at your etrecheck, a couple of things:

First you have this useless stuff installed:

Get the uninstall instructions from their website and delete it. It is worthless and will slow down your computer.

And, you still have Flash Player installed — go to the Adobe website and uninstall it. It has been discontinued.

You also have Gatekeeper disabled. Not a good idea — consider changing that back to the setting it should be.

And, I was right about your slow hard drive and the minimal RAM.

I will leave the analysis of the DriveDx report in the very capable hands of HWTech as I’m not that familiar with it.

Your hard drive is worn out as the hard drive has an extremely high «Load Cycle Count» (attribute# 193) that is at almost 2M (most drive manufacturers have a lifetime limit about 800K). Whenever the «Load Cycle Count» gets near or exceeds the manufacturer’s lifetime expectations I find hard drives tend to slow down and have other odd behaviors.

Since the hard drive is just worn out and does actually have any bad blocks you could easily clone the system to an external USB3 drive and boot from an external drive to continue using your iMac without needing to open the iMac. After cloning the drive and confirming the external drive is working properly you can erase the internal drive so macOS doesn’t get confused since I have seen macOS inadvertently access items on the other drive which can be dangerous (It is best to unmount or eject the internal drive to confirm the external drive is working fine on its own and not accessing anything from the internal drive before erasing the internal drive). Another option is to perform a clean install of macOS on an external drive and migrate just the user account(s) and manually reinstall the third party apps.

Источник

I attempted to run Diagnostics, but it did not work and I found I had lost the “.diagnostics” folder when I wiped the hard drive.

When you reinstall, Apple Diagnostics will get reinstalled as well. If it’s missing, it calls into question how you did said reinstall. Booting from Recovery, wiping the drive and installing macOS will leave a pristine, fully functional version of macOS on your drive. If you’re missing things, this was an “out of band” re-install (meaning non-standard). When that happens, you’ll have the devil’s own time trying to pinpoint the cause of your troubles.

I followed the instructions in this post (Replacing «apple hardware test» with «apple diagnostics») but the problem

No! Don’t do this! First off, Apple has diagnostic procedures specific to their machines. You can’t “willy-nilly” change them because you feel one is better than the other. Even when you upgrade, Apple doesn’t change your diagnostics. For example, a Mid 2012 MacBook Pro which is capable of running Catalina still uses AHT. Catalina doesn’t upgrade it to Apple Diagnostics.

How do we know this?

Apple tells us in their support document How to use Apple Diagnostics on your Mac:

If your Mac was introduced before June 2013, it uses Apple Hardware Test instead.

Secondly, it’s well known that Apple’s diagnostics lose usability with each subsequent version, so “upgrading” to a later version will actually give you less useful diagnostic data.

Use Internet Diagnostics

Your Mac has the ability to boot from Internet Recovery; it should also have the ability to boot Internet Diagnostics. Boot your computer while holding OptionD (obviously you need an Internet connection). This will ensure that you download and use the correct diagnostic utility for your Mac.

Do a clean, proper install of macOS

Based on what you described, it sounds like your install is a bit of a bodge. My advice is to clean things up so you’re working on a solid footing.

1. Back up your data. Verify that it’s good
2. Wipe your drive clean
3. Install the latest version of macOS (Mojave if you need 32-bit app support; Catalina if not necessary)
4. Make sure Recovery (hold CommandR) and Diagnostics(hold D) works
5. Here, step 5, is where we’re going to figure out what’s causing your crashes.
6. Once you have a stable system, use Migration Assistant to move your data over.
7. Verify that everything is working as it should. If so, immediately make a backup and verify.

I attempted to run Diagnostics, but it did not work and I found I had lost the “.diagnostics” folder when I wiped the hard drive.

When you reinstall, Apple Diagnostics will get reinstalled as well. If it’s missing, it calls into question how you did said reinstall. Booting from Recovery, wiping the drive and installing macOS will leave a pristine, fully functional version of macOS on your drive. If you’re missing things, this was an “out of band” re-install (meaning non-standard). When that happens, you’ll have the devil’s own time trying to pinpoint the cause of your troubles.

I followed the instructions in this post (Replacing «apple hardware test» with «apple diagnostics») but the problem

No! Don’t do this! First off, Apple has diagnostic procedures specific to their machines. You can’t “willy-nilly” change them because you feel one is better than the other. Even when you upgrade, Apple doesn’t change your diagnostics. For example, a Mid 2012 MacBook Pro which is capable of running Catalina still uses AHT. Catalina doesn’t upgrade it to Apple Diagnostics.

How do we know this?

Apple tells us in their support document How to use Apple Diagnostics on your Mac:

If your Mac was introduced before June 2013, it uses Apple Hardware Test instead.

Secondly, it’s well known that Apple’s diagnostics lose usability with each subsequent version, so “upgrading” to a later version will actually give you less useful diagnostic data.

Use Internet Diagnostics

Your Mac has the ability to boot from Internet Recovery; it should also have the ability to boot Internet Diagnostics. Boot your computer while holding OptionD (obviously you need an Internet connection). This will ensure that you download and use the correct diagnostic utility for your Mac.

Do a clean, proper install of macOS

Based on what you described, it sounds like your install is a bit of a bodge. My advice is to clean things up so you’re working on a solid footing.

1. Back up your data. Verify that it’s good
2. Wipe your drive clean
3. Install the latest version of macOS (Mojave if you need 32-bit app support; Catalina if not necessary)
4. Make sure Recovery (hold CommandR) and Diagnostics(hold D) works
5. Here, step 5, is where we’re going to figure out what’s causing your crashes.
6. Once you have a stable system, use Migration Assistant to move your data over.
7. Verify that everything is working as it should. If so, immediately make a backup and verify.