2006 Toyota RAV4 DTC P0037 Keeps returning

Tiny
SPARKY2013
  • MEMBER
  • 2006 TOYOTA RAV4
  • 40,000 MILES
I have an 06 Rav4 with a 2AZFE engine and 62K kms. On the Odo. Recently we had some work done on the headlights and the day after that we had rough idling on a cold start until the engine just died.

First scan with an ODB-2 reader said MAF sensor and VSV purge. So we had it sent to the dealership and they scanned again and saw DTCP0037 and P0031. This was after they cleaned the throttle body and assured us that the MAF-S and also the VSV purge were working properly.

Dealership assured us that replacing the 02 sensor and air/fuel ratio sensor would solve the problem.

2 days later we got the parts and replaced the old ones. Everything was fine for about 5 minutes, no CEL, no DTCs and engine was idling at 600 rpm. Smooth and stable.

After the 5 minutes the CEL came on again.

Scanned again and P0037 again.

Removed the negative terminal overnight to see if it would re-set the ECU.

Next morning, cold engine start, revs at 2000 rpm for 2-3 minutes before dropping to 1000 rpm.

Even after reaching operating tempt. Rpm stays at 1000 and sometimes it goes up to 1500 when stopping in traffic and putting gear in Park.

Had it scanned again and same DTC P0037, cleared the DTC and engine returned to 600 rpm at idle but

CEL came back on after 5 minutes.

Mechanics are saying it could be the ECU/ ECM.
Do you
have the same problem?
Yes
No
Saturday, November 16th, 2013 AT 4:04 PM

1 Reply

Tiny
CARADIODOC
  • MECHANIC
  • 33,689 POSTS
Yup. It's always the computer when we don't know what else to do. Actually, Engine Computers cause a lot less trouble than you would expect, considering how unreliable electronics are and the environment they live in. What you must be aware of is diagnostic fault codes never say to replace parts or that they're defective. They only indicate the circuit or system that needs further diagnosis. There's always a long list of things that must be tested to eliminate everything else, THEN a sensor or other part referenced in the code can be suspect. The sensor is the cause of a fault code only about half of the time.

To say it another way, if you just replace a sensor because of a fault code, there's fifty percent chance that will not solve the problem.
Was this
answer
helpful?
Yes
No
Saturday, November 16th, 2013 AT 4:29 PM

Please login or register to post a reply.

Sponsored links