New MacBook Pro keeps kernel-panicking, even in Recovery. What should I do?

November 19, 2026 4 answers
Asked by _v43~draxelo.7

My three-week-old MacBook Pro shows purple static or a green screen shortly after login, then restarts. It also turns itself back on after shutdown and gets hot while looping.

Disconnecting the hub and accessories, running First Aid, reinstalling macOS and trying Safe Mode haven't helped. The display glitches in Recovery too. The panic logs mention watchdog timeouts and a possible memory controller error. Does this point to hardware, and should I expect a repair or replacement?

Answers

_r74+zeldravo.6

Glitching in Recovery as well as during a normal boot, after a reinstall and with accessories disconnected, makes a hardware fault a serious possibility. It doesn't prove which component failed, though. A watchdog timeout tells you the system stopped responding, not necessarily what caused it.

I'd stop spending time reinstalling and arrange an inspection with Apple or an authorized service provider. Bring the panic reports and describe the shutdown problem too. They can run diagnostics and determine whether a board or another part needs service.

Reply to this answer
9g~canvasratchet_384

Ask the seller about a replacement or refund before agreeing to a repair, especially since it's only a few weeks old. Don't assume either is guaranteed. Return rules, warranty service and available remedies can depend on where it was bought and the seller's policies.

Have the purchase receipt handy and explain that the fault is reproducible in Recovery. If a return isn't available, ask what repair is proposed and what happens to your data.

Reply to this answer
Nuvkelo+3r

The turning itself on and getting hot part needs attention before travel. Contact Apple support or the service provider for advice on handling and transporting it in that state, and check with the airline before flying with a device that won't reliably stay off.

Keep it away from flammable materials and don't leave it running unattended while you're arranging help.

Reply to this answer
c.271!wickerpocket

That decoded controller message is a useful clue to give the technician, but I wouldn't treat the channel number as a confirmed diagnosis. The source doesn't establish how often this happens on that model either. Keep the original panic logs if you can, rather than relying only on the interpretation.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions