You know, if you're getting BSODs on Windows startup, one of two things is happening:
1. Corrupted files are being installed.
2. Bad hardware is behind it.
And "bad hardware" can be anything from "bad CD drive" to "bad RAM." Any of which could also result in corrupted files on the hard drive, too. But the stuff nLite does shouldn't alter the actual installation to the point that it would produce a BSOD. It is literally just adding files, it's not going to rewrite DLLs or anything of that sort. I've just never heard of this happening with nLite, but I have had bad RAM cause bluescreens in very predictable fashion.
1. Corrupted files are being installed.
2. Bad hardware is behind it.
And "bad hardware" can be anything from "bad CD drive" to "bad RAM." Any of which could also result in corrupted files on the hard drive, too. But the stuff nLite does shouldn't alter the actual installation to the point that it would produce a BSOD. It is literally just adding files, it's not going to rewrite DLLs or anything of that sort. I've just never heard of this happening with nLite, but I have had bad RAM cause bluescreens in very predictable fashion.