Often this error occurs without warning, somewhat randomly and usually with disastrous consequences to your ETL operation. We recently experienced a random set of these and were able to track them down to the usage of the SQL SERVER BULK LOADER delivery module in the crashing fact builds.
It appears this loader struggles somewhat if you are delivering SMALL quantities of data using this delivery.
The fix is to simply change it to the Relational Table delivery and these particular Access Violation errors go away. We have not experienced this issue with our loads that deliver a million rows or more. Possibly the commit interval could have been lowered on the failing builds to increase reliability but, at less than 100000 rows the relational delivery operates just as effectively and more reliably.