BSOD while viewing twitch.tv streams

I have consistently receiving a BSOD while viewing streams at twitch.tv. The timing is unpredictable, and it does not appear that I need to be doing anything else simultaneously to have a system lockup.

The resulting archive from the DM Log Collector are attached. In addition I have run the System File Checker and receive the message regarding a corrupt file that was unable to fix. I have attached this log file as well since I don't know whether its relevant or included in the collected zip file.

Final bit of information which may be totally unrelated. A Windows update from around 10/15/2014 has repeatedly tried and failed to update. This is:
Security Update for Microsoft .NET Framework 3.5.1 (KB2972100)

Thanks for any advice


Seth

Edit: Realized I could replace the incomplete system information archive with the proper file.

Allot of important info is missing from your zip, please follow Blue Screen of Death (BSOD) Posting Instructions to grab all and upload a new report here.

Hi koolkat77, thanks for the reply. I had not examined the zip file's contents before uploading. I had run the collector program to completion, but on my desktop I found a temporary folder which I could not access for some reason. I ran through the collector again and this time it cleared out the folder at the end and it looks like the zip archive contains more than just minidumps.
Edit: The zip file attached to the original post has been updated to include the full DM Collector output.

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\admin\Downloads\SETH-PC-Tue_11_04_2014__71907_58\110314-20763-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`0301b000 PsLoadedModuleList = 0xfffff800`0325e890
Debug session time: Tue Nov  4 06:14:46.836 2014 (UTC + 6:00)
System Uptime: 2 days 22:46:38.585
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff95ff00fb8d8, 8, fffff95ff00fb8d8, 5}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Could not read faulting driver name
Probably caused by : win32k.sys ( win32k+c7c03 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff95ff00fb8d8, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff95ff00fb8d8, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c8100
GetUlongFromAddress: unable to read from fffff800032c81c0
 fffff95ff00fb8d8 

FAULTING_IP: 
+0
fffff95f`f00fb8d8 ??              ???

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800a7891c0 -- (.trap 0xfffff8800a7891c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000053041f26
rdx=fffff8a01fe8e2a4 rsi=0000000000000000 rdi=0000000000000000
rip=fffff95ff00fb8d8 rsp=fffff8800a789358 rbp=00000000000000c0
 r8=000000000000000a  r9=0000000000000429 r10=0000000053041f26
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
fffff95f`f00fb8d8 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000310d5b3 to fffff80003090bc0

FAILED_INSTRUCTION_ADDRESS: 
+0
fffff95f`f00fb8d8 ??              ???

STACK_TEXT:  
fffff880`0a789058 fffff800`0310d5b3 : 00000000`00000050 fffff95f`f00fb8d8 00000000`00000008 fffff880`0a7891c0 : nt!KeBugCheckEx
fffff880`0a789060 fffff800`0308ecee : 00000000`00000008 fffff95f`f00fb8d8 ffffffff`c3040f00 fffff8a0`01293500 : nt! ?? ::FNODOBFM::`string'+0x43801
fffff880`0a7891c0 fffff95f`f00fb8d8 : fffff960`00167c03 00000000`53041f26 fffff960`00380e90 fffff880`0a7897f0 : nt!KiPageFault+0x16e
fffff880`0a789358 fffff960`00167c03 : 00000000`53041f26 fffff960`00380e90 fffff880`0a7897f0 00000000`00000000 : 0xfffff95f`f00fb8d8
fffff880`0a789360 00000000`53041f26 : fffff960`00380e90 fffff880`0a7897f0 00000000`00000000 00000000`000000c0 : win32k+0xc7c03
fffff880`0a789368 fffff960`00380e90 : fffff880`0a7897f0 00000000`00000000 00000000`000000c0 fffff880`02c8bc12 : 0x53041f26
fffff880`0a789370 fffff880`0a7897f0 : 00000000`00000000 00000000`000000c0 fffff880`02c8bc12 fffff8a0`01293500 : win32k+0x2e0e90
fffff880`0a789378 00000000`00000000 : 00000000`000000c0 fffff880`02c8bc12 fffff8a0`01293500 fffff880`0a7897f0 : 0xfffff880`0a7897f0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k+c7c03
fffff960`00167c03 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  win32k+c7c03

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5428aeb2

FAILURE_BUCKET_ID:  X64_0x50_BAD_IP_win32k+c7c03

BUCKET_ID:  X64_0x50_BAD_IP_win32k+c7c03

Followup: MachineOwner
---------

Here it seems like the NVIDIA drivers are creating a problem.

Code:

3: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f032000 fffff880`0fd0e000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Oct 16 18:31:28 2014 (543FBAA0)
    CheckSum:         00C97F5B
    ImageSize:        00CDC000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Reinstall an older version of the drivers and see if that provides stability.

Drivers - Download NVIDIA Drivers

Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program: How to

Perform a Clean boot:

• Troubleshoot Application Conflicts by Performing a Clean Startup

Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

• How to Change, Add, or Remove Startup Programs in Windows 7

Check for heating issues using Speccy or HWMonitor. Upload a screen shot with either of the tools:

• Speccy - System Information - Free Download
• HWMonitor CPUID - System & hardware benchmark, monitoring, reporting
• Screenshots and Files - Upload and Post in Seven Forums

Test your Hardware for Stability and Heat Problems with Prime95. Be sure to keep an eye on your temperatures when running these tests, especially the Large FFTs.

Stress Test Video Card with Furmark

Test your CPU Stability with IntelBurnTest.

The CBS.log shows the following summary for the SFC scan...

Code:

 Line 10321: 2014-11-03 19:36:46, Info                  CSI    0000031e [SR] Repairing 2 components
 Line 10322: 2014-11-03 19:36:46, Info                  CSI    0000031f [SR] Beginning Verify and Repair transaction
 Line 10323: 2014-11-03 19:36:46, Info                  CSI    00000320 [SR] Cannot verify component files for 305895c659d1ec256802c823f05edcf3, Version = 11.2.9600.17107, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
 Line 10324: 2014-11-03 19:36:46, Info                  CSI    00000321 [SR] Cannot repair member file [l:20{10}]"System.dll" of System, Version = 6.1.7601.17966, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 10325: 2014-11-03 19:36:46, Info                  CSI    00000322 [SR] Cannot repair member file [l:20{10}]"System.dll" of System, Version = 6.1.7601.17966, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 10326: 2014-11-03 19:36:46, Info                  CSI    00000323 [SR] This component was referenced by [l:156{78}]"Package_2_for_KB2742599~31bf3856ad364e35~amd64~~6.1.1.0.2742599-22_neutral_GDR"
 Line 10327: 2014-11-03 19:36:46, Info                  CSI    00000324 [SR] Could not reproject corrupted file [ml:520{260},l:98{49}]"\??\C:\Windows\Microsoft.NET\Framework\v2.0.50727"\[l:20{10}]"System.dll"; source file in store is also corrupted
 Line 10332: 2014-11-03 19:36:46, Info                  CSI    00000326 [SR] Repair complete

There could be more problems, as the manifests affected also define files that should be present.


Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it in your reply.

Please post the CheckSUR log as requested

Apart from a couple of payload files, the CheckSUR also shows this...

Code:

Unavailable repair files:
 winsxs\manifests\amd64_305895c659d1ec256802c823f05edcf3_31bf3856ad364e35_11.2.9600.17107_none_a04fc4acb2745cf9.manifest

I'll post a fix protocol for this and the other errors later.

There is no point of using 337.88. Thats the worst release by nvidia. At worst he can try 340.52.