You should be able to run this through Visual Studio using the Debug Editor Win64 configuration. The same arguments are usable on the commandline (-log, -run, -config, etc.).
Alternatively, if you have a small project that reproduces the issue and can zip it up, I can debug that. 4.6.1, right?