[sibhusz06]

Curious if anyone has come across code 133e10 valvetronic system deactivated message on their scanner. Have a 2012 X3 35i.

Today I used my foxwell to do a oil service reset and noticed on the DME scan that this code popped up.

After researching it, it could point to a valvetronic failure on the N55 engine, however I don't have any faults showing on the idrive, and I don't hear any weird noises or clicks.

Ive been driving around indefinitely with this and cant figure out if its a legitimate failure or not. The car does have some hesitation on cold start for the fist 10 seconds but drivability otherwise seems fine and no issues.

Curious if anyone has come across this with their 35i.

Thanks Kal

[hardparker]

I've seen that code intermittently recently on my X3. I haven't noticed any difference in the engine running, drive-ability or performance. Sometimes it'll trigger the dash light, but usually it's just there as a pending code. Logging shows Valvetronic active.

It only started happening after flashing the BM3 8.1 PWG OTS maps, so I suspect it may be related. There have been similar minor issues in the past with erroneous codes that get fixed eventually. There's a service bulletin somewhere from BMW that shows that earlier DME software versions are coded to be more sensitive/susceptible to throwing that code. BMW's solution is to update the DME to later software.

If it is your solenoids, they're not too bad to remove and replace. Some people just clean them and reinstall them and that solves it.

[383vett]

Clear it and see if it returns.

[sibhusz06]

The error code registers as a "permanent code" in my foxwell 410 scanner and im unable to delete it. Maybe I need the bmw INSTA software.


Today I was able to perform the valvetronic learn where it goes through 450 cycles with the engine running and afterwards I performed the valvetronic endpoint learn in the foxwell tool. I was able to perform these and the code still remained so a little muffed.