Windows 7: Random BSODs, crashes, computer slowness

jwoglom · 14 Mar 2012

I built this computer about a year ago, and have had some problems recently.
Specs:
Gigabyte ga-p55a-ud3
Core i5-650 @ 3.2GHz
ATI Radeon 5770 (powering 2 monitors w/ DVI)
Patriot "Sector 5" RAM (2x4GB)
Windows 7 Home Premium x64

I have had BSODs almost daily for the past week or so, but they're all different. Several hours ago, after leaving it unattended for a few hours, the computer just kind of turned off, but with the system fan and lights still on. My monitors has no signal, and my keyboard didn't do anything, but its light was still on. Maybe there's something wrong with my graphics card? I'm going to try to run a memtest tonight.

I uploaded some minidumps below--these are all of the ones in the past 2 weeks.

Thanks.

zigzag3143 · 14 Mar 2012

These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.

Memtest.

Quote:

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+

Driver verifier

Quote:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

jwoglom · 19 Mar 2012

Quote: Originally Posted by zigzag3143

These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

Thanks, I tried that. I ran memtest86+ overnight and it showed no errors, and enabled Driver Verifier. Crashes happened somewhat randomly, occurring while watching a Youtube video in Chrome, watching a movie in VLC, browsing the internet, and other tasks. My computer also crashed multiple times while I wasn't at it, such as overnight.
Here are some new minidumps, if it helps.

Any other suggestions?

jwoglom · 19 Mar 2012

Also, I ran a GPU stress test for half an hour and the system stayed stable (some lag while doing other tasks, however), so I'm guessing that the GPU isn't at fault.

writhziden · 19 Mar 2012

Possible out of date drivers:

Code:

gdrv	fffff880`0b74a000	fffff880`0b753000	Thu Mar 12 21:22:29 2009 (49b9d175)	000105ce		gdrv.sys
cbfs	fffff880`01200000	fffff880`01233000	Sat Mar 21 07:58:26 2009 (49c4f282)	00033662		cbfs.sys

See below for these drivers...

Code:


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\jwoglom\031912-156297-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03415000 PsLoadedModuleList = 0xfffff800`0365a670
Debug session time: Mon Mar 19 11:53:28.364 2012 (UTC - 6:00)
System Uptime: 0 days 19:59:09.332
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d89bd3a6ab, b3b7465eee507611, fffff80003512880, 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
---------

2: 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: a3a039d89bd3a6ab, Reserved
Arg2: b3b7465eee507611, Reserved
Arg3: fffff80003512880, 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 fffff80003491c40

STACK_TEXT:  
fffff880`033a85d8 00000000`00000000 : 00000000`00000109 a3a039d8`9bd3a6ab b3b7465e`ee507611 fffff800`03512880 : nt!KeBugCheckEx


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80003512b4b - nt! ?? ::FNODOBFM::`string'+57bbb
	[ 48:08 ]
1 error : !nt (fffff80003512b4b)

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 [D:\Kingston\BSODDmpFiles\jwoglom\031812-54943-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03455000 PsLoadedModuleList = 0xfffff800`0369a670
Debug session time: Sun Mar 18 15:53:33.891 2012 (UTC - 6:00)
System Uptime: 0 days 3:16:52.859
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa8007c7a5a0, fffffa8007c7a5d0, 4030005}

Probably caused by : NETIO.SYS ( NETIO!HandleFilterFree+3a )

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

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa8007c7a5a0, The pool entry we were looking for within the page.
Arg3: fffffa8007c7a5d0, The next pool entry.
Arg4: 0000000004030005, (reserved)

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


BUGCHECK_STR:  0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80003704100
 fffffa8007c7a5a0 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800035ffcae to fffff800034d1c40

STACK_TEXT:  
fffff880`0eaf87f8 fffff800`035ffcae : 00000000`00000019 00000000`00000020 fffffa80`07c7a5a0 fffffa80`07c7a5d0 : nt!KeBugCheckEx
fffff880`0eaf8800 fffff880`0150e5ea : 00000000`00000000 00000000`000005f2 fffffa80`48706657 00000000`000005f2 : nt!ExDeferredFreePool+0x12da
fffff880`0eaf88b0 fffff880`0150ea65 : fffffa80`0690fe10 fffffa80`0690fe10 00000000`000000ff fffffa80`0690fdd0 : NETIO!HandleFilterFree+0x3a
fffff880`0eaf88e0 fffff880`0150eb88 : fffffa80`0913b860 fffffa80`068dd180 00000000`000005f2 fffffa80`06c3c750 : NETIO!DeleteFilterFromIndex+0x165
fffff880`0eaf8960 fffff880`0150f454 : fffffa80`06000004 fffffa80`06bb0f80 fffffa80`0913b898 00000000`00000000 : NETIO!KfdCommitTransaction+0xe1
fffff880`0eaf89a0 fffff880`0160efcb : fffffa80`0913b860 fffffa80`06bb0f80 fffffa80`098fcf20 00000000`00000001 : NETIO!IoctlKfdCommitTransaction+0x54
fffff880`0eaf89d0 fffff800`037eca97 : fffffa80`098fcf20 fffff880`0eaf8ca0 fffffa80`098fcf20 fffffa80`0913b860 : tcpip!KfdDispatchDevCtl+0x6b
fffff880`0eaf8a10 fffff800`037ed2f6 : fffff680`0001b288 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`0eaf8b40 fffff800`034d0ed3 : 00000000`00dce9f0 0000007f`ffffffff 000007fe`ff58e0d0 00000980`00000000 : nt!NtDeviceIoControlFile+0x56
fffff880`0eaf8bb0 00000000`7755138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00dcf5f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7755138a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!HandleFilterFree+3a
fffff880`0150e5ea 48b8faaddbbafaaddbba mov rax,0BADBADFABADBADFAh

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  NETIO!HandleFilterFree+3a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79381

FAILURE_BUCKET_ID:  X64_0x19_20_NETIO!HandleFilterFree+3a

BUCKET_ID:  X64_0x19_20_NETIO!HandleFilterFree+3a

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

Loading Dump File [D:\Kingston\BSODDmpFiles\jwoglom\031612-30014-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03450000 PsLoadedModuleList = 0xfffff800`03695670
Debug session time: Fri Mar 16 12:10:36.352 2012 (UTC - 6:00)
System Uptime: 0 days 8:28:10.694
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff8800db54028, fffff8800db53880, fffff800034f8d93}

Unable to load image \SystemRoot\system32\DRIVERS\mozy.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mozy.sys
*** ERROR: Module load completed but symbols could not be loaded for mozy.sys
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonWrite+3390 )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff8800db54028
Arg3: fffff8800db53880
Arg4: fffff800034f8d93

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


EXCEPTION_RECORD:  fffff8800db54028 -- (.exr 0xfffff8800db54028)
ExceptionAddress: fffff800034f8d93 (nt!MmCopyToCachedPage+0x0000000000000223)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000a8f239
Attempt to read from address 0000000000a8f239

CONTEXT:  fffff8800db53880 -- (.cxr 0xfffff8800db53880)
rax=0000000000a8f201 rbx=0000000000000000 rcx=0000000fffffffff
rdx=fffff80003450000 rsi=ffffffffffffffff rdi=fffffa800bd01e90
rip=fffff800034f8d93 rsp=fffff8800db54260 rbp=fffff8800db542c0
 r8=0000098000000000  r9=0000000038f9701c r10=0000058000000000
r11=fffff8800db541e8 r12=fffff6fcc0159b38 r13=0000000000000000
r14=0000000000001000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!MmCopyToCachedPage+0x223:
fffff800`034f8d93 8b7838          mov     edi,dword ptr [rax+38h] ds:002b:00000000`00a8f239=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Bitcasa.exe

CURRENT_IRQL:  0

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

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000a8f239

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036ff100
 0000000000a8f239 

FOLLOWUP_IP: 
Ntfs!NtfsCommonWrite+3390
fffff880`0121dbf6 84c0            test    al,al

FAULTING_IP: 
nt!MmCopyToCachedPage+223
fffff800`034f8d93 8b7838          mov     edi,dword ptr [rax+38h]

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff800034f5e3e to fffff800034f8d93

STACK_TEXT:  
fffff880`0db54260 fffff800`034f5e3e : fffff980`2b367000 00000000`38f9701c fffff880`00000000 00000000`00001000 : nt!MmCopyToCachedPage+0x223
fffff880`0db54450 fffff800`034f63f4 : fffffa80`0cb47280 00000000`38f9701c fffff880`0db54590 00000000`00000000 : nt!CcMapAndCopyInToCache+0x20e
fffff880`0db54540 fffff880`0121dbf6 : 00000000`00000000 fffff880`0db547b0 fffffa80`07e7f230 fffffa80`07e7f230 : nt!CcCopyWrite+0x194
fffff880`0db545d0 fffff880`0121e1a3 : fffffa80`07e7f230 fffffa80`073656d0 fffff880`0db54701 fffff880`0db54700 : Ntfs!NtfsCommonWrite+0x3390
fffff880`0db54780 fffff880`01082bcf : fffffa80`07365ab8 fffffa80`073656d0 fffffa80`06e06230 00000000`00000000 : Ntfs!NtfsFsdWrite+0x1c3
fffff880`0db54840 fffff880`010816df : fffffa80`076fec90 00000000`00000000 fffffa80`076fec00 fffffa80`073656d0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0db548d0 fffff880`0162e7a9 : fffffa80`07365600 fffffa80`06b51320 fffffa80`07d79d20 fffffa80`07d79d00 : fltmgr!FltpDispatch+0xcf
fffff880`0db54930 fffffa80`07365600 : fffffa80`06b51320 fffffa80`07d79d20 fffffa80`07d79d00 fffff880`0db54a02 : mozy+0x47a9
fffff880`0db54938 fffffa80`06b51320 : fffffa80`07d79d20 fffffa80`07d79d00 fffff880`0db54a02 00000000`00000000 : 0xfffffa80`07365600
fffff880`0db54940 fffffa80`07d79d20 : fffffa80`07d79d00 fffff880`0db54a02 00000000`00000000 fffffa80`00000000 : 0xfffffa80`06b51320
fffff880`0db54948 fffffa80`07d79d00 : fffff880`0db54a02 00000000`00000000 fffffa80`00000000 00000000`38f3101c : 0xfffffa80`07d79d20
fffff880`0db54950 fffff880`0db54a02 : 00000000`00000000 fffffa80`00000000 00000000`38f3101c fffff880`0db54b40 : 0xfffffa80`07d79d00
fffff880`0db54958 00000000`00000000 : fffffa80`00000000 00000000`38f3101c fffff880`0db54b40 fffffa80`076fec90 : 0xfffff880`0db54a02


SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  Ntfs!NtfsCommonWrite+3390

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d79997b

STACK_COMMAND:  .cxr 0xfffff8800db53880 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCommonWrite+3390

BUCKET_ID:  X64_0x24_Ntfs!NtfsCommonWrite+3390

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

Possible causes are Memory problems... Drivers... Hardware... Virtual Hardware... Applications...
Possible causes are VPN... Network adapter drivers being corrupted or out of date... Audio drivers being corrupted or out of date... Antivirus software...
Likely caused by mozy.sys. Could also be hard disk file system corruption... System file corruption... Application conflicts...

We will start with the common problems first (see bold possible causes). Do the following steps and test by doing your normal routine after each step to see if stability increases. 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 can do your normal routine for a few weeks without a crash, and your crashes are usually more frequent than that, then the problem is likely solved.

If you are overclocking any hardware, please stop.
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.
For any drives that do not give the message:
Windows has checked the file system and found no problems
run disk check again as above. In other words, if it says:
Windows has made corrections to the file system
after running the disk check, run the disk check again.
Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
gdrv.sys: Remove Gigabyte Easy Saver - mobo power utility; it is known to cause crashes when out of date.
cbfs.sys: Remove Callback File System; these types of programs are notorious for causing crashes.
Troubleshoot Application Conflicts by Performing a Clean Startup
Re-install or install the latest drivers for your network adapters and audio devices.
Re-install your antivirus if you have one. If you do not have one:
Microsoft Security Essentials - Free Antivirus for Windows
Good and Free system security combination.
If you did not have antivirus software, run a full scan of your system after updating your new security software.
Uninstall your online backup software.

jwoglom · 22 Mar 2012

I ran sfc and it said that there were errors that it could not fix. Ran it about 2 times with the same error.
Here is the log file that it referenced, if that helps.

writhziden · 22 Mar 2012

See OPTION THREE of SFC /SCANNOW Command - System File Checker and post the sfcdetails.txt file instead.

The tip in that OPTION also gives information on how to replace any corrupted files found.

jwoglom · 22 Mar 2012

Here you go.

writhziden · 22 Mar 2012

Code:

2012-03-22 05:28:49, Info                  CSI    000000b8 [SR] Verifying 100 (0x0000000000000064) components
2012-03-22 05:28:49, Info                  CSI    000000b9 [SR] Beginning Verify and Repair transaction
2012-03-22 05:28:52, Info                  CSI    000000bb [SR] Cannot repair member file [l:30{15}]"MSHWCHTRIME.dll" of Microsoft-Windows-IME-Traditional-Chinese-IMEPadApplet, 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, hash mismatch
2012-03-22 05:28:55, Info                  CSI    000000ce [SR] Cannot repair member file [l:30{15}]"MSHWCHTRIME.dll" of Microsoft-Windows-IME-Traditional-Chinese-IMEPadApplet, 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, hash mismatch
2012-03-22 05:28:55, Info                  CSI    000000cf [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2012-03-22 05:28:55, Info                  CSI    000000d2 [SR] Could not reproject corrupted file [ml:520{260},l:86{43}]"\??\C:\Windows\System32\IME\IMETC10\Applets"\[l:30{15}]"MSHWCHTRIME.dll"; source file in store is also corrupted
2012-03-22 05:28:55, Info                  CSI    000000d4 [SR] Verify complete

2012-03-22 05:35:52, Info                  CSI    00000304 [SR] Verifying 52 (0x0000000000000034) components
2012-03-22 05:35:52, Info                  CSI    00000305 [SR] Beginning Verify and Repair transaction
2012-03-22 05:35:53, Info                  CSI    00000307 [SR] Verify complete
2012-03-22 05:35:53, Info                  CSI    00000308 [SR] Repairing 1 components
2012-03-22 05:35:53, Info                  CSI    00000309 [SR] Beginning Verify and Repair transaction
2012-03-22 05:35:53, Info                  CSI    0000030b [SR] Cannot repair member file [l:30{15}]"MSHWCHTRIME.dll" of Microsoft-Windows-IME-Traditional-Chinese-IMEPadApplet, 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, hash mismatch
2012-03-22 05:35:54, Info                  CSI    0000030d [SR] Cannot repair member file [l:30{15}]"MSHWCHTRIME.dll" of Microsoft-Windows-IME-Traditional-Chinese-IMEPadApplet, 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, hash mismatch
2012-03-22 05:35:54, Info                  CSI    0000030e [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2012-03-22 05:35:54, Info                  CSI    00000311 [SR] Could not reproject corrupted file [ml:520{260},l:86{43}]"\??\C:\Windows\System32\IME\IMETC10\Applets"\[l:30{15}]"MSHWCHTRIME.dll"; source file in store is also corrupted
2012-03-22 05:35:54, Info                  CSI    00000313 [SR] Repair complete

You do not appear to have major system corruption, but it should be fixed. Use the tip in OPTION THREE of SFC /SCANNOW Command - System File Checker to replace corrupted file: MSHWCHTRIME.dll.

jwoglom · 22 Mar 2012

Does it matter if I copy the dll from an original or SP1 windows 7 disk?

Windows 7: Random BSODs, crashes, computer slowness

Random BSODs, crashes, computer slowness problems?