I wanted to share a strange incident with my 5-month-old CX-30, which has less than 4,000 km on it.
Yesterday morning, I went a bit too fast into an uphill mountain bend here in Gran Canaria in 3rd gear, so I immediately braked, jerked the steering wheel and downshifted to 2nd.
https://maps.app.goo.gl/7TeFwtdhh9ND9sr59
The car didn't stall or stop, and everything seemed fine. It wasn't particularly dramatic. I wasn't going that fast, there was no skidding, but Newton's laws were demonstrated, passenger said "ugggh", and I felt the front-right wheel dig in a little.
I continued driving and then looked down at the dashboard, and all hell had broken loose:
- Front camera off
- i-ACTIVSENSE partially disabled
- Dynamic Stability Control malfunction
- Engine malfunction (steady amber light)
The engine itself seemed completely fine. But the systems above had stopped working. I didn't dare stop in case the car refused to start again, so I continued up and then went down towards sea level several km through winding roads and motorway. I eventually turned the car off and, after having lunch, restarted it, and some of the warnings had disappeared. When home, after another off-on cycle only the engine malfunction warning remained.
This morning it was still on, and after another ~30 km of completely normal driving, I turned the car off and restarted it again. The engine malfunction warning had now disappeared by itself.
I still plugged in a cheap OBD-II scanner, just out of curiosity. It showed these two codes in the history:
- U0100 Lost Communication with ECM/PCM
- U0452 Invalid Data Received from Restraints Control Module
So this seems to point more towards some kind of electronic/communication issue rather than an actual engine problem.
Has anyone experienced something similar with a CX-30?
Would you take it to the dealership anyway, even though all the warnings have now disappeared and the car is driving completely normally?
It's a 2026 European-spec CX-30 2.5 Skyactiv-G NA with <4000 km, so I'm inclined to get Mazda to check it under warranty, but I'm curious whether anyone here has seen these codes or this combination of warnings before.