2008 R2 BSOD Error 1001 Bug Check PCIIDEX.SYS
I am getting intermittent Blue Screens attached is my Dump file. Says Might be a vista driver just wondering where to start. Probably caused by : PCIIDEX.SYS ( PCIIDEX+10d3 ) Followup: MachineOwner --------- ******************************************************************************* * * * 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: fffff8800e79b978, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, 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: fffff80001ad0d40, address which referenced memory Debugging Details: ------------------ ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. MODULE_NAME: PCIIDEX FAULTING_MODULE: fffff80001a4f000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc114 READ_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd fffff8800e79b978 CURRENT_IRQL: 0 FAULTING_IP: nt!RtlCopyMemoryNonTemporal+40 fffff800`01ad0d40 4c8b0c11 mov r9,qword ptr [rcx+rdx] DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA LAST_CONTROL_TRANSFER: from fffff80001ace2a9 to fffff80001aced00 STACK_TEXT: fffff880`01e85328 fffff800`01ace2a9 : 00000000`0000000a fffff880`0e79b978 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`01e85330 fffff800`01accf20 : 00000000`00000022 00000000`00000008 fffffa80`0d89f2e0 fffff880`0e79b978 : nt!KeSynchronizeExecution+0x3d59 fffff880`01e85470 fffff800`01ad0d40 : fffff800`01a08e08 fffff880`0e79a978 00000000`00000002 fffffa80`10df3960 : nt!KeSynchronizeExecution+0x29d0 fffff880`01e85608 fffff800`01a08e08 : fffff880`0e79a978 00000000`00000002 fffffa80`10df3960 fffff880`01e5d180 : nt!RtlCopyMemoryNonTemporal+0x40 fffff880`01e85610 fffff800`01a08593 : fffffa80`0d66b660 fffffa80`0d66b600 00000000`00000000 00000000`00000000 : hal!HalMakeBeep+0x1b40 fffff880`01e856c0 fffff800`01a0b4fb : fffffa80`10d76270 fffffa80`0d66b660 fffffa80`10df3960 00000000`00000001 : hal!HalMakeBeep+0x12cb fffff880`01e85710 fffff800`01a0b472 : fffffa80`10d76270 fffffa80`10d76268 00000000`00001000 00000000`00000000 : hal!IoMapTransfer+0x117 fffff880`01e857a0 fffff800`01a0a94f : 00000000`00000000 fffff800`01a07fb9 00000000`00000000 00000000`00000002 : hal!IoMapTransfer+0x8e fffff880`01e857e0 fffff800`01a0b13d : fffffa80`0d664d40 fffffa80`0d66b660 fffffa80`0d685801 fffffa80`00000000 : hal!HalFreeCommonBuffer+0x67b fffff880`01e85880 fffff800`01a0a71f : fffffa80`10d76210 00000000`00002000 fffffa80`0d66b660 fffffa80`10df3960 : hal!HalAllocateAdapterChannel+0x101 fffff880`01e858c0 fffff880`0132c0d3 : fffffa80`10d76170 fffff880`0132c12c fffffa80`000000a0 fffffa80`0d66b660 : hal!HalFreeCommonBuffer+0x44b fffff880`01e85930 fffff880`013b9b53 : fffffa80`10d76170 fffffa80`0d6821b0 fffffa80`0d3061a0 fffffa80`10d76170 : PCIIDEX+0x10d3 fffff880`01e85990 fffff880`013b8803 : fffffa80`0d307500 fffffa80`0d6821b0 fffffa80`0d307500 fffffa80`0d3061a0 : ataport!AtaPortInitialize+0x47df fffff880`01e859c0 fffff880`013b8336 : 00000000`00000001 fffffa80`10d76170 00000000`00000001 fffffa80`10d76170 : ataport!AtaPortInitialize+0x348f fffff880`01e85a40 fffff880`013ba59a : fffffa80`0d601601 00000000`00000000 fffffa80`0d6821b0 fffffa80`10eb93f0 : ataport!AtaPortInitialize+0x2fc2 fffff880`01e85ae0 fffff880`013ba104 : fffffa80`0d3061a0 00000000`00000000 fffffa80`0d3061a0 fffffa80`10eb93f0 : ataport!AtaPortInitialize+0x5226 fffff880`01e85c10 fffff800`01ada10c : fffff880`01e5d180 00000017`fecbe1a7 fffffa80`0d306050 fffffa80`0d306118 : ataport!AtaPortInitialize+0x4d90 fffff880`01e85cd0 fffff800`01ac6a2a : fffff880`01e5d180 fffff880`01e680c0 00000000`00000000 fffff880`013b9f5c : nt!KeReleaseMutant+0x5dc fffff880`01e85d80 00000000`00000000 : fffff880`01e86000 fffff880`01e80000 fffff880`01e85d40 00000000`00000000 : nt!KiCpuId+0x79a STACK_COMMAND: kb FOLLOWUP_IP: PCIIDEX+10d3 fffff880`0132c0d3 85c0 test eax,eax SYMBOL_STACK_INDEX: b SYMBOL_NAME: PCIIDEX+10d3 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: PCIIDEX.SYS BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner ---------
May 17th, 2011 2:21pm

Bug Check Code 0xA: http://msdn.microsoft.com/en-us/library/ff560129(VS.85).aspx The BSOD was caused by PCIIDEX.SYS. Try this Microsoft update and check if it solves your proble;: http://support.microsoft.com/kb/943170 This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Free Windows Admin Tool Kit Click here and download it now
May 17th, 2011 5:47pm

Hi, You may install the latest version of PCIIDEX.SYS by the hotfix mentioned from the following Microsoft KB article: Data corruption occurs when you write data to a partition on a disk through an IDE port or a SATA port that uses IDE emulation on a Windows Server 2008 R2-based or a Windows 7-based computer http://support.microsoft.com/kb/2288487 If the issue persists, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607 Regards,Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
May 18th, 2011 2:16am

Hi, I am having the same problem you mentioned, on a Dell Precision 490, windows server 2008 R2 with 2 x 1.5 TB hard-disks, stuck in the same pciidex.sys... Can you please let us know if any of the two proposed solutions worked for you? Thank you. Regards, BugCheck A, {fffff88007949000, 2, 0, fffff80001a99d40} Page 20f539 not present in the dump file. Type ".hh dbgerr004" for details Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmSetup+6b ) Followup: MachineOwner --------- 1: 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: fffff88007949000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, 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: fffff80001a99d40, address which referenced memory Debugging Details: ------------------ Page 20f539 not present in the dump file. Type ".hh dbgerr004" for details READ_ADDRESS: fffff88007949000 CURRENT_IRQL: 2 FAULTING_IP: nt!RtlCopyMemoryNonTemporal+40 fffff800`01a99d40 4c8b0c11 mov r9,qword ptr [rcx+rdx] DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: sqlservr.exe TRAP_FRAME: fffff8800201b6a0 -- (.trap 0xfffff8800201b6a0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000001000 rbx=0000000000000000 rcx=fffff88002d98000 rdx=0000000004bb1000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80001a99d40 rsp=fffff8800201b838 rbp=0000000000000002 r8=0000000000000000 r9=0000000000000000 r10=fffffa8006c65580 r11=fffff8800201b820 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!RtlCopyMemoryNonTemporal+0x40: fffff800`01a99d40 4c8b0c11 mov r9,qword ptr [rcx+rdx] ds:9d90:9000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80001a972a9 to fffff80001a97d00 STACK_TEXT: fffff880`0201b558 fffff800`01a972a9 : 00000000`0000000a fffff880`07949000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`0201b560 fffff800`01a95f20 : 00000000`00000000 fffff880`01affdea fffffa80`00000000 fffff880`07949000 : nt!KiBugCheckDispatch+0x69 fffff880`0201b6a0 fffff800`01a99d40 : fffff800`02003e08 fffff880`07949000 00000000`00000002 fffffa80`081c3c70 : nt!KiPageFault+0x260 fffff880`0201b838 fffff800`02003e08 : fffff880`07949000 00000000`00000002 fffffa80`081c3c70 fffffa80`08e98a40 : nt!RtlCopyMemoryNonTemporal+0x40 fffff880`0201b840 fffff800`02003593 : fffffa80`06c65580 fffffa80`06c65500 00000000`00000000 00000000`00000000 : hal!HalpDmaSyncMapBuffers+0x1b0 fffff880`0201b8f0 fffff800`020064fb : fffffa80`0da3f628 fffffa80`06c65580 fffffa80`081c3c70 00000000`00000001 : hal!HalpDmaMapScatterTransfer+0xa3 fffff880`0201b940 fffff800`02006472 : fffffa80`0da3f628 fffffa80`0da3f620 00000000`00010000 00000000`00000000 : hal!HalpMapTransfer+0x7b fffff880`0201b9d0 fffff800`0200594f : 00000000`00000000 fffff800`02002fb9 00000000`00000000 00000000`00000010 : hal!IoMapTransfer+0x8e fffff880`0201ba10 fffff800`0200613d : fffffa80`06c45060 fffffa80`06c65580 fffffa80`00000001 00000000`00000000 : hal!HalpAllocateAdapterCallback+0xc7 fffff880`0201bab0 fffff800`0200571f : fffffa80`0da3f5e0 00000000`00010000 fffffa80`06c65580 fffffa80`081c3c70 : hal!HalAllocateAdapterChannel+0x101 fffff880`0201baf0 fffff880`012650d3 : fffffa80`0da3f540 fffff880`0126512c fffffa80`000001c0 fffffa80`06c65580 : hal!HalBuildScatterGatherList+0x2f3 fffff880`0201bb60 fffff880`012f9b53 : fffffa80`0da3f540 fffffa80`06c5f7d0 fffffa80`06c531a0 fffffa80`0da3f540 : PCIIDEX!BmSetup+0x6b fffff880`0201bbc0 fffff880`012f8803 : fffffa80`06c54500 fffffa80`06c5f7d0 fffffa80`06c54500 fffffa80`06c531a0 : ataport!IdeDispatchChannelRequest+0xef fffff880`0201bbf0 fffff880`012f8336 : 00000000`00000001 fffffa80`0da3f540 00000000`00000001 fffffa80`0da3f540 : ataport!IdeStartChannelRequest+0x113 fffff880`0201bc70 fffff880`012fa59a : fffffa80`06c591a0 00000000`00000000 fffffa80`06c5f7d0 fffffa80`0d7eab80 : ataport!IdeStartNextDeviceRequest+0x18e fffff880`0201bd10 fffff880`012fa104 : fffffa80`06c531a0 00000000`00000000 fffffa80`06c531a0 fffffa80`0d7eab80 : ataport!IdeProcessCompletedRequests+0x26a fffff880`0201be40 fffff800`01aa310c : fffff880`009bf180 fffff880`01aff65c fffffa80`06c53050 fffffa80`06c53118 : ataport!IdePortCompletionDpc+0x1a8 fffff880`0201bf00 fffff800`01a9a765 : 948d48c9`33452024 fffffa80`074c5b60 00000000`00000000 fffff880`012f9f5c : nt!KiRetireDpcList+0x1bc fffff880`0201bfb0 fffff800`01a9a57c : fffff880`0625bca0 fffffa80`069c9b40 00000000`00000001 ffffffff`ffffd8f0 : nt!KyRetireDpcList+0x5 fffff880`0625bbe0 fffff800`01ae3a13 : fffff800`01a93723 fffff800`01a9378f fffffa80`074c5b60 00000000`00000001 : nt!KiDispatchInterruptContinue fffff880`0625bc10 fffff800`01a9378f : fffffa80`074c5b60 00000000`00000001 fffff880`0625bbf8 fffffa80`0824e2d0 : nt!KiDpcInterruptBypass+0x13 fffff880`0625bc20 00000000`0109df13 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiChainedDispatch+0x19f 00000000`1647b960 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x109df13 STACK_COMMAND: kb FOLLOWUP_IP: PCIIDEX!BmSetup+6b fffff880`012650d3 85c0 test eax,eax SYMBOL_STACK_INDEX: b SYMBOL_NAME: PCIIDEX!BmSetup+6b FOLLOWUP_NAME: MachineOwner MODULE_NAME: PCIIDEX IMAGE_NAME: PCIIDEX.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc114 FAILURE_BUCKET_ID: X64_0xA_PCIIDEX!BmSetup+6b BUCKET_ID: X64_0xA_PCIIDEX!BmSetup+6b Followup: MachineOwner ---------
Free Windows Admin Tool Kit Click here and download it now
May 26th, 2011 9:00am

I am also having this problem on a Windows Server 2008 R2. I tried following KB 2288487 but the responce was that the update was not needed. I then reviewed the individual files and they are all already the ones listed. Attached is my debug file. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\windows\minidump\060211-334765-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available 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 x64 Product: Server, suite: TerminalServer SingleUserTS Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Machine Name: Kernel base = 0xfffff800`01861000 PsLoadedModuleList = 0xfffff800`01aa6650 Debug session time: Thu Jun 2 16:51:51.620 2011 (UTC - 7:00) System Uptime: 9 days 9:01:24.001 Loading Kernel Symbols ............................................................... ................................................................ ............. Loading User Symbols Loading unloaded module list ............... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffff88001fb6000, 2, 0, fffff800018e2d40} Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmSetup+6b ) 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: fffff88001fb6000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, 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: fffff800018e2d40, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001b10100 fffff88001fb6000 CURRENT_IRQL: 2 FAULTING_IP: nt!RtlCopyMemoryNonTemporal+40 fffff800`018e2d40 4c8b0c11 mov r9,qword ptr [rcx+rdx] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff88001e8c6a0 -- (.trap 0xfffff88001e8c6a0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000900 rbx=0000000000000000 rcx=fffff88002c92000 rdx=ffffffffff324000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800018e2d40 rsp=fffff88001e8c838 rbp=0000000000000002 r8=0000000000000038 r9=0000000000000000 r10=0000000000000000 r11=fffff88001e8c820 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!RtlCopyMemoryNonTemporal+0x40: fffff800`018e2d40 4c8b0c11 mov r9,qword ptr [rcx+rdx] ds:ea60:fffff880`01fb6000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800018e02a9 to fffff800018e0d00 STACK_TEXT: fffff880`01e8c558 fffff800`018e02a9 : 00000000`0000000a fffff880`01fb6000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`01e8c560 fffff800`018def20 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`01fb6000 : nt!KiBugCheckDispatch+0x69 fffff880`01e8c6a0 fffff800`018e2d40 : fffff800`0181ae08 fffff880`01fb5938 00000000`00000002 fffffa80`099a4160 : nt!KiPageFault+0x260 fffff880`01e8c838 fffff800`0181ae08 : fffff880`01fb5938 00000000`00000002 fffffa80`099a4160 fffffa80`091c5bf0 : nt!RtlCopyMemoryNonTemporal+0x40 fffff880`01e8c840 fffff800`0181a593 : fffffa80`06f97ea0 fffffa80`06f97e00 00000000`00000000 00000000`00000000 : hal!HalpDmaSyncMapBuffers+0x1b0 fffff880`01e8c8f0 fffff800`0181d4fb : fffffa80`0b220c68 fffffa80`06f97ea0 fffffa80`099a4160 00000000`00000001 : hal!HalpDmaMapScatterTransfer+0xa3 fffff880`01e8c940 fffff800`0181d472 : fffffa80`0b220c68 fffffa80`0b220c60 00000000`00001000 00000000`00000000 : hal!HalpMapTransfer+0x7b fffff880`01e8c9d0 fffff800`0181c94f : 00000000`00000000 fffff800`01819fb9 00000000`00000000 00000000`00000001 : hal!IoMapTransfer+0x8e fffff880`01e8ca10 fffff800`0181d13d : fffffa80`06f6a060 fffffa80`06f97ea0 fffffa80`06f7ce01 00000000`00000000 : hal!HalpAllocateAdapterCallback+0xc7 fffff880`01e8cab0 fffff800`0181c71f : fffffa80`0b220c20 00000000`00001000 fffffa80`06f97ea0 fffffa80`099a4160 : hal!HalAllocateAdapterChannel+0x101 fffff880`01e8caf0 fffff880`00fed0d3 : fffffa80`0b220b80 fffff880`00fed12c fffffa80`000000a0 fffffa80`06f97ea0 : hal!HalBuildScatterGatherList+0x2f3 fffff880`01e8cb60 fffff880`00c2eb53 : fffffa80`0b220b80 fffffa80`06f9a1b0 fffffa80`06f711a0 fffffa80`0b220b80 : PCIIDEX!BmSetup+0x6b fffff880`01e8cbc0 fffff880`00c2d803 : fffffa80`06f72500 fffffa80`06f9a1b0 fffffa80`06f72500 fffffa80`06f711a0 : ataport!IdeDispatchChannelRequest+0xef fffff880`01e8cbf0 fffff880`00c2d336 : 00000000`00000001 fffffa80`0b220b80 00000000`00000001 fffffa80`0b220b80 : ataport!IdeStartChannelRequest+0x113 fffff880`01e8cc70 fffff880`00c2f59a : fffffa80`06f6d1a0 00000000`00000000 fffffa80`06f9a1b0 fffffa80`0b2ca010 : ataport!IdeStartNextDeviceRequest+0x18e fffff880`01e8cd10 fffff880`00c2f104 : fffffa80`06f711a0 00000000`00000000 fffffa80`06f711a0 fffffa80`0b2ca010 : ataport!IdeProcessCompletedRequests+0x26a fffff880`01e8ce40 fffff800`018ec10c : fffff880`01e5d180 fffff880`03171900 fffffa80`06f71050 fffffa80`06f71118 : ataport!IdePortCompletionDpc+0x1a8 fffff880`01e8cf00 fffff800`018e3765 : c5e8c843`8949000f fffffa80`06d1ab60 00000000`00000000 fffff880`00c2ef5c : nt!KiRetireDpcList+0x1bc fffff880`01e8cfb0 fffff800`018e357c : 00000000`00000000 fffff880`00c1b6e4 fffffa80`0b2ca440 fffffa80`074a8060 : nt!KyRetireDpcList+0x5 fffff880`01fae910 fffff800`0192ca13 : fffff800`018dcb76 fffff800`018dcbe2 fffff8a0`0b294150 fffff8a0`0b294101 : nt!KiDispatchInterruptContinue fffff880`01fae940 fffff800`018dcbe2 : fffff8a0`0b294150 fffff8a0`0b294101 fffff880`01fae9d0 fffffa80`06cc9c00 : nt!KiDpcInterruptBypass+0x13 fffff880`01fae950 fffff880`014d59f5 : fffff800`01b13a40 fffffa80`07f11950 fffffa80`07f11900 fffff880`01e5d180 : nt!KiInterruptDispatch+0x212 fffff880`01faeae0 fffff800`01925e1c : fffffa80`0b1eb530 00000000`00000000 fffffa80`076749e0 fffffa80`07f11900 : Ntfs!NtfsAcquireScbForLazyWrite+0x25 fffff880`01faeb10 fffff800`01926968 : fffff800`01adf8a0 fffff880`01faec18 fffffa80`076749e0 fffff800`01adf898 : nt!CcWriteBehind+0x3c fffff880`01faebc0 fffff800`018eb021 : fffffa80`06d29500 fffff800`01bd7000 fffff800`01adf8a0 00000000`00000005 : nt!CcWorkerThread+0x1c8 fffff880`01faec70 fffff800`01b7d32e : 00000000`00000000 fffffa80`06d1ab60 00000000`00000080 fffffa80`06d0e450 : nt!ExpWorkerThread+0x111 fffff880`01faed00 fffff800`018d2666 : fffff880`01e5d180 fffffa80`06d1ab60 fffff880`01e67fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`01faed40 00000000`00000000 : fffff880`01faf000 fffff880`01fa9000 fffff880`01fae570 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: PCIIDEX!BmSetup+6b fffff880`00fed0d3 85c0 test eax,eax SYMBOL_STACK_INDEX: b SYMBOL_NAME: PCIIDEX!BmSetup+6b FOLLOWUP_NAME: MachineOwner MODULE_NAME: PCIIDEX IMAGE_NAME: PCIIDEX.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc114 FAILURE_BUCKET_ID: X64_0xA_PCIIDEX!BmSetup+6b BUCKET_ID: X64_0xA_PCIIDEX!BmSetup+6b Followup: MachineOwner --------- jst3751
June 5th, 2011 3:08am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics