Running crappy - with codes
This is a discussion on Running crappy - with codes within the General Help forums, part of the LSx Technical Help Section category; I need some advice as to how to best spend my $$ fixing this thing. Yesterday, from a cold start, ...
10-28-2009, 04:20 AM #1
Running crappy - with codes
I need some advice as to how to best spend my $$ fixing this thing.
Yesterday, from a cold start, my TA felt like it was out of gas when I was attempting to leave a parking lot. It was barely running, but if I gave it a lot of throttle it would "wake up" and go, but then bog down again at lower RPMs. After a few laps around the parking lot, it cleared itself up and I drove 17 miles to my next stop.
I had some lunch, went to leave and it did the same thing only worse. This time it wasn't clearing up. I needed to get my son from school so I kept driving it, and it kept getting worse. Eventually the SES light started flashing indicating a misfire. By the time I got to my son's school something smelled really hot. I picked him up, and realized that I wasn't going to make it home. I stopped at my ex-wife's place a couple miles away and called for a tow. By that time the SES light was on solid with a P1133 code and the P0300.
I know what the codes mean, the 300 is a misfire and the 1133 is a lazy O2 sensor. But I'm thinking both are symptoms of a different problem. I'm thinking the lazy O2 sensor would not have caused the running-out-of-gas type behavior, right? I'm reluctant to spend the $$ on the O2 sensor when the problem is really probably fuel related. I may have baked the O2 sensor by continuing to drive it in its crappy running state, but I don't think that's the real issue here.
The car did stall a couple of times, and both times I could hear the fuel pump still running. I'm thinking of starting with the fuel filter. Make sense?
Advice would be appreciated.....
10-28-2009, 08:06 AM #2
Sure you can start with a fuel filter, cant hurt. But, I think before its over you'll be buying a o2 sensor. Since that code is for the drivers side front 02 sensor, I would swap that out to the passenger side to see if the problem follows. I'm sure it will.
problem is really probably fuel related
10-28-2009, 09:53 AM #3
P0300 is a random misfire. If I were you I'd pinpoint the miss first then see if the O2 code goes away. Take a stethoscope and listen to each injector and check for tickiing. Injectors don't throw codes. You could have a dead one and not know it. I know from personal experience. I ran on 6 cylinders and felt just like you did. If it's all good, disconnect your plug wires at the plug, use a spark tester and check for spark on all 8. Good chance you'll find the problem. If you have any questions PM me and I'll try my best to point you in the right direction
10-28-2009, 09:54 AM #4
Oh and hook up a fuel pressure gauge and check your pressure. You should be at 48-50 psi running or higher. Any lower check your fuel filter yes
10-28-2009, 01:01 PM #5
10-28-2009, 07:53 PM #6
10-28-2009, 09:35 PM #7
Nice! Funny how O2 sensors can make your car cry
10-29-2009, 04:05 AM #8
Yep. I've never had one make the car behave that way, which is why I thought it had to be something else. But, I've never had a pre-cat sensor go bad before either. Live and learn, I suppose.
It was an easy fix and now I know what the symptoms are. I should have changed the oil while I was under there - it's due.
10-29-2009, 07:57 AM #9
- Join Date
- Aug 2005
- Thornton, CO
Red Tint Jewelcoat
- 2008 Trailblazer SS
O2 failed causing the computer to dumb fuel to protect itself.
Glad it was easy.
10-29-2009, 10:52 AM #10
I may have spoken too soon.....
My first trip out today was uneventful. The car ran fine, though my son said it sounded funny. Maybe it does and I'm in denial, but it seemed okay.
I deliberately left the SES light on (didn't clear the code) because I wanted to see it resolve itself. On a warm start leaving the bank, it stumbled like it did yesterday (give it gas and there's nothing there). Simultaneously, the SES light went out and it was fine. I had hoped maybe it was some sort of hiccup caused by some diagnostic running.
Then, on another warm start it did the same thing for a split second - I nailed the throttle and there was nothing there but some misfires for about one second, and then it violently woke up back to normal.
It's been fine ever since. I'm thinking whatever it is will come back and take out that O2 sensor again. It's odd that the new O2 sensor mostly cleared it up though. The old one looked okay - not caked with anything and not much carbon for a 45k mile part.
10-29-2009, 11:50 AM #11
- Join Date
- Sep 2006
Start looking at your connectors and wiring also. Just unhooking and hooking back up may have moved things enough to make connection. Warm = spread apart cold means shrink back up, connected not connected. Seems to me worth looking at.....
10-29-2009, 12:03 PM #12
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
By tommyjt2006 in forum NitrousReplies: 7Last Post: 05-02-2010, 04:29 PM
By "B4C" in forum General HelpReplies: 2Last Post: 12-04-2008, 07:06 AM
By 98-LS1 in forum General HelpReplies: 6Last Post: 07-22-2006, 01:14 PM
By ARCTICWHITE98Z28 in forum Computer & TuningReplies: 2Last Post: 09-07-2005, 05:29 AM