Hey gang - thanks for the continued discussion! Definitely not a solved problem...and now have some new data for everyone to consider.
My ride from Indy to ATL on July 3 went something like this:
1. Indy to Lville. Stop for breakfast for ~35 minutes. Bike starts up and runs fine afterwards.
2. Lville to somewhere just south of Lexington. Stop to use restroom and top off tank (because keeping the tank topped off on my way back from CO a month ago seemed to help, but now I'm not so sure the fuel level is a factor). After this quick stop of less than 10 minutes, I hit the interstate and the bike started exhibiting the same fuel starvation symptoms within a few miles. A short stop on the shoulder of less than 10 minutes and the bike fired back up again and ran fine once I got going.
3. South of Lexington to Rest Area near KY/TN border to deal with a phone call. Kept the bike running during this stop because this fuel starvation issue has only seemed to pop up after shutting the bike off for a quick stop. Since I knew this would be a quick stop, I kept it running, the temp gauge increased as normal, fan kicks on etc...and once back on the road I have no problems.
4. Rest Area to South Knoxville - fuel stop. Turned bike off to fill tank at gas station near intersection of 129 & 411 before heading towards the Dragon. Less than 15 minute stop. Bike fires right up and starts as normal. Turn onto 129 and bike starts exhibiting symptoms within 2 miles. Pulled over before it died completely and gently revved throttle listening for the bike to "correct" itself which it eventually does. Back on the road and by the time I get another few miles to the intersection of 129 & 72 where the Dragon BBQ Pit and the 129 Motorcycle Garage Restaurant are, it is wanting to die again. Since it is starting to rain and lunchtime, I pull in figuring that by the time I have lunch the bike will have sat longer than it usually needs to sit when I've been on the side of the interstate and might be ok after lunch.
5. After lunch it fired right up again, but died on me twice before I could even get to the Harley Davidson shop just a few more miles down the road (this is all still before the official start of the Dragon). Pulled in there, let it sit for another 25 minutes and decided to start heading back towards 411 where I would at least have cell service again. Died on me twice more by the time I got the few miles back to the 129 Motorcycle Garage Restaurant at 129 & 72. That is when I posted the stranded rider post from a Gold Winger's Verizon phone that had service (my Sprint phone did not). However he decided he needed to roll before I could really get a full post created, which is why it was so vague. I eventually was able to call my wife from the restaurant phone and she updated the post with a bit more info. Also had her pull up the RAN list and after seeing that there wasn't anyone in/around Knoxville (and the bike had been sitting for an hour or more), I decided to try it again to get back towards 411 where I had cell service.
6. Fired up as normal and as I rode 129 back towards 411 it ran without any issues whatsoever. Turned left on 411 and headed to ATL which was 120 miles away and decided that I wouldn't shut the bike off until I got there. Ran completely fine the entire way.
ATL to Indy on July 4th
I was in ATL to carry a videocamera guy on my motorcycle for the Peachtree 10k road race. So my morning consisted of the bike starting right up, moving it over to the start line 2 minutes away from my hotel where I turned it off and it sat for 90 minutes or so. Fired it up for the race and rode the 10k distance at just under 10mph or so covering the athletes. Once done, I kept it running as I said my goodbyes and then hit the road for home.
After seeing the day prior that fuel level didn't make any difference, I decided to keep the bike running the entire way home. So my 550 mile ride included 2 fuel stops where I refueled with the engine running and one additional stop where I did the same. The bike didn't skip a beat the entire day...nearly the entire ride was in the rain and temps were in the low 70s eventually dropping into the 60s as I got further north. One of the stints I ran the tank all the way down until the low fuel light came on - something I hadn't done since early May when I thought that there was something related to fuel level tied into all this. Had no problems running the fuel that low...
Looking for consistencies across all occurrences of this issue, it seems that it happens after the bike has been running for awhile (engine has a chance to get hot), the bike is shut off for a short period of time and then restarted.
It appears that over the last 2 days I proved that it does NOT happen when the bike has been running for awhile (engine has a chance to get hot), the bike sits for a short period but I leave the engine running and then I take off again.
Is there a component that is engaged during the process of starting the bike that would affect fuel delivery a few minutes later?
A few reminders regarding my bike: vacuum shutoff has been bypassed for a few years, no "air suck" venting occurs when I open the gas cap after the bike dies or any other time. Fuel pump has already been replaced with an Airtex that fit exactly as the OEM. Fuel filter assembly has been changed to the glass Purolator version and filter element was replaced last month as a precaution although the first one looked fine.
Have not tried running the bike with the gas cap unscrewed.