|
||||||||
| Xoutpost server transfer and maintenance is occurring.... |
| Xoutpost is currently undergoing a planned server migration.... stay tuned for new developments.... sincerely, the management |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
#1
|
|||
|
|||
|
What could be frying an ignition coil on a 2013 5.0i
So I changed the coil everything work good for about a day drive to work no problem 10 miles check engine light came back on coming home. Something fried the coil. What would fry a coil. What could it be what do I check next? |
| Sponsored Links | |
|
|
|
|
#2
|
|||
|
|||
|
Lol
1. 'The old fashioned way'???? That doesn't reset the code. 2. Is that the sum total of diagnostic info on which you have determined the coil is 'fried'????? 3. Coils fail, you replace them. 4. But lots of things besides a bad coil can cause a generic P misfire code... 5. Bad coil and/or a miss in Cyl 4 will **NOT** cause the turbo not to kick in. 6. Maybe a BMW-specific code reader would be useful...ya think? Last edited by ard; 05-27-2019 at 12:47 AM. |
|
#3
|
|||
|
|||
|
Quote:
In reply The reason I say something is frying #4 coil and the reason I ask what could be frying a coil is. I took the new coil just installed in bmw x5 5.0 that cleared the code and check engine light for a day put it in another bmw that was fine and the "new" coil caused it to through out the same miss fired code. Goes back to what could be causing this car to fryed coils. What could I be looking for. Also regarding the turbo. If the the bad coil cause a missfire would that put the car in a limp mode and cut off the turbo? Does a missfire code generally cut power to the engine? |
|
#4
|
|||
|
|||
|
Quote:
Here you go.... you are saying the motor keeps frying coils. Try this on: it isnt the coil that is causing the misfire (!!!!) If you make the assumption 'it isnt the coil", then would that not fit precisely what you have observed? misfire codes DO NOT cut boost...do not (necessarily) cut power to the motor. |
|
#5
|
|||
|
|||
|
I'll re-iterate the suggestion to buy a proper BMW code reader. Dropping by a shop for a read, then shotgunning borrowed replacement parts is so ghetto.
|
|
#6
|
||||
|
||||
|
^ What he said. With any post 2001 BMW (varies by chassis, but generally 2001) you are going to need a code reader that can give you the specific BMW trouble code. A generic P-code is not going to do the job unfortunately. I use, and suggest, the Foxwell NT520 Pro. It's about $150. Can do 95% of anything even a tech would need.
A generic misfire code isn't going to help a bunch with diagnosing the issue. On that cylinder it could be the coil, plug, injector, carbon coked valve, worn cam lobe, etc. Some of those failures are more common than others, but as Ard was hinting at, shotgunning parts is not the best approach usually.
__________________
2005 X5 4.4i Build 04/05 Maintenance/Build Log Nav, Pano, Sport (Purchased 06/14 w/ 109,000 miles) (Sold 8/15 w/121,000 miles) 2006 X5 4.8is Build 11/05 Maintenance/Build Log Nav, DSP, Pano, Running Boards, OEM Tow Hitch, Cold Weather Pckg (Purchased 08/15 w/ 90,500 miles) 2010 X5 35d Build 02/10 Nav, HiFi, 6 DVD, Sports Pckg, Cold Weather Pckg, HUD, CAS, Running Boards, Leather Dash, PDC, Pano (Purchased 03/17 w/ 136,120 miles) |
![]() |
| Bookmarks |
|
|
|
|