Check the connection on the passengers seat too. Have you unhooked the battery and the reconnected it?

 

Yes, I disconnected the battery, waited 30 minutes, and reconnected it with no luck. That was the first thing I did which I hoped would work, but did not.

 

34 - Driver Side Air Bag Circuit Low Resistance or Shorted

I'll let someone with more knowledge than I comment further.

**Sorry Bert. I had the reply box up for a few minutes while I was looking at another site.

 

Got a couple of things. First was this from another site which might be worth pursuing before pulling all of your hair out and looking like me: "My airbag light was on and failed for inspection on my 2003 Ex xlt 4x4 V6. After some research. I determined it was the white connectors under the seat. I used electrical contact cleaner spray to clean them out. Disconnect the battery first. After spraying them out thoroughly let it dry over night (you may not need to let it sit that long but I did) before you reconnect anything. Reconnect them and the battery the next day and presto, the light is gone! Worked for me. Should work for a code 33 as well I believe. Good luck!"
This quick fix makes sense as if you're building corrosion and \or oxidation, you'd have oxidation. I'd also apply some dielectric grease to prevent further degradation.

If that doesn't fix the problem, a common problem is the clock spring: http://www.justanswer.com/ford/6zvwh-air-bag-light-flashing-code-34-tools-meters.html

Unfortunately, I don't see a lot of ways to trouble shoot the clock spring.

 

Just replaced the clock spring as this is one thing that usually goes bad, and the 34 code is still there. I am so pissed off and on the verge of going ballistic since I have already thrown $200 worth of parts at it including a new seatbelt assembly for the driver's side, and it still isn't fixed. I may just have to bite the bullet and take my car to the dealer. :angry::fa::help:

 

Solved it - turns out the 34 code is ACTUALLY the passenger seatbelt pretensioner fault. Bought a passenger seatbelt from a junkyard, plugged it in, and the code is long gone. I'd like to give a very special thanks for giving me the wrong codes for a truck instead of a CVPI and making me throw away money on parts I didn't need, couldn't have done it without all of you. :neverlear :fa: :wank2: :ft: :madfawk: :ripped:

 

Maybe its my response Westbrook is referring to. If so, I apologize for any misinformation that I have given. I don't see where Bert steered you wrong with the help that he offered. He was clearly on the right track where the rest of us were wrong.

 

You only said you disconnected the battery, nothing about the passengers seat.

 

Ah, but who made the initial discovery what the REAL issue was? That's right, nobody here. Went onto another forum and got the correct diagnosis the FIRST time almost instantly.

Nothing personal or trying to put you on the spot, just calling out everyone else who replied giving misleading information which led me to wasting $60+ on a part I didn't need. This is the kind of irresponsible and lazy behavior the dealer is notorious for: not finding the actual culprit, throwing new parts on it that have absolutely nothing to do with the real issue, and make you dig deep into your pockets for it. The other forum was so helpful and precise - they immediately knew what the issue was, and even provided a comprehensive airbag code list for every Ford model from the early 90's to the present as proof. They took pride in their work and didn't rest until they knew I fixed it.

 

Actually, Bajarider set you on the right path way back when you had a code 33 issue.

http://www.fordforums.com/f102/ford-airbag-code-3-3-33-a-233201/

that was well before you joined pantherbb

Since you've had such bad luck on this forum, maybe you shouldn't come back.

 

Wrong again, this is the 34 code we're talking about, not the 33. I clearly understood what the 33 was and dealt with it accordingly until it then gave me the 34 code right after I bought and plugged in a new seatbelt for the driver's side. Catskinner was the one who gave me the correct diagnosis for the 33, not Bajarider.

 

^ I'll second that .

 

Either way it goes we're not going to make a huge ordeal over this. I've offered my apology for my part and that's all I can do. In the meantime this thread is closed. You've said what you had to say and so have I. If you would like to continue using this forum, feel free, but enough of the pissin' and moaning.