I have a 2008 Lexus GS 350 with about 90k miles. My water pump was leaking and making a terrible noise - got quotes from dealer and a few other shops for $800 and after seeing posts here decided to replace it myself. All went well and I replaced it just fine - however I accidentally ran the car with no engine coolant in it for maybe a minute, a minute and a half max after putting everything back. I did fill the radiator with coolant after my mistake but it will no longer start.

It sometimes will turn over and give me a Check VSC notification. Also, the electronics will slowly start to die after trying to start and the locks will struggle to lock/unlock. REALLLLLLLLY hoping I didn't blow a head gasket and turn this into an even more expensive repair. Anyone have any idea what might be happening? I don't think any fuses were blown and the battery should be fine - I will check it tomorrow. Think it could possibly be an alternator or starter? The strange electricity issue after trying to start has me puzzled.

 

Not likely that you would have caused much damage if any to the engine from running it for such as short time with no coolant, the water pump probably would not have liked it. The electrical problems aren't a symptom of a headgasket. Did it start fine when you started it with no coolant?

 

Yes, started just fine with no coolant and haven't had any electrical problems until just now.

 

Try disconnecting the battery for 5 minutes or so, hold the brakes on and flick your high beams on to drain any charge in the system to reset the ecu. A number on sensors may have been confused by running with no coolant, have you got any error codes or anything?

 

Just tried this and got nothing. Car isn't even turning over anymore. No error codes unfortunately.

 

Might just be a flat battery

 

Checked battery with a volt meter and it was at 11.9 - going to get my girlfriends car and charge it up a bit. Hoping this works!

 

Jumped the battery and it started right up. Cleared the check VSC light and it hasn't come back on. Appears to be fixed for now, thanks!