2013 Hyundai Elantra (20,000 miles). Check eng.light came on, but car had no symptoms. Next day, the light shut off, and all seems right with the world. Wife brings it to dealer just to check it. Two hours later, the service manager tells her the "computer is fried, and car can't even be started" . Sound normal, or sound like someone screwed up? Any ideas what could have happened??
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
New Car Question
- Thread starter phildb4
- Start date
jjb
Well-known member
Does it even matter if it's going to be covered under warranty anyway?
mechanicalmoron
Well-known member
- Joined
- Apr 28, 2014
- Messages
- 178
Sounds entirely abnormal.
Sounds like you should drop that steaming turd (either the car, or the dealer).
If it went off, my personal guess is it was a vacuum leak code from a loose gascap, or something equally small. If it drove smoothly to the dealer, and then after 2 hours there, it had a fried computer, the dealer fried the computer.
Sounds like you should drop that steaming turd (either the car, or the dealer).
If it went off, my personal guess is it was a vacuum leak code from a loose gascap, or something equally small. If it drove smoothly to the dealer, and then after 2 hours there, it had a fried computer, the dealer fried the computer.
nolimits76
Well-known member
Does it even matter if it's going to be covered under warranty anyway?
It would matter to me. Computers shouldn't be fried at 20k miles. I'd say there is a small chance the computer just died on it's own. Yes, it could and does happen, but electronics in general are getting more and more reliable. My fear would be the car experienced something else in its life that caused the computer to go blah on you. Flood, fire, other wiring damage, etc.
Has the dealer said what caused the failure?
JonnyMac
Well-known member
If you are interested in this kinda thing you should ask for the last fault codes that were recorded.
The car was drivable so it had a functional ECU and therefore the obd fault memory would be intact and should have a code indicting the failure.
The problem i see is that many dealership techs jump at the "replace the ecu" option in the event that any fault code even hints at an ecu issue. It will often be just a symptom but the fastest fix is a swap.
If you get the code pm me and I can give you the possible cause.
The car was drivable so it had a functional ECU and therefore the obd fault memory would be intact and should have a code indicting the failure.
The problem i see is that many dealership techs jump at the "replace the ecu" option in the event that any fault code even hints at an ecu issue. It will often be just a symptom but the fastest fix is a swap.
If you get the code pm me and I can give you the possible cause.
dadsEH
Well-known member
It's those pesky Koreans I tell you, it's all a commie plot!