Doen anyone have any experience with the plethora of errors I’m randomly getting once every 6 weeks?

I’ve been getting them for over 6 months now (car is 7 months old) and so far the dealer hasn’t gotten a clue on what it could be. All they did is reset it, drive around to see if it happens again and put in a new battery. I’ve tried to find something with an OBDeleven dongle but so far I haven’t had any success.

Edit: the errors do go away after not using car for about an hour

Any help or tips would be greatly appreciated.

Edited 11 May, 20251 yr by Vicros

Had those occur once recently on my Mk4 after the car had stood unused for a couple of weeks, it had also been driven only on very short runs for a few weeks prior to that. I put it down to the battery losing juice having stood idle for too long. So far, after running more normally again the battery is fully charged and the messages have not reappeared. I've just ordered a Ctek CT5 charger so I can keep it topped up when I'm using my other car.

I get a **** ton of errors like that when my 12V battery goes flat. It's getting a new 12V battery this week but I'm not convinced the battery is the problem.

Sometimes when the battery is flat the car just keeps pinging up error after error. Does my head in. Skoda aren't dealing with this problem properly.

I'm not 100% convinced either, but in the absence of any other known explanation it seems plausible. I think many cars suffer similar electrical gremlins related to the 12v battery, too many electronics that don't take kindly to voltage fluctuations. I had a previous car do very similar things until the battery was changed, although the old battery was was 7 years old.

Interesting that the OP still has the problem even with a replacement battery, but then it depends on their driving patterns eg. infrequent use, too many short/cold runs, etc?? Even a new battery is susceptible to voltage drops.

On 12/05/2025 at 06:19, SouthernComfort said:

I'm not 100% convinced either, but in the absence of any other known explanation it seems plausible. I think many cars suffer similar electrical gremlins related to the 12v battery, too many electronics that don't take kindly to voltage fluctuations. I had a previous car do very similar things until the battery was changed, although the old battery was was 7 years old.

Interesting that the OP still has the problem even with a replacement battery, but then it depends on their driving patterns eg. infrequent use, too many short/cold runs, etc?? Even a new battery is susceptible to voltage drops.

A new battery should not be doing that. The problem is something else.

I have the exact same problem with my 5 months old vrs. It always starts with "Unable to display total distance" error, then the central lock turns off and on till I turn off the car. After start the car again all the errors appear and the car cannot be turn on for about 40 minutes. I've noticed that it happens when I drove on a bumpy road so maybe the cause is some loose parts? I have an appointment with my dealer next week to discuss the problem. Lets see what will they say.

I have the exact same issue, already visited the dealership and they said they are not seeing anything wrong with the car. Does any of you happen to know what is causing the issue and what is the fix?

Hi guys!

Essential question, what's the speccs of your car? I have the RS Facelift, build early September 2024 and I have the same issues.

Let's try to find some similarities in all of this.

For me it first started about a year ago. It only happens on "longer" rides, meaning 100+ km or over an hour of continous driving. It never happens on my daily commute to the office (30km one way).

Working closely with my cardealer. Apparently, obviously, the issue is known to Skoda, and a TPI / Service Recall / Update (you name it) in the making.

When it happens, it usually is like one of you described:

-> Total distance unavailable

-> then few seconds later central locking starts to constantly UNLOCK! (this is important)

When you continue you drive, all works well, besides the beeping of the total distance, and the unlocking of the doors.

The moment you stop, turn off the car, and fire it back up: ERROR Party.

My workaround: drive as long as possible, and combine it on longer trips with breaks. I carry an RFID blocker pouch in my car, so the moment we turn off and on, face the errors, we get out of the car, lock it if possible, and still, someone stays with the car, key in the pouch! Like this, 15minutes later, soft reset happened and we're good to go again.

Now to the current facts, collected so far with my dealer, tests done and observations made.

• we rule out a battery issue, also a power issue in general, as especially after 80-100km, the car should have generated enough power to charge up the battery if it was low

• the driver door's control unit acts as a gateway for all other doors. So any comm from any unit to any door, ALWAYS passes thru the driver door too.

• bumpy roads were mentioned as possible trigger, but I could prove with dashcam footage that in the wildest Greek countryside, it worked like a charm, but on the smooth German highway, the car went loco

What we do indeed think so far, the car goes into "crash mode" -> this may flip of electronics and also cause the UNLOCKING of doors, for first responders to be able to access you!

Latest cases for me were December 28th and now today, February 1st.

Going thru the error codes in the car (via OBD, not in the infotainment) we can see the following:

Central Electrics noticed

B1468F0 - Return message regarding driver door closing condition Implausible

B1469F0 - Return message regarding passenger door closing condition Implausible

B146AF0 - Return message for left rear door closing condition Implausible

B146BF0 - Return message for right rear door closing condition Implausible

Now checking the driver door, as that's the unit communicating here; it had NOTHING. Except, an error from December 28: B1908F0 - Crash response active
Intermittent
Note: I pulled the logs the moment the car was in error mode today. Not sure if the Crash error only shows up in the log AFTER the soft reset for some reason. Will check tomorrow.

All other doors however, have the same error:

U303500 - Communication Authentication Signal Invalid Data
static

Funny enough, the FIRST error of the day occured in central electrics at 12:55:26: U14FD00 - Secure Onboard Communication Time server not available

At that time, funny enough, dashcam timestamp 12:54:30, I was driving with 60 on a quite smooth road, approaching a crossing where I pult into som parking plot at around 12:54:53. Stationary until 12:56:02. Bumpy road? Nope! But also no error on the dash, total distance not checked, but I cannot hear any "beep" in the dashcam footage and didn't notice the annoying message popping up!

The next set of errors, which happened probably when I was restarting the car, therefore power to dashcam cut, happened on another parking spot where I was aiming to take some photos of the car. I left ignition on, engine off, because I wanted the headlights to be on. Got initially out of the car at 13:15ish. Errors start showing from 13:20:44. That's probably when I noticed the headlights were OFF... Approached the car, no automatic unlock. Grabbing the handle, car's locked. Doesn't unlock. Had to use the real key to unlock the drivers door as the FOB would only unlock the fuel lid. lol.

So what's with this post now? Well, I'm trying to collect as much data as possible. My car workshop is pretty cooperative and anything plausible I suggest would be tried. Trying to figure out a logic behind our errors. For my workshop contact, it's difficult to do so, as they can only read out the fault codes, but were never present the moment the errors kicked in. Also it's quite hard for them to go on a 2h testride, hoping the error would kick in. It doesn't always happen... as usual.

So feel free to provide any infor,ation you got! I'll go with a questionnaire and fill my part out, just replace with your answers please:

• Car: Octavia 4 Facelift

• Trim: RS

• 2.0 TSI

• Model Year: 2025

• build Week 37 2024 (September 9th)

• delivered Week 39 2024

• Error first occured: February 2025

• Error frequency / pattern? No frequency, but pattern for me, usually on "longer" continious rides. 1h / 80-100 or more kms

• Error behaviour: Total Distance fail, then central locking. All errors after restart. (provide as much details as possible. mine are above in this post)

• Error workaround: put the key in an RFID blocker pouch or out of range from the car. wait 10-15mins. usually good then

• Actions taken so far: several updates of door control units and other control units

Let's get our cars fixed! <3

Sven

Edited 1 February1 Feb by teralux

Hi Sven!

Thank you of the thorough information.
I cannot add much else symptom wise, except that for me the lock/unlock of the doors is not happening every time the errors show up and the one time I did lock myself out of the car the boot was still opening, so I opened the doors from the boot... As for my car:

• Car: Octavia 4 Facelift

• Trim: Edition + 13" infotainment( might be relevant)

• 2.0 TDI

• Model Year: 2025

• build Week 34 2024

• delivered Week 39 2024

• Error first occured: August 2025
  

do you recognise a pattern? Like temperature or humidity? Or lots of sun exposure? Longer rides, short rides? Or are you even able to kind of "reproduce" it?

Agree that the most common cause is low battery voltage but that is not the issue for those above with an issue occurring after a long drive and/or had a battery replacement. Good luck getting it fixed sounds like an enormous PITA

Well, the battery aspect makes sense in regards of -> lower voltage for a control unit -> bug hits.

Now, we do have OPF's in the new petrol cars, something the TDI's have had already for a while.

Wondering if this could cause a higher need of energy (for TSI car needs to be at 80kmh between 3k-5k rpm) to generate enough heat to burn it free.
What if during this time, the alternator cannot produce enough energy to charge the battery and maintain the system running, a control unit gets a bit less power, fails, and triggers a chain reaction.

Wild guess, I know. Trying to combine my IT logic with car electronics, since it's all computers in the end. It doesn't seem to be a mechanical issue. And after having faced the issue now over 10 times, I'm challenged to find a pattern :D

Voltage while driving is about 14.75-15.30, tried it earlier. But need to go on a longer ride again the next days to try, and see if I can notice a significant drop right the moment the first symptom shows.

maybe, all I'm saying is the low battery voltage issue is more you start the car and get some random warnings that go away as you drive and the voltage goes up, whereas this is nothing wrong until some considerable time and in one case the battery's already replaced.

UPDATE: appointment mid february for an update of ALL control units. There's an entire package from Skoda available now that they gonna load on my car. We shall see if it solves the issues. Would be nice.

I have 2 days of long drives planned already right after the procedure. Once 2x210km and one 2x270km. That should be enough to figure out if it's solved, or reproduces.

I have a 2021 Octavia and don’t run the car so much. When the car was in for its 2year service I asked the dealer to check for a battery drain. They run extensive checks and found everything to be ok.

When the battery is low I get Auto handbrake error, radar error, pdc error. Local garage checked it out and all fault codes stored were low voltage errors.

Replaced the battery. 36,000 miles, 5 year old I would have expected better.

As a side note, if the battery voltage drops below 12 volts, that’s usually the end of the battery.

it's a thing with a specific range of cars from 2024 :) I can only repeat, my issues have nothing to do with the battery. I have the issues since a year now. And daily commutes to the office, 30km one way, are perfectly fine. even longer drives in Luxembourg work perfectly fine. Car starts, start stop works, etc. the issues only appear on longer drives. quite strange for the battery to die at 150km driven :D

On 07/02/2026 at 01:40, teralux said:

it's a thing with a specific range of cars from 2024 :) I can only repeat, my issues have nothing to do with the battery

Indeed, it'a a SW package called PV4RC that includes (potential) updates for all control units as you mentioned - only for the facelift versions of various cars in VAG group: Golf, Octavia, Leon, Formentor etc. The newer the car, the less updates to be performed; e.g. mine was manufactured mid-2025 and still they found a few updates to install.

I got updates!

Took them 8 full hours to update the car. 8 hours the car was blocking the PC and a bay. Hope it was worth it, for both of us, dealership and me :D

Will drive 2x215 & 2x250km on the weekend. By one day off kinda exactly when it first occurred last year! SAME route tho!

Wish me luck. I'll test my little one full on.

Gonna pull an export with OBD11 tomorrow to compare software versions. But one thing already was quite obviously visible in the car menu, 5F versions:

Before the update it was

- Partnumber 57H035816A
- Hardware H10
- Software 2565
- Display unit cp hw: H23
- DU CP SW: 266
- Nav database: 25.12
- Radio DB: 1.31.48
- Media codec 3.1.4

after the update:
- PArtnumber -> 57H035816B
- SW: 2630
- Radio DB: 1.31.52

Software version and database -> fine, changed by bits and bytes.

How can the device part number change with a simple update?

They didn't mention, but may they have changed the control unit of 5F (Infotainment)?