I'm glad that did the trick!
I've seen similar situations where simply re-naming a problem file and re-linking to it fixed some weird behavior, not just render crashes. My best guess is that a cached version of the file gets corrupted, and by changing the name, you force the cache to refresh with uncorrupted data. I've seen this in lots of places, not just Octane or even just in rendering, but in computing in general.
Flushing caches is a very useful, general-purpose problem solving trick, but there's so much caching done on so many levels by so many different processes these days, it's nearly impossible to know where they might have gone bad. And system designers rarely give users the option to manually flush them. Most of the time, they work fine, but when they don't, it can be a bugger to track down.
It's still worth passing on the crash data to Otoy, since the system really should fail more elegantly than crashing out. Bad/corrupted data should cause an error, not a crash, but it's impossible to foresee every contingency.
Technical Director - C4D, Maya, AE, - Washington DC