Our Windows 2008 Server R2 (64-bit, virtualized with Citrix XenServer 5.5 on IBM BladeCenter H and running XenApp 6) is crashing with APC_INDEX_MISMATCH error several times a week (usually up and running fine for several days then crashing two or more times in a row). I wonder if there is a way to tell from the minidump what is happening (whether this is a known issue or somehow unique to our setup)? We first thought this was happening due to Adobe´s flash component but uninstalling flash did not stop the BOD from happening.Tapani Schouwvlieger

Bug Check Code 0x1: http://msdn.microsoft.com/en-us/library/ff557419(v=VS.85).aspx Please use Microsoft Skydrive to upload dump files (%systemroot%\minidumps like c:\windows\minidumps) and post a link here. If you want to debug dump files without my help, use Windbg and refer to this Microsoft article: http://support.microsoft.com/kb/315263 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

What's your stop message and parameters? There's at least one hot fix out there for this error, but I don't know if it applies to your situation. Have a look http://support.microsoft.com/kb/2203330/en-US. Here's also some more info on the error http://msdn.microsoft.com/en-us/library/ff557419(v=vs.85).aspx.

Hi, Here´s a link for the minidump. Full dump is about 300MB. Should I upload that one somewhere, too? http://cid-0778e9d5653a34f3.skydrive.live.com/redir.aspx?page=browse&resid=778E9D5653A34F3!147&type=6&Bsrc=EMSHOO&Bpub=SN.Notifications BR, TapaniTapani Schouwvlieger

Hi, Here´s the stop message and paraters. BR, Tapani Crash List Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Computer Name Full Path Processors Count Major Version Minor Version Dump File Size 040811-40669-01.dmp 8.4.2011 7:12:28 APC_INDEX_MISMATCH 0x00000001 fffff800`019c8920 00000000`00000000 00000000`00000001 00000000`00000001 ntoskrnl.exe ntoskrnl.exe+70740 x64 Y:\minidump\040811-40669-01.dmp 4 15 7600 268 832 Tapani Schouwvlieger

******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* APC_INDEX_MISMATCH (1) This is a kernel internal error. The most common reason to see this bugcheck is when a filesystem or a driver has a mismatched number of calls to disable and re-enable APCs. The key data item is the Thread->KernelApcDisable field. A negative value indicates that a driver has disabled APC calls without re-enabling them. A positive value indicates that the reverse is true. This check is made on exit from a system call. Arguments: Arg1: fffff800019ba920, address of system function (system call) Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex Arg3: 0000000000000001, Thread->KernelApcDisable Arg4: 0000000000000001, Previous KernelApcDisable Debugging Details: ------------------ FAULTING_IP: nt!IopProcessWorkItem+0 fffff800`019ba920 fff3 push rbx CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP BUGCHECK_STR: 0x1 PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff8000166b511 to fffff800016c0740 STACK_TEXT: fffff880`021c5ca8 fffff800`0166b511 : 00000000`00000001 fffff800`019ba920 00000000`00000000 00000000`00000001 : nt!KeBugCheckEx fffff880`021c5cb0 fffff800`019637c6 : 00000000`00000000 fffffa80`06426b60 00000000`00000080 fffffa80`06408040 : nt! ?? ::FNODOBFM::`string'+0x54406 fffff880`021c5d40 fffff800`0169ec26 : fffff880`01e6a180 fffffa80`06426b60 fffff880`01e74fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`021c5d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nt!IopProcessWorkItem+0 fffff800`019ba920 fff3 push rbx SYMBOL_NAME: nt!IopProcessWorkItem+0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd FAILURE_BUCKET_ID: X64_0x1_nt!IopProcessWorkItem+0 BUCKET_ID: X64_0x1_nt!IopProcessWorkItem+0 Followup: MachineOwner --------- ________________________________________________________________________ I am not able to get much more information from the minidump. Please use 7 Zip to divide the full dump file into blocks and upload it using Microsoft Skydrive. 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

Finally got the upload done, full memory dump of the latest crash can be found in: http://cid-0778e9d5653a34f3.office.live.com/browse.aspx/BSOD%20MEMORY%20DUMP/FullMemoryDump Hope this dump gives more information on the cause of the bsod. BR, TapaniTapani Schouwvlieger

******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* APC_INDEX_MISMATCH (1) This is a kernel internal error. The most common reason to see this bugcheck is when a filesystem or a driver has a mismatched number of calls to disable and re-enable APCs. The key data item is the Thread->KernelApcDisable field. A negative value indicates that a driver has disabled APC calls without re-enabling them. A positive value indicates that the reverse is true. This check is made on exit from a system call. Arguments: Arg1: fffff800019ca920, address of system function (system call) Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex Arg3: 0000000000000001, Thread->KernelApcDisable Arg4: 0000000000000001, Previous KernelApcDisable Debugging Details: ------------------ FAULTING_IP: nt!IopProcessWorkItem+0 fffff800`019ca920 fff3 push rbx DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1 PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff8000167b511 to fffff800016d0740 STACK_TEXT: fffff880`0217fca8 fffff800`0167b511 : 00000000`00000001 fffff800`019ca920 00000000`00000000 00000000`00000001 : nt!KeBugCheckEx fffff880`0217fcb0 fffff800`019737c6 : 00000000`00000000 fffffa80`06427040 00000000`00000080 fffffa80`0640c040 : nt! ?? ::FNODOBFM::`string'+0x54406 fffff880`0217fd40 fffff800`016aec26 : fffff880`01ee1180 fffffa80`06427040 fffff880`01eebfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`0217fd80 00000000`00000000 : fffff880`02180000 fffff880`0217a000 fffff880`0217f9f0 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nt!IopProcessWorkItem+0 fffff800`019ca920 fff3 push rbx SYMBOL_NAME: nt!IopProcessWorkItem+0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd FAILURE_BUCKET_ID: X64_0x1_SysCallNum_0_nt!IopProcessWorkItem+0 BUCKET_ID: X64_0x1_SysCallNum_0_nt!IopProcessWorkItem+0 Followup: MachineOwner --------- Same thing. Have a look to this Microsoft article about such BSOD: http://msdn.microsoft.com/en-us/library/ff557419(VS.85).aspx Have you installed something recently? If yes, it could be the cause. 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

We haven´t been able to trace back any change to the system that would coincide with the start of the BSOD´s. We even tried with an earlier snapshot of the server which did not have the latest Microsoft updates (that we first suspected might have caused the problems) and experienced the same BSOD´s with that one, too. I think we just need to try installing the hotfix replacing the compositebus.sys driver provided by Microsoft and hope for the best... Many, many thanks for the help on this matter! I´ll post comment later on if the fix works.Tapani Schouwvlieger

Start by updating your Windows and disable all security softwares and check again. 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

Hi, Please understand that forum is not the best place for analyzing dump. If this issue still cannot be fixed, please contact Microsoft Customer Support Services (CSS) so that a dedicated Support Professional can help you on this issue. 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;PHONENUMBERS If you are outside the US please see http://support.microsoft.com for regional support phone numbers. Thanks, MilesPlease 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.