The dropout could also be caused by paging activity. If the player allocates a bit too much cache, this could cause pages of the player's binary to be pushed out of memory. As soon as any code-path hits one of these pages, the player will pause until the disk is spun up and the page is read back.

Has anyone who is seeing the wave dropouts tried the reserve_cache= option in config.ini?