[Subotai]

Originally Posted by sybaek9

I thought I was fine but just experienced it at 814 miles

Sybaek9 2729 April

Very concerning.

[onfireX5]

Originally Posted by Subotai

Very concerning.

Probably not updated.

[neohh]

Originally Posted by Miko M

What???
After software update still problems
That's scary now

I don't think he has the software updated. He wasn't on the list before.

[josec70]

Originally Posted by Miko M

What???
After software update still problems
That's scary now

It sounds like he had the problem after 814 miles w/o the software update. At least that's how I read it.

[Miko M]

Originally Posted by josec70

It sounds like he had the problem after 814 miles w/o the software update. At least that's how I read it.

Ok, I got mine done yesterday... been driving with kids around a lot. Want to make sure they are safe.

[walile]

Where is everyone experiencing this problem located? Is this isolated to just US and Canadian market cars or is this worldwide?

This is very disconcerting, as we don't know the root cause of the problem. Is this is just a software calibration issue, perhaps overly aggressive in trying to meet certain emission and fuel efficiency goals?

Then why was this calibration not thoroughly tested? Especially after the lesson from the N63 Customer Care Package. More importantly, it makes one wonder what other aspects of the f90 M5 were perhaps also rushed.

The worse case scenario would be a hardware problem that BMW is trying to use software to compensate or mitigate at the expense of possible shorten component life and reduced reliability. Perhaps, hoping that when the said hardware components eventually fail, the cars will be out of warranty.

The purpose of this post is not to fear-monger, but perhaps try to explore the root cause of the issue as we document the incidents.

[sybaek9]

Originally Posted by josec70

It sounds like he had the problem after 814 miles w/o the software update. At least that's how I read it.

Yes I got the car in April and just have 800+ miles and haven't had the software upgrade. I was awaiting break in period hoping no issues but looks like I'm also impacted. Will update after service in the next few days. I also have kids in back so I've been cautiously optimistic I may be ok but obviously not.

[onfireX5]

Originally Posted by sybaek9

Yes I got the car in April and just have 800+ miles and haven't had the software upgrade. I was awaiting break in period hoping no issues but looks like I'm also impacted. Will update after service in the next few days. I also have kids in back so I've been cautiously optimistic I may be ok but obviously not.

While you are there , make them order the G2 and G4 diff lube for your 1200 mile service. Ordered mine April 30.....still not here.

[sybaek9]

Originally Posted by onfireX5

While you are there , make them order the G2 and G4 diff lube for your 1200 mile service. Ordered mine April 30.....still not here.

Good advice, will do. Do you know the full list of things to do/need for the 1200 break-in?

[onfireX5]

Originally Posted by sybaek9

Good advice, will do. Do you know the full list of things to do/need for the 1200 break-in?

Front rear diff lube (different lubes)
Engine oil/filter
Transfer case lube.
Cat pipe torque spec tsb (exhaust needs to be cool)
Fuel pressure recall reprogram.

[Subotai]

Originally Posted by onfireX5

While you are there , make them order the G2 and G4 diff lube for your 1200 mile service. Ordered mine April 30.....still not here.

Thanks for the advice,just called my service adviser.

[sybaek9]

Originally Posted by walile

Where is everyone experiencing this problem located? Is this isolated to just US and Canadian market cars or is this worldwide?

This is very disconcerting, as we don't know the root cause of the problem. Is this is just a software calibration issue, perhaps overly aggressive in trying to meet certain emission and fuel efficiency goals?

Then why was this calibration not thoroughly tested? Especially after the lesson from the N63 Customer Care Package. More importantly, it makes one wonder what other aspects of the f90 M5 were perhaps also rushed.

The worse case scenario would be a hardware problem that BMW is trying to use software to compensate or mitigate at the expense of possible shorten component life and reduced reliability. Perhaps, hoping that when the said hardware components eventually fail, the cars will be out of warranty.

The purpose of this post is not to fear-monger, but perhaps try to explore the root cause of the issue as we document the incidents.

I'm in Northern VA. I think the issue is now well known and documented. Haven't heard anything after people got the SW upgrade

[gcmr]

Add another . . . Late March production at around 1450 km. Two high speed highway shut downs today in heavy holiday weekend traffic. Managed to coast to a stop on the shoulder with a dead engine both times. Restart (reboot) and off you go. This should be an absolute emergency recall someone is going to get hurt. Very dangerous.

[gcmr]

Originally Posted by neohh

Gents

Trying to consolidate the list of members that have the drivetrain issues. So far we know:

1. Most car delivered in March or earlier or with VIN # less than 2470 have no issues.
2. A significant portion of April delivery between vin # 2480 to 2713 reported malfunction. The problem started almost right after taking delivery.

We will need more new VIN# or production to conclude if this problem has been resolved on newer production.


Drivetrain issues reported:

User Delivery VIN# Mileage Issue after fix
M5Speed Mar/Apr? 2480 500 vtg control
m55551111 Apr 2511 20
404NotFound Apr 2538 30 none so far
Nocera Apr 2543 400
fmalzoni Apr 2553
DK79 Apr 2557
lectric1e Apr 2566 40
skyjunky Apr 2589 170
mad4comp Apr 2604 none so far
bryantmeyers Apr 2611 100 none so far
vesko06 Apr 2614 1555
hoffmeister Apr 2617 420
afk8445 Apr 2639 120
mayorsizzle Apr 2641
canderous Apr 2684
sollomon Apr n/a
swisstype Apr 2713 new
pilotroger n/a n/a n/a
sybaek9 Apr 2729
slalomfever Apr 2750
MagicBeast Apr 2752 16
Mporcl Apr 2766

No Issues:

User Delivery Vin# Mileage
peteratmsr Mar 2085 1200
alpinefrenchfry Mar 2118 1148
rjwtkd Mar 2143 1500
Quickburn7 Mar 2173 1700
Ikdavis Mar 2301 675
Patrick_Bateman Mar 2367 1350
getmetnow Mar 2381 950
elitex Mar 2408 1400
Hill Country F90 Mar 2422
onfireX5 Mar 2470 720
BG23 Mar n/a 1000

VIN 2486 has the problem

[JET27]

I picked mine up last Saturday, 5-19-18. Last 4 of VIN are 2858.
They did SW update before releasing it to me. I have a little over 100 miles so far and no issues.

[gcmr]

Originally Posted by JET27

I picked mine up last Saturday, 5-19-18. Last 4 of VIN are 2858.
They did SW update before releasing it to me. I have a little over 100 miles so far and no issues.

Good luck. I'm very disappointed that they did not deal with this quickly. It's a nightmare coasting to a full stop engine dead in heavy traffic. BMW is fully responsible for any rear end collisions that happen because of this stupid error. Computers gone wild. Good luck BMW. The AI world! Loyal customer lost. As I was driving today I sat behind a Tesla at home service vehicle. Somebody was happy.

[Cacou]

Originally Posted by walile

Where is everyone experiencing this problem located? Is this isolated to just US and Canadian market cars or is this worldwide?

This is very disconcerting, as we don't know the root cause of the problem. Is this is just a software calibration issue, perhaps overly aggressive in trying to meet certain emission and fuel efficiency goals?

Then why was this calibration not thoroughly tested? Especially after the lesson from the N63 Customer Care Package. More importantly, it makes one wonder what other aspects of the f90 M5 were perhaps also rushed.

The worse case scenario would be a hardware problem that BMW is trying to use software to compensate or mitigate at the expense of possible shorten component life and reduced reliability. Perhaps, hoping that when the said hardware components eventually fail, the cars will be out of warranty.

The purpose of this post is not to fear-monger, but perhaps try to explore the root cause of the issue as we document the incidents.

This is an excellent point which I've been thinking about as well.

Assuming the functions around the fuel pump had been tested properly prior to the release of the car, the fix for this is likely to include a penalty. It may still be imperceptible to us.

Unless they switched to a new part or supplier for it, and the software needed adjusting which they missed, but that would surprise me.

Regardless, it would be interesting to know what the real issue was.

[sybaek9]

So my dealer has been trying to do this programming for the recall but it keeps restarting and is identifying over 90 issues. It's also taking hours. Anyone else experiencing this? I thought it was a 30-45min programming upgrade. Why taking so long?

[sybaek9]

Originally Posted by sybaek9

So my dealer has been trying to do this programming for the recall but it keeps restarting and is identifying over 90 issues. It's also taking hours. Anyone else experiencing this? I thought it was a 30-45min programming upgrade. Why taking so long?

Anyone in DC\VA\MD area with M5 who did the Drivetrain Malfunction recall software upgrade?

Or any insight on how long it takes?

Mine is taking several hours (they said nothing is less than an hour) and it keeps restarting according to dealer.

:

[onfireX5]

Originally Posted by sybaek9

Anyone in DC\VA\MD area with M5 who did the Drivetrain Malfunction recall software upgrade?

Or any insight on how long it takes?

Mine is taking several hours (they said nothing is less than an hour) and it keeps restarting according to dealer.

:

My entire service with both diffs, engine oil, cat bolt torque, Fuel Pressure reprogram only took 4 hours.

[ZulaM5]

They have to reprogram the modules in the car.

It takes hours... then if it errors, which does happen, it has to start over.

This is not just with this car, it's any BMW that has a programming recall.

I remember when the i3 programming recall came out, was half a day per car.

[Subotai]

Originally Posted by sybaek9

So my dealer has been trying to do this programming for the recall but it keeps restarting and is identifying over 90 issues. It's also taking hours. Anyone else experiencing this? I thought it was a 30-45min programming upgrade. Why taking so long?

Several hours in my case,got it back the next day.