none
Windows 7 BSOD APC_INDEX_MISMATCH

    Question

  • Hello All,

    Currently have a Windows 7 device that continues to BSOD with the error code APC_Index_Mismatch. This issue has steadily started to affect more and more users on this particular machine build. I have noticed a pattern that it's related to docking/undocking of the PC, but of course not 100% of the time. For the 6-10 machines affected, every dump file i pull from C:\Windows\Minidump\ seems to be almost identical as it's the same issue causing this.  I believe there is a chance it's related to Windows Updates.

    Specifications:
    Dell Latitude E7470
    Intel (R) Core(TM) i7-6600U CPU @ 2.60GHz 2.80 GHz
    16.0 GB (some devices are 8.0 GB)
    64-Bit Operating System
    Microsoft Windows 7 Professional
    Intel(R) HD Graphics 520
    Speakers / Headphones (Realtek Audio)

    To troubleshoot I have reinstalled these drivers in particular from the Dell Drivers & Downloads website
    Realtek High Definition Audio Driver
    Intel 8260 7265 3165 7260 WiFi Driver
    Intel 12xx/825xx Gigabit Ethernet Network Controller Driver
    Intel HD Graphics 500 P500 600 P600 Series Driver
    http://www.dell.com/support/home/us/en/04/product-support/servicetag/5k0wgc2/drivers

    Below is the Mini Dump File I pulled from winDBG (x64):
     
    Any help, feedback, suggestions are much appreciated as its driving me crazy. Hopefully, someone can find something from the logs that I can't pinpoint below.

    Microsoft (R) Windows Debugger Version 10.0.16299.91 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Users\######\Desktop\012918-17721-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.23915.amd64fre.win7sp1_ldr.170913-0600
    Machine Name:
    Kernel base = 0xfffff800`03457000 PsLoadedModuleList = 0xfffff800`03699750
    Debug session time: Mon Jan 29 15:07:54.073 2018 (UTC - 8:00)
    System Uptime: 0 days 2:20:19.441
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................................
    Loading User Symbols
    Loading unloaded module list
    .................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1, {76dabdaa, 0, ffff, fffff8802a2e9b60}

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

    Followup:     MachineOwner
    ---------

    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        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->CombinedApcDisable field. This consists of two separate 16-bit
    fields, the SpecialApcDisable and the KernelApcDisable. A negative value
    of either indicates that a driver has disabled special or normal APCs
    (respectively) without re-enabling them; a positive value indicates that
    a driver has enabled special or normal APCs (respectively) too many times.
    Arguments:
    Arg1: 0000000076dabdaa, Address of system call function or worker routine
    Arg2: 0000000000000000, Thread->ApcStateIndex
    Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
    Arg4: fffff8802a2e9b60, Call type (0 - system call, 1 - worker routine)

    Debugging Details:
    ------------------

    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING:  7601.23915.amd64fre.win7sp1_ldr.170913-0600

    SYSTEM_MANUFACTURER:  Dell Inc.

    SYSTEM_PRODUCT_NAME:  Latitude E7470

    SYSTEM_SKU:  06DC

    BIOS_VENDOR:  Dell Inc.

    BIOS_VERSION:  1.18.5

    BIOS_DATE:  12/11/2017

    BASEBOARD_MANUFACTURER:  Dell Inc.

    BASEBOARD_PRODUCT:  0T6HHJ

    BASEBOARD_VERSION:  A00

    DUMP_TYPE:  2

    BUGCHECK_P1: 76dabdaa

    BUGCHECK_P2: 0

    BUGCHECK_P3: ffff

    BUGCHECK_P4: fffff8802a2e9b60

    FAULTING_IP: 
    +0
    00000000`76dabdaa ??              ???

    CPU_COUNT: 4

    CPU_MHZ: af8

    CPU_VENDOR:  GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 4e

    CPU_STEPPING: 3

    CPU_MICROCODE: 6,4e,3,0 (F,M,S,R)  SIG: C2'00000000 (cache) C2'00000000 (init)

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    BUGCHECK_STR:  0x1

    PROCESS_NAME:  audiodg.exe   [??]

    CURRENT_IRQL:  0

    ANALYSIS_SESSION_HOST:  ##########

    ANALYSIS_SESSION_TIME:  02-14-2018 13:33:58.0059

    ANALYSIS_VERSION: 10.0.16299.91 amd64fre     [??]

    LAST_CONTROL_TRANSFER:  from fffff800034c73a9 to fffff800034c7e00

    STACK_TEXT:  
    fffff880`2a2e9928 fffff800`034c73a9 : 00000000`00000001 00000000`76dabdaa 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
    fffff880`2a2e9930 fffff800`034c72e0 : fffffa80`2acc6060 00000000`008eded8 fffff880`2a2e9a88 00000000`00000001 : nt!KiBugCheckDispatch+0x69
    fffff880`2a2e9a70 00000000`76dabdaa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
    00000000`008edea8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76dabdaa


    THREAD_SHA1_HASH_MOD_FUNC:  713a38487ff3d82058f51d9870e0b3de39cbf964

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  561f1421a866d36916a994b3bd23a42b1aea0bb5

    THREAD_SHA1_HASH_MOD:  2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b

    FOLLOWUP_IP: 
    nt!KiSystemServiceExit+245
    fffff800`034c72e0 4883ec50        sub     rsp,50h

    FAULT_INSTR_CODE:  50ec8348

    SYMBOL_STACK_INDEX:  2

    SYMBOL_NAME:  nt!KiSystemServiceExit+245

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  59b946d1

    IMAGE_VERSION:  6.1.7601.23915

    STACK_COMMAND:  .thread ; .cxr ; kb

    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:  2018-01-29T23:07:54.000Z

    OSBUILD:  7601

    OSSERVICEPACK:  1000

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK:  272

    PRODUCT_TYPE:  1

    OSPLATFORM_TYPE:  x64

    OSNAME:  Windows 7

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

    OS_LOCALE:  

    USER_LCID:  0

    OSBUILD_TIMESTAMP:  2017-09-13 07:55:13

    BUILDDATESTAMP_STR:  170913-0600

    BUILDLAB_STR:  win7sp1_ldr

    BUILDOSVER_STR:  6.1.7601.23915.amd64fre.win7sp1_ldr.170913-0600

    ANALYSIS_SESSION_ELAPSED_TIME:  453

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:x64_0x1_syscallnum_4_nt!kisystemserviceexit+245

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

    Followup:     MachineOwner


    Monday, February 19, 2018 10:37 PM

All replies

  • This is most likely linked to a problem with a driver (Might be audiodg.exe). I would advise to install the latest updates of your drivers, including the audio one, and check again.

    This posting is provided AS IS with no warranties or guarantees , and confers no rights.

    Ahmed MALEK

    My Website Link

    My Linkedin Profile

    My MVP Profile

    Monday, February 19, 2018 11:09 PM
  • Hi,

    Did you mean that the machine which installed updates all have the same issue? If so, which kb did you installed, you can check this in Control Panel>Windows update>view update history.

    I think it may be caused by Intel Graphics driver, Realtek High Defination Audio Function driver.

    Please go to manufacturer's website to download the latest drivers for them.

    Also, update BIOS is necessary.

    The same issue here:

    https://social.technet.microsoft.com/Forums/windows/en-US/a70f7bf2-6366-4c95-a158-94a243cf37ce/apcindexmismatch-0x00000001?forum=w7itprogeneral 


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, February 20, 2018 2:24 AM
  • The APC_INDEX_MISMATCH bug check has a value of 0x00000001. This indicates that there has been a mismatch in the APC (asynchronous procedure calls) state index.

    To evaluate the BSOD please post logs for troubleshooting.

    Using administrative command prompt copy and paste this whole command:

    Make sure the default language is English so that the logs can be scanned and read.

    https://www.tenforums.com/tutorials/3813-language-add-remove-change-windows-10-a.html

    The command will automatically collect the computer files and place them on the desktop.

    Then use one drive or drop box to place share links into the thread for troubleshooting.

    https://support.office.com/en-us/article/Share-OneDrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07

    It will automatically collect these files:  msinfo32, dxdiag, mini dumps, drivers hosts, install, uninstall, services, startup, event viewer files, etc.

    Open administrative command prompt and copy and paste the whole command:

    copy %SystemRoot%\minidump\*.dmp "%USERPROFILE%\Desktop\"&dxdiag /t %Temp%\dxdiag.txt&copy %Temp%\dxdiag.txt "%USERPROFILE%\Desktop\SFdebugFiles\"&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"&driverquery /v > "%USERPROFILE%\Desktop\drivers.txt" &msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"&net start > "%USERPROFILE%\Desktop\services.txt"&REM wmic startup list full /format:htable >"%USERPROFILE%\Desktop\startup.html"&wmic STARTUP GET Caption, Command, User >"%USERPROFILE%\Desktop\startup.txt"

    There is 1 file for you to find manually:  memory dump file:

    C:\Windows\MEMORY.DMP

    Use file explorer > this PC > local C: drive > right upper corner search enter each of the above to find results.

    Sometimes the dxdiag file needs to be found and saved manually:  In the left lower corner search type:  dxdiag > When the DirectX Diagnostic Tool opens click on the next page button so that each tab is opened > click on save all information > save to desktop > post one drive or drop box share link into the thread

    Tuesday, February 20, 2018 3:21 AM
  • Taking this step first. Thank you!
    Tuesday, February 20, 2018 6:17 PM
  • Hi,

    If there is any updates on dealing with the bsod issue, please let me know.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, February 21, 2018 1:47 AM
  • Did you ever get this resolved?  I'm having the exact same issue with one user.
    Tuesday, July 10, 2018 12:03 PM
  • Mike_P_SC

    Please open a new thread and post a link into this thread.

    In the new thread post computer log files (see post on Tuesday, February 20, 2018 3:21 AM) for troubleshooting.

    Tuesday, July 10, 2018 1:56 PM