Originally Posted by FunfDreisig

FWIW this is a classic "problem" thread on this and other X5 forums.

0 - A forum member's X5 displays a warning light that can be triggered by lots of different problems.
1 - The member posts that the warning light came on and takes their X5 into the dealer.
2 - The dealer SA tells them some garbled story about what MIGHT be wrong before the problem is actually fixed.
3 - Other forum members chime in with possible causes and comments.
4 - The OP gets the vehicle back with minimal hard info on what was actually fixed and another story from the SA.

A lot of this is good. The member with the problem gets support/advice from the forum. The member usually gets their X5 back fixed. We all learn at least one problem that can trigger the warning light. And everyone feels good about it. BUT...We are all left to speculate again the next time, which of many possible problems have triggered the warning light.

What is missing is hard data about what actually caused the problem. BMW's warranty works against us by encouraging owner's to 'not worry their pretty little heads'. And the great irony is that our X5's are equipped with a socket that allows US to read the codes.

As many of you know, the engine light on our 2009 35d came on at around 4000 miles. And I know exactly what code was set when this happened. Because I read it BEFORE I took the X5 to the dealer. Thanks to the help of forum members, I even knew the exact part that the dealer would need to fix it. And more importantly, my SA knew that I knew. The result was that the dealer managed to source a hard to get part and replaced the turbo inter-cooler temp sensor while my wife waited drinking lattes and eating pastries

Anyone who owns an X5 can probably afford to buy a <$50 OBD II code reader. The plug is in the left hand foot well. You can learn a lot without even opening the hood. And the advice you get on this forum can shift from speculation to specification

Funf Dreisig