Did you recompile the code? We normally compile with the /traceback option enabled so we can see what lines a job bombs on. You could use that to see what line it is trying to read and then look at the source code. Without that information, it is impossible for us to tell you what is wrong with your input file. You may have added or removed one of the lines and the code is looking on the wrong line for something.
Have you tried turning on the Echo flag at the top of the .fst file? It will create a file with the root name of the .fst file, but with a .ech (or .echo) extension. That will show what has been read in. Having never used the noise feature, I have no idea if the noise data gets echoed too.
You may also want to look at your input file side-by-side with one we distribute with the code to ensure everything still lines up.