Incompatibility of BSOD APC Index

After more than 8 weeks of solid work, I get the BSOD. It happens almost every time I save to my desktop to Word 2007 (2nd or 3rd save the same doc).

Fault bucket: 0x1_SysCallNum_b3_RapportPG = 14fe, Type 0

Recent change was the installation of an external USB SATA connection, installation seems to be OK.

Solution Center suggests material update or deletion. There is no update and the connection is is attached.

Hello

If you run BlueScreenView to view codes BCCode or Stop - mode or Windows without failure.

See the troubleshooting of blue screen above dated Monday, March 29, 2010 19:48.

BCCode: 24 0 x 00000024

Cause

One possible cause of this bug check is damaged drive. Corruption in the system of NTFS file or defective (sectors) on the hard disk can cause this error. Corrupted drivers SCSI and IDE may also compromise the ability to read and write to the disk system, so causing the error.

Another possible cause is the depletion of memory pool non paged. If the nonpaged memory is exhausted, this error can shut down the system. However, during the indexing process, if the amount of memory available nonpaged pool is very small, another driver in nonpaged kernel memory in pool mode may also cause this error.

Solve the problem

To debug this problem: Use the command .cxr (display context record) with the 3 parameter and then use the command KB (display Stack Trace).

To solve a problem of hard drive corruption: Check Event Viewer for error of SCSI and FASTFAT (syslog) messages or Autochk (the application log) that might help determine the device or driver that generated the error. Try disabling any antivirus software or Disk Defragmenter tools that continually monitor the system. You must also run the diagnostics of material provided by the manufacturer of the system. For more information about these procedures, see the manual of your computer. Run Chkdsk /f /r to detect and resolve any file system structural corruption. You must reboot the system before the start of the analysis of disk on a system partition.

To solve a problem of impoverishment of nonpaged memory: Add new physical memory to the computer (which increases the amount of memory available to the kernel nonpaged pool), or reduce the number of files on the volume Macintosh (SFM) Services.

BCCode: 24 0 x 00000024<-- read="">
http://www.faultwire.com/solutions-fatal_error/NTFS-file-system-0x00000024-* 1051.html? order = votes

Rob - bicycle - Mark Twain said it is good.

Tags: Windows

Similar Questions

  • Blue Screen Windows 7 on consecutive weeks. Need help with mini dump APC INDEX MISMATCH

    Computer crash on 8/3, and then again on 8/10, around the same time. 8/10 have not spared no dump file, but I was able to get the mini dump 8/3.

    Microsoft (R) Windows debug 10.0.14321.1024 AMD64 Version
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading dump file [C:\Users\Roberto\Pictures\080316-110214-01.dmp]
    The mini kernel dump file: only registers and the trace of the stack are available

    Symbol of validation of the path summary *.
    Location of response time (ms)
    Deferred SRV * c:\symbols* http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV * c:\symbols* http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) free x 64
    Product: WinNt, suite: TerminalServer SingleUserTS
    By: 7601.23455.amd64fre.win7sp1_ldr.160516 - 0600
    Computer name:
    Kernel base = 0xfffff800 '02e4c000 PsLoadedModuleList = 0xfffff800' 0308e730
    The debugging session: 02:40:48.259 Wed Aug 3 2016 (UTC - 04:00)
    System: 12 days 10:24:33.931
    Loading the kernel symbols
    .

    Press (cdb, ntsd, kd) ctrl-c or ctrl-BREAK (windbg) to drop the charges of symbol that take too much time.
    Run! SYM noisy before .reload to track symbols loading issues.

    ..............................................................
    ................................................................
    .........................................................
    Loading user symbols
    Loading unloaded module list
    ..................................................
    *******************************************************************************
    *                                                                             *
    * Bugcheck analysis *.
    *                                                                             *
    *******************************************************************************

    Use! analyze - v to obtain detailed debugging information.

    Error checking 1, {746c2e09, 0, 1, fffff8801296eca0}

    Probably caused by: ntkrnlmp.exe (nt! KiSystemServiceExit + 245)

    Follow-up: MachineOwner
    ---------

    3: kd >! analyze - v
    *******************************************************************************
    *                                                                             *
    * Bugcheck analysis *.
    *                                                                             *
    *******************************************************************************

    LEAPC_INDEX_MISMATCHERREUR (1)
    This is an internal error in the kernel. The most common reason to see this
    error checking is when a file system or a driver has several mismatched
    visits to disable and re-enable the TTB. The data key item is the
    Thread-> CombinedApcDisable field. It's two separate 16-bit
    the SpecialApcDisable and the KernelApcDisable fields. A negative value
    either indicates that a driver has disabled APC normal or special
    (respectively) without reactivation; a positive value indicates that
    a driver allowed normal or special APCS (respectively) too many times.
    Arguments:
    Arg1: 00000000746c2e09, address of function or worker system call
    Arg2: 0000000000000000, thread-> ApcStateIndex
    Arg3: 0000000000000001 (thread-> SpecialApcDisable < 16)="" |="" thread-=""> KernelApcDisable)
    Arg4: fffff8801296eca0, call type (system call 0-, 1 - routine worker)

    Debugging information:
    ------------------

    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING: 7601.23455.amd64fre.win7sp1_ldr.160516 - 0600

    SYSTEM_MANUFACTURER: Dell Inc.

    SYSTEM_PRODUCT_NAME: Precision T3500 workstation

    BIOS_VENDOR: Dell Inc.

    BIOS_VERSION: A17

    BIOS_DATE: 28/05/2013

    BASEBOARD_MANUFACTURER: Dell Inc.

    BASEBOARD_PRODUCT: 09KPNV

    BASEBOARD_VERSION: A01

    DUMP_TYPE: 2

    BUGCHECK_P1: 746c2e09

    BUGCHECK_P2: 0

    BUGCHECK_P3: 1

    BUGCHECK_P4: fffff8801296eca0

    FAULTING_IP:
    + 0
    00000000' 746c2e09?              ???

    CPU_COUNT: 4

    CPU_MHZ: bfa

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 1a

    CPU_STEPPING: 5

    CPU_MICROCODE: 6, 1, 5, 0 (F, M, S, R) GIS: 19'00000000 (cache) 11'00000000 (init)

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    BUGCHECK_STR: 0X1

    Nom_processus: NIS.exe

    CURRENT_IRQL: 0

    ANALYSIS_SESSION_HOST: NFI-ROBERTO

    ANALYSIS_SESSION_TIME: 10/08/2016 14:46:50.0800

    ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

    LAST_CONTROL_TRANSFER: from fffff80002eba9a9 to fffff80002ebb400

    STACK_TEXT:
    fffff880 '1296ea68 fffff800' 02eba9a9: 00000000'00000001 00000000' 746c2e09 00000000'00000000 00000000'00000001: nt! KeBugCheckEx
    fffff880 '1296ea70 fffff800' 02eba8e0: fffffa80 '097a 4370 00000000' 592de3a8 fffff880' 1296ebc8 00000000' 00000000: nt! KiBugCheckDispatch + 0 x 69
    fffff880 '1296ebb0 00000000' 746c2e09: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiSystemServiceExit + 0 x 245
    00000000' 592decb8 00000000'00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: 0x746c2e09

    STACK_COMMAND: kb

    THREAD_SHA1_HASH_MOD_FUNC: 713a38487ff3d82058f51d9870e0b3de39cbf964

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 561f1421a866d36916a994b3bd23a42b1aea0bb5

    THREAD_SHA1_HASH_MOD: 2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b

    FOLLOWUP_IP:
    NT! KiSystemServiceExit + 245
    fffff800'02eba8e0 4883ec50 sub rsp, 50 h

    FAULT_INSTR_CODE: 50ec8348

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: nt! KiSystemServiceExit + 245

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    Nom_image: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 573a38fc

    IMAGE_VERSION: 6.1.7601.23455

    FAILURE_BUCKET_ID: X64_0x1_SysCallNum_4_nt! KiSystemServiceExit + 245

    BUCKET_ID: X64_0x1_SysCallNum_4_nt! KiSystemServiceExit + 245

    PRIMARY_PROBLEM_CLASS: X64_0x1_SysCallNum_4_nt! KiSystemServiceExit + 245

    TARGET_TIME: 2016-08 - 03T 06: 40:48.000Z

    OSBUILD: 7601

    OSSERVICEPACK: 1000

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 272

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x 64

    OSNAME: Windows 7

    OSEDITION: Windows 7 Windows NT (Service Pack 1) TerminalServer SingleUserTS

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2016-05-16 17:17:48

    BUILDDATESTAMP_STR: 160516-0600

    BUILDLAB_STR: win7sp1_ldr

    BUILDOSVER_STR: 6.1.7601.23455.amd64fre.win7sp1_ldr.160516 - 0600

    ANALYSIS_SESSION_ELAPSED_TIME: 5 D 7

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:x64_0x1_syscallnum_4_nt! kisystemserviceexit + 245

    FAILURE_ID_HASH: {e506ede0-d282-2e4c-5056-6cb373197a73}

    Follow-up: MachineOwner
    ---------

    3: kd >! analyze - v
    *******************************************************************************
    *                                                                             *
    * Bugcheck analysis *.
    *                                                                             *
    *******************************************************************************

    LEAPC_INDEX_MISMATCHERREUR (1)
    This is an internal error in the kernel. The most common reason to see this
    error checking is when a file system or a driver has several mismatched
    visits to disable and re-enable the TTB. The data key item is the
    Thread-> CombinedApcDisable field. It's two separate 16-bit
    the SpecialApcDisable and the KernelApcDisable fields. A negative value
    either indicates that a driver has disabled APC normal or special
    (respectively) without reactivation; a positive value indicates that
    a driver allowed normal or special APCS (respectively) too many times.
    Arguments:
    Arg1: 00000000746c2e09, address of function or worker system call
    Arg2: 0000000000000000, thread-> ApcStateIndex
    Arg3: 0000000000000001 (thread-> SpecialApcDisable < 16)="" |="" thread-=""> KernelApcDisable)
    Arg4: fffff8801296eca0, call type (system call 0-, 1 - routine worker)

    Debugging information:
    ------------------

    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING: 7601.23455.amd64fre.win7sp1_ldr.160516 - 0600

    SYSTEM_MANUFACTURER: Dell Inc.

    SYSTEM_PRODUCT_NAME: Precision T3500 workstation

    BIOS_VENDOR: Dell Inc.

    BIOS_VERSION: A17

    BIOS_DATE: 28/05/2013

    BASEBOARD_MANUFACTURER: Dell Inc.

    BASEBOARD_PRODUCT: 09KPNV

    BASEBOARD_VERSION: A01

    DUMP_TYPE: 2

    BUGCHECK_P1: 746c2e09

    BUGCHECK_P2: 0

    BUGCHECK_P3: 1

    BUGCHECK_P4: fffff8801296eca0

    FAULTING_IP:
    + 0
    00000000' 746c2e09?              ???

    CPU_COUNT: 4

    CPU_MHZ: bfa

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 1a

    CPU_STEPPING: 5

    CPU_MICROCODE: 6, 1, 5, 0 (F, M, S, R) GIS: 19'00000000 (cache) 11'00000000 (init)

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    BUGCHECK_STR: 0X1

    Nom_processus: NIS.exe

    CURRENT_IRQL: 0

    ANALYSIS_SESSION_HOST: NFI-ROBERTO

    ANALYSIS_SESSION_TIME: 10/08/2016 14:46:52.0300

    ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

    LAST_CONTROL_TRANSFER: from fffff80002eba9a9 to fffff80002ebb400

    STACK_TEXT:
    fffff880 '1296ea68 fffff800' 02eba9a9: 00000000'00000001 00000000' 746c2e09 00000000'00000000 00000000'00000001: nt! KeBugCheckEx
    fffff880 '1296ea70 fffff800' 02eba8e0: fffffa80 '097a 4370 00000000' 592de3a8 fffff880' 1296ebc8 00000000' 00000000: nt! KiBugCheckDispatch + 0 x 69
    fffff880 '1296ebb0 00000000' 746c2e09: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiSystemServiceExit + 0 x 245
    00000000' 592decb8 00000000'00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: 0x746c2e09

    STACK_COMMAND: kb

    THREAD_SHA1_HASH_MOD_FUNC: 713a38487ff3d82058f51d9870e0b3de39cbf964

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 561f1421a866d36916a994b3bd23a42b1aea0bb5

    THREAD_SHA1_HASH_MOD: 2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b

    FOLLOWUP_IP:
    NT! KiSystemServiceExit + 245
    fffff800'02eba8e0 4883ec50 sub rsp, 50 h

    FAULT_INSTR_CODE: 50ec8348

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: nt! KiSystemServiceExit + 245

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    Nom_image: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 573a38fc

    IMAGE_VERSION: 6.1.7601.23455

    FAILURE_BUCKET_ID: X64_0x1_SysCallNum_4_nt! KiSystemServiceExit + 245

    BUCKET_ID: X64_0x1_SysCallNum_4_nt! KiSystemServiceExit + 245

    PRIMARY_PROBLEM_CLASS: X64_0x1_SysCallNum_4_nt! KiSystemServiceExit + 245

    TARGET_TIME: 2016-08 - 03T 06: 40:48.000Z

    OSBUILD: 7601

    OSSERVICEPACK: 1000

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 272

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x 64

    OSNAME: Windows 7

    OSEDITION: Windows 7 Windows NT (Service Pack 1) TerminalServer SingleUserTS

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2016-05-16 17:17:48

    BUILDDATESTAMP_STR: 160516-0600

    BUILDLAB_STR: win7sp1_ldr

    BUILDOSVER_STR: 6.1.7601.23455.amd64fre.win7sp1_ldr.160516 - 0600

    ANALYSIS_SESSION_ELAPSED_TIME: 581

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:x64_0x1_syscallnum_4_nt! kisystemserviceexit + 245

    FAILURE_ID_HASH: {e506ede0-d282-2e4c-5056-6cb373197a73}

    Follow-up: MachineOwner
    ---------

    3: kd >! analyze - v
    *******************************************************************************
    *                                                                             *
    * Bugcheck analysis *.
    *                                                                             *
    *******************************************************************************

    LEAPC_INDEX_MISMATCHERREUR (1)
    This is an internal error in the kernel. The most common reason to see this
    error checking is when a file system or a driver has several mismatched
    visits to disable and re-enable the TTB. The data key item is the
    Thread-> CombinedApcDisable field. It's two separate 16-bit
    the SpecialApcDisable and the KernelApcDisable fields. A negative value
    either indicates that a driver has disabled APC normal or special
    (respectively) without reactivation; a positive value indicates that
    a driver allowed normal or special APCS (respectively) too many times.
    Arguments:
    Arg1: 00000000746c2e09, address of function or worker system call
    Arg2: 0000000000000000, thread-> ApcStateIndex
    Arg3: 0000000000000001 (thread-> SpecialApcDisable < 16)="" |="" thread-=""> KernelApcDisable)
    Arg4: fffff8801296eca0, call type (system call 0-, 1 - routine worker)

    Debugging information:
    ------------------

    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING: 7601.23455.amd64fre.win7sp1_ldr.160516 - 0600

    SYSTEM_MANUFACTURER: Dell Inc.

    SYSTEM_PRODUCT_NAME: Precision T3500 workstation

    BIOS_VENDOR: Dell Inc.

    BIOS_VERSION: A17

    BIOS_DATE: 28/05/2013

    BASEBOARD_MANUFACTURER: Dell Inc.

    BASEBOARD_PRODUCT: 09KPNV

    BASEBOARD_VERSION: A01

    DUMP_TYPE: 2

    BUGCHECK_P1: 746c2e09

    BUGCHECK_P2: 0

    BUGCHECK_P3: 1

    BUGCHECK_P4: fffff8801296eca0

    FAULTING_IP:
    + 0
    00000000' 746c2e09?              ???

    CPU_COUNT: 4

    CPU_MHZ: bfa

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 1a

    CPU_STEPPING: 5

    CPU_MICROCODE: 6, 1, 5, 0 (F, M, S, R) GIS: 19'00000000 (cache) 11'00000000 (init)

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    BUGCHECK_STR: 0X1

    Nom_processus: NIS.exe

    CURRENT_IRQL: 0

    ANALYSIS_SESSION_HOST: NFI-ROBERTO

    ANALYSIS_SESSION_TIME: 10/08/2016 14:46:53.0713

    ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

    LAST_CONTROL_TRANSFER: from fffff80002eba9a9 to fffff80002ebb400

    STACK_TEXT:
    fffff880 '1296ea68 fffff800' 02eba9a9: 00000000'00000001 00000000' 746c2e09 00000000'00000000 00000000'00000001: nt! KeBugCheckEx
    fffff880 '1296ea70 fffff800' 02eba8e0: fffffa80 '097a 4370 00000000' 592de3a8 fffff880' 1296ebc8 00000000' 00000000: nt! KiBugCheckDispatch + 0 x 69
    fffff880 '1296ebb0 00000000' 746c2e09: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiSystemServiceExit + 0 x 245
    00000000' 592decb8 00000000'00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: 0x746c2e09

    STACK_COMMAND: kb

    THREAD_SHA1_HASH_MOD_FUNC: 713a38487ff3d82058f51d9870e0b3de39cbf964

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 561f1421a866d36916a994b3bd23a42b1aea0bb5

    THREAD_SHA1_HASH_MOD: 2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b

    FOLLOWUP_IP:
    NT! KiSystemServiceExit + 245
    fffff800'02eba8e0 4883ec50 sub rsp, 50 h

    FAULT_INSTR_CODE: 50ec8348

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: nt! KiSystemServiceExit + 245

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    Nom_image: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 573a38fc

    IMAGE_VERSION: 6.1.7601.23455

    FAILURE_BUCKET_ID: X64_0x1_SysCallNum_4_nt! KiSystemServiceExit + 245

    BUCKET_ID: X64_0x1_SysCallNum_4_nt! KiSystemServiceExit + 245

    PRIMARY_PROBLEM_CLASS: X64_0x1_SysCallNum_4_nt! KiSystemServiceExit + 245

    TARGET_TIME: 2016-08 - 03T 06: 40:48.000Z

    OSBUILD: 7601

    OSSERVICEPACK: 1000

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 272

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x 64

    OSNAME: Windows 7

    OSEDITION: Windows 7 Windows NT (Service Pack 1) TerminalServer SingleUserTS

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2016-05-16 17:17:48

    BUILDDATESTAMP_STR: 160516-0600

    BUILDLAB_STR: win7sp1_ldr

    BUILDOSVER_STR: 6.1.7601.23455.amd64fre.win7sp1_ldr.160516 - 0600

    ANALYSIS_SESSION_ELAPSED_TIME: 562

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:x64_0x1_syscallnum_4_nt! kisystemserviceexit + 245

    FAILURE_ID_HASH: {e506ede0-d282-2e4c-5056-6cb373197a73}

    Follow-up: MachineOwner
    ---------

    3: kd >! thread
    GetPointerFromAddress: unable to read from fffff800030f8000
    WIRE fffffa80097a4370 Teb 087c.2f00 Cid: 000000007eede000 Win32Thread: fffff900c1e29c10 PROCESSOR 3
    Impersonation token: fffff8a0219c7100 (level impersonation)
    GetUlongFromAddress: cannot read fffff80003036c18
    Owning process fffffa8004e03a10 Image: NIS.exe
    Joint process s/o Image: n/a
    fffff78000000000: cannot get shared data

    fffff880 '1296e680 fffff880' 01d21647Unable to load the image \SystemRoot\system32\drivers\NISx64\1606040.005\SYMEFASI64. SYS, 0n2 error Win32
    WARNING: Unable to verify timestamp for SYMEFASI64. SYS
    ERROR: Module load completed but symbols can not be loaded for SYMEFASI64. SYS
    SYMEFASI64 + 0 X 104647

    Norton caused this crash. I suggest that uninstall you it and try Microsoft security essentials and windows firewall.

    Download and run the Norton removal tool.

    https://support.Norton.com/SP/en/us/home/current/solutions/v60392881_EndUserProfile_en_us

  • In Vista, APC Index Mismatch blue screen error

    I recently started getting this error. I'm not entirely sure of what he calls, but I have some information here:

    Signature of the problem:
    Problem event name: BlueScreen
    OS version: 6.0.6001.2.1.0.256.1
    Locale ID: 1033

    More information about the problem:
    BCCode: 1
    BCP1: 8385B 526
    BCP2: 00000000
    BCP3: 0000FFFE
    BCP4: 00000000
    OS version: 6_0_6001
    Service Pack: 1_0
    Product: 256_1

    Files helping to describe the problem:
    C:\Windows\Minidump\Mini052511-01.dmp
    C:\Users\mdk\AppData\Local\Temp\WER-32432-0.SysData.XML
    C:\Users\mdk\AppData\Local\Temp\WER7FB.tmp.version.txt

    The main problem is, I restart my computer often and this is the only time where I had this happen so far. I probably reboot my computer once a month or so, sometimes more if there is no reason to restart. Between the last time I have now and the last time that I restarted, I installed a few games. GTA 4, GTA SA, SC 2, AOE 2/3, 1/2 SC and Grid. Also with some games came Steam and this thing of Rockstar club. I don't remember if or what else I installed it, I'm sure that there are more good.

    I have no new hardware changes.

    Off a response that I've read here, I open CMD and typed: SFC/scannow

    I don't know much of what the log file, but in the CMD window, it stated that it finds corrupted files, but cannot fix them.

    It would be great if someone could help me if I can avoid this problem in the future. If you need information let me know.

    EDIT: I just looked through some of the file and noticed several files that were trying to be repaired.

    ---------------------------------------------------------------------

    2011-05-25 05:01:03, CSI Info 0000006b transaction [SR] beginning verify and repair
    2011-05-25 05:01:05, CSI Info 0000006 c hashes of file members \SystemRoot\WinSxS\x86_microsoft-windows-b... OS-Loader.resources_31bf3856ad364e35_6.0.6001.18000_en-us_7698ba05e403d673\winload.exe.mui are not real file [l:30 {15}] "winload.exe.mui": "
    Found: {l:32 b:3LWnAHQ + tXNZYwpT2WjJ0Vux4kGWnrBpp6f/951z5qs =} expected: {l:32 = b:YJkIUI1nSp830jIFl7w4pFkQNolxyerSrcUeSi3WGAg}
    2011-05-25 05:01:05, Info CSI 0000006 d [SR] cannot repair the military record [l:30 {15}] "winload.exe.mui" Microsoft-Windows-BootEnvironment-OS - Loader.Resources, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10 {5}] 'en-US', VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
    2011-05-25 05:01:07, CSI 0000006e Info ignoring duplicate for directory property [l:64 {32}] '------? \C:\Windows\Branding\Shellbrd' in the component Microsoft-Windows-Branding-Shell-Ultimate, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

    2011-05-25 05:01:07, CSI Info repaired 0000006f [SR] file \SystemRoot\WinSxS\Manifests\\[l:30{15}]"winload.exe.mui" by copying from backup
    2011-05-25 05:01:07, info CSI 00000070 hashes for Member file? \C:\Windows\System32\en-US\winload.exe.MUI are not real file [l:30 {15}] "winload.exe.mui": "
    Found: {l:32 b:3LWnAHQ + tXNZYwpT2WjJ0Vux4kGWnrBpp6f/951z5qs =} expected: {l:32 = b:YJkIUI1nSp830jIFl7w4pFkQNolxyerSrcUeSi3WGAg}
    2011-05-25 05:01:07, info CSI 00000071 [SR] repair file corrupted [ml:520 {260}, l:58 {29}] '------? \C:\Windows\System32\en-us"\[l:30{15}]"Winload.exe.MUI' of the store
    2011-05-25 05:01:08, Info CSI 00000072 repair results created:
    POQ 25 begins:
    0: move the file: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\90ae8a48ba1acc014b0a0000a8138016._0000000000000000.cdf-ms', Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms'
    1: move the file: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\60aa8c48ba1acc014c0a0000a8138016.$$.cdf-ms', Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms'
    2: move the file: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\a0ec9b48ba1acc014d0a0000a8138016.$$_branding_1728f5d8b15e5263.cdf-ms', Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_branding_1728f5d8b15e5263.cdf-ms'
    3: move the file: Source = [l:232{116}]"\SystemRoot\WinSxS\Temp\PendingRenames\b0849e48ba1acc014e0a0000a8138016.$$_branding_shellbrd_be1f632087fb0947.cdf-ms', Destination = [l:144{72}]"\SystemRoot\WinSxS\FileMaps\$$_branding_shellbrd_be1f632087fb0947.cdf-ms'
    4: create the file: file = [l:268 {134}] "\SystemRoot\WinSxS\x86_microsoft-windows-b... OS-Loader.resources_31bf3856ad364e35_6.0.6001.18000_en-us_7698ba05e403d673\winload.exe.mui ', attributes = 00000080 '.
    5: move the file: Source = [l:174{87}]"\SystemRoot\WinSxS\Temp\PendingRenames\d007ab48ba1acc014f0a0000a8138016.winload.exe.mui', Destination = [l:268 {134}]" \SystemRoot\WinSxS\x86_microsoft-windows-b... "] OS-Loader.resources_31bf3856ad364e35_6.0.6001.18000_en-us_7698ba05e403d673\winload.exe.mui ".
    6: move the file: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\10bbbc48ba1acc01500a0000a8138016.$$_system32_21f9a9c4a2f8b514.cdf-ms', Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_system32_21f9a9c4a2f8b514.cdf-ms'
    7: move the file: Source = [l:226{113}]"\SystemRoot\WinSxS\Temp\PendingRenames\e07ac848ba1acc01510a0000a8138016.$$_system32_en-us_429cd25484dc6f94.cdf-ms', Destination = [l:138{69}]"\SystemRoot\WinSxS\FileMaps\$$_system32_en-us_429cd25484dc6f94.cdf-ms'
    8: hard link file: Source = [l:268 {134}] "\SystemRoot\WinSxS\x86_microsoft-windows-b... operating system loader.
    2011-05-25 05:01:08, resources_31bf3856ad364e35_6.0.6001.18000_en-us_7698ba05e403d673\winload.exe.mui CSI Info", Destination = [l:90 {45}] '------? \C:\Windows\System32\en-US\winload.exe.MUI ".
    9: move the file: Source = [l:244{122}]"\SystemRoot\WinSxS\Temp\PendingRenames\60cada48ba1acc01520a0000a8138016.$$_system32_branding_en-us_86fc4588168f7f89.cdf-ms', Destination = [l:156{78}]"\SystemRoot\WinSxS\FileMaps\$$_system32_branding_en-us_86fc4588168f7f89.cdf-ms'
    10: move the file: Source = [l:224{112}]"\SystemRoot\WinSxS\Temp\PendingRenames\50770b49ba1acc01530a0000a8138016.$$_system32_boot_06654401df2fc50e.cdf-ms', Destination = [l:136{68}]"\SystemRoot\WinSxS\FileMaps\$$_system32_boot_06654401df2fc50e.cdf-ms'

    POQ 25 ends.

    ----------------------------------------------------------------------------------------------------------------

    2011-05-25 05:07:51, CSI Info 000001 d 6 [SR] check all the
    2011-05-25 05:07:51, CSI Info 000001 d 7 [SR] repair 4 components
    2011-05-25 05:07:51, CSI Info 000001 d 8 [SR] beginning operation check and repair
    2011-05-25 05:07:51, CSI Info 000001 d 9 hashes of file members \SystemRoot\WinSxS\x86_microsoft-windows-b... OS-Loader.resources_31bf3856ad364e35_6.0.6001.18000_en-us_7698ba05e403d673\winload.exe.mui are not real file [l:30 {15}] "winload.exe.mui": "
    Found: {l:32 b:3LWnAHQ + tXNZYwpT2WjJ0Vux4kGWnrBpp6f/951z5qs =} expected: {l:32 = b:YJkIUI1nSp830jIFl7w4pFkQNolxyerSrcUeSi3WGAg}
    2011-05-25 05:07:51, 000001da CSI Info [SR] cannot repair the military record [l:30 {15}] "winload.exe.mui" Microsoft-Windows-BootEnvironment-OS - Loader.Resources, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10 {5}] 'en-US', VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
    2011-05-25 05:07:51, CSI Info 000001db hashes of file members \SystemRoot\WinSxS\x86_microsoft-windows-m... kstvtuner.resources_31bf3856ad364e35_6.0.6000.16386_en-us_ee2f878f69953660\kstvtune.ax.mui is not actual file [l:30 {15}] "kstvtune.ax.mui": "
    Found: {l:32 b:hQNU0fCJdGk8GuQJVI42hRCDFa + IC6mQCHIAX9wrdtA =} expected: {l:32 = b:CDmwEbDCz0vSYR35m7LVLRYRvK20qLUQx8JHVuNbFoQ}
    2011-05-25 05:07:51, 000001dc CSI Info [SR] cannot repair the military record [l:30 {15}] "kstvtune.ax.mui" Microsoft-Windows - MultimediaDShowFilters.ksTvtuner.Resources, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10 {5}] 'en-US', VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
    2011-05-25 05:07:51, CSI Info 000001dd hashes of file members \SystemRoot\WinSxS\x86_microsoft-windows-m... kstvtuner.resources_31bf3856ad364e35_6.0.6000.16386_en-us_ee2f878f69953660\ksxbar.ax.mui is not actual file [l:26 {13}] "ksxbar.ax.mui": "
    Found: {l:32 b:gwkLWxG23qrsVXMTp28wbRst31NtjwVDaV3RcejL52A =} expected: {l:32 b:mylaPWn03FrAYffJ0U08I4louHDCQL7 / hzhwLbADqr4 =}
    2011-05-25 05:07:51, 000001de CSI Info [SR] cannot repair the military record [l:26 {13}] "ksxbar.ax.mui" Microsoft-Windows - MultimediaDShowFilters.ksTvtuner.Resources, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10 {5}] 'en-US', VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
    2011-05-25 05:07:51, CSI Info hashes of file Member \SystemRoot\WinSxS\x86_microsoft-windows-s 000001df... Ity-Licensing-tools_31bf3856ad364e35_6.0.6001.18000_none_c54a066e67e43f8b\slmgr.vbs are not real file [l:18 {9}] "slmgr.vbs": "
    Found: {l:32 b:XLFm0OrxFOcfPwLmEmEZE7bL82S9O9V8LNT64iPMRs0 =} expected: {l:32 b:hRxdB6AeaWMctn7TKffFNs80DZr4Yo + br9mqSuoqI5s =}
    2011-05-25 05:07:51, CSI Info 000001e0 [SR] cannot repair the military record [l:18 {9}] "slmgr.vbs" Microsoft-Windows-Security-Licensing-Tools, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
    2011-05-25 05:07:51, CSI Info 000001e1 Member \SystemRoot\WinSxS\x86_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6001.18000_none_cedcabbd26a81ad6\sidebar.exe file hashes are not actual file [l:22 {11}] "sidebar.exe": "
    Found: {l:32 b:VHEqT6KWrijPg0 + Qt3su62kCDj1bXPJGdL2NrKJRlbk =} expected: {l:32 b:8P8g4ArT7hei5GsbbQmehzMLvleUH22x2BWdcO / Sz + s =}
    2011-05-25 05:07:51, 000001e2 CSI Info [SR] cannot repair the military record [l:22 {11}] "sidebar.exe" Microsoft-Windows-Sidebar, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
    2011-05-25 05:07:51, CSI Info 000001e3 Member \SystemRoot\WinSxS\x86_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6001.18000_none_cedcabbd26a81ad6\settings.ini file hashes are not actual file [l:24 {12}] "settings.ini": "
    Found: {l:32 b:wNeWss6G0fGwdn0LaXnKhTtWW7gE3Wt6NsXoFNt7vj4 =} expected: {l:32 = b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o}
    2011-05-25 05:07:51, 000001e4 CSI Info [SR] cannot repair the military record [l:24 {12}] "settings.ini" Microsoft-Windows-Sidebar, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
    2011-05-25 05:07:51, CSI Info 000001e5 hashes of file members \SystemRoot\WinSxS\x86_microsoft-windows-m... kstvtuner.resources_31bf3856ad364e35_6.0.6000.16386_en-us_ee2f878f69953660\kstvtune.ax.mui is not actual file [l:30 {15}] "kstvtune.ax.mui": "
    Found: {l:32 b:hQNU0fCJdGk8GuQJVI42hRCDFa + IC6mQCHIAX9wrdtA =} expected: {l:32 = b:CDmwEbDCz0vSYR35m7LVLRYRvK20qLUQx8JHVuNbFoQ}
    2011-05-25 05:07:51, 000001e6 CSI Info [SR] cannot repair the military record [l:30 {15}] "kstvtune.ax.mui" Microsoft-Windows - MultimediaDShowFilters.ksTvtuner.Resources, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10 {5}] 'en-US', VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
    2011-05-25 05:07:51, 000001e7 CSI Info [SR] this element is referenced by [l:262{131}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~x86~en-US~6.0.6000.16386.Microsoft-Windows-Client-Features-Language-Pack'
    2011-05-25 05:07:51, CSI Info 000001e8 hashes of file members \SystemRoot\WinSxS\x86_microsoft-windows-m... kstvtuner.resources_31bf3856ad364e35_6.0.6000.16386_en-us_ee2f878f69953660\ksxbar.ax.mui is not actual file [l:26 {13}] "ksxbar.ax.mui": "
    Found: {l:32 b:gwkLWxG23qrsVXMTp28wbRst31NtjwVDaV3RcejL52A =} expected: {l:32 b:mylaPWn03FrAYffJ0U08I4louHDCQL7 / hzhwLbADqr4 =}
    2011-05-25 05:07:51, 000001e9 CSI Info [SR] cannot repair the military record [l:26 {13}] "ksxbar.ax.mui" Microsoft-Windows - MultimediaDShowFilters.ksTvtuner.Resources, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10 {5}] 'en-US', VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
    2011-05-25 05:07:51, 000001ea CSI Info [SR] this element is referenced by [l:262{131}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~x86~en-US~6.0.6000.16386.Microsoft-Windows-Client-Features-Language-Pack'
    2011-05-25 05:07:51, CSI 000001eb hashes for Member file Info? \C:\Windows\System32\en-US\kstvtune.AX.MUI are not real file [l:30 {15}] "kstvtune.ax.mui": "
    Found: {l:32 b:hQNU0fCJdGk8GuQJVI42hRCDFa + IC6mQCHIAX9wrdtA =} expected: {l:32 = b:CDmwEbDCz0vSYR35m7LVLRYRvK20qLUQx8JHVuNbFoQ}
    2011-05-25 05:07:51, CSI Info 000001ec hashes of file members \SystemRoot\WinSxS\x86_microsoft-windows-m... kstvtuner.resources_31bf3856ad364e35_6.0.6000.16386_en-us_ee2f878f69953660\kstvtune.ax.mui is not actual file [l:30 {15}] "kstvtune.ax.mui": "
    Found: {l:32 b:hQNU0fCJdGk8GuQJVI42hRCDFa + IC6mQCHIAX9wrdtA =} expected: {l:32 = b:CDmwEbDCz0vSYR35m7LVLRYRvK20qLUQx8JHVuNbFoQ}
    2011-05-25 05:07:51, 000001ed CSI Info [SR] could not reproject corrupted file [ml:520 {260}, l:58 {29}] '------? \C:\Windows\System32\en-us"\[l:30{15}]"Kstvtune.AX.MUI '; source file in the store is also corrupted
    2011-05-25 05:07:51, Info CSI 000001ee hashes for Member file? \C:\Windows\System32\en-US\ksxbar.AX.MUI are not real file [l:26 {13}] "ksxbar.ax.mui": "
    Found: {l:32 b:gwkLWxG23qrsVXMTp28wbRst31NtjwVDaV3RcejL52A =} expected: {l:32 b:mylaPWn03FrAYffJ0U08I4louHDCQL7 / hzhwLbADqr4 =}
    2011-05-25 05:07:51, CSI Info 000001ef hashes of file members \SystemRoot\WinSxS\x86_microsoft-windows-m... kstvtuner.resources_31bf3856ad364e35_6.0.6000.16386_en-us_ee2f878f69953660\ksxbar.ax.mui is not actual file [l:26 {13}] "ksxbar.ax.mui": "
    Found: {l:32 b:gwkLWxG23qrsVXMTp28wbRst31NtjwVDaV3RcejL52A =} expected: {l:32 b:mylaPWn03FrAYffJ0U08I4louHDCQL7 / hzhwLbADqr4 =}
    2011-05-25 05:07:51, 000001f0 CSI Info [SR] could not reproject corrupted file [ml:520 {260}, l:58 {29}] '------? \C:\Windows\System32\en-us"\[l:26{13}]"ksxbar.AX.MUI '; source file in the store is also corrupted
    2011-05-25 05:07:51, 000001f1 CSI repaired Info [SR] file \SystemRoot\WinSxS\Manifests\\[l:30{15}]"winload.exe.mui" by copying from backup
    2011-05-25 05:07:51, CSI 000001f2 hashes for Member file Info? \C:\Windows\System32\en-US\winload.exe.MUI are not real file [l:30 {15}] "winload.exe.mui": "
    Found: {l:32 b:3LWnAHQ + tXNZYwpT2WjJ0Vux4kGWnrBpp6f/951z5qs =} expected: {l:32 = b:YJkIUI1nSp830jIFl7w4pFkQNolxyerSrcUeSi3WGAg}
    2011-05-25 05:07:51, 000001f3 CSI Info [SR] repair corrupted file [ml:520 {260}, l:58 {29}] '------? \C:\Windows\System32\en-us"\[l:30{15}]"Winload.exe.MUI' of the store
    2011-05-25 05:07:51, CSI Info 000001f4 hashes of file members \SystemRoot\WinSxS\x86_microsoft-windows-s... Ity-Licensing-tools_31bf3856ad364e35_6.0.6001.18000_none_c54a066e67e43f8b\slmgr.vbs are not real file [l:18 {9}] "slmgr.vbs": "
    Found: {l:32 b:XLFm0OrxFOcfPwLmEmEZE7bL82S9O9V8LNT64iPMRs0 =} expected: {l:32 b:hRxdB6AeaWMctn7TKffFNs80DZr4Yo + br9mqSuoqI5s =}
    2011-05-25 05:07:51, 000001f5 CSI Info [SR] cannot repair the military record [l:18 {9}] "slmgr.vbs" Microsoft-Windows-Security-Licensing-Tools, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
    2011-05-25 05:07:51, 000001f6 CSI Info [SR] this element is referenced by [l:160 {80}] "' Package_30_for_KB936330 ~ 31bf3856ad364e35 ~ x 86 ~ ~ 6.0.1.18000.936330 - 187_neutral_GDR" "
    2011-05-25 05:07:51, CSI 000001f7 hashes for Member file Info? \C:\windows\system32\slmgr.vbs are not real file [l:18 {9}] "slmgr.vbs": "
    Found: {l:32 b:XLFm0OrxFOcfPwLmEmEZE7bL82S9O9V8LNT64iPMRs0 =} expected: {l:32 b:hRxdB6AeaWMctn7TKffFNs80DZr4Yo + br9mqSuoqI5s =}
    2011-05-25 05:07:51, CSI Info hashes of file Member \SystemRoot\WinSxS\x86_microsoft-windows-s 000001f8... Ity-Licensing-tools_31bf3856ad364e35_6.0.6001.18000_none_c54a066e67e43f8b\slmgr.vbs are not real file [l:18 {9}] "slmgr.vbs": "
    Found: {l:32 b:XLFm0OrxFOcfPwLmEmEZE7bL82S9O9V8LNT64iPMRs0 =} expected: {l:32 b:hRxdB6AeaWMctn7TKffFNs80DZr4Yo + br9mqSuoqI5s =}
    2011-05-25 05:07:51, 000001f9 CSI Info [SR] could not reproject corrupted file [ml:520 {260}, l:46 {23}] '------? \C:\Windows\System32"\[l:18{9}]"slmgr.vbs '; source file in the store is also corrupted
    2011-05-25 05:07:51, CSI Info 000001fa Member \SystemRoot\WinSxS\x86_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6001.18000_none_cedcabbd26a81ad6\sidebar.exe file hashes are not actual file [l:22 {11}] "sidebar.exe": "
    Found: {l:32 b:VHEqT6KWrijPg0 + Qt3su62kCDj1bXPJGdL2NrKJRlbk =} expected: {l:32 b:8P8g4ArT7hei5GsbbQmehzMLvleUH22x2BWdcO / Sz + s =}
    2011-05-25 05:07:51, 000001fb CSI Info [SR] cannot repair the military record [l:22 {11}] "sidebar.exe" Microsoft-Windows-Sidebar, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
    2011-05-25 05:07:51, CSI Info 000001 fc [SR] this element is referenced by [l:158 {79}] "' Package_20_for_KB936330 ~ 31bf3856ad364e35 ~ x 86 ~ ~ 6.0.1.18000.936330 - 33_neutral_GDR" "
    2011-05-25 05:07:51, CSI Info 000001fd Member \SystemRoot\WinSxS\x86_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6001.18000_none_cedcabbd26a81ad6\settings.ini file hashes are not actual file [l:24 {12}] "settings.ini": "
    Found: {l:32 b:wNeWss6G0fGwdn0LaXnKhTtWW7gE3Wt6NsXoFNt7vj4 =} expected: {l:32 = b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o}
    2011-05-25 05:07:51, 000001fe CSI Info [SR] cannot repair the military record [l:24 {12}] "settings.ini" Microsoft-Windows-Sidebar, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
    2011-05-25 05:07:51, CSI 000001ff [SR] Info this item is referenced by [l:158 {79}] "' Package_20_for_KB936330 ~ 31bf3856ad364e35 ~ x 86 ~ ~ 6.0.1.18000.936330 - 33_neutral_GDR" "
    2011-05-25 05:07:51, info CSI 00000200 hashes for Member file? \C:\Program Files\Windows Sidebar\sidebar.exe do not actual file [l:22 {11}] "sidebar.exe": "
    Found: {l:32 b:VHEqT6KWrijPg0 + Qt3su62kCDj1bXPJGdL2NrKJRlbk =} expected: {l:32 b:8P8g4ArT7hei5GsbbQmehzMLvleUH22x2BWdcO / Sz + s =}
    2011-05-25 05:07:51, info CSI 00000201 Member \SystemRoot\WinSxS\x86_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6001.18000_none_cedcabbd26a81ad6\sidebar.exe file hashes are not actual file [l:22 {11}] "sidebar.exe": "
    Found: {l:32 b:VHEqT6KWrijPg0 + Qt3su62kCDj1bXPJGdL2NrKJRlbk =} expected: {l:32 b:8P8g4ArT7hei5GsbbQmehzMLvleUH22x2BWdcO / Sz + s =}
    2011-05-25 05:07:51, info CSI 00000202 [SR] could not reproject corrupted file [ml:520 {260}, l:72 {36}] '------? "\C:\Program Files\Windows Sidebar"------[l:22 {11}] "sidebar.exe"; source file in the store is also corrupted
    2011-05-25 05:07:51, info CSI 00000203 hashes for Member file? \C:\Program Files\Windows Sidebar\settings.ini do not actual file [l:24 {12}] "settings.ini": "
    Found: {l:32 b:wNeWss6G0fGwdn0LaXnKhTtWW7gE3Wt6NsXoFNt7vj4 =} expected: {l:32 = b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o}
    2011-05-25 05:07:51, info CSI 00000204 Member \SystemRoot\WinSxS\x86_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6001.18000_none_cedcabbd26a81ad6\settings.ini file hashes are not actual file [l:24 {12}] "settings.ini": "
    Found: {l:32 b:wNeWss6G0fGwdn0LaXnKhTtWW7gE3Wt6NsXoFNt7vj4 =} expected: {l:32 = b:v6OQf2AJO5FVbRBJuIwXxkdkCoOaSk3y0ol6uTH491o}
    2011-05-25 05:07:51, info CSI 00000205 [SR] could not reproject corrupted file [ml:520 {260}, l:72 {36}] '------? "\C:\Program Files\Windows Sidebar"------[l:24 {12}] "settings.ini"; source file in the store is also corrupted
    2011-05-25 05:07:51, Info CSI 00000206 repair results created:
    POQ 83 begins:
    0: create file: file = [l:268 {134}] "\SystemRoot\WinSxS\x86_microsoft-windows-b... OS-Loader.resources_31bf3856ad364e35_6.0.6001.18000_en-us_7698ba05e403d673\winload.exe.mui ', attributes = 00000080 '.
    1: move the file: Source = [l:174{87}]"\SystemRoot\WinSxS\Temp\PendingRenames\c0019d39bb1acc0198230000a8138016.winload.exe.mui', Destination = [l:268 {134}]" \SystemRoot\WinSxS\x86_microsoft-windows-b... "] OS-Loader.resources_31bf3856ad364e35_6.0.6001.18000_en-us_7698ba05e403d673\winload.exe.mui ".
    2: move the file: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\60dba539bb1acc0199230000a8138016._0000000000000000.cdf-ms', Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms'
    3: move the file: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\8029a639bb1acc019a230000a8138016.$$.cdf-ms', Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms'
    4: move the file: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\b0f1ad39bb1acc019b230000a8138016.$$_system32_21f9a9c4a2f8b514.cdf-ms', Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_system32_21f9a9c4a2f8b514.cdf-ms'
    5: move the file: Source = [l:226{113}]"\SystemRoot\WinSxS\Temp\PendingRenames\6063b939bb1acc019c230000a8138016.$$_system32_en-us_429cd25484dc6f94.cdf-ms', Destination = [l:138{69}]"\SystemRoot\WinSxS\FileMaps\$$_system32_en-us_429cd25484dc6f94.cdf-ms'
    6: hard link file: Source = [l:268 {134}] "\SystemRoot\WinSxS\x86_microsoft-windows-b... OS-Loader.resources_31bf3856ad364e35_6.0.6001.18000_en-us_7698ba05e403d673\winload.exe.mui', Destination = [l:90 {45}] '------? \C:\Windows\System32\en-US\winload.exe.MUI ".
    7: move the file: Source = [l:218{109}]"\SystemRoot\WinSxS\Temp\PendingRenames\a034c639bb1acc019d230000a8138016.program_files_ffd0cbfc813cc4f1.cdf-ms', Destination = [l:130{65}]"\SystemRoot\WinSxS\FileMaps\program_files_ffd0cbfc813cc4f1.cdf-ms'
    8: move the file: Source = [l:250 {125}] \SystemRoot\WinSxS\Temp\PendingRenames\b05bc639bb1acc019e230 «»
    "2011-05-25 05:07:51, CSI Info 000a8138016.program_files_windows_sidebar_8d6dbc4becba56da.cdf - ms", Destination = [l:162{81}]"\SystemRoot\WinSxS\FileMaps\program_files_windows_sidebar_8d6dbc4becba56da.cdf-ms'
    9: move the file: Source = [l:266{133}]"\SystemRoot\WinSxS\Temp\PendingRenames\c082c639bb1acc019f230000a8138016.program_files_windows_sidebar_gadgets_265d2ddf4d58a723.cdf-ms', Destination = [l:178{89}]"\SystemRoot\WinSxS\FileMaps\program_files_windows_sidebar_gadgets_265d2ddf4d58a723.cdf-ms'

    POQ 83 ends.

    It was only a matter of time, the system failed to start well and did a clean reinstall of the operating system. Works fine now.

  • Error on blue screen during windows startup - LeAPC_INDEX_MISMATCHErreur

    When starting my pc I get a blue error screen saying LeAPC_INDEX_MISMATCHErreur, my pc restarts and I get error when loading of the readers saying: 3rd master ST31000528AS CC38 ultra DMA mode 6 S.M.A.R.T capable but failed the control. 3rd drive hard master S.M.A.R.T command failed, press F1 continue.

    I also have this error report for blue screen event.

    Signature of the problem:
    Problem event name: BlueScreen
    The system version: 6.0.6002.2.2.0.768.3
    Locale ID: 2057

    More information about the problem:
    BCCode: 1
    BCP1: 85212696
    BCP2: 00000000
    BCP3: 0000FFFE
    BCP4: 00000000
    OS version: 6_0_6002
    Service Pack: 2_0
    Product: 768_1

    Files helping to describe the problem:
    C:\Windows\Minidump\Mini020712-01.dmp
    C:\Users\Kiro\AppData\Local\Temp\WER-278446-0.SysData.XML
    C:\Users\Kiro\AppData\Local\Temp\WER254B.tmp.version.txt

    Read our privacy statement:
      http://go.Microsoft.com/fwlink/?LinkId=50163&clcid=0x0409

    Is someone can you please tell me what has gone wrong, this has happened more than 3 times now.

    Hello

    What to do if Windows does not start correctly
    http://Windows.Microsoft.com/en-US/Windows-Vista/What-to-do-if-Windows-wont-START-correctly#.

    Pick up the pieces after a computer crash
    http://Windows.Microsoft.com/en-us/Windows-Vista/picking-up-the-pieces-after-a-computer-crash

    For the methods of troubleshooting blue screen using BlueScreenView and MyEventViewer see my answers
    If this thread - top 3 RESPONSES (+ 1 other).

    http://social.answers.Microsoft.com/forums/en-us/vistarepair/thread/3deab2fa-4000-4136-8c78-a3d22b1db009

    We can analyze the minidumps if make you it available to the SkyDrive or another file
    sharing sites (such as MediaFire). If you have problems to download the copy of minidumps
    for the office or in the Documents folder and download them from there.

    ZIP or download the content of the C:\Windows\minidump

    Use SkyDrive to upload collected files.
    http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02dB-4665-993a-08d865088d65

    =============================================================

    BCCode: 01 0x00000001

    The most common cause of this Bug_Check is drivers then use the methods in the next message
    updated the BIOS and drivers major. If necessary we can tell you how to run the Verifier however
    with Windows Vista, it's a good idea to update all the main drivers as the maturation process is
    still in force. (See how to update the drivers and run driver verifier in the next message).

    --------------------------------------------------------------------------------------------------------------

    Bug Check 0x1: LeAPC_INDEX_MISMATCHErreur

    LeAPC_INDEX_MISMATCHErreur bug control has a value of 0x00000001. This indicates that there is an inconsistency in the index of State APC.

    Important information if you have received a STOP Code

    If you have received a blue screen error, or stop code, the computer stopped abruptly to protect against data loss. A hardware device, its driver or software might have caused this error. If your copy of Windows is shipped with your computer, contact your computer manufacturer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact information for Microsoft or the manufacturer of your computer, Contact Support.

    If you have experience with computers and try to recover from this error, follow the steps in the Microsoft article solution STOP (blue screen) errors in Windows.

    The following actions could prevent a mistake like this does not happen:

    1. Download and install updates for your computer from Windows Update device drivers.
    2. Scan your computer for computer viruses.
    3. Check your hard drive for errors.

    LeAPC_INDEX_MISMATCHErreur settings

    The following settings are displayed on the blue screen.

    Parameter Description

    1

    The address of the system (system call) function or a worker routine.

    2

    The value of the field ApcStateIndex of the current thread.

    3

    The value of the field CombinedApcDisable of the current thread. This field consists of two separate 16-bit fields: (thread-> SpecialApcDisable < 16)=""> wire-> KernelApcDisable.)

    4

    Type (system call 0-, 1 - routine worker) of the call.

    Cause

    The most common cause of this bug check is when a system file or driver has a sequence are mismatched calls to deactivate and reactivate the APCs. The data key item is theThread-> CombinedApcDisable field. The CombinedApcDisable field is composed of two separate 16-bit fields: SpecialApcDisable and KernelApcDisable. A negative value of field indicates that a driver has disabled APC normal or special (respectively) without them the reactivation. A positive value indicates that a pilot has allowed normal TTB or special too many times.

    BCCode: 01 0x00000001<-- read="" this="">
    http://www.faultwire.com/solutions-fatal_error/APC-index-mismatch-0x00000001-* 1016.html

    ====================================================================

    Look in the Event Viewer to see if something is reported on those.
    http://www.computerperformance.co.UK/Vista/vista_event_viewer.htm

    MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
    TIP - Options - Advanced filter allows you to see a period of time instead of the entire file.

    http://www.NirSoft.NET/utils/my_event_viewer.html

    -------------------------------------------------------------------------
    Also this, so you can see the probable bluescreens.

    Windows Vista restarts automatically if your computer encounters an error that requires him to plant.
    http://www.winvistatips.com/disable-automatic-restart-T84.html

    -------------------------------------------------------------------------

    Here are a few ways to possibly fix the blue screen issue. If you could give the blue screen
    info that would help. Such as ITC and 4 others entered at the bottom left. And all others
    error information such as codes of STOP and info like IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.

    As examples:

    BCCode: 116
    BCP1: 87BC9510
    BCP2: 8C013D80
    BCP3: 00000000
    BCP4: 00000002

    or in this format:

    Stop: 0 x 00000000 (oxoooooooo oxoooooooo oxoooooooo oxooooooooo)
    Tcpip.sys - address blocking 0 x 0 00000000 000000000 DateStamp 0 x 000000000

    It is an excellent tool for displaying the blue screen error information

    BlueScreenView scans all your minidump files created during 'blue screen of death '.
    hangs and displays information about all accidents of a table - free

    http://www.NirSoft.NET/utils/blue_screen_view.html

    BlueScreens many are caused by old or damaged, in particular the video drivers drivers however
    There are other causes.

    You can do without if needed fail or the Vista DVD or recovery command prompt mode
    Options if your system was installed by the manufacturer.

    This tells you how to access the System Recovery Options and/or a Vista DVD
    http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

    You can try a system restore to a point before the problem started when one exists.

    How to make a Vista system restore
    http://www.Vistax64.com/tutorials/76905-System-Restore-how.html

    -------------------------------------------------------------------------

    Start - type this in the search box-> find COMMAND at the top and RIGHT CLICK – RUN AS ADMIN

    Enter this at the command prompt - sfc/scannow

    How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program
    generates in Windows Vista cbs.log
    http://support.Microsoft.com/kb/928228

    The log can give you the answer if there is a corrupted driver. (Says not all possible
    driver problems).

    Also run CheckDisk, so we cannot exclude as much as possible of the corruption.

    How to run the check disk at startup in Vista
    http://www.Vistax64.com/tutorials/67612-check-disk-Chkdsk.html

    -------------------------------------------------------------------------

    Often drivers up-to-date will help, usually video, sound, network card (NIC), WiFi, part 3
    keyboard and mouse, as well as of other major device drivers.

    Look at the sites of the manufacturer for drivers - and the manufacturer of the device manually.
    http://pcsupport.about.com/od/driverssupport/HT/driverdlmfgr.htm

    How to install a device driver in Vista Device Manager
    http://www.Vistax64.com/tutorials/193584-Device-Manager-install-driver.html

    How to disable automatic driver Installation in Windows Vista - drivers
    http://www.AddictiveTips.com/Windows-Tips/how-to-disable-automatic-driver-installation-in-Windows-Vista/
    http://TechNet.Microsoft.com/en-us/library/cc730606 (WS.10) .aspx

    -------------------------------------------------------------------------

    How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart
    quit unexpectedly
    http://support.Microsoft.com/kb/958233

    Troubleshooting, STOP error blue screen Vista
    http://www.chicagotech.NET/Vista/vistabluescreen.htm

    Understanding and decoding BSOD (blue screen of death) Messages
    http://www.Taranfx.com/blog/?p=692

    Windows - troubleshooting blue screen errors
    http://KB.wisc.edu/page.php?id=7033

    -------------------------------------------------------------------------

    In some cases, it may be necessary.

    The Options or Vista recovery disk Startup Repair

    How to do a startup repair
    http://www.Vistax64.com/tutorials/91467-startup-repair.html

    This tells you how to access the System Recovery Options and/or a Vista DVD
    http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

    I hope this helps.

    Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle=""><- mark="" twain="" said="" it="">

  • pilot ntkrnlpa.exe ntkrnlpa.exe + 4dfd9 IRQL_NOT_LESS_OR_EQUAL causing blue screen

    I get the BSOD and have no idea how fix and or repair.

    I ran a memory test using cd ISO and memory checks very well.

    Errors seem to be due to

    Mini090610 - 05.dmp 06/09/2010 19:23:24 IRQL_NOT_LESS_OR_EQUAL 0x0000000A 0 x 00000078 0x0000001b 0x00000001 0x81eda5ae Ntkrnlpa.exe Ntkrnlpa.exe + 4dfd9

    and

    Mini090410 - 03.dmp 04/09/2010 16:49:22 UNEXPECTED_KERNEL_MODE_TRAP 0x0000007f 0x0000000d 0x00000000 0x00000000 0x00000000 Ntkrnlpa.exe Ntkrnlpa.exe + 4e74f NT kernel & system Microsoft® Windows® operating system Microsoft Corporation 6.0.6002.18267 (vistasp2_gdr.100608 - 0458) 32 bit   C:\Windows\Minidump\Mini090410-03.dmp 2 15 6002

    I can do when I'm trying to download the video corder cam panasonic HDD. Whenever I go to some video and am trying to download to my hard drive I get the blue screen every time.

    Any ideas or suggestions?

    Hello

    Remember, test the memory and pay attention to the argument in the above troubleshooting utility
    This memory test intercept all errors. Try to run with less than sticks and change the place-
    Order lying sticks to try to ensure faster (even if the same card) is installed in the front
    slower.

    Have you checked on the other Bug_Checks to FaultWire? 1, 1 a, FE, 8th and D1? When you get this
    several BSOD is its best for a very broad approach basis for trying to limit problems. Which
    means, update ALL your main drivers, BIOS and drivers of the low-level chipset. Remove your gift
    antivirus/security programs and run the removal of their creator tools. Do the same for others who
    never been in the machine, not used, or uninstalled. See below for recommendations of use
    during the test, however in permanently would be even better.

    BCCode: 7F 0x0000007F which is the same as 0x1000007F<-- read="">
    * 1304.html http://www.faultwire.com/solutions-fatal_error/Run-a-System-diagnostic-Utility-supplied-by-your-0x1000007F-

    BCCode: 0a 0x0000000A<-- read="">
    * 1025.html http://www.faultwire.com/solutions-fatal_error/IRQL-not-less-or-Equal-0x0000000A-

    BCCode: 01 0x00000001<-- read="">
    http://www.faultwire.com/solutions-fatal_error/APC-index-mismatch-0x00000001-* 1016.html? order = votes

    BCCode: 1a 0x0000001A<-- read="">
    http://www.faultwire.com/solutions-fatal_error/memory-management-0x0000001A-* 1041.html? order = votes

    BCCode: FE 0x000000FE<-- read="">
    http://www.faultwire.com/solutions-fatal_error/BUGCODE-USB-driver-0x000000FE-* 1251.html? = date order

    BCCode: 8th 0x0000008E<-- read="" this="" read="">
    * 1151.html? order = date http://www.faultwire.com/solutions-fatal_error/kernel-mode-exception-not-HANDLED-0x0000008E-

    BCCode: D1 0x000000D1<-- read="">
    * 1210.html? order = votes http://www.faultwire.com/solutions-fatal_error/Driver-IRQL-not-less-or-Equal-0x000000D1-=.

    If a PC remove ALL power and reinstall the cards memory and cables (at both ends where possible)
    -in fact, remove and replace - do not just tight. Clean the dust bunnies and ensure that the
    fans are running (when the case is enabled). Try using a small fan blowing in the intake to reduce
    the effects of the heat. On a laptop computer on all you can do is to reinstall the memory, clean the vents, and
    try using a small fan.

    =============

    List of tools to clean/uninstall anti-malware programs
    http://social.answers.Microsoft.com/forums/en-us/msestart/thread/407bf6da-C05D-4546-8788-0aa4c25a1f91/

    Here's what I use and recommend: (these are all free and very effective versions.)

    Avast and Prevx proved extremely reliable and compatible with all I have
    launched on them. Microsoft Security Essentials and Prevx have also proven to be very
    reliable and compatible. Use MSE or Avast and Prevx, Prevx 3 but not all.

    Avast Home free - stop any shields is not necessary except leaving Standard, Web, and
    Operation of the network.

    Prevx - Home - free

    Windows Firewall

    Windows Defender (is not necessary if you use MSE)

    Protected IE - mode

    IE 8 - SmartScreen filter WE (IE 7 phishing filter)

    I also IE always start with asset if filter InPrivate IE 8.
    (It may temporarily turn off with the little icon to the left of the + bottom
    right of IE)

    Two versions of Avast are available 5.x and 4.8 x

    Avast - home - free - 5.x stop shields you do not use (except files, Web, network, &)
    Shields of behavior) - double click on the icon in the Notification area - real time Orange - click on the
    Shield that you want to stop - STOP. To stop the Orange icon to show an error indicator-
    Click on the Orange icon - top right - settings - click on the status bar - uncheck shields you
    disabled - click OK
    http://www.avast.com/free-antivirus-download

    Avast 4.8 x - home - free - stop shields, you don't need except leaving Standard, Web,.
    and the network running. (Double-click the blue icon - look OK. - upper left - Shields details
    Finish those you don't use).
    http://www.avast.com/free-antivirus-download#TAB4

    Or use Microsoft Security Essentials - free
    http://www.Microsoft.com/Security_Essentials/

    Prevx works well alongside MSE or Avast

    Prevx - home - free small, fast, exceptional protection CLOUD, working with other security
    programs. It is a single scanner, VERY EFFICIENT, if it finds something come back here
    or use Google to see how to remove.
    http://www.prevx.com/   <-->
    http://info.prevx.com/downloadcsi.asp  <-->

    PCmag - Prevx - Editor's choice
    http://www.PCMag.com/Article2/0, 2817,2346862,00.asp

    Also get Malwarebytes - free - use as scanner only. If you ever think malware and that
    would be unusual with Avast and occasional Prevx running with the exception of a low level cookie
    (not much), to UPDATE and then run it as a scanner. I have a lot of scanners and they
    never find anything of note that I started to use this configuration.

    http://www.Malwarebytes.org/

    I hope this helps.

    Rob Brown - MS MVP - Windows Desktop Experience: Bike - Mark Twain said it right.

  • Cloning three-tiered process

    Hello members of Lenovo.

    Recently, I have damaged my x220t that was more repairable... so I just bought another x230t. Unfortunately I do not have the means the SSD lenovo stock, but I absolutely loved on my x220t. My x220t is still in working order, so I use it as a desk at home.

    My x230t comes Monday, and I bought a samsung 830 series 256 GB SSD at a relatively cheap price. I plan to make a clone of my HD x230t stock to my new samsung 830 series 256 GB. I was wondering, though, if it would be possible to clone then my SSD in my old x220t to the 830 series of samsung 256Go to avoid to reinstall all my software. Would that screw up my samsung 830 series since it will clone the old drivers x220t through and interfere with x230t drivers? What are the potential problems you guys see by this method?

    Thank you guys so much.

    Sincerely,

    Ksonguyen

    Hi ksonguyen,

    Since X 220 series and X 230 series is similar, they are based on completely different chipset. You risk incompatibility and BSOD here.

    Fred

  • The computer crashes during Gaming (BSOD) and Windows performance index

    Windows 7, 64-bit

    OK, so I've had this problem for weeks. Initially, I thought the graphics card was defective. When I ran the Windows experience index, it would break on the part where he is to note the graphics card. So what I did I sent to the manufacturer and got a new, but the computer STILL crashes. Maybe the motherboard is damaged - I don't know.

    Another measure taken was to use the command prompt and the "sfc/scannow". It did not work.

    I have almost all the necessary drivers. The only one, I can not install is the Display Driver for the graphics card, for some reason any.
    The graphics card is an NVIDIA GeForce GTX 660 TI and the motherboard is an ASUS P9X79. They are compatible with each other.
    Here is the BSOD code that appears on the crash on Windows Experience Index (Rating)
    Problem event name: BlueScreen
    OS version: 6.1.7601.2.1.0.256.48
    Locale ID: 1033
    More information about the problem:
    BCCode: 116
    BCP1: FFFFFA801DE874E0
    BCP2: FFFFF880051D4F50
    BCP3: FFFFFFFFC000009A
    BCP4: 0000000000000004
    OS version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1
    Files helping to describe the problem:
    C:\Windows\Minidump\100813-17128-01.dmp
    C:\Users\###\AppData\Local\Temp\WER-64225-0.SysData.XML
    Read our privacy statement online:
    http://go.Microsoft.com/fwlink/?LinkId=104288&clcid=0x0409
    If the online privacy statement is not available, please read our offline privacy statement:
    C:\Windows\system32\en-US\erofflps.txt

    Please help me, I'm getting sick and tired of these accidents. They become a nuisance.
    Sincerely,
    Saikex

    OK, so I thought I should touch basis with you guys, because although no one answered for a while.

    The problem is certainly a problem of overheating.

    I figured out how to fix the problem - all I had to do was increase the GPU fan speed.of. Because of this, I was able to install the GPU driver successfully and play video games. (Use the GPU Tweak to increase the fan speed)
    I hope that whoever reads this found useful.
  • BSOD when running games and windows experience index

    Plug-

    AMD phenom 2 x 6

    2 GB ram EVM

    local power 450w

    card Gigabyte mother

    synergy gta 610 2 GB NVIDIA Edition

    I get bsod when running WEI and games

    I have no idea why its happening

    using archer gamma deeepcool for cooling the processor and have a firm of 80 mm fan

    Minidump files - http://1drv.ms/1wD3qeZ (OneDrive)

    Help, please

    CA

    Memtest for the utility of manufacturers of RAM and HD, and CHKDSK for HD.  You did everything

    These accidents were related to the corruption of memory (probably caused by a driver).

    Please run these tests to check your memory and find which driver is causing the problem.


    If you're overclocking (pushing components beyond their design) return you to default at least until the crash is resolved. If you don't know what it is that you're probably not overclocking.

    1-Driver Verifier (for full instructions, see our wiki here)

    If the auditor does not have the issue we move to it.

    2-Memtest. (You can learn more about running memtest here)


    If you cannot start after you have enabled the auditor reboot in safe mode
    In Vista & win 7 (F8)

    Co-written by JMH3143

    .

    CHKDSK /R
    CHKDSK WARNING: while running chkdsk on the drive if bad sectors are found all the data available in this area could be lost so as always back up your data.
    Run CHKDSK /R from a high command (run as administrator).
    Do this for each hard drive on your system.
    When he tells you, he cannot do at the moment – and ask you if you do not want to do it at the next reset - answer Y (for Yes) and press ENTER.

    Then restart and let the test to run.
    It may take some time for him to run, but keep an occasional eye on it to see if it generates errors.
    http://www.howtogeek.com/HOWTO/Windows-Vista/Guide-to-using-check-disk-in-Windows-Vista/

    See "CHKDSK LogFile' below to verify the test results.

    CHKDSK LogFile:
    Click Start and type "eventvwr.msc" (without the quotes) and press enter
    Expand the topic the Windows logs, and then select the Application log file entry.
    Double-click the Source column heading.
    Scroll down the list until you find the entrance to Chkdsk (wininit for Win7) (winlogon for XP).
    Copy / paste the results in your next post.

  • Firefox hangs (?.) BSOD) (/ questions/971282)

    For this last month that my computer has been lock up intermittently during the night. I traced the
    Firefox worm 26 problem. Sometimes the cursor will slow down and then freeze while using Firefox. The computer is completely enclosed and necessary for a hard reset. I installed the latest beta 27. Now, Firefox crashes for the BSOD. I need to resolve this problem quickly. There are questions killer deal with all other browsers, but they all work and do not freeze.
    Windows 7 64 bit
    8G memory
    256 GB, 1 TB HD SS system disc
    Intel Q9950
    MB GIGABYTE.

    Blue screen crashes are rare and usually require an incompatibility with driver graphics card. Launch Firefox in its Safe Mode and disable hardware acceleration.

    Hold down the SHIFT key when you start Firefox

    In the small dialog box that appears, click on 'Start mode safe' (not Reset)

    The orange open Firefox button (or Tools menu) > Options > advanced

    In the mini ' General' tab, uncheck the box for "use hardware acceleration when available.

    While you are in the settings view, disable all non-essential or unrecognized modules on these two tabs:

    Firefox orange (or the Tools menu) button > addons > Plugins category

    Firefox orange (or the Tools menu) button > addons > Extensions category

    Typically, a link will appear above at least an extension disabled to restart Firefox. You can complete your work on the tab and click one of the links in the last step.

  • Can not correct 'incompatibility of cookie.

    use a web page to about 2 months of access email through google mail. Now open in Explorer. Have you tried the suggestions online to solve the incompatibility of cookie: clear memory cache but has not worked. Tried to uninstall and reinstall Moxilla but has not solved.

    Do a check with some malware malware, analysis of programs on the Windows computer.

    You need to scan with all programs, because each program detects a different malicious program.

    Make sure that you update each program to get the latest version of their databases before scanning.

    Alternatively, you can write a check for an infection rootkit TDSSKiller.

    See also:

  • Spectrum HP convertible x 360: blue spectrum HP x 360 13-4105dx MEMORY_MANAGEMENT BSOD screen and gauge battery only "calculation".

    I am Brazilian and acquired in the United States thanks to a friend, a spectrum of HP x 360 Convertible Notebooh - Win 10 - i7-6500u - 8 GB of RAM - 512 ssd

    He constantly showed an error on blue screen of death BSOD (Blue Screen Of Death) with the "MEMORY_MANAGEMENT" error

    However, other messages such as "PAGE_FAULT_IN_NONPAGED_AREA (Wdf01000.sys)" or "IRQL_NOT_LESS_OR_EQUAL" or "KERNEL_SECURITY_CHECK_FAILURE" are also presented at other times.

    Sometimes, after much searching on the forums, I've seen a lot of people complaining that the video driver was the cause of the problem.

    As I read on the forums, follow the instructions to update the BIOS to the latest version (F.35), then put to update the driver Intel(r) HD Graphics 520 to the latest version available on HP website (20.19.15.4360 from 21/12 / 2015).

    The mistakes continued. I abandon me when I noticed something new, be the subject of an investigation. After a long comment, I realized that when the laptop is powered energy he not crushed and does not give problems, he gave when the battery.

    When removing the power supply, after a short period, about 5 to 10 minutes, the mistakes began to appear, and then the question arises:

    -It would be the parameter in battery power settings that could be the cause of the error (like setting up optimization, performance, etc) or is it really problem in the battery causing the error?
    -Because the estimated Win10 battery life indicator has no estimate of consumption, keeping the status always "computation". This last fact strengthens the thesis that the problem is the battery.

    Before ask you, I used the HP Suport Assistent to the battery test and he informs that the battery is standard, which goes against my thesis which is the problem of power or the power configuration in a device driver (probably the driver Intel(r) HD Graphics 520). I did tests of memory and the SSD and quite normal.

    I decided to disable the battery driver in dispostivos Manager. Its name in dispostivos Manager is 'Control method battery Microsoft ACPI-Compatible'. To my surprise, Guess, the laptop did not, I'm still testing, but it doesn't seem that it was driver stack of conflict. The machine did not fall down, but bad disable the driver, it's that we lose track of how much time we have autonomy, but rather sacrifice the autonomy of the video driver (was palliative that he used to be able to work with the battery). Go figure... Wells is now to see if HP will solve this problem of incompatibility, because I found the potential conflict and now awaits the solution. Let's see what will give... all new review here.

    Solution to the problem on the link:

    http://h30487.www3.HP.com/T5/TELA-v%C3%ADdeo-e-GR%C3%A1ficos-para-notebooks/HP-spectre-x360-13-4105dx-TELA-Azul-BSOD-memory-management-e/m-p/634510

  • Satellite C660 - Windows 7 64 bit BSOD after upgrade RAM

    Hi guys

    my laptop Specs: Satellite C660-1JG
    -Genuine Windows® 7 Home Premium 64-bit (pre-installed, Toshiba-HDD recovery)
    -Intel® Celeron® Processor T3500
    -2048 MB of RAM DDR3 (800 MHz).

    recently I increase my RAM to 4 GB (2 + 2 GB), since its installation, as soon windows7 64 bit beginning of loading, finished with BSOD. load BSOD Windows sometimes very well, but in a minute or two appears. I can confirm that it does not read the total RAM of 4 GB, I checked while the laptop was about 2 to 3 minutes ON. then I go out 1 RAM stick laptop is fine, no BSOD!

    so question raises if the RAM is at fault, incompatibility etc, but I have the dual boot OS and other OS is Ubuntu 11. who reads the 3.84 GB RAM and without crashing or BSOD or any question.

    Then I installed Windos 7 32 bit to see if that still has problems with 4 GB of RAM, but NO, 32 bit reads RAM 4 GB (usable 2.8 GB). without crashing or BSOD with 32, only problem with windows 64-bit version!
    I checked the specification it says Max RAM 4 GB Ram and yes it supports 4 GB RAM with Linux and win7 32-bit.

    I tried to update BIOS version 1.20 (currently on 1.40), but still got error: Firmware has no support of Flash (AFUWINGUI).
    I was wondering if any of you can guide me to the right direction.
    Thanks in advance
    Concerning

    I can't say for sure, but perhaps BSOD due to a compatibility issue.
    What RAM you bought as add-on (brand and specification)?

  • BSOD everytime I try to install updates on newly installed windows 7 64-bit on the computer newly built

    just built a computer a week 7 there and installed.  my computer currently has no installed updates.  whenever I try to install updates (one of them) I get the bsod and need to restore several times, computer works fine until I turn it off.

    the screen will change resolution 1280 x 1024 at ~ 600 x 800 for about five seconds then bluescreen when it spoil.
    my initial error code: 100007e.
    0000005,4843518, 3c3c628, 3c3be80.  any help will be greatly appreciated.

    Hello

    Drivers of suspects, including video, BIOS, drivers ChipSet at low altitude, antivirus and anitspyware/safety programs
    and hardware issues including such as bad sitting cards, memory problems and wiring. Power supply
    is a real possibility. Are the updates of Windows he chokes on driver updates - if so right click on
    These and HIDE?

    When you get to the pilot and sections of the memory of the troubleshooter check the following message to
    update drivers and memory test and then return to the troubleshooter if necessary.

    1000007E and 0000007E are the same

    Cause

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug control is a very common bug control. To interpret it, you must identify which exception has been generated.

    Common exception codes are:

    • 0 x 80000002: STATUS_DATATYPE_MISALIGNMENT indicates an unaligned data reference was encountered.
    • 0 x 80000003: STATUS_BREAKPOINT indicates a breakpoint or ASSERTION was met when no kernel debugger was attached to the system.
    • 0xc0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation has occurred.

    For a complete list of exception codes, see the Ntstatus.h file located in the directory Inc. of the Microsoft Windows Driver Kit (WDK).

    Solve the problem

    If you do not have to debug this problem, you must use certain basic troubleshooting techniques.

    • Make sure you have enough disk space.
    • If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
    • Try changing video cards.
    • Check with your hardware vendor for updates to the BIOS.
    • Disable the BIOS memory options such as implementing caching or shading.

    If you plan to debug this problem, you may find it difficult to get a stack trace. Parameter 2 (the address of the exception) should identify the driver or function that caused the problem.

    If exception code 0 x 80000003 occurs, a hard-coded breakpoint or assertion was hit, but the system was launched with the /nodebug. switch. This problem should occur infrequently. If it occurs repeatedly, make sure that a kernel debugger is connected and the system is booted with the Switch/DEBUG .

    In case of exception code 0 x 80000002, the trap frame provides additional information.

    If you do not know the specific cause of the exception, consider the following questions:

    • Hardware incompatibility. Ensure that any new hardware that is installed is listed in the list of the products tested Microsoft Windows market.
    • Service driver or defective peripheral system. A chauffeur service or defective peripheral system could be responsible for this error. The hardware problems, such as BIOS incompatibilities, conflicts of memory and IRQ conflicts can also generate this error.

    If a driver is listed by name in the bug check message, disable or remove that driver. Disable or remove drivers or services that have been recently added. If the error occurs during the startup sequence and the system partition is formatted with the NTFS file system, you may be able to use Safe Mode to rename or to delete the faulty driver. If the driver is used as part of the start-up procedure of the system Safe Mode, you must start the computer by using the Recovery Console to access the file.

    If the problem is associated with Win32k.sys, the source of the error may be a third-party remote control program. If this software is installed, you can remove the service by starting the computer by using the recovery and then Console by removing the offending system service file.

    Check the system log in Event Viewer for additional error messages that might help identify the device or driver responsible for control of bug 0x7E.

    You can also disable memory cache BIOS may try to resolve the error. You must also run the diagnostics of material, especially the scanner memory, which provides the manufacturer of the system. For more information about these procedures, see the manual of your computer.

    The error that generates this message may occur after the first reboot during Windows Setup, or after installation is complete. A possible cause of the error is lack of disk space for installation and the system BIOS incompatibilities. For any problems during the installation of Windows that are associated with lack of disk space, reduce the number of files on the hard disk drive target. Search and delete temporary files that you do not have to have, files hidden Internet, application backup files and files saved .chk , which contain fragments of files on disk scans. You can also use an another hard disk drive with more free space for the installation. You can solve the problems of BIOS by upgrading the version of the system BIOS.

    =====================================================

    This solving generic problems but it should help you resolve the issue however remember them ALL
    This new material is very suspicious.

    Look in the Event Viewer to see if something is reported on those.
    http://www.computerperformance.co.UK/Vista/vista_event_viewer.htm

    MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
    TIP - Options - Advanced filter allows you to see a period of time instead of the entire file.

    http://www.NirSoft.NET/utils/my_event_viewer.html

    Here are a few ways to possibly fix the blue screen issue. If you could give the info from the blue screen that would be
    Help. Such as ITC and 4 others entered at the bottom left. And any other information such as STOP error
    codes and info like IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.

    As examples:

    BCCode: 116
    BCP1: 87BC9510
    BCP2: 8C013D80
    BCP3: 00000000
    BCP4: 00000002

    or in this format:

    Stop: 0 x 00000000 (oxoooooooo oxoooooooo oxoooooooo oxooooooooo)
    Tcpip.sys - address blocking 0 x 0 00000000 000000000 DateStamp 0 x 000000000

    It is an excellent tool for displaying the blue screen error information

    BlueScreenView scans all your minidump files created during "blue screen of death," collisions
    Displays information on all the "crash" of a table - free

    http://www.NirSoft.NET/utils/blue_screen_view.html

    BlueScreens many are caused by old or damaged drivers, video drivers in particular, but there are other causes.

    You can follow these steps in the Safe Mode if necessary or the command prompt Vista DVD or Options of recovery if your
    system installed by the manufacturer.

    This tells you how to access the System Recovery Options and/or a Vista DVD
    http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

    You can try a system restore to a point before the problem started when one exists.

    How to make a Vista system restore
    http://www.Vistax64.com/tutorials/76905-System-Restore-how.html

    -------------------------------------------------------------------------

    Start - type this in the search box-> find COMMAND at the top and RIGHT CLICK – RUN AS ADMIN

    Enter this at the command prompt - sfc/scannow

    How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program
    generates in Windows Vista cbs.log
    http://support.Microsoft.com/kb/928228

    The log can give you the answer if there is a corrupted driver. (Says not all possible driver problems).

    Also run CheckDisk, so we cannot exclude as much as possible of the corruption.
    How to run the check disk at startup in Vista

    http://www.Vistax64.com/tutorials/67612-check-disk-Chkdsk.html

    -------------------------------------------------------------------------

    Often drivers up-to-date will help, usually video, sound, network card (NIC), WiFi, 3rd party keyboard and
    smile, as well as of other major device drivers.

    Look at the sites of the manufacturer for drivers - and the manufacturer of the device manually.
    http://pcsupport.about.com/od/driverssupport/HT/driverdlmfgr.htm

    How to install a device driver in Vista Device Manager
    http://www.Vistax64.com/tutorials/193584-Device-Manager-install-driver.html

    How to disable automatic driver Installation in Windows Vista - drivers
    http://www.AddictiveTips.com/Windows-Tips/how-to-disable-automatic-driver-installation-in-Windows-Vista/
    http://TechNet.Microsoft.com/en-us/library/cc730606 (WS.10) .aspx

    -------------------------------------------------------------------------

    How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart unexpectedly
    http://support.Microsoft.com/kb/958233

    Troubleshooting, STOP error blue screen Vista
    http://www.chicagotech.NET/Vista/vistabluescreen.htm

    Understanding and decoding BSOD (blue screen of death) Messages
    http://www.Taranfx.com/blog/?p=692

    Windows - troubleshooting blue screen errors
    http://KB.wisc.edu/page.php?id=7033

    -------------------------------------------------------------------------

    In some cases, it may be necessary.

    The Options or Vista recovery disk Startup Repair

    How to do a startup repair
    http://www.Vistax64.com/tutorials/91467-startup-repair.html

    This tells you how to access the System Recovery Options and/or a Vista DVD
    http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

    I hope this helps.

    Rob - bicycle - Mark Twain said it is good.

  • X201i: BSOD on shutdown

    Suddenly, I get a BSOD that the computer shuts down. It seems to be just before the power is cut, i.e. After Windows' disconnect and stop messages. Event Viewer, I had error messages pasted below. As you can see, the messages aren't exactly the same thing about these two samples (I get the BSOD * every * time, however), but the common denominator is the driver of smihlp2 - and I understand that this has something to do with the fingerprint reader.

    I'm on a 324CTO X201i with Win7 Home Premium, 64-bit. Please do help - suggestions is greatly appreciated.

    22/03/2012 08:07:40: service the SMI Helper Driver (smihlp2) could not start due to the following error: the system cannot find the specified file.

    22/03/2012 08:07:45: the computer was restarted after a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80002e9dbac, 0xfffff8800414b728, 0xfffff8800414af80). A dump was saved in the: C:\Windows\MEMORY. DMP. Report ID: 032212-22105-01.

    22/03/2012 08:08:16: Microsoft anti-malware real-time Protection feature has encountered an error and has failed.
    Feature: Behavior management
    Error code: 0x80004005
    Error description: unspecified error
    Reason: The filter driver requires an engine update in order to work. You must install the latest definition updates in order to activate the protection in real time.

    and

    22/03/2012 13:35:40: service the SMI Helper Driver (smihlp2) could not start due to the following error: the system cannot find the specified file.

    22/03/2012 13:35:46: the computer was restarted after a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80002ea2be3, 0xfffff8800414b728, 0xfffff8800414af80). A dump was saved in the: C:\Windows\MEMORY. DMP. Report ID: 032212-23384-01.

    Note from Moderator: Edition subject to the content of the game.

    I managed to finish with the problem, but I don't know exactly why. I repaired the installation of the software to print digital and empty the Windows Search Index, and then I don't have the BSOD stop anymore.

  • BSOD no error checking for does not aspire VN7 - 792G

    Hello world

    I got my aspire VN7 - 792G (v17 nitro Black edition) since November 2015 and since last week, I was doing some odd BSOD bugcheck (0x000001d3) without errors. Using BlueScreenView I noticed that the error came from QCAMainx64.

    This happened last week and so I did a system restore and then updated my drivers wireless at 11.0.0.471. I've also updated my Nvidia drivers to the latest version in the case who had problems.

    I did a sfc scannow which gave rise to no error, I did a check of windows memory which gave rise to no problem and a disk check which resulted without any problem.

    The strangest thing was that the BSOD is produced especially when my laptop was being called in the upper left corner. But after a week of no BSOD they now returned at random moments.

    The first BSOD happened on cdrom.sys and netio.sys (also 0x000001d3) and then 2 other BSOD's happened (one while doing a system restore point) and the other so I just browsing youtube, which happened on the QCAMainx64 again.

    I left the Netherlands in Dubai and I left my receipt to the Netherlands, so I only have a scan of my warranty paper and ordering the product emails to prove that the laptop is mine. I was not able to repair yet because I need my laptop for work as well.

    I'll add my minidump files to this post. If anyone knows anything I might have missed or which is better I can do to avoid BSOD.

    I am running Windows 8.1. It seems that, on the acer site, that I can not download more updates to driver for windows 8.1 because they offer only win 10. And I'd rather not updated for windows 10 in all.

    Thank you for your time.

    http://www.filedropper.com/desktop_27

    Try to update the driver with this version:

    http://www.station-drivers.com/index.php?option=com_remository&Itemid=353&func=FileInfo&ID=2011&lang...

    Click Download, double-click the auto unpacking package and look for a configuration or install the file.

    Web site is 100% reliable.

    have an update on nvidia drivers too:

    http://www.GeForce.com/drivers/results/99508

Maybe you are looking for