Thank you, Nathan. I have separated out the loops and multi-parts from my load feature class. I then had to partition the load feature into 7 different features classes and load each individually until I find the offending feature(s). This is a very cumbersome and time consuming process. We're all hoping this issue is resolved in 10.6. However, I do wonder how that could be. Perhaps you can shed some light on this?
In the meantime, I will submit a ticket to ESRI most likely on Monday.