Exception in rendering! Message: window is not defined ReferenceError: window is not defined at new c (/tmp/execjs20161208-5336-w7o936js:136:3912) at m.mountComponent (/tmp/execjs20161208-5336-w7o936js:47:15602) at /tmp/execjs20161208-5336-w7o936js:49:31860 at a.r.perform (/tmp/execjs20161208-5336-w7o936js:47:12503) at Object.a [as renderToString] (/tmp/execjs20161208-5336-w7o936js:49:31821) at r (/tmp/execjs20161208-5336-w7o936js:50:21164) at Object.S.ReactOnRails.serverRenderReactComponent (/tmp/execjs20161208-5336-w7o936js:32:6073) at eval (eval at <anonymous> (/tmp/execjs20161208-5336-w7o936js:173:8), <anonymous>:10:23) at eval (eval at <anonymous> (/tmp/execjs20161208-5336-w7o936js:173:8), <anonymous>:17:3) at /tmp/execjs20161208-5336-w7o936js:173:8
I own a super duty XLT 5 passenger van with 110,000 miles on it. Last month I did a full tune up - changed the spark plugs, fuel filter and air filter. I drove about 800 miles this month. Last week my van died while driving 50 mph on major highway. I lost power control, and it wouldn't start. When I turned the ignition it made an alarm sound - ti to ti to ti to - and where the odometer is it read “Rsc not working.” I had my van towed to a Ford specialist. The van started while the repairman checked it out. He left it on for a few hours and drove 20 miles with no problem. He said it’s a harness or wiring issue for sure, but he can’t figure out the problem until the van goes dead again. It died driving 80 more miles at 55 mph. The same alarm noise went off when I turned the ignition. The check engine and a few other warning lights came on after it died. The battery and lights worked fine. It started 10 minute later and ran like new then died after driving 2 miles. It started again 5 minute later but died after driving 3 miles. The next day it wouldn't start at all, so I had it towed it to the mechanic on Saturday. When he checked it on Monday he said the van started fine. I had him drive it for 4 days until he put 100 miles on it. Nothing went wrong. Then I put on another 350 miles last week. I don’t know what to do. Do you have any ideas or suggestions as how to solve this problem?
Hi there, thanks for writing in about your 2007 Ford Econoline E-350. I could only speculate that if you lost power and the computer did not set any codes, then you may have a problem with power to the computer system. Either the main computer power relay or connection to it is causing the issue. The fuse box on this year's vehicles were problems that the fuses were losing contact and causing stalling due to the fuel pump relay fuse. Pull out each fuse and relay separately and look for heat marks and repair connection as needed. Some may need to have a harness made outside the box. If you would like assistance having this checked, a certified technician, such as one from YourMechanic, can come to your home or office to diagnose the stalling issue and let you know what needs repair.
Have a car question? Get free advice from our top-rated mechanics.
Our certified mechanics come to you ・Backed by 12-month, 12,000-mile guarantee・Save up to 30%