On 5/29/07 8:00 AM, in article 135o8uhk1odute6@corp.supernews.com, "Chuck
Tribolet" <triblet@garlic.com> wrote:

I was having similar code experiences with the '02 Pathfinder.  It would
throw the swirl control valve solenoid code, one of the variable valve
timing codes, or, one time, even an o2 code, every so often, usually in the
middle of long road trips.  While the truck was still under warranty, the
dealer would simply replace the components and the light would go out out
for 6 months to a year.  Once it was out of warranty, I started testing the
actual components, but never found anything out of spec, and simply
reseating the connectors and resetting the light would give the same 6
months to a year of no complaints.

In the process of doing something else one day, I released the first hold
down on the top of the engine on the fat cable bundle that comes off the
firewall and just happens to carry all the wires associated with the codes
it had been occasionally throwing.  All the codes went away and have not
returned in a year and a half now.  My hypothesis is that cable was pulled
to tightly between the firewall and the engine and engine movement relative
to the firewall was stretching some of the wires (which of course don't want
to stretch), causing the intermittent fault sensings.  You might try adding
a little slack between the engine and firewall on that cable bundle and see
if your problems subside.