I'll start off by saying that I've been working on a game that would serve as a standalone for the desktop. I noticed that the standalones Adobe released all have the same issue (At least for my OS, win7), "waiting for next frame". Although when I play it on Chrome, it plays without grey bars exceeding the red line at 60fps. When using the standalone my game tends to stutter and behave unusual, which leads me to the real question:
What does scout mean "waiting for next frame"?
What can be done to resolve this?
Is there another form of standalone I could use without defects?
"Waiting for next frame" covers all the time when Flash Player is inactive, and waiting to be woken up by the operating system - i.e. it's finished all its current tasks, and is waiting for an event or a timer to happen, that would trigger that it needs to do something. You can read more detail about how Flash Player works here: http://www.adobe.com/devnet/scout/articles/understanding-flashplayer-with-scout.html
If waiting for next frame is taking you over your per-frame budget, then check that you're not running a lot of other processes at the same time - you can see what the CPU-usage is in Scout. Flash Player relies on the operating system to 'wake it up' for the next frame, so if the OS is busy with a lot of other processing, it may not reliably wake up Flash Player.
The chances are that what you're experiencing is a problem with the environment on your machine, rather than with the standalone flash player.