For the record,
Adaway doesn't cause any app to crash, nor does it prevent any ad from being displayed. It merely provides a mechanism to simplify the tedious process of editing the
hosts file manually. What really matters is which URLs are redirected via that hosts file. Those URLs come from either the hosts sources that you ask AdAway to download and apply, or from any whitelist or blacklist you may have created. Don't blame or credit AdAway for your selection of URLs, it merely does what you ask it (unknowingly?) to do...
For example, if you have an app that crashes when AdAway is enabled but runs fine without it, enable the convenient DNS Requests Log and find out which URLs that particular app needs to access. The default lists are useful starting points but they may be overly aggressive or let too many ads through. Loading more lists is not necessarily a wise option. There are no universal answers even when referring to a specific app since it often depends on your ISP, location, settings, etc. In other words, simply asking here what to do to allow "MyRandomApp" to run can only bring you guesses from other members and if they don't work in your case, look at your own DNS log, on your own device, while running your own copy of "MyRandomApp". Spend a few minutes understanding the basic wildcard mechanism (not specific to AdAway) and you'll be able to quickly enable or disable any URL you desire.
Note that none of that matters if an app bypasses the hosts mechanism and calls a numeric IP directly. Those direct calls, common in some games, don't go through DNS at all and therefore can't be altered by AdAway or the hosts file. The same applies to processes that use an external DNS resolution scheme, such as the Chrome proxy ("reduce bandwidth usage") or the DNS bypass used by some ISPs (Satellite providers, for example).
AdAway is a wonderfully useful application and a "must have" for any Internet-enabled Android device. Expect it to do its job perfectly, but don't expect it to perform any magic!