So first off, let me preface by saying that my computer is not overheating. It's not even two months old, and I play tons of other games on it just fine, some even simultaneously.

My computer is an ASUS G20AJ-B07 purchased from my local Best Buy. It has enough power to throw at just about anything I want to do. I have upgraded it to Windows 10, and I have all updates installed as of my check last night. I have nVidia Experience installed and have the most recent drivers. Beta drivers channel does not have a new version. I have a two monitor setup.

So here's what happens. When I'm playing BnS, after a seemingly arbitrary period of time, I'll make some action, whether it is movement or interacting with an NPC, and the game sound will stutter and the video will go black, grey, blue, or white. My second monitor (which I use for watching streams and interacting with Teamspeak) will also turn to one of those colors, not always the same one. Teamspeak and my stream will continue making sound for as much as 30 seconds, and then cease. My computer will sit there with no change happening thereafter; I have waited 2 minutes once and saw no change. No input is accepted either. The only solution at that point is to hard power down my PC and turn it back on.

I had a theory that it was graphics settings, as I had only ever experienced it after I turned up my graphics. I tested this and turned settings down, and experienced it again.

I'm willing to locate system log files and pastebin whatever is needed. Just help me out here and I'll work with you. I appreciate all help I get.

SOLVED? Maybe? THAT WAS NOT IT!
It appears that Google Chrome's sandboxing feature is causing Game Guard to flip out. The solution is to not have Chrome open, or to execute it with the --no-sandbox flag. I haven't tested this rigorously yet, but it appears to be correct.

ACTUAL SOLUTION!
So as it turns out, it has NOTHING to do with Chrome. Turns out, it was a malfunctioning driver. Of this I am 95% sure, as I've yet to get another crash in my limited testing. I found this out by running Window's Driver Verifier program from the command line.

For those who may share this issue and wish to repeat my steps yourself, type "verifier /standard /all" without quotes from an elevated (Run as Administrator) Command Prompt. It'll ask for a reboot. After rebooting, it'll attempt to boot up, and probably crash before you even see your desktop, at least that's what happened for me. After booting into safe mode and running the command to deactivate verifier ("verifier /reset"), you can reboot normally and download the program WhoCrashed to analyze the log. If you need it, the log can be found at "C:\Windows\Minidumps". After finding out what the issue is, you can update or uninstall the drivers for the bothersome device.

For me, the device causing the kernel panics was my Wifi card, which has never worked on Windows 10. Not sure if it ever worked on 8.1 before I upgraded. I went into Device Manager and actually uninstalled the device entirely, as I have no need for Wifi. I also made sure to check the "Remove Drivers" tickbox during the uninstall process.

That was the actual solution. Again, I've only played a little bit since then, but I did manage to start and run the game for a while with a second verifier session running, in hopes that it WOULD crash again and I could further isolate the issue. But alas, it never did. Verifier takes a lot of memory, and the game failed to make it through a loading screen at one point, sitting idly by all night as I slept. After that, I ended up closing the game and disabling verifier again, and rebooting to get a clean session.

I've only tested for a little while since then, but things seem much better. I'll follow up if I get get any more crashes.