Driver BSODs on Windows 8 and 7

[moromis]

I started having BSODs a while ago while I was on Windows 8 and 8.1, but they weren't too bad for some time so I didn't really feel the need to take care of them. Unfortunately, the frequency of the occurrences began to increase, and so I did a fresh OS install and moved back to Windows 7, hoping that all it was were just some badly optimized drivers. Unfortunately, I just got my first BSOD, so I decided to finally get some help.

Thanks in advance for any help you can provide.

Note: the BSOD title is DRIVER_IRQL_NOT_LESS_OR_EQUAL, if that's any help. I'm going to turn off automatic restart so I can catch the stop #s next time around.

Here's the BSOD package:
View attachment 300965

 

[moromis]

Bump.

Haven't had a BSOD since, but I'd love to make sure it doesn't happen anymore. Thanks.

 

[moromis]

Bump.

 

[moromis]

More BSODs over the past few days, mostly KERNEL_MODE_EXCEPTION_NOT_HANDLED, with a ATTEMPTED_WRITE_TO_READONLY_MEMORY just now. It seems as though there's a different driver involved in each new BSOD. Also, all of the Kernel Mode errors had a stop of 0x1000008e and 0xc0000005, but different Parameter 2 on each.

The actions I've performed since my last post:

I rolled back my graphics driver to the previous version after using Driver Verifier and getting BSODs with nvlddmkm.sys as the culprit.

I reset the BIOS to fail-safe defaults.

Here's a new zip of Minidump:
View attachment 301832

 

[Anak]

There were a few .dmps I couldn't open, but from what I saw you have a problem with an Altheros driver, Steam, and something called migetnextnode that refers to a Doxygen Program used for C++ programming.

There is some dxm and chrome problems, but I believe those are artifacts from the bigger problems mentioned above.

How did you do your re-install? Did you follow something like this? http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html

Since it is a custom build I would go back to the basics and remove anything that specifically does not have anything to do with the OS.

Make sure the OS is running strong, double check that altheros driver. Then add your desired programs one at a time and run then for a while to see if one of them makes your machine cough up a BSOD.

If it balks at the first new program then I'd say there's something wrong with the OS or Hardware that is not up to snuff, and you will have to go back and check those areas out.

 

[moromis]

Ok. I went ahead and deleted all installed programs that were not made by Microsoft. From there, I installed my network adapter driver from its installation cd, Nvidia graphics driver 314.22, and Chrome. I'm going to leave it at that for a couple days and see if I get any BSODs.

 

[moromis]

I went yesterday without a BSOD, and installed Ableton Live last night. Woke up this morning to find a blue screen. I'd like to note that recently the BSODs haven't been happening while I'm on the computer, but while I'm away rather.

Here's the minidump of the most recent BSOD:
View attachment 302033

 

[Anak]

Your new .dmp points to:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR=Blue]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/COLOR]
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c000001d, The exception code that was not handled
Arg2: 8ae46801, The address that the exception occurred at
Arg3: 8cd134ac, Exception Record Address
Arg4: 8cd13090, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
cng!SHA512Transform+1361
8ae46801 0facfe1c        shrd    esi,edi,1Ch

EXCEPTION_RECORD:  8cd134ac -- (.exr 0xffffffff8cd134ac)
ExceptionAddress: 8ae46801 (cng!SHA512Transform+0x00001361)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  8cd13090 -- (.cxr 0xffffffff8cd13090)
eax=00000010 ebx=2e070ff6 ecx=6d0e0981 edx=e070ff67 esi=2e070ff6 edi=7d237072
eip=8ae46801 esp=8cd13574 ebp=8cd138fc iopl=0         ov up ei ng nz na po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010a83
cng!SHA512Transform+0x1361:
8ae46801 0facfe1c        shrd    esi,edi,1Ch
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

LAST_CONTROL_TRANSFER:  from 8ae47c3a to 8ae46801

FAILED_INSTRUCTION_ADDRESS: 
cng!SHA512Transform+1361
8ae46801 0facfe1c        shrd    esi,edi,1Ch

STACK_TEXT:  
8cd138fc 8ae47c3a 8cd1395c 0000000e 0000000b cng!SHA512Transform+0x1361
8cd1391c 8ae36561 00000000 affb1000 00000006 cng!SHA512Update+0xea
8cd13c78 8ae1315e 00000000 00000000 8cd13c98 cng!GatherRandomKey+0x508
8cd13cdc 8ae131bf 00000000 8cd13d00 8324b62f cng!ReadExternalEntropyIntoPool+0x1a6
8cd13ce8 8324b62f 85f0fdc8 00000000 85b12730 cng!scavengingWorkItemRoutine+0x15
8cd13d00 830b414b 85b12730 00000000 8560c020 nt!IopProcessWorkItem+0x2d
8cd13d50 8324013d 00000001 a59cb491 00000000 nt!ExpWorkerThread+0x10d
8cd13d90 830e7559 830b403e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


FOLLOWUP_IP: 
cng!SHA512Transform+1361
8ae46801 0facfe1c        shrd    esi,edi,1Ch

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  cng!SHA512Transform+1361

FOLLOWUP_NAME:  MachineOwner

[COLOR=Blue]MODULE_NAME: cng

IMAGE_NAME:  cng.sys
[/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP:  501946b4

STACK_COMMAND:  .cxr 0xffffffff8cd13090 ; kb

FAILURE_BUCKET_ID:  0x7E_BAD_IP_cng!SHA512Transform+1361

BUCKET_ID:  0x7E_BAD_IP_cng!SHA512Transform+1361

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

1: kd> .exr 0xffffffff8cd134ac
ExceptionAddress: 8ae46801 (cng!SHA512Transform+0x00001361)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

The explanation for 0x7e is Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (Windows Debuggers) and offers a list of resolutions.

There is an expanded explanation here: STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED - carrona.org

The cng.sys file is an OS file - Microsoft Windows Kernel Cryptography, Next Generation file.
It may be possible to repair this with a http://www.sevenforums.com/tutorials/433-disk-check.html then http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html after that.
If these two scans finish okay, and you worked through the resolutions of the bugcheck, but still continue to have BSOD's after you install a third-party program, you should try a re-install of the OS.

I would say you are having problems with your OS.

• Where did you obtain your copy of Windows?
• Did you have any problems with the install?
• Did you trim the SSD?
• Can you post a screenshot of your http://www.sevenforums.com/tutorials/274797-disk-management-post-screen-capture-image.html

 

[moromis]

1. I bought my copy of Windows from the Microsoft Company Store.
2. No problems with the install.
3. Running a regular hard drive, so no trimming.
4. View attachment 302096

I'm going to run chkdsk and then SFC /SCANNOW now, but before I do, here's another BSOD that I came home to.
View attachment 302097

Thanks for your help.

 

[moromis]

Chkdsk finished with nothing out of order, no problems. Then I ran sfc /scannow, and it gave me this:
View attachment 302118

I couldn't open the CBS file it directed me to, so here's the whole CBS folder: View attachment 302117
I'll be waiting on your response to this, as I don't know what to do now.

Thanks.

 

[moromis]

I went through the list of resolutions, and these two look plausible:
-Operating system intermittently crashes with a "0x0000007E" Stop error message on a computer that is running Windows 7 or Windows Server 2008 R2
-Stop error message in Windows 7 or Windows Server 2008 R2: "Stop error code 0x0000007E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)" or "Stop error code 0x00000050 (PAGE_FAULT_IN_NONPAGED_AREA)"

How can I know if I should install the hotfixes associated with those articles? Also, is there any probable cause that I should update the BIOS? The current version I have installed is from 10/13/2009.

 

[Anak]

3. Running a regular hard drive, so no trimming.

So the CORSAIR CMFSSD is is wrong in your system specs?


Your most recent .dmp points to memory corruption:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000014, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 830ba2cb, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 8318884c
Unable to read MiSystemVaType memory at 83167e20
 00000014 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiFindNodeOrParent+5
830ba2cb f7401400ffffff  test    dword ptr [eax+14h],0FFFFFF00h

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  9c82569c -- (.trap 0xffffffff9c82569c)
ErrCode = 00000000
eax=00000000 ebx=86dbff38 ecx=00000000 edx=00000000 esi=86dbff38 edi=807c3120
eip=830ba2cb esp=9c825710 ebp=9c825710 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!MiFindNodeOrParent+0x5:
830ba2cb f7401400ffffff  test    dword ptr [eax+14h],0FFFFFF00h ds:0023:00000014=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 830ba2cb to 8305fb7f

STACK_TEXT:  
9c82569c 830ba2cb badb0d00 00000000 9c8256bc nt!KiTrap0E+0x1b3
9c825710 830bae5d 9c825724 9c82573c 830d7254 nt!MiFindNodeOrParent+0x5
9c82571c 830d7254 00000000 86dbff10 86dbff80 nt!MiLocateAddressInTree+0x11
9c82573c 830a806e 86dbff10 00000000 00000000 nt!MiGetSharedProtos+0x5d
9c82575c 830c127b 96422788 846601f8 84660200 nt!MiComputeStartingOffset+0x61
9c8257a0 83050bdc 85b3db60 85b3d000 9c825844 nt!MiIdentifyPfn+0x29e
9c8257c8 8329f295 00b3d060 b5c8104c 9c825858 nt!MmQueryPfnList+0xa6
9c825810 83254b6c 91007001 b5c810cc 00000000 nt!PfpPfnPrioRequest+0xde
9c825890 83240837 00000000 91007001 9c825cd0 nt!PfQuerySuperfetchInformation+0xea
9c825d00 8324ffbb 0000004f 00000000 00000000 nt!ExpQuerySystemInformation+0x2477
9c825d1c 8305c8c6 0000004f 0133ed90 00000014 nt!NtQuerySystemInformation+0x76
9c825d1c 778170f4 0000004f 0133ed90 00000014 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
0133cc50 00000000 00000000 00000000 00000000 0x778170f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiFindNodeOrParent+5
830ba2cb f7401400ffffff  test    dword ptr [eax+14h],0FFFFFF00h

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiFindNodeOrParent+5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  521e9cb6

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiFindNodeOrParent+5

BUCKET_ID:  0xA_nt!MiFindNodeOrParent+5

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

Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL (Windows Debuggers)


Okay on the CHKDSK. Thank you for the disk management and SFC snips they're helpful.

Usually to open system files you need to copy them to your desktop, then you should be able to open them. I applaud your initiative in uploading the CBS. logs.

'bout that SFC scan, I believe we found your problem. Hold off on running those hotfixes. I know enough about CBS logs to be dangerous, but I'm going to see if I can get NoelDP to stop by and take a look at them, he may be able to write a batch file that would fix your SFC scan problem and having those CBS logs ready is very helpful.

Until Noel does stop by Have you tried to run the SFC scan at least three times or more with restarts in between?

See Note after Option Two step #4:

   Note

• If SFC could not fix something, then run the command again to see if it may be able to the next time. Sometimes it may take running the sfc /scannow command 3 or more times to completely fix everything that it's able to.
• If not, then download and run the 32-bit (x86) or 64-bit (x64) System Update Readiness Tool for your same installed 32-bit or 64-bit Windows 7, restart the PC afterwards, and try the sfc /scannow command again.
• If still not, then you can attempt to run a System Restore using a restore point dated before the bad file occured to fix it. You may need to repeat doing a System Restore until you find a older restore point that may work.
• If still not, then you can use the steps in the TIP box in the OPTION THREE section below to manually replace the files that SFC could not fix.

• Only do the first bullet.
• Noel may instruct you to run the System Update Readiness Tool (SURT) and then upload the newer CBS logs.
• Ignore the third bullet.
• The fourth bullet is where he might be able to write up the batch file to make replacement easier.
• Let us know if running SFC 3x's helps.

The old BIOS? Well, 4years is starting to get a little long in the tooth, but hold off on that also. Our goal is to see if we can get your present setup running once we get the system files straightened out and when your OS is steady you could consider updating the BIOS.

 

[A Guy]

You can also upload just the sfcdetails.txt as per OPTION THREE of the tutorial

How to See and Read Only the "SFC" Scan Results from the CBS.LOG

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

A Guy

 

[NoelDP]

The SFC results are unusual...
Here's the brief summary

 Line 3370: 2014-01-17 21:22:34, Info                  CSI    0000029c [SR] Repairing 4 components
 Line 3371: 2014-01-17 21:22:34, Info                  CSI    0000029d [SR] Beginning Verify and Repair transaction
 Line 3374: 2014-01-17 21:22:34, Info                  CSI    0000029f [SR] Cannot repair member file [l:24{12}]"keyboard.drv" of Microsoft-Windows-NTVDM-System32, Version = 6.1.7601.17514, 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
 Line 3377: 2014-01-17 21:22:34, Info                  CSI    000002a1 [SR] Cannot repair member file [l:20{10}]"mmtask.tsk" of Microsoft-Windows-NTVDM-System32, Version = 6.1.7601.17514, 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
 Line 3380: 2014-01-17 21:22:34, Info                  CSI    000002a3 [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
 Line 3383: 2014-01-17 21:22:34, Info                  CSI    000002a5 [SR] Cannot repair member file [l:20{10}]"mmtask.tsk" 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
 Line 3386: 2014-01-17 21:22:35, Info                  CSI    000002a7 [SR] Cannot repair member file [l:18{9}]"l2057.ngr" 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
 Line 3389: 2014-01-17 21:22:35, Info                  CSI    000002a9 [SR] Cannot repair member file [l:18{9}]"l2057.smp" 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
 Line 3392: 2014-01-17 21:22:35, Info                  CSI    000002ab [SR] Cannot repair member file [l:18{9}]"l2057.phn" 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
 Line 3395: 2014-01-17 21:22:35, Info                  CSI    000002ad [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
 Line 3398: 2014-01-17 21:22:35, Info                  CSI    000002af [SR] Cannot repair member file [l:18{9}]"l2057.wwd" 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
 Line 3401: 2014-01-17 21:22:35, Info                  CSI    000002b1 [SR] Cannot repair member file [l:22{11}]"AI032057.am" 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
 Line 3404: 2014-01-17 21:22:35, Info                  CSI    000002b3 [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
 Line 3407: 2014-01-17 21:22:35, Info                  CSI    000002b5 [SR] Cannot repair member file [l:18{9}]"s2057.ngr" 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
 Line 3410: 2014-01-17 21:22:35, Info                  CSI    000002b7 [SR] Cannot repair member file [l:18{9}]"s2057.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
 Line 3413: 2014-01-17 21:22:35, Info                  CSI    000002b9 [SR] Cannot repair member file [l:18{9}]"p2057.ngr" 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
 Line 3416: 2014-01-17 21:22:35, Info                  CSI    000002bb [SR] Cannot repair member file [l:18{9}]"p2057.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
 Line 3419: 2014-01-17 21:22:35, Info                  CSI    000002bd [SR] Cannot repair member file [l:22{11}]"AF032057.am" 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
 Line 3422: 2014-01-17 21:22:35, Info                  CSI    000002bf [SR] Cannot repair member file [l:22{11}]"AM032057.am" 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
 Line 3425: 2014-01-17 21:22:35, Info                  CSI    000002c1 [SR] Cannot repair member file [l:22{11}]"c2057dsk.fe" 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
 Line 3428: 2014-01-17 21:22:35, Info                  CSI    000002c3 [SR] Cannot repair member file [l:16{8}]"l2057.cw" 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
 Line 3431: 2014-01-17 21:22:36, Info                  CSI    000002c5 [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
 Line 3434: 2014-01-17 21:22:36, Info                  CSI    000002c7 [SR] Cannot repair member file [l:22{11}]"ai031033.am" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3437: 2014-01-17 21:22:36, Info                  CSI    000002c9 [SR] Cannot repair member file [l:22{11}]"lsr1033.lxa" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3440: 2014-01-17 21:22:36, Info                  CSI    000002cb [SR] Cannot repair member file [l:18{9}]"l1033.ngr" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3443: 2014-01-17 21:22:36, Info                  CSI    000002cd [SR] Cannot repair member file [l:18{9}]"l1033.dlm" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3446: 2014-01-17 21:22:36, Info                  CSI    000002cf [SR] Cannot repair member file [l:22{11}]"c1033dsk.fe" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3449: 2014-01-17 21:22:36, Info                  CSI    000002d1 [SR] Cannot repair member file [l:22{11}]"af031033.am" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3452: 2014-01-17 21:22:36, Info                  CSI    000002d3 [SR] Cannot repair member file [l:22{11}]"am031033.am" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3455: 2014-01-17 21:22:37, Info                  CSI    000002d5 [SR] Cannot repair member file [l:16{8}]"l1033.cw" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

I'll post a fix protocol a bit later (maybe tomorrow, now )

 

[Anak]

You can also upload just the sfcdetails.txt as per OPTION THREE of the tutorial

How to See and Read Only the "SFC" Scan Results from the CBS.LOG

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

A Guy

The SFC results are unusual...
Here's the brief summary

 Line 3370: 2014-01-17 21:22:34, Info                  CSI    0000029c [SR] Repairing 4 components.........
.......Line 3455: 2014-01-17 21:22:37, Info                  CSI    000002d5 [SR] Cannot repair member file [l:16{8}]"l1033.cw" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

I'll post a fix protocol a bit later (maybe tomorrow, now )

Thank you A Guy, I forgot to mention that.

A big thank you Noel, your efforts are appreciated.

moromis, Noel should give you the procedure to run the fix, please read the instructions carefully before you try, then let us know the results.

   Warning

I have noticed other members viewing this thread.


The fix protocol that Noel will post later only applies to moromis's situation / problem.

Any attempt to try it on your own system would result in irreparable harm to the extent that you would have to re-install your operating system (OS).

 

[moromis]

Oh, I did do step three to see it for myself, although to me it's all gobbledygook. Here's the .txt. file:
View attachment 302250

I'll run 3 more sfc /scannow now, with restarts inbetween each, as per request.

 

[NoelDP]

I've uploaded a file - mmsaa.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:\mmsaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\mmsaa
or
DIR E:\mmsaa

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

XCOPY <drive>:\mmsaa <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.

 

[moromis]

While I wait for it to finish uploading, here's the results of the original sfc scan, as well as the three subsequent scans.
View attachment 302275

Also, here's the last three BSODs, one or two of which I got today.
View attachment 302276

None of them came back with positive results.
I'll follow your directions once the file shows up in your SkyDrive.

Thanks for all your help so far.

 

[Anak]

Your SFC logs are an expanded version of what Noel posted earlier in his code box.

Of the two .dmps from yesterday the 18th; The first one wouldn't open for me and the second referred to NETIO.
If you have any type of card that facilitates or program that measures network speeds you may want to consider removing it after you run Noels fix protocol.

The one for today the 19th refers to athur.sys and USB ports.

I wouldn't do anything right now until you finish with Noel's fix protocol and instructions to post a new CBS log. You have to get that straightened out first.

 

[moromis]

Interestingly enough, I got a BSOD after I booted into the Repair Environment and opened up the command prompt. A minidump wasn't made, so I don't have anything for you, unfortunately. I rebooted and performed all the steps, and then as requested, ran a scannow, and it still was not able to repair all problems.

I also want to mention I've previously gotten BSODs recently when I was on the Windows CD performing repairs. That just seemed odd to me, and this reminded me of that.

Here's the log file:
View attachment 302316