User profile for user: manjotgwl
manjotgwl Author
User level: Level 1
4 points

MacBook Pro M3 crashing with ANE errors after macOS Tahoe 26.0.1 update

I have a M3 MacBook Pro, I recently upgraded to macOS Tahoe 26.0.1 and ever since then I've had this issue. It first started by crashing out of the blue, then it would restart, make me enter my password again and on the log in loading bar, it would crash again. This happened infinitely until instead of logging in, I shut down and then boot in via safe mode. If I look at the system reports, it's usually a core panicking or some issue with ANE (Apple Neural Engine) not responding or failing to idle, or timing out.


Here are some snippets of panic logs


1) 

{"bug_type":"210","timestamp":"2025-10-09 00:26:53.00 -0700","os_version":"macOS 26.0 (25A354)","roots_installed":0,"incident_id":"D3389F70-B4BE-4387-B37C-E8F9A948C6CA"}
{
  "crashReporterKey" : "[REDACTED]",
  "panicProcessingFlags" : "0x0",
  "product" : "Mac15,6",
  "kernel" : "Darwin Kernel Version 25.0.0: Mon Aug 25 21:17:56 PDT 2025; root:xnu-12377.1.9~3/RELEASE_ARM64_T6030",
  "socRevision" : "11",
  "panicString" : "panic(cpu 0 caller 0xfffffe004f91f88c): Sleep transition timed out after 35 seconds while notifying clients about upcoming system capability changes. Suspected bundle: com.apple.driver.AppleH11ANEInterface. Thread 0x7c."
}


2) 

{"bug_type":"210","timestamp":"2025-10-09 00:31:04.00 -0700","os_version":"macOS 26.0 (25A354)","roots_installed":0,"incident_id":"2004667D-5C8B-44F4-A6B3-F4D63BDDF4AD"}
{
  "crashReporterKey" : "[REDACTED]",
  "panicProcessingFlags" : "0x0",
  "product" : "Mac15,6",
  "kernel" : "Darwin Kernel Version 25.0.0: Mon Aug 25 21:17:56 PDT 2025; root:xnu-12377.1.9~3/RELEASE_ARM64_T6030",
  "socRevision" : "11",
  "panicString" : "panic(cpu 2 caller 0xfffffe00427a9d10): \"ANE failed to become idle (0x00000008) in 10ms\" @AppleA7IOP.cpp:357"
}


3) 

{"bug_type":"210","timestamp":"2025-10-09 23:15:39.00 -0700","os_version":"macOS 26.0.1 (25A362)","roots_installed":0,"incident_id":"198274B7-F478-4B7E-A881-65E16658DD5A"}
{
  "crashReporterKey" : "[REDACTED]",
  "panicProcessingFlags" : "0x0",
  "product" : "Mac15,6",
  "kernel" : "Darwin Kernel Version 25.0.0: Wed Sep 17 21:41:50 PDT 2025; root:xnu-12377.1.9~141/RELEASE_ARM64_T6030",
  "socRevision" : "11",
  "panicString" : "panic(cpu 6 caller 0xfffffe004268e908): \"ANEHWDevice::Failed to validate ANE register offset 0xc008 with expected value: 0, read register value: 0xff\" @ANERegisterControl.cpp:177"
}


Any insight helps.


Thanks




[Re-Titled by Moderator]

Original Title: Mac crashing

MacBook Pro 14″

Posted on Oct 9, 2025 11:41 PM

Reply
Question marked as Top-ranking reply
User profile for user: Grant Bennet-Alder
Grant Bennet-Alder
User level: Level 10
139,103 points

Posted on Oct 10, 2025 1:04 PM

Not caring about your files is unusual, but you know best.


In this case, where a never-seen-before hardware issue is suspected, you will likely need to follow ALL the steps I mention here:


General debugging tips:

Make certain you have applied all available software updates, because no one is willing to debug a problem that might have been seen and solved already.


Then you need to go through the “regular" steps to eliminate added software as the cause of the problem:


• Run In Safe Mode, where no third-party add-ons are loaded

• create a new "clean" User account, and run with that to eliminate contamination in your regular User account

• run the diagnostic to check for GROSS issues. "no fault found" is not the same as "all is well".


You are seeing kernel panics, but they are showing in your Etrecheck report. Otherwise you would need to find and post a panic report.


Telephone Support:

The telephone support people are more likely to work with you. They will insist that you go through the motions to eliminate software issues. But when they get to the end of their list, Do NOT allow them to tell your it’s fine or there is nothing more they can do for you!


You should insist on having your problem escalated to a specialist. Specialists are more likely to actually read your panic other reports. If still no resolution, ask them to start a formal, tracked Bug Report on your behalf. If they think this might be a Hardware problem they can DIRECT an Apple service provider to swap things (likely mainboard) for a new one.


Apple support does appreciate what we do as Volunteers here on the forums. They can and should read what has already been posted. Be sure to tell them where they can read it. But they do NOT take our conclusions at face value -- they have their own more rigorous procedures they follow.


You MUST have a Trusted backup before submitting your Mac for service. if the mainboard is swapped out, the boot drive will be swapped out as well, and you will not get your files back.


Genius Bar:

if you take it to an Apple service provider first, they CAN run their diagnostics, which are a bit more comprehensive than the User diagnostics. In the very small amount of time they are run, “No faults detected” still does not mean “All is Well” but at least there are no detected GROSS problems. Unless they can find a fault, they will return your computer unchanged. Genius Bar technicians are NOT trained to read panic reports and computer logs.


When you present your computer at the Genius Bar with the expectation of a quote to repair it, you must generally meet these criteria:


• your Mac won't do anything

• your Mac fails diagnostics

• your Mac has a problem you can repeatably demonstrate on demand

one other oddball case:

• Apple online support has DIRECTED a Service Provider to replace specific components inside your Mac, such as the mainboard or display. Bring proof, such as case number.


View in context
12 replies
Question marked as Top-ranking reply
User profile for user: Grant Bennet-Alder
Grant Bennet-Alder
User level: Level 10
139,103 points

Oct 10, 2025 1:04 PM in response to manjotgwl

Not caring about your files is unusual, but you know best.


In this case, where a never-seen-before hardware issue is suspected, you will likely need to follow ALL the steps I mention here:


General debugging tips:

Make certain you have applied all available software updates, because no one is willing to debug a problem that might have been seen and solved already.


Then you need to go through the “regular" steps to eliminate added software as the cause of the problem:


• Run In Safe Mode, where no third-party add-ons are loaded

• create a new "clean" User account, and run with that to eliminate contamination in your regular User account

• run the diagnostic to check for GROSS issues. "no fault found" is not the same as "all is well".


You are seeing kernel panics, but they are showing in your Etrecheck report. Otherwise you would need to find and post a panic report.


Telephone Support:

The telephone support people are more likely to work with you. They will insist that you go through the motions to eliminate software issues. But when they get to the end of their list, Do NOT allow them to tell your it’s fine or there is nothing more they can do for you!


You should insist on having your problem escalated to a specialist. Specialists are more likely to actually read your panic other reports. If still no resolution, ask them to start a formal, tracked Bug Report on your behalf. If they think this might be a Hardware problem they can DIRECT an Apple service provider to swap things (likely mainboard) for a new one.


Apple support does appreciate what we do as Volunteers here on the forums. They can and should read what has already been posted. Be sure to tell them where they can read it. But they do NOT take our conclusions at face value -- they have their own more rigorous procedures they follow.


You MUST have a Trusted backup before submitting your Mac for service. if the mainboard is swapped out, the boot drive will be swapped out as well, and you will not get your files back.


Genius Bar:

if you take it to an Apple service provider first, they CAN run their diagnostics, which are a bit more comprehensive than the User diagnostics. In the very small amount of time they are run, “No faults detected” still does not mean “All is Well” but at least there are no detected GROSS problems. Unless they can find a fault, they will return your computer unchanged. Genius Bar technicians are NOT trained to read panic reports and computer logs.


When you present your computer at the Genius Bar with the expectation of a quote to repair it, you must generally meet these criteria:


• your Mac won't do anything

• your Mac fails diagnostics

• your Mac has a problem you can repeatably demonstrate on demand

one other oddball case:

• Apple online support has DIRECTED a Service Provider to replace specific components inside your Mac, such as the mainboard or display. Bring proof, such as case number.


Reply
User profile for user: Grant Bennet-Alder
Grant Bennet-Alder
User level: Level 10
139,103 points

Oct 10, 2025 12:54 PM in response to manjotgwl

if your computer is eventually determined to have a Hardware problem, the mainboard will be repaired. Apple does not do ANY field repairs of customer mainboards, they are simply replaced with an equivalent board to get your computer working again quickly and easily.


Unfortunately, the drive with all your files on it is soldered to the mainboard, so all your files will be discarded in the process.


If you do not have a recent local, disk-based backup, your computer is like a ticking Time bomb. You are only one disk failure, one mainboard failure, one crazy software, or one "oops" away from losing EVERYTHING! Drives do not last forever. It is not a question of IF it will fail, only WHEN it will fail. In addition, you never know when crazy software or Pilot Error throws away far more than you intended.


If you are using another direct-to-disk backup method that you prefer, and you currently have a recent disk-based backup, that is great. If not, you should consider using Built-in Time Machine. Take steps to acquire an external drive as soon as possible. If you buy one, a drive 2 to 3 times or larger than your boot drive is preferable for long term trouble-free operation. Do not pay extra for a drive that is fast.  (You can get by for a while with a "found" smaller drive if necessary, but it will eventually become annoying).


Attach your external drive and use

Settings > General > Time machine ...


... to turn on Time Machine and specify what drive to store your Backups on.  It may ask to initialize the new drive, and that is as expected. APFS format is default format if running MacOS 11 Big Sur or later.


Time machine works quietly and automatically in the background, without interrupting your regular work, and only saves the incremental changes (after the first full backup). Time machine backs up your machine — including every connected drive that is in a Mac compatible format. it can not back up Windows format drives.


Time Machine's "claim to fame" is that it is the backup that gets done. It does not ruin performance of the rest of the computer while doing its backup operations. You do not have to set aside a "Special Time" when you only do backups. When you need it, your Time machine Backup is much more likely to be there and be current.


How to use Time Machine to Backup or Restore your Mac:

Back up your Mac with Time Machine - Apple Support


Reply
User profile for user: Grant Bennet-Alder
Grant Bennet-Alder
User level: Level 10
139,103 points

Oct 10, 2025 12:10 PM in response to manjotgwl

You should run the user diagnostic.


Use Apple Diagnostics to test your Mac - Apple Support


Result code ADP000 says that in the very small amount of time allotted, using the extremely limited set of tests built-in, no hardware faults were detected. That is a far cry form "All is Well"



¿What is the date of your most recent backup of all your files, and by what method?

Reply
User profile for user: Barney-15E
Barney-15E
User level: Level 10
121,646 points

Oct 10, 2025 6:04 PM in response to manjotgwl

manjotgwl wrote:

this crashing problem only happens like once every day and I really don't know what's wrong. I think this has to be a software related issue, I will probably just back it up and factory reset it or something.

You don't need to wipe out the OS. It is mounted read only from a sealed snapshot that cannot be modified. You have a third-party software problem. You can Erase all contents and settings, then when you migrate from your backup, do not migrate any apps. You may be better served creating a dummy account where you don't migrate anything. Just see if it works correct.

Despite all of the evidence, if you think it is an OS problem, then just reinstall macOS. No need for global thermonuclear war unless you want to play a game.

Reply
User profile for user: Grant Bennet-Alder
Grant Bennet-Alder
User level: Level 10
139,103 points

Oct 10, 2025 4:21 PM in response to manjotgwl

panic(cpu 6 caller 0xfffffe004268e908): "ANEHWDevice::Failed to validate ANE register offset 0xc008 with expected value: 0, read register value 0xff\


panic(cpu 2 caller 0xfffffe00427a9d10): "ANE failed to become idle (0x00000008) in 10ms"@AppleA7IOP.cpp:357   Panicked task 0xfffffe2317f28088: 0 pages, 662 threads: pid 0: kernel_task


[in my opinion] that is far more likely to be a (rare) hardware issue.



Reply

MacBook Pro M3 crashing with ANE errors after macOS Tahoe 26.0.1 update

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