Windows 7: Non-repeatable BSOD with two different HDDs, mulitiple codes

alecbh · 20 Jan 2012

Hi everyone, having some really frustrating problems I've been trying to fix myself, but nothing's helped yet. Hopefully you guys can help by analyzing my BSOD dumps.

My computer just likes to crash. I haven't run into any way to repeat any of these, and there's no common factors. This has been happening for months, and I've been able to stand it until now. I'm just sick of never having a working computer. Hundreds of blue screens, at least 6 different error codes over the last 6 months. I've attached the latest few.

The last problem I had with this computer was a rash of BSODs every few minutes, rendering my computer completely inoperable. It was bad caps on an old motherboard, which forced me to upgrade my mobo, CPU and RAM; that was done Sep 23 last year. I've still been getting a few lately, so I tried switching to an older hard drive I have on hand, which helped some, but didn't solve the problem completely. Here's the specs as of now.

Win 7 64 bit
Brand new case with two big fans to hopefully rule out overheating
Gigabyte GA-880GA-UD3H
AMD 955
Sector 5 DDR3 8GB
Rebranded MSI Nvidia 9500 GT
Secondhand PSU, 480W or 550W, don't remember which (suspected cause)
Drives:
Western Digital 40gig IDE (current boot drive

)
Secondhand Seagate Barracuda Green 2TB SATA (problem child)
Generic IDE DVD R/RW

Yes, I know, it's weird mixup of parts that could run a lot better with newer hardware. That's what happens when you take what you can get and spend money only when you have to. I don't have money to throw at this stupid thing, money is in short supply. So don't just say, "buy a brand new this, that and the other and your troubles will be over," unless that is the ONLY option to fix this. I simply can't afford it.

So without further ado, I present the error files. Please help me on this one. I'm about to just use this computer for target practice.

EDIT TO ADD:

A short list of codes and associated files I've gotten in the last couple BSODs, just for quick review and in no specific order:

50, ntfs.sys
3B, ntfs.sys
D1, ndis.sys
3B, tcpip.sys

Because of the ntfs.sys being a common factor, I suspect the hard drives, but I'm also wondering if it's not something else, because this happens with two different drives, one IDE, the other SATA.

Also, the errors below are from both drives, both with Win 7 installed. The perfmon was run on the IDE drive, as the SATA drive is too unstable to run reliably for 30 minutes.

writhziden · 20 Jan 2012

Code:



Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\alecbh\alecbh\Windows_NT6_BSOD_jcgriff2\011912-73616-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a57000 PsLoadedModuleList = 0xfffff800`02c9ce90
Debug session time: Thu Jan 19 11:47:30.588 2012 (UTC - 7:00)
System Uptime: 0 days 0:01:26.775
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88001687ffb, fffff8800672c8c0, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88001687ffb, Address of the instruction which caused the bugcheck
Arg3: fffff8800672c8c0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
tcpip!TcpContinueCreateAndConnect+2ab
fffff880`01687ffb 4ccb            retf

CONTEXT:  fffff8800672c8c0 -- (.cxr 0xfffff8800672c8c0)
rax=fffffa8007a09400 rbx=fffffa8009d9b880 rcx=0000000000000000
rdx=fffff8800177e9a0 rsi=0000000000005000 rdi=fffffa800adf69b0
rip=fffff88001687ffb rsp=fffff8800672d2a0 rbp=000000000000bac0
 r8=0000000000000180  r9=0000000000000002 r10=0000000000000000
r11=0000000000000000 r12=0000000000000004 r13=fffffa800adf7680
r14=0000000000000000 r15=8000080400000084
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
tcpip!TcpContinueCreateAndConnect+0x2ab:
fffff880`01687ffb 4ccb            retf
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  AvastSvc.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88001687ffb

STACK_TEXT:  
fffff880`0672d2a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!TcpContinueCreateAndConnect+0x2ab


CHKIMG_EXTENSION: !chkimg -lo 50 -d !tcpip
    fffff88001687ffc - tcpip!TcpContinueCreateAndConnect+2ac
	[ 8b:cb ]
1 error : !tcpip (fffff88001687ffc)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

STACK_COMMAND:  .cxr 0xfffff8800672c8c0 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\alecbh\alecbh\Windows_NT6_BSOD_jcgriff2\011912-36254-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02e4f000 PsLoadedModuleList = 0xfffff800`0308ce70
Debug session time: Thu Jan 19 06:33:59.268 2012 (UTC - 7:00)
System Uptime: 0 days 0:30:00.000
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d89d55e4eb, b3b7465eefd3b435, fffff80002e12f6c, 1}

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

Followup: memory_corruption
---------

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89d55e4eb, Reserved
Arg2: b3b7465eefd3b435, Reserved
Arg3: fffff80002e12f6c, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
	0 : A generic data region
	1 : Modification of a function or .pdata
	2 : A processor IDT
	3 : A processor GDT
	4 : Type 1 process list corruption
	5 : Type 2 process list corruption
	6 : Debug routine modification
	7 : Critical MSR modification

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


BUGCHECK_STR:  0x109

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002ebf5c0

STACK_TEXT:  
fffff880`031a15d8 00000000`00000000 : 00000000`00000109 a3a039d8`9d55e4eb b3b7465e`efd3b435 fffff800`02e12f6c : nt!KeBugCheckEx


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !hal
    fffff80002e12ffc - hal!HalpPCIConfigHoldingConfigLock+90
	[ 81:c1 ]
1 error : !hal (fffff80002e12ffc)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\alecbh\alecbh\Windows_NT6_BSOD_jcgriff2\011912-69592-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a5b000 PsLoadedModuleList = 0xfffff800`02ca0e90
Debug session time: Thu Jan 19 05:59:23.282 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:40.859
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8b7f1a0, 2, 1, fffff88001461dff}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000008b7f1a0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88001461dff, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0c0e8
 0000000008b7f1a0 

CURRENT_IRQL:  2

FAULTING_IP: 
ndis!ndisCreateIrpHandler+df
fffff880`01461dff 0000            add     byte ptr [rax],al

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xD1

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff880063bf520 -- (.trap 0xfffff880063bf520)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000008b7f1a0 rbx=0000000000000000 rcx=fffffa8008b7ff68
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001461dff rsp=fffff880063bf6b0 rbp=0000000000000000
 r8=0000058000000000  r9=0000000000000000 r10=fffff8a00137f060
r11=fffff880063bf680 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
ndis!ndisCreateIrpHandler+0xdf:
fffff880`01461dff 0000            add     byte ptr [rax],al ds:a8b8:00000000`08b7f1a0=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002adabe9 to fffff80002adb640

STACK_TEXT:  
fffff880`063bf3d8 fffff800`02adabe9 : 00000000`0000000a 00000000`08b7f1a0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`063bf3e0 fffff800`02ad9860 : fffffa80`06af7700 fffff880`063bf5f0 00000000`00000000 00000000`00000025 : nt!KiBugCheckDispatch+0x69
fffff880`063bf520 fffff880`01461dff : fffffa80`07979c28 00000000`00000000 fffffa80`08b7f1a0 00000000`00000025 : nt!KiPageFault+0x260
fffff880`063bf6b0 fffff800`02dd9495 : 00000000`00000025 fffffa80`08f33700 fffffa80`0a95e900 fffffa80`0a2d7b00 : ndis!ndisCreateIrpHandler+0xdf
fffff880`063bf730 fffff800`02dd5d38 : fffffa80`08b7f050 00000000`00000000 fffffa80`08f33610 00000000`00000001 : nt!IopParseDevice+0x5a5
fffff880`063bf8c0 fffff800`02dd6f56 : 00000000`00000000 fffffa80`08f33610 00000000`00000000 fffffa80`06af77b0 : nt!ObpLookupObjectName+0x588
fffff880`063bf9b0 fffff800`02dd885c : fffffa80`0a3392f0 00000000`00000000 fffffa80`07973d01 00000000`00000000 : nt!ObOpenObjectByName+0x306
fffff880`063bfa80 fffff800`02dc4134 : 00000000`01c1f6c0 fffff8a0`0012019f 00000000`01c1f6e0 00000000`01c1f710 : nt!IopCreateFile+0x2bc
fffff880`063bfb20 fffff800`02ada8d3 : fffffa80`0a2d09a0 00000000`00000001 fffffa80`0a880760 fffff800`02dd2a34 : nt!NtOpenFile+0x58
fffff880`063bfbb0 00000000`7781164a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01c1f678 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7781164a


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !ndis
    fffff88001461dfc - ndis!ndisCreateIrpHandler+dc
	[ 87:c7 ]
1 error : !ndis (fffff88001461dfc)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\alecbh\alecbh\Windows_NT6_BSOD_jcgriff2\011812-40357-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a5d000 PsLoadedModuleList = 0xfffff800`02ca2e90
Debug session time: Wed Jan 18 19:05:54.122 2012 (UTC - 7:00)
System Uptime: 0 days 0:27:22.698
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff880093e03e8, 0, fffff880012e5df6, 0}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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: fffff880093e03e8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880012e5df6, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0e0e8
 fffff880093e03e8 

FAULTING_IP: 
Ntfs!NtOfsSetLength+1a6
fffff880`012e5df6 488b8c2408014000 mov     rcx,qword ptr [rsp+400108h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x50

PROCESS_NAME:  DXSETUP.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88008fe0150 -- (.trap 0xfffff88008fe0150)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80079c9a01 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff8a0001da158 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880012e5df6 rsp=fffff88008fe02e0 rbp=fffff88008fe0980
 r8=0000000000000000  r9=0000000000000000 r10=0001001800180040
r11=fffff88008fe02b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
Ntfs!NtOfsSetLength+0x1a6:
fffff880`012e5df6 488b8c2408014000 mov     rcx,qword ptr [rsp+400108h] ss:0018:fffff880`093e03e8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a892ac to fffff80002add640

STACK_TEXT:  
fffff880`08fdffe8 fffff800`02a892ac : 00000000`00000050 fffff880`093e03e8 00000000`00000000 fffff880`08fe0150 : nt!KeBugCheckEx
fffff880`08fdfff0 fffff800`02adb76e : 00000000`00000000 fffff880`093e03e8 00000000`00000000 fffff8a0`001da140 : nt! ?? ::FNODOBFM::`string'+0x4621f
fffff880`08fe0150 fffff880`012e5df6 : fffff880`08fe0770 00000000`00002400 fffff8a0`001da140 00000000`0005e8a0 : nt!KiPageFault+0x16e
fffff880`08fe02e0 fffff880`012bcce4 : fffff880`08fe0770 fffffa80`07b2af20 00000000`0001e800 fffff880`08fe0770 : Ntfs!NtOfsSetLength+0x1a6
fffff880`08fe03e0 fffff880`012ed520 : fffff880`08fe0770 fffff8a0`02580a40 00000000`0001e7fc 00000000`0001e800 : Ntfs!GetSecurityIdFromSecurityDescriptorUnsafe+0x13c
fffff880`08fe0490 fffff880`012a11fa : fffff880`08fe0770 fffff880`08fe0770 fffff8a0`025ec5d0 00000000`00000000 : Ntfs!NtfsCacheSharedSecurityByDescriptor+0xa0
fffff880`08fe04e0 fffff880`012a0f6c : fffff880`08fe0770 fffff8a0`030cef80 fffff8a0`025ec5d0 fffff8a0`030cef00 : Ntfs!NtfsModifySecurity+0xde
fffff880`08fe0620 fffff880`012b83a9 : fffff880`08fe0770 fffffa80`08b32c10 fffff8a0`025ec5d0 fffffa80`08a30180 : Ntfs!NtfsCommonSetSecurityInfo+0x150
fffff880`08fe06d0 fffff880`012b8f01 : fffff880`08fe0770 fffffa80`08b32c10 fffffa80`08b32c10 00000000`000c0000 : Ntfs!NtfsFsdDispatchSwitch+0x169
fffff880`08fe0750 fffff880`010d3bcf : fffffa80`08b32c10 fffff880`010d4329 fffff880`63694d46 fffff880`08fe0915 : Ntfs!NtfsFsdDispatch+0x2d
fffff880`08fe0940 fffff880`010d26df : fffffa80`079c9c90 00000000`00000000 fffffa80`079c9c00 fffffa80`08b32c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`08fe09d0 fffff800`02dbcd43 : fffffa80`06fd7a40 00000000`00000000 00000000`00000000 fffffa80`08b32c10 : fltmgr!FltpDispatch+0xcf
fffff880`08fe0a30 fffff800`02d7974e : 00000000`00000000 00000000`02846ad0 fffff880`08fe0b58 fffff8a0`02005f70 : nt!IopGetSetSecurityObject+0x183
fffff880`08fe0af0 fffff800`02d79640 : fffffa80`00000000 00000000`00000007 00000000`00000001 00000000`00000001 : nt!ObSetSecurityObjectByPointer+0x5a
fffff880`08fe0b50 fffff800`02adc8d3 : 00000000`00000394 fffffa80`097bd060 00000000`7efdb000 00000000`0000ed75 : nt!NtSetSecurityObject+0x108
fffff880`08fe0c20 00000000`77ae29da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000bdd28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ae29da


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !Ntfs
    fffff880012e5dfc - Ntfs!NtOfsSetLength+1ac
	[ 00:40 ]
1 error : !Ntfs (fffff880012e5dfc)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\alecbh\alecbh\Windows_NT6_BSOD_jcgriff2\011812-39047-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a1d000 PsLoadedModuleList = 0xfffff800`02c62e90
Debug session time: Wed Jan 18 18:37:37.506 2012 (UTC - 7:00)
System Uptime: 0 days 0:28:48.693
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8800105edf9, fffff880083a7ac0, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8800105edf9, Address of the instruction which caused the bugcheck
Arg3: fffff880083a7ac0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
fltmgr!FltpCreateInstanceFromName+f9
fffff880`0105edf9 ff15f1f2feff    call    qword ptr [fltmgr!`string'+0x60 (fffff880`0104e0f0)]

CONTEXT:  fffff880083a7ac0 -- (.cxr 0xfffff880083a7ac0)
rax=0000000000000000 rbx=fffff8a002ecf850 rcx=fffff880083a84f0
rdx=fffff8800104a990 rsi=ffffffff80003cfc rdi=0000000000000000
rip=fffff8800105edf9 rsp=fffff880083a84a0 rbp=0000000000000005
 r8=fffffa80071f1710  r9=fffffa8006d3e268 r10=0000000000000000
r11=fffffa800a5bf8e0 r12=fffff880083a85c8 r13=0000000000000050
r14=fffffa8007824be0 r15=fffffa8007a3e7f0
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210246
fltmgr!FltpCreateInstanceFromName+0xf9:
fffff880`0105edf9 ff15f1f2feff    call    qword ptr [fltmgr!`string'+0x60 (fffff880`0104e0f0)] ds:002b:fffff880`0104e0f0=6568742065737561
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800105edf9

STACK_TEXT:  
fffff880`083a84a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : fltmgr!FltpCreateInstanceFromName+0xf9


CHKIMG_EXTENSION: !chkimg -lo 50 -d !fltmgr
    fffff8800105edfc - fltmgr!FltpCreateInstanceFromName+fc
	[ b2:f2 ]
1 error : !fltmgr (fffff8800105edfc)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

STACK_COMMAND:  .cxr 0xfffff880083a7ac0 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

Has Avast been present from the beginning? It caused your latest crash.
Can be caused by hardware failure... Drivers doing something they should not be doing... Viruses...
Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Antivirus Software...
Possible causes are Memory problems... Graphics card memory problems... CMOS... Corrupted hard disk system files... Corrupted System Files... Missing Windows Updates... Drivers...
Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Graphics Driver...

Thanks to Dave76 for help understanding possible causes.

We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

If you are overclocking anything, please stop.
Use the AVAST uninstall utility and replace with Microsoft Security Essentials - Free Antivirus for Windows to run with Windows firewall. Let us know if stability improves, otherwise continue to the next step.
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log Let us know if stability improves, otherwise continue to the next step.
Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors. Post back if it continues to show errors after the third run or if the first run comes back with no integrity violations. If it fixes errors, and all errors have been fixed, let us know if stability improves, otherwise continue to the next step.
Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory.
Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.

alecbh · 02 Feb 2012

First, thanks for the help.

I'm not overclocking anything, and never have.

1. Avast has been present from the beginning, it's one of the first things I install. Uninstalling Avast didn't help at all, still having serious issues.
2. I'm having a miserable time getting memtest86+ to boot off a USB drive, and I don't have any blank CDs. I'll use the Windows utility tonight.
3. I was running disk check when the computer BSODed on my again. That was weird, because normally if it doesn't BSOD within the first 30 minutes of it running, it will run indefinitely. This happened right after I started SFC. This was especially weird because I was running the checker on an external USB HDD.
4. SFC was interrupted the first time almost immediately by a blue screen while I was running the disk checker. I ran it again just now and it came up with errors, but couldn't fix all of them. I've attached the log file, for what it's worth.
5. I've yet to run the stress tests and verifier, but I have run the driver verifier in the recent past with no problems. I'll run it again, just because.

I can post another zip with the dumps and perfmon, if you want. I've had at least 11 BSODs since I posted this.

In chronological order,
3B, System service exception
109
109, shortly after log in
50, Page fault in nonpaged area, before log in
50, Page fault in nonpaged area, before log in
109, shortly after log in
24, before log in
50, Page fault in nonpaged area, shortly after log in
3B, System service exception while booting from the SATA drive(all others IDE), tcpip.sys, no crash dump made
50, Page fault in nonpaged area, before log in
50, Page fault in nonpaged area, before log in
A, IRQL not less than or equal
3B

Want those?

writhziden · 02 Feb 2012

The disk check and system file check should be run separately. I have updated my original post to reflect this and make the steps a little clearer. I also updated the hardware stress test prime95 with better troubleshooting information.

We would prefer that you run memtest86+ since it does a more thorough test of the memory than windows memory diagnostic. It is good to run both so that more tests are done on the memory. Also, memtest86+ may need to be run more than once to find errors. If you need help getting memtest86+ to run from USB, try the following method:

Download the memtest86+ iso file
Download Gentoo Linux Bootable USB Maker. (it will say Kaspersky, but it is just the Gentoo Linux Bootable USB Maker).
Unzip Gentoo.
Put the memtest86+ iso file in the folder with fixgt2.bat
Double click fixgt2.bat
Enter the drive letter of your USB drive (Careful that you get the drive letter correct since this will format the drive and you will lose all data)
Follow the instructions given by the batch file and you should be able to create a bootable USB with memtest86+ on it.

System file check details:

Code:

2012-02-02 00:42:09, Info                  CSI    00000009 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:42:09, Info                  CSI    0000000a [SR] Beginning Verify and Repair transaction
2012-02-02 00:42:13, Info                  CSI    0000000c [SR] Verify complete
2012-02-02 00:42:13, Info                  CSI    0000000d [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:42:13, Info                  CSI    0000000e [SR] Beginning Verify and Repair transaction
2012-02-02 00:42:17, Info                  CSI    00000010 [SR] Verify complete
2012-02-02 00:42:17, Info                  CSI    00000011 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:42:17, Info                  CSI    00000012 [SR] Beginning Verify and Repair transaction
2012-02-02 00:42:21, Info                  CSI    00000014 [SR] Verify complete
2012-02-02 00:42:21, Info                  CSI    00000015 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:42:21, Info                  CSI    00000016 [SR] Beginning Verify and Repair transaction
2012-02-02 00:42:27, Info                  CSI    00000018 [SR] Verify complete
2012-02-02 00:42:27, Info                  CSI    00000019 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:42:27, Info                  CSI    0000001a [SR] Beginning Verify and Repair transaction
2012-02-02 00:42:34, Info                  CSI    0000001c [SR] Verify complete
2012-02-02 00:42:34, Info                  CSI    0000001d [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:42:34, Info                  CSI    0000001e [SR] Beginning Verify and Repair transaction
2012-02-02 00:42:38, Info                  CSI    00000020 [SR] Verify complete
2012-02-02 00:42:38, Info                  CSI    00000021 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:42:38, Info                  CSI    00000022 [SR] Beginning Verify and Repair transaction
2012-02-02 00:42:41, Info                  CSI    00000024 [SR] Verify complete
2012-02-02 00:42:41, Info                  CSI    00000025 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:42:41, Info                  CSI    00000026 [SR] Beginning Verify and Repair transaction
2012-02-02 00:42:43, Info                  CSI    00000028 [SR] Verify complete
2012-02-02 00:42:44, Info                  CSI    00000029 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:42:44, Info                  CSI    0000002a [SR] Beginning Verify and Repair transaction
2012-02-02 00:42:48, Info                  CSI    0000002c [SR] Verify complete
2012-02-02 00:42:48, Info                  CSI    0000002d [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:42:48, Info                  CSI    0000002e [SR] Beginning Verify and Repair transaction
2012-02-02 00:42:51, Info                  CSI    00000030 [SR] Verify complete
2012-02-02 00:42:51, Info                  CSI    00000031 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:42:51, Info                  CSI    00000032 [SR] Beginning Verify and Repair transaction
2012-02-02 00:42:53, Info                  CSI    00000034 [SR] Verify complete
2012-02-02 00:42:53, Info                  CSI    00000035 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:42:53, Info                  CSI    00000036 [SR] Beginning Verify and Repair transaction
2012-02-02 00:42:55, Info                  CSI    00000038 [SR] Verify complete
2012-02-02 00:42:55, Info                  CSI    00000039 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:42:55, Info                  CSI    0000003a [SR] Beginning Verify and Repair transaction
2012-02-02 00:43:00, Info                  CSI    0000003d [SR] Verify complete
2012-02-02 00:43:00, Info                  CSI    0000003e [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:43:00, Info                  CSI    0000003f [SR] Beginning Verify and Repair transaction
2012-02-02 00:43:02, Info                  CSI    00000040 [SR] Cannot repair member file [l:6{3}]"BCD" of Microsoft-Windows-BootEnvironment-DVD-EFI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2012-02-02 00:43:05, Info                  CSI    00000043 [SR] Cannot repair member file [l:6{3}]"BCD" of Microsoft-Windows-BootEnvironment-DVD-EFI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2012-02-02 00:43:05, Info                  CSI    00000044 [SR] This component was referenced by [l:192{96}]"Microsoft-Windows-RecDisc-SDP-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsRecoveryDisc"
2012-02-02 00:43:05, Info                  CSI    00000045 [SR] This component was referenced by [l:170{85}]"Microsoft-Windows-Backup-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsBackup"
2012-02-02 00:43:05, Info                  CSI    00000046 [SR] Could not reproject corrupted file [ml:520{260},l:54{27}]"\??\C:\Windows\Boot\DVD\EFI"\[l:6{3}]"BCD"; source file in store is also corrupted
2012-02-02 00:43:05, Info                  CSI    00000049 [SR] Verify complete
2012-02-02 00:43:05, Info                  CSI    0000004a [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:43:05, Info                  CSI    0000004b [SR] Beginning Verify and Repair transaction
2012-02-02 00:43:09, Info                  CSI    0000004e [SR] Verify complete
2012-02-02 00:43:09, Info                  CSI    0000004f [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:43:09, Info                  CSI    00000050 [SR] Beginning Verify and Repair transaction
2012-02-02 00:43:13, Info                  CSI    00000052 [SR] Verify complete
2012-02-02 00:43:13, Info                  CSI    00000053 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:43:13, Info                  CSI    00000054 [SR] Beginning Verify and Repair transaction
2012-02-02 00:43:19, Info                  CSI    00000073 [SR] Verify complete
2012-02-02 00:43:19, Info                  CSI    00000074 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:43:19, Info                  CSI    00000075 [SR] Beginning Verify and Repair transaction
2012-02-02 00:43:23, Info                  CSI    0000007d [SR] Verify complete
2012-02-02 00:43:23, Info                  CSI    0000007e [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:43:23, Info                  CSI    0000007f [SR] Beginning Verify and Repair transaction
2012-02-02 00:43:28, Info                  CSI    00000081 [SR] Verify complete
2012-02-02 00:43:28, Info                  CSI    00000082 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:43:28, Info                  CSI    00000083 [SR] Beginning Verify and Repair transaction
2012-02-02 00:43:32, Info                  CSI    00000085 [SR] Verify complete
2012-02-02 00:43:32, Info                  CSI    00000086 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:43:32, Info                  CSI    00000087 [SR] Beginning Verify and Repair transaction
2012-02-02 00:43:36, Info                  CSI    00000089 [SR] Verify complete
2012-02-02 00:43:36, Info                  CSI    0000008a [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:43:36, Info                  CSI    0000008b [SR] Beginning Verify and Repair transaction
2012-02-02 00:43:41, Info                  CSI    0000008d [SR] Verify complete
2012-02-02 00:43:41, Info                  CSI    0000008e [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:43:41, Info                  CSI    0000008f [SR] Beginning Verify and Repair transaction
2012-02-02 00:43:48, Info                  CSI    00000093 [SR] Verify complete
2012-02-02 00:43:48, Info                  CSI    00000094 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:43:48, Info                  CSI    00000095 [SR] Beginning Verify and Repair transaction
2012-02-02 00:43:56, Info                  CSI    000000b6 [SR] Verify complete
2012-02-02 00:43:56, Info                  CSI    000000b7 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:43:56, Info                  CSI    000000b8 [SR] Beginning Verify and Repair transaction
2012-02-02 00:44:17, Info                  CSI    000000ba [SR] Verify complete
2012-02-02 00:44:17, Info                  CSI    000000bb [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:44:17, Info                  CSI    000000bc [SR] Beginning Verify and Repair transaction
2012-02-02 00:44:26, Info                  CSI    000000c0 [SR] Verify complete
2012-02-02 00:44:26, Info                  CSI    000000c1 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:44:26, Info                  CSI    000000c2 [SR] Beginning Verify and Repair transaction
2012-02-02 00:44:29, Info                  CSI    000000c4 [SR] Verify complete
2012-02-02 00:44:29, Info                  CSI    000000c5 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:44:29, Info                  CSI    000000c6 [SR] Beginning Verify and Repair transaction
2012-02-02 00:44:30, Info                  CSI    000000c8 [SR] Verify complete
2012-02-02 00:44:30, Info                  CSI    000000c9 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:44:30, Info                  CSI    000000ca [SR] Beginning Verify and Repair transaction
2012-02-02 00:44:33, Info                  CSI    000000cc [SR] Verify complete
2012-02-02 00:44:33, Info                  CSI    000000cd [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:44:33, Info                  CSI    000000ce [SR] Beginning Verify and Repair transaction
2012-02-02 00:44:41, Info                  CSI    000000e1 [SR] Verify complete
2012-02-02 00:44:41, Info                  CSI    000000e2 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:44:41, Info                  CSI    000000e3 [SR] Beginning Verify and Repair transaction
2012-02-02 00:44:42, Info                  CSI    000000e5 [SR] Verify complete
2012-02-02 00:44:43, Info                  CSI    000000e6 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:44:43, Info                  CSI    000000e7 [SR] Beginning Verify and Repair transaction
2012-02-02 00:44:47, Info                  CSI    000000e9 [SR] Verify complete
2012-02-02 00:44:47, Info                  CSI    000000ea [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:44:47, Info                  CSI    000000eb [SR] Beginning Verify and Repair transaction
2012-02-02 00:44:49, Info                  CSI    000000ed [SR] Verify complete
2012-02-02 00:44:49, Info                  CSI    000000ee [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:44:49, Info                  CSI    000000ef [SR] Beginning Verify and Repair transaction
2012-02-02 00:44:55, Info                  CSI    000000f2 [SR] Verify complete
2012-02-02 00:44:55, Info                  CSI    000000f3 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:44:55, Info                  CSI    000000f4 [SR] Beginning Verify and Repair transaction
2012-02-02 00:45:01, Info                  CSI    000000f6 [SR] Verify complete
2012-02-02 00:45:01, Info                  CSI    000000f7 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:45:01, Info                  CSI    000000f8 [SR] Beginning Verify and Repair transaction
2012-02-02 00:45:03, Info                  CSI    000000fa [SR] Verify complete
2012-02-02 00:45:03, Info                  CSI    000000fb [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:45:03, Info                  CSI    000000fc [SR] Beginning Verify and Repair transaction
2012-02-02 00:45:05, Info                  CSI    000000fe [SR] Verify complete
2012-02-02 00:45:05, Info                  CSI    000000ff [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:45:05, Info                  CSI    00000100 [SR] Beginning Verify and Repair transaction
2012-02-02 00:45:13, Info                  CSI    00000102 [SR] Verify complete
2012-02-02 00:45:13, Info                  CSI    00000103 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:45:13, Info                  CSI    00000104 [SR] Beginning Verify and Repair transaction
2012-02-02 00:45:18, Info                  CSI    00000106 [SR] Verify complete
2012-02-02 00:45:18, Info                  CSI    00000107 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:45:18, Info                  CSI    00000108 [SR] Beginning Verify and Repair transaction
2012-02-02 00:45:25, Info                  CSI    0000010a [SR] Verify complete
2012-02-02 00:45:26, Info                  CSI    0000010b [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:45:26, Info                  CSI    0000010c [SR] Beginning Verify and Repair transaction
2012-02-02 00:45:32, Info                  CSI    00000124 [SR] Verify complete
2012-02-02 00:45:32, Info                  CSI    00000125 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:45:32, Info                  CSI    00000126 [SR] Beginning Verify and Repair transaction
2012-02-02 00:45:37, Info                  CSI    00000128 [SR] Verify complete
2012-02-02 00:45:37, Info                  CSI    00000129 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:45:37, Info                  CSI    0000012a [SR] Beginning Verify and Repair transaction
2012-02-02 00:45:51, Info                  CSI    0000012c [SR] Verify complete
2012-02-02 00:45:51, Info                  CSI    0000012d [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:45:51, Info                  CSI    0000012e [SR] Beginning Verify and Repair transaction
2012-02-02 00:45:59, Info                  CSI    00000131 [SR] Verify complete
2012-02-02 00:45:59, Info                  CSI    00000132 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:45:59, Info                  CSI    00000133 [SR] Beginning Verify and Repair transaction
2012-02-02 00:46:05, Info                  CSI    00000135 [SR] Verify complete
2012-02-02 00:46:05, Info                  CSI    00000136 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:46:05, Info                  CSI    00000137 [SR] Beginning Verify and Repair transaction
2012-02-02 00:46:10, Info                  CSI    00000139 [SR] Verify complete
2012-02-02 00:46:10, Info                  CSI    0000013a [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:46:10, Info                  CSI    0000013b [SR] Beginning Verify and Repair transaction
2012-02-02 00:46:14, Info                  CSI    0000013d [SR] Verify complete
2012-02-02 00:46:14, Info                  CSI    0000013e [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:46:14, Info                  CSI    0000013f [SR] Beginning Verify and Repair transaction
2012-02-02 00:46:18, Info                  CSI    00000143 [SR] Verify complete
2012-02-02 00:46:18, Info                  CSI    00000144 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:46:18, Info                  CSI    00000145 [SR] Beginning Verify and Repair transaction
2012-02-02 00:46:29, Info                  CSI    00000147 [SR] Verify complete
2012-02-02 00:46:30, Info                  CSI    00000148 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:46:30, Info                  CSI    00000149 [SR] Beginning Verify and Repair transaction
2012-02-02 00:46:37, Info                  CSI    0000014c [SR] Verify complete
2012-02-02 00:46:37, Info                  CSI    0000014d [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:46:37, Info                  CSI    0000014e [SR] Beginning Verify and Repair transaction
2012-02-02 00:46:43, Info                  CSI    00000150 [SR] Verify complete
2012-02-02 00:46:43, Info                  CSI    00000151 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:46:43, Info                  CSI    00000152 [SR] Beginning Verify and Repair transaction
2012-02-02 00:46:48, Info                  CSI    00000155 [SR] Verify complete
2012-02-02 00:46:48, Info                  CSI    00000156 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:46:48, Info                  CSI    00000157 [SR] Beginning Verify and Repair transaction
2012-02-02 00:46:56, Info                  CSI    0000015a [SR] Verify complete
2012-02-02 00:46:56, Info                  CSI    0000015b [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:46:56, Info                  CSI    0000015c [SR] Beginning Verify and Repair transaction
2012-02-02 00:47:03, Info                  CSI    0000015e [SR] Verify complete
2012-02-02 00:47:03, Info                  CSI    0000015f [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:47:03, Info                  CSI    00000160 [SR] Beginning Verify and Repair transaction
2012-02-02 00:47:07, Info                  CSI    00000162 [SR] Verify complete
2012-02-02 00:47:07, Info                  CSI    00000163 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:47:07, Info                  CSI    00000164 [SR] Beginning Verify and Repair transaction
2012-02-02 00:47:12, Info                  CSI    00000166 [SR] Verify complete
2012-02-02 00:47:12, Info                  CSI    00000167 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:47:12, Info                  CSI    00000168 [SR] Beginning Verify and Repair transaction
2012-02-02 00:47:16, Info                  CSI    0000016b [SR] Verify complete
2012-02-02 00:47:16, Info                  CSI    0000016c [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:47:16, Info                  CSI    0000016d [SR] Beginning Verify and Repair transaction
2012-02-02 00:47:22, Info                  CSI    0000016f [SR] Verify complete
2012-02-02 00:47:22, Info                  CSI    00000170 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:47:22, Info                  CSI    00000171 [SR] Beginning Verify and Repair transaction
2012-02-02 00:47:28, Info                  CSI    00000174 [SR] Verify complete
2012-02-02 00:47:28, Info                  CSI    00000175 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:47:28, Info                  CSI    00000176 [SR] Beginning Verify and Repair transaction
2012-02-02 00:47:29, Info                  CSI    00000177 [SR] Cannot repair member file [l:90{45}]"Add_a_device_or_computer_to_a_network_usb.rtf" of Microsoft-Windows-WCN-Config-Registrar-Wizard.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2012-02-02 00:47:32, Info                  CSI    00000178 [SR] Cannot repair member file [l:90{45}]"Add_a_device_or_computer_to_a_network_usb.rtf" of Microsoft-Windows-WCN-Config-Registrar-Wizard.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2012-02-02 00:47:32, Info                  CSI    00000179 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.Microsoft-Windows-Client-Features-Language-Pack"
2012-02-02 00:47:32, Info                  CSI    0000017a [SR] Could not reproject corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\WCN\en-US"\[l:90{45}]"Add_a_device_or_computer_to_a_network_usb.rtf"; source file in store is also corrupted
2012-02-02 00:47:33, Info                  CSI    0000017c [SR] Verify complete
2012-02-02 00:47:33, Info                  CSI    0000017d [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:47:33, Info                  CSI    0000017e [SR] Beginning Verify and Repair transaction
2012-02-02 00:47:38, Info                  CSI    00000182 [SR] Verify complete
2012-02-02 00:47:38, Info                  CSI    00000183 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:47:38, Info                  CSI    00000184 [SR] Beginning Verify and Repair transaction
2012-02-02 00:47:45, Info                  CSI    00000186 [SR] Verify complete
2012-02-02 00:47:45, Info                  CSI    00000187 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:47:45, Info                  CSI    00000188 [SR] Beginning Verify and Repair transaction
2012-02-02 00:47:50, Info                  CSI    0000018b [SR] Verify complete
2012-02-02 00:47:50, Info                  CSI    0000018c [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:47:50, Info                  CSI    0000018d [SR] Beginning Verify and Repair transaction
2012-02-02 00:47:55, Info                  CSI    0000018f [SR] Verify complete
2012-02-02 00:47:55, Info                  CSI    00000190 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:47:55, Info                  CSI    00000191 [SR] Beginning Verify and Repair transaction
2012-02-02 00:47:56, Info                  CSI    00000193 [SR] Verify complete
2012-02-02 00:47:56, Info                  CSI    00000194 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:47:56, Info                  CSI    00000195 [SR] Beginning Verify and Repair transaction
2012-02-02 00:48:00, Info                  CSI    00000197 [SR] Verify complete
2012-02-02 00:48:00, Info                  CSI    00000198 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:48:00, Info                  CSI    00000199 [SR] Beginning Verify and Repair transaction
2012-02-02 00:48:05, Info                  CSI    0000019b [SR] Verify complete
2012-02-02 00:48:05, Info                  CSI    0000019c [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:48:05, Info                  CSI    0000019d [SR] Beginning Verify and Repair transaction
2012-02-02 00:48:10, Info                  CSI    0000019f [SR] Verify complete
2012-02-02 00:48:10, Info                  CSI    000001a0 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:48:10, Info                  CSI    000001a1 [SR] Beginning Verify and Repair transaction
2012-02-02 00:48:12, Info                  CSI    000001a3 [SR] Verify complete
2012-02-02 00:48:12, Info                  CSI    000001a4 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:48:12, Info                  CSI    000001a5 [SR] Beginning Verify and Repair transaction
2012-02-02 00:48:18, Info                  CSI    000001a7 [SR] Verify complete
2012-02-02 00:48:18, Info                  CSI    000001a8 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:48:18, Info                  CSI    000001a9 [SR] Beginning Verify and Repair transaction
2012-02-02 00:48:37, Info                  CSI    000001ab [SR] Verify complete
2012-02-02 00:48:37, Info                  CSI    000001ac [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:48:37, Info                  CSI    000001ad [SR] Beginning Verify and Repair transaction
2012-02-02 00:48:56, Info                  CSI    000001af [SR] Verify complete
2012-02-02 00:48:57, Info                  CSI    000001b0 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:48:57, Info                  CSI    000001b1 [SR] Beginning Verify and Repair transaction
2012-02-02 00:49:04, Info                  CSI    000001b3 [SR] Verify complete
2012-02-02 00:49:04, Info                  CSI    000001b4 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:49:04, Info                  CSI    000001b5 [SR] Beginning Verify and Repair transaction
2012-02-02 00:49:11, Info                  CSI    000001b7 [SR] Verify complete
2012-02-02 00:49:11, Info                  CSI    000001b8 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:49:11, Info                  CSI    000001b9 [SR] Beginning Verify and Repair transaction
2012-02-02 00:49:13, Info                  CSI    000001bb [SR] Verify complete
2012-02-02 00:49:13, Info                  CSI    000001bc [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:49:13, Info                  CSI    000001bd [SR] Beginning Verify and Repair transaction
2012-02-02 00:49:16, Info                  CSI    000001bf [SR] Verify complete
2012-02-02 00:49:16, Info                  CSI    000001c0 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:49:16, Info                  CSI    000001c1 [SR] Beginning Verify and Repair transaction
2012-02-02 00:49:23, Info                  CSI    000001c3 [SR] Verify complete
2012-02-02 00:49:23, Info                  CSI    000001c4 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:49:23, Info                  CSI    000001c5 [SR] Beginning Verify and Repair transaction
2012-02-02 00:49:27, Info                  CSI    000001cd [SR] Verify complete
2012-02-02 00:49:27, Info                  CSI    000001ce [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:49:27, Info                  CSI    000001cf [SR] Beginning Verify and Repair transaction
2012-02-02 00:49:30, Info                  CSI    000001d1 [SR] Verify complete
2012-02-02 00:49:30, Info                  CSI    000001d2 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:49:30, Info                  CSI    000001d3 [SR] Beginning Verify and Repair transaction
2012-02-02 00:49:33, Info                  CSI    000001d5 [SR] Verify complete
2012-02-02 00:49:33, Info                  CSI    000001d6 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:49:33, Info                  CSI    000001d7 [SR] Beginning Verify and Repair transaction
2012-02-02 00:49:36, Info                  CSI    000001d9 [SR] Verify complete
2012-02-02 00:49:36, Info                  CSI    000001da [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:49:36, Info                  CSI    000001db [SR] Beginning Verify and Repair transaction
2012-02-02 00:49:37, Info                  CSI    000001dc [SR] Cannot repair member file [l:24{12}]"mtsadmin.tlb" of Microsoft-Windows-COM-ComPlus-Admin, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2012-02-02 00:49:40, Info                  CSI    000001dd [SR] Cannot repair member file [l:24{12}]"mtsadmin.tlb" of Microsoft-Windows-COM-ComPlus-Admin, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2012-02-02 00:49:40, Info                  CSI    000001de [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"
2012-02-02 00:49:40, Info                  CSI    000001df [SR] Could not reproject corrupted file [ml:56{28},l:54{27}]"\??\C:\Windows\SysWOW64\Com"\[l:24{12}]"mtsadmin.tlb"; source file in store is also corrupted
2012-02-02 00:49:42, Info                  CSI    000001e2 [SR] Verify complete
2012-02-02 00:49:42, Info                  CSI    000001e3 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:49:42, Info                  CSI    000001e4 [SR] Beginning Verify and Repair transaction
2012-02-02 00:49:46, Info                  CSI    000001e6 [SR] Verify complete
2012-02-02 00:49:46, Info                  CSI    000001e7 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:49:46, Info                  CSI    000001e8 [SR] Beginning Verify and Repair transaction
2012-02-02 00:49:47, Info                  CSI    000001ea [SR] Verify complete
2012-02-02 00:49:47, Info                  CSI    000001eb [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:49:47, Info                  CSI    000001ec [SR] Beginning Verify and Repair transaction
2012-02-02 00:49:52, Info                  CSI    000001ee [SR] Verify complete
2012-02-02 00:49:52, Info                  CSI    000001ef [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:49:52, Info                  CSI    000001f0 [SR] Beginning Verify and Repair transaction
2012-02-02 00:50:02, Info                  CSI    000001f5 [SR] Verify complete
2012-02-02 00:50:02, Info                  CSI    000001f6 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:50:02, Info                  CSI    000001f7 [SR] Beginning Verify and Repair transaction
2012-02-02 00:50:08, Info                  CSI    000001fc [SR] Verify complete
2012-02-02 00:50:08, Info                  CSI    000001fd [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:50:08, Info                  CSI    000001fe [SR] Beginning Verify and Repair transaction
2012-02-02 00:50:14, Info                  CSI    00000204 [SR] Verify complete
2012-02-02 00:50:14, Info                  CSI    00000205 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:50:14, Info                  CSI    00000206 [SR] Beginning Verify and Repair transaction
2012-02-02 00:50:21, Info                  CSI    0000020f [SR] Verify complete
2012-02-02 00:50:21, Info                  CSI    00000210 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:50:21, Info                  CSI    00000211 [SR] Beginning Verify and Repair transaction
2012-02-02 00:50:26, Info                  CSI    00000216 [SR] Verify complete
2012-02-02 00:50:26, Info                  CSI    00000217 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:50:26, Info                  CSI    00000218 [SR] Beginning Verify and Repair transaction
2012-02-02 00:50:29, Info                  CSI    0000021b [SR] Repairing corrupted file [ml:76{38},l:74{37}]"\??\C:\Windows\SysWOW64\wdi\perftrack"\[l:24{12}]"AltTab.ptxml" from store
2012-02-02 00:50:29, Info                  CSI    0000021d [SR] Verify complete
2012-02-02 00:50:29, Info                  CSI    0000021e [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:50:29, Info                  CSI    0000021f [SR] Beginning Verify and Repair transaction
2012-02-02 00:50:30, Info                  CSI    00000220 [SR] Cannot repair member file [l:32{16}]"MigRegDB.exe.mui" of Microsoft-Windows-COM-ComPlus-Setup-MIGREGDB.Resources, 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, file is missing
2012-02-02 00:50:30, Info                  CSI    00000221 [SR] Cannot repair member file [l:30{15}]"comrepl.exe.mui" of Microsoft-Windows-COM-ComPlus-Admin-COMREPL.Resources, 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, file is missing
2012-02-02 00:50:33, Info                  CSI    00000222 [SR] Cannot repair member file [l:30{15}]"comrepl.exe.mui" of Microsoft-Windows-COM-ComPlus-Admin-COMREPL.Resources, 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, file is missing
2012-02-02 00:50:33, Info                  CSI    00000223 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.Windows Foundation Language Pack"
2012-02-02 00:50:33, Info                  CSI    00000224 [SR] Could not reproject corrupted file [ml:68{34},l:66{33}]"\??\C:\Windows\SysWOW64\Com\en-US"\[l:30{15}]"comrepl.exe.mui"; source file in store is also corrupted
2012-02-02 00:50:33, Info                  CSI    00000225 [SR] Cannot repair member file [l:32{16}]"MigRegDB.exe.mui" of Microsoft-Windows-COM-ComPlus-Setup-MIGREGDB.Resources, 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, file is missing
2012-02-02 00:50:33, Info                  CSI    00000226 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.Windows Foundation Language Pack"
2012-02-02 00:50:33, Info                  CSI    00000227 [SR] Could not reproject corrupted file [ml:68{34},l:66{33}]"\??\C:\Windows\SysWOW64\com\en-US"\[l:32{16}]"MigRegDB.exe.mui"; source file in store is also corrupted
2012-02-02 00:50:33, Info                  CSI    00000229 [SR] Verify complete
2012-02-02 00:50:33, Info                  CSI    0000022a [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:50:33, Info                  CSI    0000022b [SR] Beginning Verify and Repair transaction
2012-02-02 00:50:38, Info                  CSI    0000024c [SR] Verify complete
2012-02-02 00:50:38, Info                  CSI    0000024d [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:50:38, Info                  CSI    0000024e [SR] Beginning Verify and Repair transaction
2012-02-02 00:50:41, Info                  CSI    00000254 [SR] Verify complete
2012-02-02 00:50:41, Info                  CSI    00000255 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:50:41, Info                  CSI    00000256 [SR] Beginning Verify and Repair transaction
2012-02-02 00:50:45, Info                  CSI    00000258 [SR] Verify complete
2012-02-02 00:50:45, Info                  CSI    00000259 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:50:45, Info                  CSI    0000025a [SR] Beginning Verify and Repair transaction
2012-02-02 00:50:49, Info                  CSI    0000025c [SR] Verify complete
2012-02-02 00:50:49, Info                  CSI    0000025d [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:50:49, Info                  CSI    0000025e [SR] Beginning Verify and Repair transaction
2012-02-02 00:50:51, Info                  CSI    0000026c [SR] Verify complete
2012-02-02 00:50:51, Info                  CSI    0000026d [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:50:51, Info                  CSI    0000026e [SR] Beginning Verify and Repair transaction
2012-02-02 00:51:00, Info                  CSI    00000270 [SR] Verify complete
2012-02-02 00:51:00, Info                  CSI    00000271 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:51:00, Info                  CSI    00000272 [SR] Beginning Verify and Repair transaction
2012-02-02 00:51:04, Info                  CSI    00000280 [SR] Verify complete
2012-02-02 00:51:04, Info                  CSI    00000281 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:51:04, Info                  CSI    00000282 [SR] Beginning Verify and Repair transaction
2012-02-02 00:51:06, Info                  CSI    00000284 [SR] Verify complete
2012-02-02 00:51:06, Info                  CSI    00000285 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:51:06, Info                  CSI    00000286 [SR] Beginning Verify and Repair transaction
2012-02-02 00:51:10, Info                  CSI    00000288 [SR] Verify complete
2012-02-02 00:51:10, Info                  CSI    00000289 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:51:10, Info                  CSI    0000028a [SR] Beginning Verify and Repair transaction
2012-02-02 00:51:13, Info                  CSI    0000028c [SR] Verify complete
2012-02-02 00:51:13, Info                  CSI    0000028d [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:51:13, Info                  CSI    0000028e [SR] Beginning Verify and Repair transaction
2012-02-02 00:51:14, Info                  CSI    00000290 [SR] Verify complete
2012-02-02 00:51:15, Info                  CSI    00000291 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:51:15, Info                  CSI    00000292 [SR] Beginning Verify and Repair transaction
2012-02-02 00:51:21, Info                  CSI    00000294 [SR] Verify complete
2012-02-02 00:51:21, Info                  CSI    00000295 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:51:21, Info                  CSI    00000296 [SR] Beginning Verify and Repair transaction
2012-02-02 00:51:25, Info                  CSI    00000298 [SR] Verify complete
2012-02-02 00:51:25, Info                  CSI    00000299 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:51:25, Info                  CSI    0000029a [SR] Beginning Verify and Repair transaction
2012-02-02 00:51:32, Info                  CSI    000002ae [SR] Verify complete
2012-02-02 00:51:32, Info                  CSI    000002af [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:51:32, Info                  CSI    000002b0 [SR] Beginning Verify and Repair transaction
2012-02-02 00:51:35, Info                  CSI    000002b8 [SR] Verify complete
2012-02-02 00:51:35, Info                  CSI    000002b9 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:51:35, Info                  CSI    000002ba [SR] Beginning Verify and Repair transaction
2012-02-02 00:51:48, Info                  CSI    000002bc [SR] Verify complete
2012-02-02 00:51:48, Info                  CSI    000002bd [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:51:48, Info                  CSI    000002be [SR] Beginning Verify and Repair transaction
2012-02-02 00:51:51, Info                  CSI    000002c0 [SR] Verify complete
2012-02-02 00:51:51, Info                  CSI    000002c1 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:51:51, Info                  CSI    000002c2 [SR] Beginning Verify and Repair transaction
2012-02-02 00:51:53, Info                  CSI    000002c6 [SR] Verify complete
2012-02-02 00:51:53, Info                  CSI    000002c7 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:51:53, Info                  CSI    000002c8 [SR] Beginning Verify and Repair transaction
2012-02-02 00:51:56, Info                  CSI    000002ca [SR] Verify complete
2012-02-02 00:51:56, Info                  CSI    000002cb [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:51:56, Info                  CSI    000002cc [SR] Beginning Verify and Repair transaction
2012-02-02 00:51:59, Info                  CSI    000002ce [SR] Verify complete
2012-02-02 00:51:59, Info                  CSI    000002cf [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:51:59, Info                  CSI    000002d0 [SR] Beginning Verify and Repair transaction
2012-02-02 00:52:02, Info                  CSI    000002d2 [SR] Verify complete
2012-02-02 00:52:02, Info                  CSI    000002d3 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:52:02, Info                  CSI    000002d4 [SR] Beginning Verify and Repair transaction
2012-02-02 00:52:05, Info                  CSI    000002d7 [SR] Verify complete
2012-02-02 00:52:05, Info                  CSI    000002d8 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:52:05, Info                  CSI    000002d9 [SR] Beginning Verify and Repair transaction
2012-02-02 00:52:07, Info                  CSI    000002db [SR] Verify complete
2012-02-02 00:52:07, Info                  CSI    000002dc [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:52:07, Info                  CSI    000002dd [SR] Beginning Verify and Repair transaction
2012-02-02 00:52:08, Info                  CSI    000002de [SR] Cannot repair member file [l:90{45}]"Add_a_device_or_computer_to_a_network_usb.rtf" of Microsoft-Windows-WCN-Config-Registrar-Wizard.Resources, 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, file is missing
2012-02-02 00:52:10, Info                  CSI    000002df [SR] Cannot repair member file [l:22{11}]"wiatwain.ds" of Microsoft-Windows-WindowsImageAcquisition-WIATwainCompat, 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, file is missing
2012-02-02 00:52:10, Info                  CSI    000002e0 [SR] Cannot repair member file [l:90{45}]"Add_a_device_or_computer_to_a_network_usb.rtf" of Microsoft-Windows-WCN-Config-Registrar-Wizard.Resources, 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, file is missing
2012-02-02 00:52:10, Info                  CSI    000002e1 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.Microsoft-Windows-Client-Features-Language-Pack"
2012-02-02 00:52:10, Info                  CSI    000002e2 [SR] Could not reproject corrupted file [ml:68{34},l:66{33}]"\??\C:\Windows\SysWOW64\WCN\en-US"\[l:90{45}]"Add_a_device_or_computer_to_a_network_usb.rtf"; source file in store is also corrupted
2012-02-02 00:52:10, Info                  CSI    000002e3 [SR] Cannot repair member file [l:22{11}]"wiatwain.ds" of Microsoft-Windows-WindowsImageAcquisition-WIATwainCompat, 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, file is missing
2012-02-02 00:52:10, Info                  CSI    000002e4 [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.Microsoft-Windows-Client-Features-Update"
2012-02-02 00:52:10, Info                  CSI    000002e5 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\twain_32"\[l:22{11}]"wiatwain.ds"; source file in store is also corrupted
2012-02-02 00:52:11, Info                  CSI    000002e7 [SR] Verify complete
2012-02-02 00:52:11, Info                  CSI    000002e8 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:52:11, Info                  CSI    000002e9 [SR] Beginning Verify and Repair transaction
2012-02-02 00:52:14, Info                  CSI    000002ea [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:16{8}]"boot.sdi" from store
2012-02-02 00:52:14, Info                  CSI    000002ec [SR] Verify complete
2012-02-02 00:52:14, Info                  CSI    000002ed [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:52:14, Info                  CSI    000002ee [SR] Beginning Verify and Repair transaction
2012-02-02 00:52:22, Info                  CSI    000002f1 [SR] Verify complete
2012-02-02 00:52:22, Info                  CSI    000002f2 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:52:22, Info                  CSI    000002f3 [SR] Beginning Verify and Repair transaction
2012-02-02 00:52:24, Info                  CSI    000002f5 [SR] Verify complete
2012-02-02 00:52:24, Info                  CSI    000002f6 [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:52:24, Info                  CSI    000002f7 [SR] Beginning Verify and Repair transaction
2012-02-02 00:52:28, Info                  CSI    000002f9 [SR] Verify complete
2012-02-02 00:52:28, Info                  CSI    000002fa [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:52:28, Info                  CSI    000002fb [SR] Beginning Verify and Repair transaction
2012-02-02 00:52:30, Info                  CSI    000002fd [SR] Verify complete
2012-02-02 00:52:31, Info                  CSI    000002fe [SR] Verifying 100 (0x0000000000000064) components
2012-02-02 00:52:31, Info                  CSI    000002ff [SR] Beginning Verify and Repair transaction
2012-02-02 00:52:34, Info                  CSI    00000301 [SR] Verify complete
2012-02-02 00:52:34, Info                  CSI    00000302 [SR] Verifying 15 (0x000000000000000f) components
2012-02-02 00:52:34, Info                  CSI    00000303 [SR] Beginning Verify and Repair transaction
2012-02-02 00:52:35, Info                  CSI    00000305 [SR] Verify complete
2012-02-02 00:52:35, Info                  CSI    00000306 [SR] Repairing 9 components
2012-02-02 00:52:35, Info                  CSI    00000307 [SR] Beginning Verify and Repair transaction
2012-02-02 00:52:35, Info                  CSI    00000308 [SR] Cannot repair member file [l:6{3}]"BCD" of Microsoft-Windows-BootEnvironment-DVD-EFI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2012-02-02 00:52:35, Info                  CSI    00000309 [SR] Cannot repair member file [l:90{45}]"Add_a_device_or_computer_to_a_network_usb.rtf" of Microsoft-Windows-WCN-Config-Registrar-Wizard.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2012-02-02 00:52:35, Info                  CSI    0000030a [SR] Cannot repair member file [l:24{12}]"mtsadmin.tlb" of Microsoft-Windows-COM-ComPlus-Admin, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2012-02-02 00:52:35, Info                  CSI    0000030b [SR] Cannot repair member file [l:30{15}]"comrepl.exe.mui" of Microsoft-Windows-COM-ComPlus-Admin-COMREPL.Resources, 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, file is missing
2012-02-02 00:52:35, Info                  CSI    0000030c [SR] Cannot repair member file [l:32{16}]"MigRegDB.exe.mui" of Microsoft-Windows-COM-ComPlus-Setup-MIGREGDB.Resources, 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, file is missing
2012-02-02 00:52:35, Info                  CSI    0000030d [SR] Cannot repair member file [l:90{45}]"Add_a_device_or_computer_to_a_network_usb.rtf" of Microsoft-Windows-WCN-Config-Registrar-Wizard.Resources, 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, file is missing
2012-02-02 00:52:35, Info                  CSI    0000030e [SR] Cannot repair member file [l:22{11}]"wiatwain.ds" of Microsoft-Windows-WindowsImageAcquisition-WIATwainCompat, 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, file is missing
2012-02-02 00:52:35, Info                  CSI    0000030f [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:16{8}]"boot.sdi" from store
2012-02-02 00:52:35, Info                  CSI    00000310 [SR] Cannot repair member file [l:6{3}]"BCD" of Microsoft-Windows-BootEnvironment-DVD-EFI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2012-02-02 00:52:35, Info                  CSI    00000311 [SR] This component was referenced by [l:192{96}]"Microsoft-Windows-RecDisc-SDP-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsRecoveryDisc"
2012-02-02 00:52:35, Info                  CSI    00000312 [SR] This component was referenced by [l:170{85}]"Microsoft-Windows-Backup-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsBackup"
2012-02-02 00:52:35, Info                  CSI    00000313 [SR] Could not reproject corrupted file [ml:520{260},l:54{27}]"\??\C:\Windows\Boot\DVD\EFI"\[l:6{3}]"BCD"; source file in store is also corrupted
2012-02-02 00:52:35, Info                  CSI    00000314 [SR] Repairing corrupted file [ml:76{38},l:74{37}]"\??\C:\Windows\SysWOW64\wdi\perftrack"\[l:24{12}]"AltTab.ptxml" from store
2012-02-02 00:52:35, Info                  CSI    00000315 [SR] Cannot repair member file [l:22{11}]"wiatwain.ds" of Microsoft-Windows-WindowsImageAcquisition-WIATwainCompat, 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, file is missing
2012-02-02 00:52:35, Info                  CSI    00000316 [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.Microsoft-Windows-Client-Features-Update"
2012-02-02 00:52:35, Info                  CSI    00000317 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\twain_32"\[l:22{11}]"wiatwain.ds"; source file in store is also corrupted
2012-02-02 00:52:35, Info                  CSI    00000318 [SR] Cannot repair member file [l:32{16}]"MigRegDB.exe.mui" of Microsoft-Windows-COM-ComPlus-Setup-MIGREGDB.Resources, 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, file is missing
2012-02-02 00:52:35, Info                  CSI    00000319 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.Windows Foundation Language Pack"
2012-02-02 00:52:35, Info                  CSI    0000031a [SR] Could not reproject corrupted file [ml:68{34},l:66{33}]"\??\C:\Windows\SysWOW64\com\en-US"\[l:32{16}]"MigRegDB.exe.mui"; source file in store is also corrupted
2012-02-02 00:52:35, Info                  CSI    0000031b [SR] Cannot repair member file [l:90{45}]"Add_a_device_or_computer_to_a_network_usb.rtf" of Microsoft-Windows-WCN-Config-Registrar-Wizard.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2012-02-02 00:52:35, Info                  CSI    0000031c [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.Microsoft-Windows-Client-Features-Language-Pack"
2012-02-02 00:52:35, Info                  CSI    0000031d [SR] Could not reproject corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\WCN\en-US"\[l:90{45}]"Add_a_device_or_computer_to_a_network_usb.rtf"; source file in store is also corrupted
2012-02-02 00:52:35, Info                  CSI    0000031e [SR] Cannot repair member file [l:90{45}]"Add_a_device_or_computer_to_a_network_usb.rtf" of Microsoft-Windows-WCN-Config-Registrar-Wizard.Resources, 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, file is missing
2012-02-02 00:52:35, Info                  CSI    0000031f [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.Microsoft-Windows-Client-Features-Language-Pack"
2012-02-02 00:52:35, Info                  CSI    00000320 [SR] Could not reproject corrupted file [ml:68{34},l:66{33}]"\??\C:\Windows\SysWOW64\WCN\en-US"\[l:90{45}]"Add_a_device_or_computer_to_a_network_usb.rtf"; source file in store is also corrupted
2012-02-02 00:52:35, Info                  CSI    00000321 [SR] Cannot repair member file [l:24{12}]"mtsadmin.tlb" of Microsoft-Windows-COM-ComPlus-Admin, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2012-02-02 00:52:35, Info                  CSI    00000322 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"
2012-02-02 00:52:35, Info                  CSI    00000323 [SR] Could not reproject corrupted file [ml:56{28},l:54{27}]"\??\C:\Windows\SysWOW64\Com"\[l:24{12}]"mtsadmin.tlb"; source file in store is also corrupted
2012-02-02 00:52:35, Info                  CSI    00000324 [SR] Cannot repair member file [l:30{15}]"comrepl.exe.mui" of Microsoft-Windows-COM-ComPlus-Admin-COMREPL.Resources, 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, file is missing
2012-02-02 00:52:35, Info                  CSI    00000325 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.Windows Foundation Language Pack"
2012-02-02 00:52:35, Info                  CSI    00000326 [SR] Could not reproject corrupted file [ml:68{34},l:66{33}]"\??\C:\Windows\SysWOW64\Com\en-US"\[l:30{15}]"comrepl.exe.mui"; source file in store is also corrupted
2012-02-02 00:52:35, Info                  CSI    00000328 [SR] Repair complete
2012-02-02 00:52:35, Info                  CSI    00000329 [SR] Committing transaction
2012-02-02 00:52:36, Info                  CSI    0000032d [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired

Did you run the system file check three times? Also, have you at any time used automated system optimizers? Have you at any time used automated registry cleaners?

alecbh · 04 Feb 2012

I really need to know if we can rule out this being a hard drive issue. I have a HDD I bought, thinking that was the solution, and I need to return it in the next few days or else I won't be able to return the drive.

I've never used any automated performance-enhancer type programs at all. The closest thing to that would be an occasional CCleaner cleaning/registry fix. FWIW, I seriously doubt that being the problem, especially considering a fresh install of Windows on my SATA HDD exhibited the exact same symptoms as this install on this HDD, and the SATA install didn't have CCleaner installed yet. But, I could always be wrong.

Okay, I've run the system file checker 3 times now, and included the log file. It's telling me there are some corrupt system files, but it can't fix them.

I've also run the pre-boot disk checker on both harddrives. I have a USB external HDD, but it's only used for music and games. If that should be checked, let me know. The logs are in Logs.zip.

Memtest86+ USB is created, I'll run that once tonight. I already ran the most intensive Windows memory test overnight, and it ran for 21 passes with no errors.

I also included the latest crash dumps in Windows_NT6_BSOD_jcgriff2.zip.

Hope this helps narrow it down. I'm off to run stress tests.

writhziden · 04 Feb 2012

Code:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" /> 
  <EventID Qualifiers="16384">1001</EventID> 
  <Version>0</Version> 
  <Level>4</Level> 
  <Task>0</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2012-02-04T17:37:09.000000000Z" /> 
  <EventRecordID>30096</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="0" ThreadID="0" /> 
  <Channel>Application</Channel> 
  <Computer>ALEC-PC</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>Checking file system on C: 
The type of the file system is NTFS. 
A disk check has been scheduled. Windows will now check the disk. 
CHKDSK is verifying files (stage 1 of 5)... 
224256 file records processed. File verification completed. 472 large file records processed. 0 bad file records processed. 0 EA records processed. 60 reparse records processed. 
CHKDSK is verifying indexes (stage 2 of 5)... 
305742 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. 
CHKDSK is verifying security descriptors (stage 3 of 5)... 
224256 file SDs/SIDs processed. Cleaning up 588 unused index entries from index $SII of file 0x9. 
Cleaning up 588 unused index entries from index $SDH of file 0x9. Cleaning up 588 
unused security descriptors. Security descriptor verification completed. 40744 data 
files processed. CHKDSK is verifying Usn Journal... 34985896 USN bytes processed. Usn 
Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... 224240 
files processed. File data verification completed. 
CHKDSK is verifying free space (stage 5 of 5)... 
193910 free clusters processed. Free space verification is complete. CHKDSK 
discovered free space marked as allocated in the volume bitmap. 
Windows has made corrections to the file system. 

38977535 KB total disk space. 37796076 KB in 146835 files. 78908 KB in 40745 indexes. 0 KB in bad 
sectors. 326907 KB in use by the system. 65536 KB occupied by the log file. 775644 KB 
available on disk. 4096 bytes in each allocation unit. 9744383 total allocation units on 
disk. 193911 allocation units available on disk. Internal Info: 00 6c 03 00 c8 dc 02 00 
f5 05 05 00 00 00 00 00 .l.............. 2c 06 00 00 3c 00 00 00 00 00 00 00 00 00 00 00 
,...<........... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 
Windows has finished checking your disk. Please wait while your computer restarts.</Data> 
  </EventData>
  </Event>

Run disk check again on C:

Code:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" /> 
  <EventID Qualifiers="16384">1001</EventID> 
  <Version>0</Version> 
  <Level>4</Level> 
  <Task>0</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2012-02-04T00:31:35.000000000Z" /> 
  <EventRecordID>30018</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="0" ThreadID="0" /> 
  <Channel>Application</Channel> 
  <Computer>ALEC-PC</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>Checking file system on F: The type of the file system is NTFS. A disk check 
has been scheduled. Windows will now check the disk. 
CHKDSK is verifying files (stage 1 of 5)... 
65024 file records processed. File verification completed. 40 large file records processed. 0 bad file records processed. 2 EA records processed. 60 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 
94754 index entries processed. Index verification completed. 0 unindexed files scanned. 
0 unindexed files recovered. 
CHKDSK is verifying security descriptors (stage 3 of 5)... 
65024 file SDs/SIDs processed. Cleaning up 53 unused index entries from index $SII of 
file 0x9. Cleaning up 53 unused index entries from index $SDH of file 0x9. Cleaning up 
53 unused security descriptors. Security descriptor verification completed. 14866 data 
files processed. CHKDSK is verifying Usn Journal... 28817560 USN bytes processed. Usn 
Journal verification completed. 
CHKDSK is verifying file data (stage 4 of 5)... 
65008 files processed. File data verification completed. 
CHKDSK is verifying free space (stage 5 of 5)... 
480365124 free clusters processed. Free space verification is complete. 
Windows has checked the file system and found no problems.
 
1953410047 KB total disk space. 31691616 KB in 49974 files. 38672 KB in 14867 
indexes. 0 KB in bad sectors. 219259 KB in use by the system. 65536 KB occupied by 
the log file. 1921460500 KB available on disk. 4096 bytes in each allocation unit. 
488352511 total allocation units on disk. 480365125 allocation units available on disk. 
Internal Info: 00 fe 00 00 54 fd 00 00 ea 00 02 00 00 00 00 00 ....T........... 34 00 00 
00 3c 00 00 00 00 00 00 00 00 00 00 00 4...<........... 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 ................</Data> 
  </EventData>
  </Event>

It is going to be difficult to determine whether your hard drive is at fault unless these errors keep popping up. Have you run any hard disk diagnostics on the drive from the drive manufacturer?

If you want to speed up the hard drive debugging process, please fill out your system specs using step 5 of System Info - See Your System Specs and steps 1-4 to find the information.

alecbh · 04 Feb 2012

I'm not sure if you noticed, but those are two different hard drives. The first log you copied is for the C: drive, a 40gig Western Digital IDE drive. That's my boot drive, because the second drive isn't stable enough. The second drive(F: ) is a 2TB SATA Seagate drive. I can run the check on the C: drive again if you want.

I ran a Seagate utility on the SATA drive a while ago that said it was okay. I haven't run anything on this(IDE) drive, but it will actually boot and stay up, unlike the SATA drive. Should I run a diagnostics program on the IDE drive?

writhziden · 04 Feb 2012

The 2 TB SATA drive came back clean. I am surprised it is causing you problems if it comes up clean in Windows and with the diagnostics. Is it possible your installation DVD is corrupt? Did you do a clean install on the 40 GB drive?

alecbh · 04 Feb 2012

I'm feeling rather silly now.. it's very possible it could be the installation disk. I haven't done a clean install on the 40gig because I need to back it up first, and I need a computer for school, with all of my stuff on it. The odd thing is that the 40 gig usually works, but when I got the 2TB, I used Seagate's disc wizard utility to copy the drive over. To my mind, they should both work about the same, but the SATA was crashing all the time, whereas the IDE ran (mostly)fine.

writhziden · 04 Feb 2012

When you are able to, you will want to do a clean install and see if sfc /scannow still has errors. If you get errors right off the bat, chances are good that it is the install disc. You will want to make sure there are no problems with the hard disk first (before installing) by running a disk check, but if it comes back with Windows has checked the file system and found no problems, the install should go smoothly unless the install disc is bad.

Also, I wanted to clear up the CCleaner use for registry cleaning; for future reference...

Many of us on the forums actually do not recommend automated optimization tools for Windows 7. Windows 7 does a much better job of handling its own optimization than its predecessors did. We especially do not recommend registry cleaning as an "optimization" step because automated registry cleaning causes more harm to the registry than it actually repairs.

In the future, if you need help optimizing Windows 7, please post a thread in Performance & Maintenance - Windows 7 Forums or follow the tutorial enclosed in that forum to Optimize Windows 7.

How did the clean install go?

Windows 7: Non-repeatable BSOD with two different HDDs, mulitiple codes

Non-repeatable BSOD with two different HDDs, mulitiple codes problems?