We have duplicated this issue with multiple ODBC drivers and the native SQL Server driver. It appears to be unrealted to the data source and instead a generic problem with relationship building when cross filter detection is set to "both" in Power BI Desktop (Nov 2018 release tested, but previous releases have the same issue as well).
Steps to duplicate:
1) Connect to data source
2) Load a couple tables (ideally tables that don't already have relationships)
3) Create a relationship between 2 tables. 2 keys about this...
++ You must select "Cross Filter direction = both".
++ You must click "OK" while the dialog still says "Validating...". (use a data source on a slow network if possible, or otherwise slow down your data source at this point)
4) Power BI will present the above Validating Relationship dialog. Hit "Skip" while this is still present. SQLDUMPER is called, and Power BI crashes.
++ Note this only happens if you've selected "both" for cross filter detection. "single" works just fine.
With tracing turned on, you can see this exception in the logs when it happens...
Message: Unable to read beyond the end of the stream.
at System.IO.BinaryReader.FillBuffer(Int32 numBytes)
at Microsoft.Mashup.Evaluator.MessageSerializer.Deserialize(BinaryReader reader)
Since the app fully crashes, I can't send a frown/traces but would be happy to provide more details to get this issue cleaned up for our customers.