BSOD while viewing twitch.tv streams

NoelDP · 06 Nov 2014

Let's start with the easy one...

I've uploaded afile - shkaa.zip - to my OneDrive at Noel's OneDrive

Please downloadand save it.
Right-click onthe downloaded file, and select Extract all…
Extract to thedefault location - which will create a new folder shkaa in the same place.
Open this folder- there should be one folder inside it (Manifests)

Copy the content of the manifestsfolder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Nowrun the CheckSUR tool again (it may take a while)

Postthe new CheckSUR.log file, and the CheckSUR.persist.log file.

Sethlock · 06 Nov 2014

Thanks again for the responses.
After about 90 minutes with a twitch channel streaming my system locked up. There was no blue screen, but the display froze and sound began to loop. After a few minutes this was not changed so I rebooted from the tower. Windows wanted to do a disk check on reboot, which I let continue. I did not see any note of errors found or repaired, but I don't know if this would leave a log that might be useful.

Since then I have removed my Nvidia driver and installed 340.52. I also followed NoelDP's direction with the manifest file. The new CheckSUR logs are attached

This evening I decided to try the Intel Burn Test on my system. The program is unable to run, giving an error of a corrupt file.
C:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll is corrupt and unreadable.
Chkdsk does not appear to change anything, and as before no bad file records are noted or other problems. Searching a bit suggests an issue with .Net framework. I attempted to remove and repair this installation with the Microsoft Fixit program, however this fails to run with the same error.
After removing .NET components I attempt to reinstall from the full dotNetFx45_Full_setup and receive a fatal error. These logs are also attached.

NoelDP · 07 Nov 2014

OK - the fix I gave you repaired the Manifest file error - now we have to fix the other files - one of which may be related to the error you're seeing.

I've uploaded afile - shkab.zip - to my OneDrive at Noel'sOneDrive

Please downloadand save it.

Right-click onthe saved file and select Extract all...

Change the targetto C:\ and click on Extract
Close all windows(it would be a good idea to print these instructions!)

Now reboot to theRepair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced BootMenu, at the top of which should be the option'Repair my Computer'
Pick that

You'll have tolog in with your username and password.

Pick the optionto use a Command Prompt
At the prompttype
DIR C:\shkab

hit the enter key- if you get a 'Not Found' error try
DIR D:\shkab
or
DIR E:\shkab

The drive letterin use when you find the folder will need to be substituted (for<drive>)into the following command...

XCOPY <drive>:\shkab <drive>:\windows\winsxs /y /i /s /v /h

(e.g. XCOPYP:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command(it should take almost no time) and when the prompt returns, type

EXIT

and hit the Enterkey to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt

then reboot andupload the new CBS.log file to your reply

Sethlock · 07 Nov 2014

I had hoped to copy the files you shared and do the repair this morning, however I ran into an annoying issue. I cannot seem to get mouse or keyboard support once I get to the Windows Repair screen. I have both available in BIOS, but as soon as I select the repair option I lose them. They are both typically plugged into the two USB 2.0 ports on the back panel of my PC. I tried the other ports which did not work, although this could simply be because they're all USB 3.0. I also tried the front panel ports which are USB 2.0, but no success there. My mouse LED remains on but this just means there is power as the LED is on with the system powered down so long as the PSU is switched on.

In BIOS I didn't find anything I could toggle that might help. Legacy USB support was already enabled. The only possibility I found would be switching USB support from partial to full. However, this was section was grayed out as its part of Fast Boot options, which as a group isn't enabled. This evening I may try switching Fast Boot on and enabling full USB support. I am also trying to scrounge around at work for a PS/2 keyboard, but I'm not expecting any luck there.

I don't recall having any issues with my initial installation of Windows 7 on this machine, which was done with the same peripherals. Hopefully I will get some time at home this evening and can actually implement your fix and post the SFC results.

Sethlock · 07 Nov 2014

No success with any combination of BIOS changes or USB ports. I am unable to get peripherals to function when entering Windows System Repair. Guess I have really managed to screw things up.

NoelDP · 08 Nov 2014

No PS/2 Keyboard available anywhere?
Never mind, we can always try using a DVD ...
Since you install appears to be based on a OEM System Builder license, you should have the OS DVD available.
Boot with that - make sure that you choose the option to Repair rather than install!
Once you have accessed the system, follow the same instructions as above.

Sethlock · 08 Nov 2014

Thanks for your patience with this, it does seem like each bit of help reveals some other issue.
I had no luck tracking down a PS/2 keyboard or mouse. Any old hardware I could find around the floor came from 10+ year old Macs, and so the peripherals were useless.
I do have the Win7 SP1 DVD I originally installed from. When I select Repair from there I am told I am attempting to repair a different version of Windows from the one on the media and have no recourse but to exit.
I went digging around my own boxes of old crap at home, knowing I definitely have no non-USB keyboards. I did find a turn of the century adapter for USB-PS/2. So I was finally able to boot into the repair mode (not from the DVD), albeit with only keyboard support. Regardless I followed your directions, finding that I had to switch to D: rather than C: for whatever reason. I copied the files with all flags noted, and the new CBS.log is attached.

Regarding the usage of this message board, I realize that this specific area is for BSOD issues which is what initially brought me here. As of last night I have not had any of the PAGE_FAULT type errors that I'd been experiencing. Now I have still had complete lockups requiring hard reboots while streaming (and only then near as I can tell), but in terms of how this area is meant to operate, should I mark this thread as solved? Do I migrate discussion and further questions elsewhere?

I really appreciate all the help, and clearly have many more system problems to resolve than what I initially realized. At this point I have Windows wanting to (and subsequently failing to) install updates to .NET frameworks which I do not have, and am unable to install. The dwm.exe must have shutdown 4 times last night.

NoelDP · 08 Nov 2014

No problem.
The SFC log shows that we managed to fix the problem with the system.dll file - hopefully this will reduce the error-count from that source.

SFC is happy - but the system needs a reboot to properly 'set' the repair. Once you've done that, the BSOD guy can carry on with their stuff and I'll retire back to my WGA/WU grotto

Sethlock · 09 Nov 2014

Thanks again for your help.

I did not get an opportunity to leave the computer streaming yesterday. Today within about 10 minutes loading twitch.tv I got a BSOD. There was no system lockup, just an immediate crash and automatic reboot. I've attached a newly collected system information collection including the minidump.

NoelDP · 09 Nov 2014

Code:

Event[2670]:
  Log Name: System
  Source: Ntfs
  Date: 2014-11-09T10:34:06.676
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Seth-PC
  Description: 
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume4.

Click on Start > All Programs > Accessories

Right-click onthe Command Prompt entry

Select Run as Administrator and accept the UAC prompt- the Elevated Command Prompt window should pop up.

At the Commandprompt, type

CHKDSK C: /R

and hit the Enter key.

You will be toldthat the drive is locked, and the CHKDSK will run at the next boot - hit the Ykey, and then reboot.

The CHKDSK willtake a few hours depending on the size of the drive, so be patient!

After the CHKDSK has run, Windows should bootnormally (possibly after a secondauto-reboot) hen post a new set of logs.