Driver BSODs on Windows 8 and 7

All of the files here are in the original list - I missed them

Code:

2014-01-19 08:21:26, Info                  CSI    000001e2 [SR] Repairing 3 components
2014-01-19 08:21:26, Info                  CSI    000001e3 [SR] Beginning Verify and Repair transaction
2014-01-19 08:21:26, Info                  CSI    000001e5 [SR] Cannot repair member file [l:24{12}]"keyboard.drv" of Microsoft-Windows-NTVDM-System, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-01-19 08:21:26, Info                  CSI    000001e7 [SR] Cannot repair member file [l:18{9}]"l2057.dlm" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-01-19 08:21:27, Info                  CSI    000001e9 [SR] Cannot repair member file [l:20{10}]"wp2057.bin" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-01-19 08:21:27, Info                  CSI    000001eb [SR] Cannot repair member file [l:20{10}]"tn2057.bin" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

I can't see the third affected component - perhaps it'll show up once we fix the others.

I've uploaded a file - mmsab.zip - to my SkyDrive at Noel's SkyDrive

(note - this may take a while to finish uploading - it's a large file, and I have a slow connection today)

Please download and save it.
Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.
Pick the option to use a Command Prompt
At the prompt type
DIR C:\mmsab
hit the enter key - if you get a 'Not Found' error try
DIR D:\mmsab
or
DIR E:\mmsab

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

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

(e.g.XCOPY P:\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 Enter key to exit Command Prompt - reboot to Normal Mode Windows.
Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply. we need the FULL data this time.

I'm here, but I'm just watching and, learning.

Here's the SFC summary

Code:

 Line 22524: 2014-01-19 12:38:35, Info                  CSI    000001c2 [SR] Repairing 1 components
 Line 22525: 2014-01-19 12:38:35, Info                  CSI    000001c3 [SR] Beginning Verify and Repair transaction
 Line 22528: 2014-01-19 12:38:35, Info                  CSI    000001c5 [SR] Repairing corrupted file [ml:520{260},l:42{21}]"\??\C:\Windows\system"\[l:24{12}]"keyboard.drv" from store
 Line 22537: 2014-01-19 12:38:35, Info                  CSI    000001c7 [SR] Repair complete

The CBS log appears to be otherwise error-free.

Before I hand you back to the BSOD specialists, perhaps we'd better run CheckSUR as well...

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 to your reply

The 0xc80003f3 error is an 'put of memory' error - which often means something completely different :)
Perhaps the BSOD guys should take back over again? -
:waves:

You were downloading a 174.8MB chksur file and you decided to run a query for windows updates? It is no wonder you received an out of memory error. What type of ISP do you have, is it fast or somewhat fast?

I would've rebooted my machine and used Internet Explorer (IE) to download chksur, not Chrome. Maybe its me, but anytime a download has anything to do with the Windows OS, I use IE.

If you're still having problems reboot and use IE to navigate to and download: Download System Update Readiness Tool for Windows 7 (KB947821) [November 2013] from Official Microsoft Download Center

Noel, hopefully we can get those chksur logs for you.

The ,dmp file wouldn't open for me, please re-run and post the SF Diagnostic tool results. See Edit.

Were you able to run the chksur file and get logs for Noel?


EDIT:

I was looking around to see if I could find a reason why your .dmp file wouldn't open and using a different cmd - !analyze –v - I was able to open it.

Listen to your friend:

Code:

1: kd> !analyze –v 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {f6c72c74, 0, 919b4835, 2}


Could not read faulting driver name
Probably caused by : hardware ( dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+36d )

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

Cause

• Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
• Another common cause is the installation of a faulty system service.
• Antivirus software can also trigger this error, as can a corrupted NTFS volume.

Source: Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA (Windows Debuggers)

Looks like you're in for running a few stress tests:

Memory:
RAM - Test with Memtest86+

Those two Hard Drives although the first one you list in your specs is a SSD, but you say you don't have one.

The Seagate:
SeaTools for Windows | Seagate

For the Corsair if it is a SSD:
Crystal Dew World

Chksur is still running into the same error upon running the installer. Also, sorry. The 128 gb drive is a SSD, just not my main drive. Sorry for the confusion. I'll run the tests and report back.

EDIT:
Here's the results from Crystal and SeaTools.
Attachment 302510
I'm going to run the Memtest now.