Duke:
I thought that maybe your problem was related to an 91 NSX I owned. However, now I am not so sure. Nevertheless, your VIN is low, so maybe there is a similarity.
The ALB and TCS warning lights came on twice, simultaneously, with the attendant "jolt" you reported. On the third instance, the engine and dash lights went completed dead. Then, mysteriously, after about a half-hour, the car started and the dash lights worked, however, both the TCS and ALB lights were illuminated.
It took four trips to the dealer (September/90 through May/91) to diagnose and find the problem.
Nevertheless, here is what I was told, at that time, during those service visits.
1. Early and later production 91 NSX's had different grounding systems. As you know, there is a preponderance of aluminum used in the NSX. Typically using the chassis as a master ground system (as in a steel body car) is problematical in the NSX because aluminum does not conduct electricity as well as steel, and a surface oxide forms on aluminum which does not conduct electricity. It was originally conjectured that this was the problem with my vehicle -- a bad ground, somewhere.
2. Many telephone calls were made to the Acura "Tech Line" in California. The first recommendation that they made was to update the engine ground. (Acura Op Code 737099-066-D99.
3. This did not fix the problem, and in fact after this repair, the engine and dash went completely dead as noted above.
Back to the dealer it went. An original ground strap that was supposed to be removed during No. 2 above, was removed. The service order also said an "open" circuit was fixed (the open circuit was unidentified).
Regretfully, the Acura service repair codes were not listed on the service order for the removal of the ground strap and the repair of the open circuit.
Anecdotally, I later spoke with the NSX Technician in California and he reported to me that the NSX test vehicle at his disposal had the same missing ground strap as my vehicle. He was quite surprised.
I later sold the vehicle, so I have no idea whether the problem was conclusively repaired.
Checking those computer codes is a good first step, although in my case, there was no uniformity in what the computer reported.
Good luck.
[This message has been edited by nsxman (edited 06 December 2001).]
