YES!!jcbecker28 said:If you can't fix it when there is a problem, then don't build it.
"Codes" are a programmers best guess at what will go wrong. So the lack of codes should not mean there is nothing wrong. The lack of codes during an actual problem actually means someone didn't do their job in writing the codes. It should not shift liability away from the manufacturer and onto the customer.
If there is no code, the next step should be diagnostics. Simple, sometimes time consuming tests, to validate what is know and eliminate variables.
Once a level of confidence is gained, then start replacing parts.
Once parts are replaced, and the problem solved, write a TSB, make them publicly available, and disseminate the information as quickly as you possibly can. One disgruntled customer will take 10 more people with him. I know for a fact that we will be leaving GM products. And telling everyone we know about our experience. My friend that owns the local garage also told us not to buy a GM product. Unfortunately at the time the Traverse was really the only vehicle that fit our needs and looked good doing it.
Another friend that owns a heavy truck repair business said it best "When the service guy tells you they've never heard of this before that is absolute BULL$HIT!"
In this case my problem seems to be one of two choices. I'll know by 2pm Saturday.
Now, on the topic of "no codes." A friend is the head mechanic at our local Ford dealer. He called me up and was explaining how he had a Mustang that was backfiring flames out the intake - the entire time setting no codes! Imagine that? Would GM simply tell us that a burned air filter was "normal?" I stopped in on my way by. He went to his toolbox and got out a good old fashioned analog vacuum gauge. The other mechanics in the shop came over bewildered as if he had a piece of alien technology in his hands. Surely a puck like object with only a hose dangling from it could be of no value!