If you still can't find a fix, I've figured out a sloppy way to work around the bug, after running into the issue a bunch of times. Basically, blueprint your turret wall without the searchlights, then paste them in afterwards. It's not ideal, but at least it keeps the game from crashing.
I'm also playing with Rampant, so it's nearly impossible to completely clear biters within 100 tiles of the wall. I'm usually building my wall within searchlight range of the biters, which causes the searchlights to change state from safe->warning->firing immediately after they're placed, but while the rest of the blueprint is being built. That might be part of the issue, which would make it difficult to reproduce in the testing lab without enemies.
I've had to find a half-decent solution to this issue, because the The Ghostplacer mod is really good at triggering the bug, because it makes it easy to place down objects in a random=ish order by quickly moving your mouse over the blueprint. Bots always build the farthest away blueprints first, which means they don't usually trigger the bug if you're building your wall from the inside and the searchlights are on the interior side. Now that I have tons of fast bots and I don't need to use the ghostplacer mod to build walls while under biter attacks, I haven't run into the issue anymore.