Allegedly, on or about 21 February 2018, Stephen Morris sent:
I been in the situation of compiling kernel modules in other linux distributions where you could put statements in your source to stop these messages, but I have forgotten what they were.
A install is tainted by having certain kinds of things installed (in this case, binary support files that are not open-source).
It will still be tainted (i.e. not suitable for providing bug reports to sources that need the computer to be running in a defined state), even if you try and pretend that it is not (faking the flags).
To untaint a a kernel (e.g. for the purposes of debugging something), you have to stop using the modules that cause the tainting (you'd unload the Nvidia graphics driver and use a generic one, in this case). If, after doing that, the problem still occurs, you can make a bug report that can be used by the debugging team. But, if after that, the fault goes away, it points rather firmly at your binary blob being the cause of the problem. And since nobody here can debug closed source software, you're stuck.