soladis66 said:
and I already know it is due to OBS not communicating correcting with the CPU.
If OBS were "not communicating correctly with the CPU", as in just executing bad machine code or something, the app would crash. It would not cause a blue screen of death, as OBS runs no kernel code. Only kernel code can cause a BSOD. They cannot be directly caused by OBS, because OBS is a user level program. Sigh, sadly, as a developer, when I try to explain to the user the concept of blue screens of death, they tend to ignore me. Listen, I understand that you don't wish to be told that you are incorrect, but unfortunately in this case you are indeed incorrect.
Let me yet again go into the concepts of how operating systems work. An operating system typically has two operating levels, kernel level, and user level. The
kernel comprises of the actual kernel, drivers, and everything that needs to access devices and the system directly. When the kernel crashes, this causes a blue screen of death. This is typically caused by either a bug in kernel code or instabilities or bugs in hardware, or a combination. A blue screen of death can only happen in kernel code, which OBS does not have.
Then there's user space.
User space is for user programs, such as OBS, your web browsers, games, and everthing that is run by a user. In user space, when something is not executed correctly, or doesn't work right, it can safely be recovered and simply crashes the program itself. A user space program cannot directly crash the kernel, because it does not execute kernel code. It can increase system instability, especially in the case of stressing out your CPU, by, say, running a heavy-duty encoder and game at the same time, but it cannot cause a blue screen of death directly. Of course, a user space program does communicate with the kernel, but only the kernel code can cause a blue screen of death. This is simply a fact. Again, OBS cannot directly cause a BSOD.
What people don't realize is they play their game and stream at the same time, both of which are two CPU/GPU intensive activities going at the same exact time on the same CPU/GPU. You are probably going to use quite a bit more CPU/GPU while streaming a game than you will any other activity, so it will bring out the possibility of instabilities with overclocks. It's like running multiple games at once, only encoding typically takes even more CPU power. It stresses the CPU quite a bit.
I know you'll probably just ignore everything I've written because you don't want to be told this, but you cannot make such statements without at least a proper citation to back up such a claim. "Only happens while streaming" does not equal "Proof that OBS is not communicating with the CPU properly". If it were "not communicating with the CPU properly", would that mean an incorrect instruction was executed? If that were the case, all it would do is just cause the application itself to crash, not the kernel. Your statement unfortunately has no basis in actual computer science.
See
http://en.wikipedia.org/wiki/Blue_screen_of_death for more information. Specifically, the part where it says "BSoDs can be caused by poorly written device drivers or malfunctioning hardware, such as faulty memory, power supply issues, overheating of components, or hardware running beyond its specification limits"
