TwinTurbo.NET: Nissan 300ZX forum - Suspected blown head gaskets. Please help.
People Seeking Info
 
   


     
Subject Suspected blown head gaskets. Please help.
     
Posted by OpticalZ on April 25, 2008 at 12:02 PM
  This message has been viewed 161 times.
     
     
Message I was driving on the freeway the other day when suddenly coolant
sprayed my windshield. I pull over and realize that the radiator hose
coming from the engine to the radiator (the top one) was just off the
radiator completely. I put it back on and think it was just loose or
something. Keep driving, about a mile down the road i start to loose
power and everything in my car just shuts off. I put a bunch of coolant
in and try to start my car. It didnt want to but i gave it some gas and it
started eventually. I thought it was ok, so kept driving. About another
mile down the road i loose power again. Open the hood and there is a
gigantic amount of white smoke coming from that same hose fitting on
the radiator. So i put a gallon of water into the radiator and it dosent
seem to help. My radiator cap has a ton of rust on it and the coolant dip
stick is stained rust color. My car wont start.

I had it towed to a pep boys to just diagnose it. They were pretty sure
that i blew the head gaskets. I just ran an ECU diagnostic and i got code
21, Ignition signal circuit.

Does this code coincide with a blown head gasket?

Also, i would prefer to replace the gaskets myself, but i know that it
would be a long process. Has anyone done this without a lift?

I am also a bit skeptical as to weather or not i even blew the head
gasket. Dose the info i gave sound like that was the case? The
mechanic said i didnt even do anything but have me try to start it and
look at the dip stick. He didnt think there was coolant in the oil and said
there wasnt compression when i tried to start it.

Any help is greatly appreciated, thank you!

"...to die is to know that you're alive..."

     
Follow Ups  
     
Post a
Followup

You cannot reply to this message because you are not logged in.