Hi,

I have a Skoda Fabia and sometimes when i start the car the screen shows the date 01.01.1970.

What may be the problem? Do you have solutions? Hope someone can help me

Edited 13 February13 Feb by Pasquale2000

January 1, 1970 (01.01.1970) is the UNIX Epoch, serving as a foundational "date zero" for UNIX-based computers and many programming languages, and acts as a default date-value when systems encounter errors or missing date inputs. The phenomenon is not confined to vehicles, but can also occur on smartphones and computers that use a UNIX-type operating system.

Where cars are concerned, it isn't just Skoda or VW Group vehicles that can be affected. This link is to a Vauxhall "Mokka" forum discussion

https://www.mokkaownersclub.co.uk/threads/time-and-date-change-overnight.4692/

and includes this posting.

Now having this problem too. Mokka X, 2016, elite. When the engine is turned on the clock has reset its self to 0.00, and the date to 01/01/1970. This has happened everyday now for the last week. Using the touchscreen I reset the date and time for each trip, all is well for the journey, until the engine is turned off then it goes back to 1970 and 0.00, is anyone able to help please?

My 2024 Fabia has an Amundsen infotainment unit, but (based on your photo) I think your car has a Bolero.

When the sort of problem you have is discussed on-line, it's sometimes suggested that the car-owner sets the date and time manually (rather than choosing the GPS option) and that he/she ensures that a correct geographic region is selected. Conversely, it's sometimes suggested that GPS rather than setting the date/time manually is worth trying (!!!) or (as mentioned on the Vauxhall Mocca forum) that the car's battery be disconnected, left disconnected for a while and then reconnected, in the hope that this will 'reboot' the system and clear the problem.

In your case you've said that the date-change only occurs "sometimes" when you start your car. As you are having other problems with your car's infotainment unit

https://www.briskoda.net/forums/topic/534312-infotainment-fabia-22-plate/

if you cannot cure the 01.01.1970 fault by playing around with your Fabia's time/date settings (or by 'rebooting' the system by disconnecting/reconnecting its battery) you should add this fault to the other problems you'll need to tell your Skoda dealer about.

Edited 13 February13 Feb by DerekU

11 minutes ago, DerekU said:

January 1, 1970 (01.01.1970) is the UNIX Epoch, serving as a foundational "date zero" for UNIX-based computers and many programming languages, and acts as a default date-value when systems encounter errors or missing date inputs. The phenomenon is not confined to vehicles, but can also occur on smartphones and computers that use a UNIX-type operating system.

Where cars are concerned, it isn't just Skoda or VW Group vehicles that can be affected. This link is to a Vauxhall "Mokka" forum discussion

https://www.mokkaownersclub.co.uk/threads/time-and-date-change-overnight.4692/

and includes this posting.

Now having this problem too. Mokka X, 2016, elite. When the engine is turned on the clock has reset its self to 0.00, and the date to 01/01/1970. This has happened everyday now for the last week. Using the touchscreen I reset the date and time for each trip, all is well for the journey, until the engine is turned off then it goes back to 1970 and 0.00, is anyone able to help please?

My 2024 Fabia has an Amundsen infotainment unit, but (based on your photo) I think your car has a Bolero.

When the sort of problem you have is discussed on-line, it's sometimes suggested that the car-owner sets the date and time manually (rather than choosing the GPS option) and that he/she ensures that a correct geographic region is selected. Conversely, it's sometimes suggested that GPS rather than setting the date/time manually is worth trying (!!!) or (as mentioned on the Vauxhall Mocca forum) that the car's battery be disconnected, left disconnected for a while and then reconnected, in the hope that this will 'reboot' the system and clear the problem.

In your case you've said that the date-change only occurs "sometimes" when you start your car. As you are having other problems with your car's infotainment unit

https://www.briskoda.net/forums/topic/534312-infotainment-fabia-22-plate/

if you cannot cure the 01.01.1970 fault by playing around with your Fabia's time/date settings (or by 'rebooting' the system by disconnecting/reconnecting its battery) you should add this fault to the other problems you'll need to tell your Skoda dealer about.

Thanks for your reply.

I also have on other problem, sometimes I receive error of Component Protection Active.

Radio don't work, parking sensor don't work..need to wait some times, then after some reboot it starts working.

There has been some past BRISKODA discussions about the "component protection active" message.

https://www.briskoda.net/forums/search/?&q=%22component%20protection%20active%22&search_and_or=or

This 2022 BRISKODA discussion was in the Kodiaq Mk 1 forum

https://www.briskoda.net/forums/topic/504653-component-protection-active-in-infotainment-columbus-92/

and included this final comment

Component protection is designed to prevent (deter) people from stealing head units. Each unit is coded to a particular vehicle and this message will come up if a head unit has been put in a different vehicle. But sometimes these highly computerised cars just like to do random things at random times for no apparent reason before reverting back to normal

I notice that the 'disconnecting/reconnecting the battery' ploy was mentioned in the discussion as a way to get rid of the message, so you could try that to see if it works with your car (and, possibly, might also correct the 01.01.1970 problem). On the other hand, if you plan to involve a Skoda dealer with sorting out the problems you are having with your car's display-screen, it might be best to let them investigate/diagnose the faults, rather than trying to do it yourself.

On 13/02/2026 at 18:21, DerekU said:

There has been some past BRISKODA discussions about the "component protection active" message.

https://www.briskoda.net/forums/search/?&q=%22component%20protection%20active%22&search_and_or=or

This 2022 BRISKODA discussion was in the Kodiaq Mk 1 forum

https://www.briskoda.net/forums/topic/504653-component-protection-active-in-infotainment-columbus-92/

and included this final comment

Component protection is designed to prevent (deter) people from stealing head units. Each unit is coded to a particular vehicle and this message will come up if a head unit has been put in a different vehicle. But sometimes these highly computerised cars just like to do random things at random times for no apparent reason before reverting back to normal

I notice that the 'disconnecting/reconnecting the battery' ploy was mentioned in the discussion as a way to get rid of the message, so you could try that to see if it works with your car (and, possibly, might also correct the 01.01.1970 problem). On the other hand, if you plan to involve a Skoda dealer with sorting out the problems you are having with your car's display-screen, it might be best to let them investigate/diagnose the faults, rather than trying to do it yourself.

Thanks, I took the car to the dealer yesterday and made an appointment for next week and they will examine the car for this problem.