We are experiencing random reboots on our Windows Server 2008 Std. 64bitwith SQL Server 2005 installed. We have two identical machines and we already swapped the database to the other machine, but the same problems occur.The machines are equipped 2x quad core cpu's, 16gb ram, 2x 250GB HD in software mirror, 2x 500GB HD in software mirror.The minidump for 2 crashes are below, hopefully someone can point us to a solution.Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [c:\windows\minidump\Mini060909-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available WARNING: Inaccessible path: 'c:\windows\i386'Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbolsExecutable search path is: c:\windows\i386Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (8 procs) Free x64Product: Server, suite: TerminalServer SingleUserTSBuilt by: 6001.18226.amd64fre.vistasp1_gdr.090302-1506Machine Name:Kernel base = 0xfffff800`01846000 PsLoadedModuleList = 0xfffff800`01a0bdb0Debug session time: Tue Jun 9 11:02:45.904 2009 (GMT+2)System Uptime: 0 days 0:06:02.714Loading Kernel Symbols..........................................................................................................................Loading User SymbolsLoading unloaded module list......******************************************************************************** ** Bugcheck Analysis ** ******************************************************************************** Use !analyze -v to get detailed debugging information. BugCheck A, {fffffa6001f02000, 2, 0, fffff8000189f390} Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmSetup+6b ) Followup: MachineOwner--------- 0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ******************************************************************************** IRQL_NOT_LESS_OR_EQUAL (a)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high. This is usuallycaused by drivers using improper addresses.If a kernel debugger is available get the stack backtrace.Arguments:Arg1: fffffa6001f02000, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000000, bitfield :bit 0 : value 0 = read operation, 1 = write operationbit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)Arg4: fffff8000189f390, address which referenced memory Debugging Details:------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001a6f080fffffa6001f02000 CURRENT_IRQL: 2 FAULTING_IP: nt!RtlCopyMemoryNonTemporal+40fffff800`0189f390 4c8b0c11 mov r9,qword ptr [rcx+rdx] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: sqlservr.exe TRAP_FRAME: fffff80003e868a0 -- (.trap 0xfffff80003e868a0)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000001000 rbx=0000000000000000 rcx=fffffa6002284000rdx=ffffffffffc7e000 rsi=0000000000000000 rdi=0000000000000000rip=fffff8000189f390 rsp=fffff80003e86a38 rbp=0000000000000002r8=0000000000000000 r9=0000000000000000 r10=fffffa800cf7e990r11=fffff80003e86a20 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl nz na po ncnt!RtlCopyMemoryNonTemporal+0x40:fffff800`0189f390 4c8b0c11 mov r9,qword ptr [rcx+rdx] ds:d320:fffffa60`01f02000=????????????????Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000189a3ee to fffff8000189a650 STACK_TEXT: fffff800`03e86758 fffff800`0189a3ee : 00000000`0000000a fffffa60`01f02000 00000000`00000002 00000000`00000000 : nt!KeBugCheckExfffff800`03e86760 fffff800`018992cb : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa60`01f02000 : nt!KiBugCheckDispatch+0x6efffff800`03e868a0 fffff800`0189f390 : fffff800`01802ca9 fffffa60`01f02000 00000000`00000002 fffffa80`0e4df6b0 : nt!KiPageFault+0x20bfffff800`03e86a38 fffff800`01802ca9 : fffffa60`01f02000 00000000`00000002 fffffa80`0e4df6b0 00000000`00000002 : nt!RtlCopyMemoryNonTemporal+0x40fffff800`03e86a40 fffff800`01802423 : fffffa80`0cf7e990 fffffa80`0cf7e900 00000000`00000000 fffffa80`0e4df6b0 : hal!HalpDmaSyncMapBuffers+0x1b1fffff800`03e86af0 fffff800`01805399 : fffffa80`0ee170f8 fffffa80`0cf7e990 fffffa80`0e4df6b0 fffffa80`0f0c7dc3 : hal!HalpDmaMapScatterTransfer+0xa3fffff800`03e86b40 fffff800`01805312 : fffffa80`0ee170f8 fffffa80`0ee170f0 00000000`00001000 00000000`00000001 : hal!HalpMapTransfer+0x79fffff800`03e86bc0 fffff800`0180480f : 00000000`00000000 fffff800`01801e45 00000000`00000000 00000000`00000001 : hal!IoMapTransfer+0x8efffff800`03e86c00 fffff800`01804fdd : fffffa80`0cf53a20 fffffa80`0cf7e990 fffffa80`0cf7e901 00000000`00000000 : hal!HalpAllocateAdapterCallback+0xc7fffff800`03e86ca0 fffff800`018045df : fffffa80`0ee170b0 00000000`00001000 fffffa80`0cf7e990 fffffa80`0e4df6b0 : hal!HalAllocateAdapterChannel+0x101fffff800`03e86ce0 fffffa60`00c750d3 : fffffa80`0ee17010 fffffa60`00c7512c 00000000`000000a0 fffffa80`0d386d80 : hal!HalBuildScatterGatherList+0x2f3fffff800`03e86d50 fffffa60`00ca7566 : fffffa80`0ee17010 00000000`00000000 fffffa80`0ecaf010 fffffa80`0d52c590 : PCIIDEX!BmSetup+0x6bfffff800`03e86db0 fffffa60`00ca7d40 : 00000000`00000001 00000000`00000000 fffff800`019bda80 00000000`00000002 : ataport!IdeDispatchChannelRequest+0x106fffff800`03e86de0 fffffa60`00ca79dd : fffffa80`0cf851a0 00000000`00000000 fffff800`019bda80 00000000`00000001 : ataport!IdeProcessCompletedRequests+0x1e4fffff800`03e86e90 fffff800`018a3cd7 : fffffa80`0cf85118 fffffa60`04509ca0 fffffa60`04509ca0 fffff800`019bda80 : ataport!IdePortCompletionDpc+0x15dfffff800`03e86f40 fffff800`0189db25 : fffffa60`00ca7880 fffff800`019ba680 fffffa60`04509ca0 fffffa80`0cf1fb40 : nt!KiRetireDpcList+0x117fffff800`03e86fb0 fffff800`0189d937 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5fffffa60`04509be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue STACK_COMMAND: kb FOLLOWUP_IP: PCIIDEX!BmSetup+6bfffffa60`00c750d3 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: 479198a5 FAILURE_BUCKET_ID: X64_0xA_PCIIDEX!BmSetup+6b BUCKET_ID: X64_0xA_PCIIDEX!BmSetup+6b Followup: MachineOwner--------- **********************************Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [c:\windows\minidump\Mini060909-02.dmp]Mini Kernel Dump File: Only registers and stack trace are available WARNING: Inaccessible path: 'c:\windows\i386'Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbolsExecutable search path is: c:\windows\i386Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (8 procs) Free x64Product: Server, suite: TerminalServer SingleUserTSBuilt by: 6001.18226.amd64fre.vistasp1_gdr.090302-1506Machine Name:Kernel base = 0xfffff800`0181a000 PsLoadedModuleList = 0xfffff800`019dfdb0Debug session time: Tue Jun 9 11:23:43.333 2009 (GMT+2)System Uptime: 0 days 0:18:56.208Loading Kernel Symbols..........................................................................................................................Loading User SymbolsLoading unloaded module list......******************************************************************************** ** Bugcheck Analysis ** ******************************************************************************** Use !analyze -v to get detailed debugging information. BugCheck A, {fffffa6004f4f000, 2, 0, fffff80001873390} Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmSetup+6b ) Followup: MachineOwner--------- 3: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ******************************************************************************** IRQL_NOT_LESS_OR_EQUAL (a)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high. This is usuallycaused by drivers using improper addresses.If a kernel debugger is available get the stack backtrace.Arguments:Arg1: fffffa6004f4f000, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000000, bitfield :bit 0 : value 0 = read operation, 1 = write operationbit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)Arg4: fffff80001873390, address which referenced memory Debugging Details:------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001a43080fffffa6004f4f000 CURRENT_IRQL: 2 FAULTING_IP: nt!RtlCopyMemoryNonTemporal+40fffff800`01873390 4c8b0c11 mov r9,qword ptr [rcx+rdx] CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffffa60017ff620 -- (.trap 0xfffffa60017ff620)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000001000 rbx=0000000000000000 rcx=fffffa6002b35000rdx=000000000241a000 rsi=0000000000000000 rdi=0000000000000000rip=fffff80001873390 rsp=fffffa60017ff7b8 rbp=0000000000000002r8=0000000000000000 r9=0000000000000000 r10=fffffa800cf5a990r11=fffffa60017ff7a0 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl nz na po ncnt!RtlCopyMemoryNonTemporal+0x40:fffff800`01873390 4c8b0c11 mov r9,qword ptr [rcx+rdx] ds:fffffa60`04f4f000=????????????????Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000186e3ee to fffff8000186e650 STACK_TEXT: fffffa60`017ff4d8 fffff800`0186e3ee : 00000000`0000000a fffffa60`04f4f000 00000000`00000002 00000000`00000000 : nt!KeBugCheckExfffffa60`017ff4e0 fffff800`0186d2cb : 00000000`00000000 fffffa60`00cadb67 00000000`00000000 fffffa60`04f4f000 : nt!KiBugCheckDispatch+0x6efffffa60`017ff620 fffff800`01873390 : fffff800`01d34ca9 fffffa60`04f4f000 00000000`00000002 fffffa80`0f1354f0 : nt!KiPageFault+0x20bfffffa60`017ff7b8 fffff800`01d34ca9 : fffffa60`04f4f000 00000000`00000002 fffffa80`0f1354f0 fffffa80`0d35f2a0 : nt!RtlCopyMemoryNonTemporal+0x40fffffa60`017ff7c0 fffff800`01d34423 : fffffa80`0cf5a990 fffffa80`0cf5a900 00000000`00000000 fffffa80`0f1354f0 : hal!HalpDmaSyncMapBuffers+0x1b1fffffa60`017ff870 fffff800`01d37399 : fffffa80`0ebddc68 fffffa80`0cf5a990 fffffa80`0f1354f0 00000000`00000000 : hal!HalpDmaMapScatterTransfer+0xa3fffffa60`017ff8c0 fffff800`01d37312 : fffffa80`0ebddc68 fffffa80`0ebddc60 00000000`00001000 00000000`00000001 : hal!HalpMapTransfer+0x79fffffa60`017ff940 fffff800`01d3680f : 00000000`00000000 fffff800`01d33e45 00000000`00000000 00000000`00000001 : hal!IoMapTransfer+0x8efffffa60`017ff980 fffff800`01d36fdd : fffffa80`0cf44060 fffffa80`0cf5a990 fffffa80`0cf5a901 fffffa60`00000000 : hal!HalpAllocateAdapterCallback+0xc7fffffa60`017ffa20 fffff800`01d365df : fffffa80`0ebddc20 00000000`00001000 fffffa80`0cf5a990 fffffa80`0f1354f0 : hal!HalAllocateAdapterChannel+0x101fffffa60`017ffa60 fffffa60`00c780d3 : fffffa80`0ebddb80 fffffa60`00c7812c fffffa80`000000a0 fffffa80`0d388000 : hal!HalBuildScatterGatherList+0x2f3fffffa60`017ffad0 fffffa60`00caa566 : fffffa80`0ebddb80 fffffa80`0ebddb80 fffffa80`0cf5d1a0 fffffa80`0cf5d1a0 : PCIIDEX!BmSetup+0x6bfffffa60`017ffb30 fffffa60`00ca9788 : fffffa80`0cf5e4e8 fffffa60`00caeec0 00000000`00000013 00000000`00000000 : ataport!IdeDispatchChannelRequest+0x106fffffa60`017ffb60 fffffa60`00caae72 : 00000000`00000001 00000000`00000000 fffffa80`0ebddb80 00000000`00000000 : ataport!IdeStartChannelRequest+0xd8fffffa60`017ffbb0 fffffa60`00caa9dd : fffffa80`0cf5d1a0 00000000`00000000 fffffa60`017db580 00000000`00000001 : ataport!IdeProcessCompletedRequests+0x316fffffa60`017ffc60 fffff800`01877cd7 : fffffa80`0cf5d118 fffff800`01889ae0 00000000`00000000 fffffa60`017db580 : ataport!IdePortCompletionDpc+0x15dfffffa60`017ffd10 fffff800`01878e72 : fffffa60`00caa880 fffffa60`017d8180 00000000`00000000 fffffa60`017e1d40 : nt!KiRetireDpcList+0x117fffffa60`017ffd80 fffff800`01a475c0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x62fffffa60`017ffdb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4 STACK_COMMAND: kb FOLLOWUP_IP: PCIIDEX!BmSetup+6bfffffa60`00c780d3 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: 479198a5 FAILURE_BUCKET_ID: X64_0xA_PCIIDEX!BmSetup+6b BUCKET_ID: X64_0xA_PCIIDEX!BmSetup+6b Followup: MachineOwner---------

hi there, please understand that this forum doesnt help in analyzing dumps / memory dumps , as this is an offline forum analyzing dumps would not be efficient as this requires thorough interaction and might be sharing of data. Also there might be chances of performing livekd which is not possible in this forum.you may consider contacting Microsoft Customer Support service and a dedicated support professional will help you in a more efficient way. https://support.microsoft.com/common/international.aspx?iid=174859&iguid=56907522-6886-4238-a70f-a1d06a4473c7_2_2&rdpath=1thanks for understanding.===================================================================From the dump which you have posted i could say that pciidex.sys file might be the culprit.try updating pciidex.sys to latest version.sainath windows driver development.

We are having the same problem with our Serer 2008 , X64, 16GB Ram, Software RAID (x1) based system. We have a HP DL160 G5, and have even gone as far to replace motherboard as we found some hardware issues. But the reboots still occur, and all are related to PCIIDEX.sys according to the minidumps (and full memory dump) that has been analyzed. HP support has basically given up and thrown us to Microsoft.. which I have yet to do. While I feel strongly we're likely to just pay for Microsoft support, this is the closest sign that we have found where someone else may have a similar issue.. and your configuration is eerily similar to ours.We also have SQL 2008 on our machine, with 2 physical CPu's (8 virtual).... almost identical.

We are having the same problem with our Serer 2008 , X64, 16GB Ram, Software RAID (x1) based system. We have a HP DL160 G5, and have even gone as far to replace motherboard as we found some hardware issues. But the reboots still occur, and all are related to PCIIDEX.sys according to the minidumps (and full memory dump) that has been analyzed. HP support has basically given up and thrown us to Microsoft.. which I have yet to do. While I feel strongly we're likely to just pay for Microsoft support, this is the closest sign that we have found where someone else may have a similar issue.. and your configuration is eerily similar to ours.We also have SQL 2008 on our machine, with 2 physical CPu's (8 virtual).... almost identical. This problem has been SOLVED (we hope). The problem is a bug in PCIIDEX.sys which unfortunately, as of the time of this writing is not patchable or fixable. However, a workaround is to inject the MSAHCI.SYS driver (google for the KB article for Vista and Windows 7) into Windows (registry) and switch your SATA mode from PCI to AHCI. At least in this case, you will have an alternate driver running which may not have the same bug.WARNING: If you are a NOVICE user, you MUST inject the MSAHCI.SYS driver into your installation PRIOR to switching your BIOS settings or you will have a bluescreen on start-up (inaccessable_boot_device)Good luck,

We are having this same bug too. This is terrible!! It is on a production machine and we have thousands of customers down right now. Microsoft hasn't fixed this yet? Are you kidding me? I'll go switch the driver to AHCI. I sure hope that works.

Same bug here. Server crashes and after analyzing the mini dump the fault is the PCIIDEX.SYS "Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmSetup+6b )". The servers that we running is Dell R300 with Xeon CPU , with Windows 2008R2 Standard x64.