idrive just rebooted twice, prelude to a dying battery?

[texsn95]

Build date 11/2013

Bought it with 11,800 a year ago, now at 17,050. Runs like a top and stock except for charcoal filters removed and AFE dry filters. No codes so far. Always starts like a champ.

Today while idling to pick up my girls, I flipped up the e-brake and the idrive rebooted. It did it again a few minutes later still idling, then I drove the 3 minutes home and haven't started it again. This past week I hardly drove it due to vacation and crappy weather. It was fine on the way to work this morning. Car does not sit on a trickle charger.

I had an E60 M5 (with voltage regulator issues) so I know how picky those can be relating to voltage and battery issues. Are the F10s the same?

Is this a sign of a dying battery? I did some searching but couldn't really find a consensus on a good aftermarket battery to go with. I use Bimmercode, and can purchase Bimmerlink in order to register a battery if I need one.

1) Are the idrive menu settings erased when changing the battery?
2) I have some coding done via Bimmercode, will that be erased?
3) Got 12.25 off and 14.84 idling with the multimeter.

I also saw this quote, secret menu?

Originally Posted by Chauncey.Bishop

5 years sounds about correct for a battery replacement. I just replaced mine and the car is four years old. Look into your car's secret menu so you can see voltage with the car off and voltage with the car on. Those two things will tell you everything you need to know about your battery's life.

[texsn95]

So last night I got a "no signal" screen for about 10 seconds, kept driving and then it rebooted and was still on the same FM station. Researching this "no signal" issue leads to quite a few folks in the BMW family seeing this, but no confirmed fix. Some folks said even after a HU swap out that it kept showing up intermittently, others say after forcing an idrive reboot then it went away. So who knows.

[technician117]

Mine will occasionally do this. Black out, then usually "no signal" followed by reboot. First time it happened was over a year ago. Happens infrequently enough that I haven't bothered to do anything.

[texsn95]

Appreciate the comment. If you do end up having to address it please post up the fix...cheers.