New
#1
ACP_INDEX_MISMATCH and other BSOD's
I have a lot of problem with Random BSOD's
It's a pretty new installation. Also new hardware.
I have been running mentest86+ and no problem there.
Someone that can help me?
I have a lot of problem with Random BSOD's
It's a pretty new installation. Also new hardware.
I have been running mentest86+ and no problem there.
Someone that can help me?
Try enabling driver verifier: Driver Verifier - Enable and Disable
MagicDisc has my attention, but we'll see.
...Summary of the Dumps:Code:Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Tue Sep 14 17:11:15.628 2010 (UTC - 4:00) System Uptime: 0 days 2:35:18.454 BugCheck 1, {7747bb2a, 0, 1, fffff8800651bca0} Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 ) BUGCHECK_STR: 0x1 PROCESS_NAME: explorer.exe จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Mon Sep 13 04:06:17.396 2010 (UTC - 4:00) System Uptime: 0 days 0:07:14.222 BugCheck 3B, {c0000005, fffff80002cae1e6, fffff880095adf30, 0} Probably caused by : ntkrnlmp.exe ( nt!ExfReleasePushLock+4bb ) BUGCHECK_STR: 0x3B PROCESS_NAME: WmiPrvSE.exe จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Mon Sep 13 03:58:05.660 2010 (UTC - 4:00) System Uptime: 0 days 0:04:17.486 BugCheck 50, {fffff88005d85224, 0, fffff96000671686, 0} Probably caused by : cdd.dll ( cdd!CopyMemoryCallback+12 ) BUGCHECK_STR: 0x50 PROCESS_NAME: explorer.exe จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Mon Sep 13 03:42:04.021 2010 (UTC - 4:00) System Uptime: 0 days 3:44:22.474 BugCheck 1E, {ffffffffc0000005, 1, 8, 1} Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 ) BUGCHECK_STR: 0x1E_c0000005 PROCESS_NAME: SkypeNames2.ex จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ
I enabled the driver verifier and got a bluescreens when trying to boot
(IRQ IS LES OR EQUAL)
Hello and Welcome !
Then dump is pointing to Code Integrity (CI) protects Windows by verifying that system binaries haven’t been tampered with by malicious code and by ensuring that there are no unsigned drivers running in kernel mode on the system. So i would recommend Download Malwarebytes and run a complete scan under Safe mode.
Run SFC /SCANNOW Command - System File Checker and see if that fixes the problem.
Run a Hardware Diagnostic (Memory and Hard Drive) follow this link for instructions Hardware Diagnostic !! ซ Captain Debugger
Bugcheck:
Hope this helps,Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {e, 2, 1, fffff80002cdb44b} Probably caused by : CI.dll ( CI!SHATransform+236 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 000000000000000e, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80002cdb44b, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef30e0 000000000000000e CURRENT_IRQL: 2 FAULTING_IP: nt!IopCompleteRequest+c88 fffff800`02cdb44b 48894108 mov qword ptr [rcx+8],rax CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: System IRP_ADDRESS: ffffffffffffff8e TRAP_FRAME: fffff880031c32c0 -- (.trap 0xfffff880031c32c0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000003eea04c rbx=0000000000000000 rcx=00000000d804900d rdx=000000002a2eee3f rsi=0000000000000000 rdi=0000000000000000 rip=fffff88000c56cd6 rsp=fffff880031c3450 rbp=0000000075d8488b r8=00000000d47a7fb0 r9=00000000d8adfe6d r10=00000000c81b20bb r11=00000000ea5c8a85 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc CI!SHATransform+0x236: fffff880`00c56cd6 8b7334 mov esi,dword ptr [rbx+34h] ds:00000000`00000034=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002cbaca9 to fffff80002cbb740 STACK_TEXT: fffff880`031c2d08 fffff800`02cbaca9 : 00000000`0000000a 00000000`0000000e 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`031c2d10 fffff800`02cb9920 : 00000000`00000000 fffff980`039dcee0 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`031c2e50 fffff800`02cdb44b : fffff780`c0000000 00000000`00000001 00000000`00040400 fffffa80`07ce3600 : nt!KiPageFault+0x260 fffff880`031c2fe0 fffff800`02c980c7 : 00000000`00000006 fffffa80`04604040 fffff880`031c3100 fffff800`00000000 : nt!IopCompleteRequest+0xc88 fffff880`031c30b0 fffff800`02c6ebb5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7 fffff880`031c3130 fffff800`02cd6c44 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffffa80`0342c8a0 : nt!KiCheckForKernelApcDelivery+0x25 fffff880`031c3160 fffff800`02cb982e : 00000000`00000000 fffff980`04240fcc 00000980`00000000 0000007f`fffffff8 : nt!MmAccessFault+0x1844 fffff880`031c32c0 fffff880`00c56cd6 : 008a88d3`a802742b c0360000`3fdceb29 33ed488b`83380500 4f8d3e14`1a0f6420 : nt!KiPageFault+0x16e fffff880`031c3450 fffff880`00c57d0c : fffff880`031c3648 fffffa80`2e08ab8b fffff980`c9e0f532 fffff800`123caa46 : CI!SHATransform+0x236 fffff880`031c34e0 fffff880`00c14824 : fffff8a0`06a1f5c0 fffff980`042000d8 00000000`00000000 00000000`00000000 : CI!A_SHAUpdate+0xcc fffff880`031c3520 fffff880`00c0cb38 : fffff980`04200180 00000000`00000000 00000000`00000400 00000007`00001000 : CI!HashpHashBytes+0x40 fffff880`031c3550 fffff880`00c0c281 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : CI!CipImageGetImageHash+0x310 fffff880`031c3730 fffff880`00c0afbb : 00000000`00000001 fffff880`031c39f0 fffff880`031c39f0 00000000`00000000 : CI!CipValidateFileHash+0x211 fffff880`031c38a0 fffff800`02f2668e : 00000000`00000056 00000000`000fffff fffffa80`07ce3600 00000000`00000000 : CI!CiValidateImageHeader+0x213 fffff880`031c3980 fffff800`02f2657c : 00000000`00000001 00000000`01000000 fffffa80`07ce54a0 00000000`00000000 : nt!SeValidateImageHeader+0x2e fffff880`031c39c0 fffff800`02fb6d95 : fffffa80`07ce3600 fffffa80`07ce54a0 00000000`00000001 00000000`00000056 : nt!MiValidateImageHeader+0xa4 fffff880`031c3a80 fffff800`02fac013 : fffff880`031c3ce0 00000000`00000000 fffff880`031c3f98 00000000`00000001 : nt!MmCreateSection+0x8c9 fffff880`031c3c90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtCreateSection+0x162 STACK_COMMAND: kb FOLLOWUP_IP: CI!SHATransform+236 fffff880`00c56cd6 8b7334 mov esi,dword ptr [rbx+34h] SYMBOL_STACK_INDEX: 8 SYMBOL_NAME: CI!SHATransform+236 FOLLOWUP_NAME: MachineOwner MODULE_NAME: CI IMAGE_NAME: CI.dll DEBUG_FLR_IMAGE_TIMESTAMP: 4a5be01d FAILURE_BUCKET_ID: X64_0xA_VRF_CI!SHATransform+236 BUCKET_ID: X64_0xA_VRF_CI!SHATransform+236 Followup: MachineOwner --------- 2: kd> lmvm CI start end module name fffff880`00c00000 fffff880`00cc0000 CI (pdb symbols) c:\symbols\ci.pdb\5F1BDC2205AC402CB0F09FC7CF17A3701\ci.pdb Loaded symbol image file: CI.dll Mapped memory image file: C:\Symbols\CI.dll\4A5BE01Dc0000\CI.dll Image path: \SystemRoot\system32\CI.dll Image name: CI.dll Timestamp: Tue Jul 14 07:02:13 2009 (4A5BE01D) CheckSum: 000C6E0E ImageSize: 000C0000 File version: 6.1.7600.16385 Product version: 6.1.7600.16385 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 3.7 Driver File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Microsoft Corporation ProductName: Microsoftฎ Windowsฎ Operating System InternalName: ci.dll OriginalFilename: ci.dll ProductVersion: 6.1.7600.16385 FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255) FileDescription: Code Integrity Module LegalCopyright: ฉ Microsoft Corporation. All rights reserved.
Captain
I suggest a repair install, to start out.
Do you have another graphics card you can try? Perhaps borrow one from a friend, or take one from another computer.
...Summary of the Dumps:Code:Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Wed Sep 15 13:14:55.160 2010 (GMT-4) System Uptime: 0 days 0:00:18.002 BugCheck A, {e, 2, 1, fffff80002cdb44b} Probably caused by : CI.dll ( CI!SHATransform+236 ) DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: System จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ
I have one more identical graphic card to try or I can remove the one I have and run with the built in
If I run a SFC /SCANNOW it says:
Windows Resource Protection did not find any integrity violations.
I have been running memtest86+ for 4 hours without any errors. And both tried
Seagate and WD's diagnostic programs for harddrives without any reports of problems.
I will try the maleware scanner and try to remove the graphic card. However, i had bluescreens that I thought was solved in earlier thread here by removing Acronis True Image a couple
of weeks agao running without this graphic card
YES!
When I removed the nvidia card and rebooted and then enabled the driver verifiera I could boot without a blue screen. Hope it's not to early to be hapy.
Now the question is if I dare to buy a new nvidia card and run togeter with ati onboard graphic card or if I should buy a ATI card instead.
Take a look around the web, even on this forum! You will see fanboys for both ATI and nVidia, pointing out failures in the other party's cards.
Honestly, I don't see a difference. Buy whatever card fits your needs, but take my word that both ATI and nVidia cards fail with approximately the same frequencies.
Since you have one on hand, I recommend trying the other nVidia card you have. Perhaps your old nVidia card is just faulty.
I will do so. The other card is identical. Was running SLI on another machine that crashed compleatly
one month ago. (Motherboard and cpu was broken atleast. I guess that could have destroyed the graphic card to)
I'm not a gaming fan so I don't need that good graphic card. I was just thinking that since I have ati onboard it might don't like that I put a nvidia in.