Skip to content
Miatafy

Black Screen / Reboots / No Audio

Black screen, random reboots, and silent audio are the three most-reported Gen 6 Mazda Connect failures, and they overlap because they share one stack: the CMU runs the UI and the screen, a separate Tuner and Amplifier Unit (TAU) does the radio and drives the speakers, and on Bose trims a third box, the external amp, sits downstream of that. A fault anywhere in that chain shows up as one of these three symptoms, so the first job is figuring out which box is misbehaving before anyone replaces anything.

This is the platform reference. The same CMU is in the 2014–2018 Mazda3, 2016–2020 Mazda6, CX-3, CX-5, CX-9, and MX-5 (ND1/ND2), so everything below applies across the lineup. Model-specific details live on the per-model pages that link here: button-cluster layout, amp location, used-unit swap notes.

Start with voltage — most of these aren’t infotainment faults

Section titled “Start with voltage — most of these aren’t infotainment faults”

The Gen 6 CMU is intolerant of low 12V supply. When system voltage sags (a tired battery, a parasitic drain, a bad ground), the CMU is one of the first modules to misbehave: it browns out mid-boot, drops audio, or loops. Owners chase the screen for weeks before finding a battery reading 11.8V at rest.

Check this before anything else:

  • Resting voltage. With the car off and settled for a few hours, a healthy 12V battery reads ~12.4–12.7V. Below ~12.4V it’s discharged; below ~12.0V it’s failing.
  • Cranking/load behavior. If the screen reboots specifically when you start the car, or when a heavy load switches on (rear defrost, blower, headlights), the battery can’t hold voltage under load even if it looks fine at rest. That’s a battery or charging-system problem, not a CMU problem.
  • Parasitic drain. If the symptoms are worst after the car sits overnight, something is draining the battery while parked. The CMU itself has a documented appetite for staying awake longer than it should.

Fix the electrical side first. A surprising share of “my screen is broken” threads end with a new battery. See keeps rebooting for the full boot-loop workup.

Forced reboot — the first software step

Section titled “Forced reboot — the first software step”

A locked-up or black screen often clears with a forced reboot, which does not touch settings:

Hold Mute + Nav + Back together for about 10 seconds. The screen goes dark, the Mazda logo appears, and the unit restarts. These three hard buttons sit around the commander knob; exact placement varies by model and trim, so check your per-model page if the cluster looks different.

This restarts the CMU only. If audio is dead but the UI works, a reboot can still help (the TAU re-initializes on restart), but it won’t fix a hardware-failed amp.

Black screen: is it dead, or just dark?

Section titled “Black screen: is it dead, or just dark?”

Two very different failures look the same from the driver’s seat.

  • Backlight/UI still alive. If the screen is black but you can hear startup chimes, the backup camera still appears in reverse, or the commander knob still clicks through menus you can’t see, the CMU is running and the display or its backlight is the suspect. On some units the LVDS link or backlight inverter fails while the computer behind it is fine.
  • Whole unit down. No chime, no camera, no response to the button combo — the CMU isn’t booting. This is the boot-loop family, and the cause is usually voltage (above) or storage corruption (below), not the panel.

A quick test: select reverse with the engine running. If the backup camera fills the screen, the display hardware works and your problem is software/boot. If the screen stays black in reverse too, suspect the display or the CMU’s video output.

Random reboots: cause table

Section titled “Random reboots: cause table”

Reboots cluster into a few causes. Work them top to bottom — cheapest and most common first.

Symptom patternMost likely causeWhat to do
Reboots on startup or under electrical loadLow/weak 12V supplyTest battery resting + load voltage; check grounds
Boot loop: logo → black → logo, never reaches UICorrupted navigation SD card or storage/firmware corruptionPull the nav SD and try booting without it; if it boots, the card is bad. If no card or still looping, reinstall firmware
Reboots when plugging in a specific phone/USB deviceBad cable or a device the CMU chokes onSwap cable; try another port/device. See USB not working
Reboots randomly, voltage and SD ruled outCMU hardware (DRAM/board) degradingReflash firmware; if it persists, the CMU is the fault

The nav SD card is worth emphasizing: a corrupted or failing card sends a Gen 6 unit into a loop, and pulling the card to test is a free diagnostic. The car runs fine without it — you just lose embedded navigation until you replace it. See navigation SD cards.

No audio: walk the path

Section titled “No audio: walk the path”

If the screen works but nothing comes out of the speakers, the failure is downstream of the UI. Trace it source by source.

  1. Confirm it’s not muted or zeroed. Obvious, but check volume and that Mute isn’t latched after a button-combo reboot.
  2. Test every source. Bluetooth, USB, FM/AM, CarPlay/Android Auto. If one source is silent but others play, the problem is that source (a Bluetooth pairing issue, a dead tuner, a CarPlay handshake) — not the amp. See Bluetooth pairing / no audio.
  3. All sources silent = downstream hardware. If the UI works, sources switch, levels move, but nothing plays on any source, the TAU or (on Bose cars) the external amplifier has failed. An amp failure produces no warning lights and no other symptoms — it just kills output. This is diagnosed by checking the amp’s power and output, and it usually means replacement.
  4. Wait a full minute after a reboot before judging. The audio path re-initializes after the UI is already drawn; testing too early reads as “no audio” when it’s just not up yet.

On Bose-equipped trims the external amp is a separate, more expensive failure point than the standard TAU; Bose audio covers what’s specific there.

When it’s actually the CMU

Section titled “When it’s actually the CMU”

Mazda acknowledged a hardware-level cause for blank-screen and reboot complaints in service alert SA-011-20 (and revisions), covering 2014–2018 Mazda3, 2016–2020 Mazda6, CX-3, CX-5, CX-9, and MX-5. The root cause cited is the CMU failing during startup initialization due to a board/DRAM defect. The dealer remedy is, in order: reflash the CMU software, check or replace the navigation SD card, and, when the hardware is at fault, replace the CMU with an improved-DRAM unit.

Before you accept a CMU replacement quote, exhaust the cheaper causes:

  • Reinstall firmware. A clean reinstall clears storage/software corruption that produces boot loops without touching hardware. This is the step that resolves a large fraction of “needs a new CMU” diagnoses. See factory reset vs firmware reinstall — they are not the same operation.
  • Confirm you’re on current firmware. The supported baseline here is v74.00.324A; the version Mazda’s alert references (70.00.352B) is older. See check firmware and get to v74.
  • Rule out the SD card and voltage per the sections above.

Only after firmware, SD card, and electrical are cleared does a persistent reboot or true no-boot point at the CMU itself. A used CMU from the same model year is generally the cheapest path back; navigation and connected services may need configuration to come back after a swap.

If it comes to warranty or dealer work, the dealer visit guide covers how to describe the symptom and reference the service alert so the conversation starts at the right place.

Section titled “Related”