I see a paradox that the null bytes are "not related" to the current situation and yet deleting the file seems to cure the issue. Perhaps the CS official statem

I see a paradox that the null bytes are "not related" to the current situation and yet deleting the file seems to cure the issue. Perhaps the CS official statement that "This is not related to null bytes contained within Channel File 291 or any other Channel File." is poorly worded. My opinion is that CS is trying to say the null bytes themselves aren't the actual root cause of the issue, but merely a trigger for the actual root cause, which is that CSAgent.sys has a problem where malformed input vectors can cause it to crash. Well designed programs should error out gracefully for foreseeable errors, like corrupted config files. If we interpret that quoted sentence such that "this" is referring to "the logical error", and that "the logical error" is the error in CSAgent.sys that causes it to crash upon reading a bad channel file, then that statement makes sense. This is a bit of a stretch, but so far my impression with CS corporate communication regarding this issue has been nothing but abject chaos, so this is totally on-brand for them.