Thanks John! From the code sample you've sent, I've managed to reproduce and analyse the issue.
The problem is caused by the NUnit.Framework.dll assembly being resolved twice inside the NCrunch test environment. NCrunch V2.X is packaged with NUnit 2.6.3, and the solution you're working with uses NUnit 2.6.2. Because of the version inconsistency, the framework DLL gets loaded twice each time under a different version. This skews the CLR's internal logic and causes some very strange things to happen inside NUnit.
Most NUnit features seem to be able to operate normally, but ITestAction appears to be different. The difference between assemblies causes NUnit's references to this interface to fail without a consistent pattern. This means that on some systems the problem appears, while other systems are perfectly OK.
The easiest solution is to just delete the file: C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Remco Software\NCrunch for Visual Studio 2013\NUnit.Framework.dll
This file was never supposed to be included in the NCrunch installer, as there is no need for it when solutions already have it included. It only seems to be causing problems anyway. I'll ensure its removed for all future versions of NCrunch.
Thanks for all your help in getting to the bottom of this one.
Cheers,
Remco