Windows 10: APC_INDEX_MISMATCH ( win32kfull!EditionIsSAS+1197 ) randomly when I move the touchpad after...

Discus and support APC_INDEX_MISMATCH ( win32kfull!EditionIsSAS+1197 ) randomly when I move the touchpad after... in Windows 10 BSOD Crashes and Debugging to solve the problem; Crash Dump: https://1drv.ms/u/s!Au2M6ZFEMRrklAEYzKJIeoHfw-V9?e=YZ3gLk This is so confusing I hardly know how to explain it. Once in a while, I move... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Naimarnold2000, Jul 14, 2019.

  1. APC_INDEX_MISMATCH ( win32kfull!EditionIsSAS+1197 ) randomly when I move the touchpad after...


    Crash Dump: https://1drv.ms/u/s!Au2M6ZFEMRrklAEYzKJIeoHfw-V9?e=YZ3gLk


    This is so confusing I hardly know how to explain it. Once in a while, I move the mouse, and it crashes.


    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: ffffaf93e8f30bf7, Address of system call function or worker routine
    Arg2: 0000000000000000, Thread->ApcStateIndex
    Arg3: 0000000000000001, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
    Arg4: 0000000000000000, Call type (0 - system call, 1 - worker routine)

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


    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.Sec
    Value: 3

    Key : Analysis.Elapsed.Sec
    Value: 4

    Key : Analysis.Memory.CommitPeak.Mb
    Value: 75


    PROCESSES_ANALYSIS: 1

    SERVICE_ANALYSIS: 1

    STACKHASH_ANALYSIS: 1

    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING: 15063.0.amd64fre.rs2_release.170317-1834

    SYSTEM_MANUFACTURER: ASUSTeK COMPUTER INC.

    SYSTEM_PRODUCT_NAME: E203NAS

    SYSTEM_VERSION: 1.0

    BIOS_VENDOR: American Megatrends Inc.

    BIOS_VERSION: E203NAS.306

    BIOS_DATE: 12/01/2017

    BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

    BASEBOARD_PRODUCT: E203NAS

    BASEBOARD_VERSION: 1.0

    DUMP_TYPE: 2

    BUGCHECK_P1: ffffaf93e8f30bf7

    BUGCHECK_P2: 0

    BUGCHECK_P3: 1

    BUGCHECK_P4: 0

    FAULTING_IP:
    win32kfull!EditionIsSAS+1197
    ffffaf93`e8f30bf7 8bd8 mov ebx,eax

    CPU_COUNT: 2

    CPU_MHZ: 446

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 5c

    CPU_STEPPING: 9

    CPU_MICROCODE: 6,5c,9,0 (F,M,S,R) SIG: 2C'00000000 (cache) 2C'00000000 (init)

    BLACKBOXBSD: 1 (
    !blackboxbsd)


    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: 0x1

    PROCESS_NAME: dwm.exe

    CURRENT_IRQL: 0

    ANALYSIS_SESSION_HOST: DESKTOP-V1OBQNI

    ANALYSIS_SESSION_TIME: 07-14-2019 14:39:07.0052

    ANALYSIS_VERSION: 10.0.18914.1001 amd64fre

    LAST_CONTROL_TRANSFER: from fffff8002f2901d2 to fffff8002edf5310

    STACK_TEXT:
    ffff9881`1d86b1f8 fffff800`2f2901d2 : 00000000`00000001 ffffaf93`e8f30bf7 00000000`00000000 00000000`00000001 : nt!KeBugCheckEx
    ffff9881`1d86b200 ffffaf93`e8f30bf7 : ffffb709`0000007e ffff9881`1d86b300 00000000`00000130 ffff9881`1d86b2d8 : nt!KeUserModeCallback+0x150272
    ffff9881`1d86b2a0 ffffaf93`e8f09fa0 : ffff9881`1d86b540 ffffb709`3e5045e0 ffffb709`3bd1ccc0 ffffaf93`e91dc27e : win32kfull!EditionIsSAS+0x1197
    ffff9881`1d86b450 ffffaf93`e923b096 : 00000000`00000000 ffffb709`3e504640 ffffaf93`00000000 00000000`00000000 : win32kfull!EditionInputExtensibilityCallout+0x10
    ffff9881`1d86b480 ffffaf93`e92428db : 00000000`00000001 ffffb709`3bd1cd02 00000000`00000001 ffffafd5`80004140 : win32kbase!ApiSetEditionInputExtensibilityCallout+0x26
    ffff9881`1d86b4b0 ffffaf93`e91b0193 : 00000000`00000001 ffffafd5`80007010 ffff9881`1d86b690 ffffafd5`80004140 : win32kbase!InputExtensibilityCallout::CallUserModeWithDeviceLock+0xbb
    ffff9881`1d86b500 ffffaf93`e91affc7 : 00000000`00000000 ffff9881`00000000 00000000`0004004b ffffb709`3bd1ccc0 : win32kbase!CBaseInput:APC_INDEX_MISMATCH ( win32kfull!EditionIsSAS+1197 ) randomly when I move the touchpad after... :performPnpNotification+0x157
    ffff9881`1d86b670 ffffaf93`e91af2f5 : ffffb709`3bd1cd00 ffffb709`3ae9dea8 00000000`00000001 ffffb709`3ae9dbf0 : win32kbase!CBaseInput::RIMCallBack+0x193
    ffff9881`1d86b6e0 ffffaf93`e9250b69 : ffffb709`3bd1cd00 00000000`00000001 00000000`00000001 ffffaf93`e92034da : win32kbase!rimDoRimDevChangeCallback+0x5d
    ffff9881`1d86b740 ffffaf93`e91adc2c : 00000000`00000000 00000000`00000000 ffff9881`1d86b800 00000000`00000000 : win32kbase!rimHandleAnyPnpRemovePendingDevices+0xa4b2d
    ffff9881`1d86b790 ffffaf93`e91b0912 : ffffafd5`80007010 ffffafd5`80007058 ffffafd5`80007060 00000000`00000000 : win32kbase!RIMReadInput+0xac
    ffff9881`1d86b830 ffffaf93`e9242500 : ffffafd5`80007010 00000000`00000001 ffffafd5`80007060 00000000`00000003 : win32kbase!CBaseInput::Read+0x42
    ffff9881`1d86b880 ffffaf93`e91afcc7 : 00000000`00000000 00000000`00000001 00000000`00000001 ffffafd5`80007010 : win32kbase!CBaseInput::OnReadNotification+0x60
    ffff9881`1d86b8c0 ffffaf93`e9204d15 : ffffafd5`83b42038 00000000`00000001 ffffafd5`83b42010 00000000`00000000 : win32kbase!CBaseInput::OnDispatcherObjectSignaled+0x7f
    ffff9881`1d86b910 ffffaf93`e9204e96 : ffff9881`1d86b970 ffffaf93`e91dc27e 00000000`00000040 ffff9881`1d86bb80 : win32kbase!IOCPDispatcher::HandleSensorDispatcherSignal+0x61
    ffff9881`1d86b960 ffffaf93`e920493e : 00000000`00000000 ffffaf93`e9312a01 00000000`00000013 00000000`00000013 : win32kbase!IOCPDispatcher::WaitAndDispatch+0xc6
    ffff9881`1d86b9b0 ffffaf93`e9204804 : ffffafd5`843ea570 ffffafd5`83f8e3a8 ffffafd5`843b22d0 ffffffff`80006fdc : win32kbase!UserProcessMITInput+0xa2
    ffff9881`1d86ba50 fffff800`2ee00213 : ffffb709`3bce2700 000000d8`ae28f208 ffff9881`1d86bb28 000000d8`ae28f3a4 : win32kbase!NtMITWaitForMultipleObjectsEx+0x2c4
    ffff9881`1d86bb10 00007ffe`5ed56f64 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    000000d8`ae28f1e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`5ed56f64


    THREAD_SHA1_HASH_MOD_FUNC: cbf2d19d9dfc7f3ce74b1d2103dbefa4bcfd7d03

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: c0a1f6412087320f5b5f454e18ca7fcc7885a992

    THREAD_SHA1_HASH_MOD: d43b938ee58a652a368e6585482a2a9891cf282b

    FOLLOWUP_IP:
    win32kfull!EditionIsSAS+1197
    ffffaf93`e8f30bf7 8bd8 mov ebx,eax

    FAULT_INSTR_CODE: 7eb9d88b

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: win32kfull!EditionIsSAS+1197

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME:
    win32kfull

    IMAGE_NAME: win32kfull.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    IMAGE_VERSION: 10.0.15063.296

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 1197

    FAILURE_BUCKET_ID: 0x1_SysCallNum_5_win32kfull!EditionIsSAS

    BUCKET_ID: 0x1_SysCallNum_5_win32kfull!EditionIsSAS

    PRIMARY_PROBLEM_CLASS: 0x1_SysCallNum_5_win32kfull!EditionIsSAS

    TARGET_TIME: 2019-07-06T15:40:32.000Z

    OSBUILD: 15063

    OSSERVICEPACK: 296

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 272

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2017-04-27 18:52:30

    BUILDDATESTAMP_STR: 170317-1834

    BUILDLAB_STR: rs2_release

    BUILDOSVER_STR: 10.0.15063.0.amd64fre.rs2_release.170317-1834

    ANALYSIS_SESSION_ELAPSED_TIME: 1062

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x1_syscallnum_5_win32kfull!editionissas

    FAILURE_ID_HASH: {ca7bebfe-4653-eca0-81d0-314e5466ef97}

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



    :)
     
    Naimarnold2000, Jul 14, 2019
    #1
  2. nxavis9 Win User

    I want to disable touchpad on Dell laptop


    Hello everyone,
    My laptop's touchpad works and I don't want it to, because I prefer a mouse. It's a Dell Inspiron 11 3000 series on windows 10 OS.

    What I have tried that hasn't worked:
    • start<settings<devices<mouse & touchpad<additional mouse options. This opens a window called Mouse Options which has 5 tabs up top, none of which involve the touchpad. The Hardware tab shows 2 devices: the mouse itself, and the USB. No touchpad there.
    • windows key+x<mobility center. No touchpad to be found.
    • various function keys. No options for touchpad on/off.
    • device manager<mice and other pointing devices. Again, only the mouse and usb show up. It appears the touchpad is working without a driver, which is a little spooky.
    Any other suggestions? I could try downloading a third party driver, but that seems like a step in the wrong direction.
    Thanks
     
    nxavis9, Jul 14, 2019
    #2
  3. Stop code APC_INDEX_MISMATCH

    Hi,

    The error you've encounter usually appears when a new hardware was installed on the computer. It could be a USB device that is newly installed. It's recommended that you install and update the device's drivers.

    For you to update the driver manually, follow the steps below:

    • Right-click on the Windows key.
    • Click Device Manager.
    • Locate and expand the category where the new device belong.
    • Right-click the device’s name from the list and click Update Driver Software.

    If the above steps did not resolve the issue, we suggest that you follow the instructions given to troubleshoot blue screen errors found in this
    article.

    For more information regarding the error, refer to this article:
    Bug Check 0x1: APC_INDEX_MISMATCH
    .

    Let us know if you need further assistance.
     
    Reymichael Ros, Jul 14, 2019
    #3
  4. APC_INDEX_MISMATCH ( win32kfull!EditionIsSAS+1197 ) randomly when I move the touchpad after...

    TouchPad problem


    see attached screenshot of the keys after I re ran the scan

    so i assume next steps are to have that program open that you suggested whilst using the laptop and then when the touchpad gets disabled to check if the keys have changed?
     
    bartjunited, Jul 14, 2019
    #4
Thema:

APC_INDEX_MISMATCH ( win32kfull!EditionIsSAS+1197 ) randomly when I move the touchpad after...

Loading...
  1. APC_INDEX_MISMATCH ( win32kfull!EditionIsSAS+1197 ) randomly when I move the touchpad after... - Similar Threads - APC_INDEX_MISMATCH win32kfull EditionIsSAS+1197

  2. BSOD win32kfull

    in Windows 10 Drivers and Hardware
    BSOD win32kfull: HiI have started to get this blue screen error any ideas. There are no driver problems in device manager. Please let me know if you can see what has happened,I have left the latest dmp files herehttps://www.dropbox.com/sh/ei6t5oy0u4afik3/AAB8iAzMZhNvWtGnSTHePIK3a?dl=0Thanks...
  3. APC_INDEX_MISMATCH

    in Windows 10 Installation and Upgrade
    APC_INDEX_MISMATCH: Hi, Both of my computers now shut down with the code APC_INDEX_MISMATCH when I try to print anything. ??? Is there a resolve? Thanks, https://answers.microsoft.com/en-us/windows/forum/all/apcindexmismatch/efde9070-2fc3-4e5f-a9d2-5495f1fa031e
  4. win32kfull Randomly Crashes

    in Windows 10 BSOD Crashes and Debugging
    win32kfull Randomly Crashes: Hi, In the last two weeks my computer started to have randomly bsod's related to win32kfull, the last time it has happened the computer was idle. Windows 10 64bits. 164924
  5. Apc_index_mismatch

    in Windows 10 BSOD Crashes and Debugging
    Apc_index_mismatch: Hi, I get often this blue screen APC_INDEX_MISMATCH Can you help me to debug that ? I downloaded your tool Beta-Log-collector. Attached my results. Thank you very much for your help, and your time. Cheers, 131747
  6. Apc_index_mismatch

    in Windows 10 BSOD Crashes and Debugging
    Apc_index_mismatch: My Hewlitt Packard laptop (windows 10 64 bit) gave a light blue screen when I was using it all of a sudden with the message "Your PC ran into a problem and needs to restart. We're just collecting some error info and then will restart soon (100% complete) If you'd like to...
  7. BSOD after wake, error code APC_INDEX_MISMATCH

    in Windows 10 BSOD Crashes and Debugging
    BSOD after wake, error code APC_INDEX_MISMATCH: Hey! I'm having a hard time figuring out what is causing this BSOD. It started in Windows 8, and after reading around, and trying several things (changing parameters in the BIOS, updating drivers, etc.) I thought (well..hoped..) that upgrading to Windows 10 might solve...
  8. Webcam + VLC = APC_INDEX_MISMATCH

    in Windows 10 BSOD Crashes and Debugging
    Webcam + VLC = APC_INDEX_MISMATCH: I have a webcam as capture device with 32 bit VLC, and every 2 weeks or so when I start the cam/VLC I get APC mismatch. The system restarts, and I try again - usually takes several attempts (ie crashes) before the cam/VLC works. Webcam is USB Logitech C270 and VLC is latest...
  9. Apc_index_mismatch [bsod]

    in Windows 10 BSOD Crashes and Debugging
    Apc_index_mismatch [bsod]: Hello Yesterday after coming back to my laptop after about 5 hours I brought it out of standby and whilst doing some work it blue screened with the error APC_INDEX_MISMATCH. I think I was trying to enter the character 1/2 with an ALT code. The error happened 3 times. I ran...
  10. BSOD [APC_INDEX_MISMATCH] after some changes on the pc

    in Windows 10 BSOD Crashes and Debugging
    BSOD [APC_INDEX_MISMATCH] after some changes on the pc: Hi, the last week I'm been suffering freezes and reboots. I never had a BSOD dump until today. I have recently changed from a HDD to a SSD, I have applied a theme on my Windows 10, and I have updated to Fall Creators update. I cloned the HDD block by block to the new SSD,...