I wanted to add that I get a similar error when I run 3dDeconvolve on my data as well...and like Iggy, the majority of my data ran fine using the same script, but there were a couple subjects that caused a BUS error in 3dDeconvolve.
I figured out that if I take out my motion regressors, then 3dDeconvolve will work without any problems, but if I add in the motion regressors, then the command will not function.
I suggest taking out the motion regressors to see what happens when you run 3dDeconvolve again.
Rick, have you encountered a BUS error? I'm not sure what it means and why taking out my motion regressors causes a difference. I've checked the motion volume registration file and it has the correct number of volumes, etc. Do you have any thoughts?
David