BSOD while streaming to Twitch, error 0x8000000000000002

I have searched for a solution to this problem but haven't had any luck. Last night I was playing Dark Souls and streaming to Twitch. About an hour and a half into the stream my computer locked up and a BSOD appeared a moment later. I'm attaching a log of the BSOD and I'll be pasting the Event Viewer info below. This happens every time I stream to Twitch no matter what game I play pretty much anytime after the one hour mark.

But here's the thing. I have gotten the same BSOD in several other situations. It happened several times while playing Rust and talking to a friend with Ventrilo and also while playing League of Legends and using Google Hangouts for voice chat. It also happened while video chatting with a group of friends using Google Hangouts with no gaming involved. The only thing all of these events have in common (that I can see) is that I had my Astro A40 headset plugged in and in use. I have tried plugging it into the back ports and top ports as well as only plugging in the mic or only the headphones. None of that seems to make a difference in the BSODs. I may be completely wrong about the headset having anything to do with it. That's why I'm here seeking help.

Here is the Event Viewer log:

System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2014-08-14T05:54:02.518414100Z

EventRecordID 34847

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Ross-PC

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 292
BugcheckParameter1 0x0
BugcheckParameter2 0xfffffa800d964028
BugcheckParameter3 0xbe000000
BugcheckParameter4 0x100110a
SleepInProgress false
PowerButtonTimestamp 0

I've attached the BSOD logs. Thanks in advance for any help you all can provide! Let me know if you need more info and I will do my best to get it to you.

Giving this a bump since its several pages back now. I would really appreciate anyone's help with this. I tried to interpret the minidumps on my own but I don't know what I'm looking at. Thanks!

Thanks for the help!

I did a Clean Boot as requested and did 5 cycles of rebooting and scanning. The fifth scan still said there were errors that couldn't be repaired. Should I continue rebooting and scanning or is it unlikely to fix the errors at this point?

Hello,

The Nvstreamsvc has shown up in some crashes that I have, often which occour during streaming.

After reading about it, the process is unable to be terminated (it will say you do not have permission). It only appeared for me after updating to the latest Nvidia drivers, and did throw an error on initial restart after installaion, saying the service could not be started, as the machine was shutting down.

I hope you fix it!

I did run the command prompt as an administrator so sounds like that's not going to work. I attached the zipped CBS.log file.

Just to let you guys know.

After fixing my hdd index errors, and still getting BSOD similar to this, I removed all the new nvidia software except the drivers - audio, 3d, experience...

Since then - I have had NO BSOD at all while streaming across my network, or to the internet.

Nvstreamsvc.exe process, I couldn't terminate to test. Removing that process fixed the BSOD, I hope!!!

The only problem was that Photoshop didn't recognise the openGL function, and I had to enable it manually - after restart of photoshop, it recognised the card and all software functions were restored!

I hope my issue is sorted, and I hope this guy's issue can be sorted by removing the offending Nvidia software!

I will stream to twitch all afternoon, when I am home - and we will see if this was the problem!
Thanks!!!

Okay, sorry for the delay. Been a busy couple days.

I ran the SURT and then rebooted and ran another SFC scan. It still found errors that it couldn't repair unfortunately.

Also, tehsaccade did that fix your problem? I may be having a separate issue entirely because this has been happening since at least February not just since the most recent driver update. But I'm still curious.