Bsod During Boot Up 0x00000001 Apc_index_mismatch Vsserv.exe

2 days ago I uninstalled BitDefender 2015 and installed 2016. Since then I've rebooted the PC 3 times, the third boot Blue-Screened the PC before the Windows 10 logon screen.


0x00000001 APC_INDEX_MISMATCH


I debugged the MEMORY.DMP file using WinDbg.exe and it points to vsserv.exe which is BitDefenders real-time protection service.


Anyone else seen this BSOD?


Hopefully it was a one off instance. It never happened with 2015.


Heres the memory dump if its any help for the devs.


Microsoft ® Windows Debugger Version 6.2.9200.20512 X86


Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]


Kernel Bitmap Dump File: Only kernel address space is available


Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols


Executable search path is:


Windows 8 Kernel Version 10240 MP (8 procs) Free x64


Product: WinNt, suite: TerminalServer SingleUserTS


Built by: 10240.16545.amd64fre.th1.150930-1750


Machine Name:


Kernel base = 0xfffff803`f3c86000 PsLoadedModuleList = 0xfffff803`f3fab070


Debug session time: Mon Nov 9 17:41:36.535 2015 (UTC + 11:00)


System Uptime: 0 days 0:00:14.243


Loading Kernel Symbols


...............................................................


................................................................


..................................


Loading User Symbols


PEB is paged out (Peb.Ldr = 00007ff6`f1cc8018). Type ".hh dbgerr001" for details


*******************************************************************************


* *


* Bugcheck Analysis *


* *


*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck 1, {7ffc5c1a356a, 0, ffff, ffffd0017b3c5b80}


Page 112866 not present in the dump file. Type ".hh dbgerr004" for details


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


Followup: MachineOwner


---------


4: 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: 00007ffc5c1a356a, Address of system call function or worker routine


Arg2: 0000000000000000, Thread->ApcStateIndex


Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable


Arg4: ffffd0017b3c5b80, Call type (0 - system call, 1 - worker routine)


Debugging Details:


------------------


Page 112866 not present in the dump file. Type ".hh dbgerr004" for details


FAULTING_IP:


+a10441e158


00007ffc`5c1a356a ?? ???


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT


BUGCHECK_STR: 0x1


PROCESS_NAME: vsserv.exe


CURRENT_IRQL: 0


LAST_CONTROL_TRANSFER: from fffff803f3ddeca9 to fffff803f3dd42e0


STACK_TEXT:


ffffd001`7b3c5948 fffff803`f3ddeca9 : 00000000`00000001 00007ffc`5c1a356a 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx


ffffd001`7b3c5950 fffff803`f3ddebb5 : ffffc000`625e5680 fffff803`f40b6b2d 00000000`00000000 fffff803`f40a2448 : nt!KiBugCheckDispatch+0x69


ffffd001`7b3c5a90 00007ffc`5c1a356a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x24a


00000048`c25a3308 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`5c1a356a


STACK_COMMAND: kb


FOLLOWUP_IP:


nt!KiSystemServiceExit+24a


fffff803`f3ddebb5 4883ec50 sub rsp,50h


SYMBOL_STACK_INDEX: 2


SYMBOL_NAME: nt!KiSystemServiceExit+24a


FOLLOWUP_NAME: MachineOwner


MODULE_NAME: nt


IMAGE_NAME: ntkrnlmp.exe


DEBUG_FLR_IMAGE_TIMESTAMP: 560ca418


BUCKET_ID_FUNC_OFFSET: 24a


FAILURE_BUCKET_ID: 0x1_SysCallNum_7_nt!KiSystemServiceExit


BUCKET_ID: 0x1_SysCallNum_7_nt!KiSystemServiceExit


Followup: MachineOwner

Comments

  • Exactly the same BSOD in my computer, one restart after installing Antivirus Plus 2016 on Win 10.

  • ryspredator
    edited January 2016

    I have seen such, some were caused due to a mismatched APC call or because the IRQL level was too high when attempting to read/write data from/to the memory.

  • Georgia
    Georgia ✭✭✭

    Hello,


    According to your DMP the BSOD was caused by ntkrnlmp.exe ( nt!KiSystemServiceExit+24a ) which is the 'heart' of the Windows operating system.


    Please install all available Windows and Bitdefender updates and if the BSOD still occurs we need the most recent complete memory dump & a Bitdefender diagnostic log for further debugging.


    You can upload the logs to a file transfer site such as https://www.wetransfer.com and then reply with the download link at bitsy@bitdefender.com

  • K24A3
    edited January 2016
    Hello,


    According to your DMP the BSOD was caused by ntkrnlmp.exe ( nt!KiSystemServiceExit+24a ) which is the 'heart' of the Windows operating system.


    Please install all available Windows and Bitdefender updates and if the BSOD still occurs we need the most recent complete memory dump & a Bitdefender diagnostic log for further debugging.


    You can upload the logs to a file transfer site such as https://www.wetransfer.com and then reply with the download link at bitsy@bitdefender.com


    Hi guys,


    Sorry I didnt respond to the first two who posted, I didnt get the notifications in gmail until Georgia's post. Gmail is a bit funny that way, so much spam may have clouded the genuine posts.


    But anyway my PC has been running fine since the initial post (or at least a few days after the post). no BSOD's at all.


    The only problem now is that the whole PC hangs when encoding MPEG2 TS to h264 after a few hours using handbrake video encoding, which may have nothing to do with BitDefender. I think it may be a CPU or RAM issue, or an Intel driver issue, but I cant seem to narrow the problem down since its so intermittent.


    I'm running Win10 Pro build 1511 now and Bitdefender is running perfectly fine. A prior Bitdefender patch or MS Hotfix may have resolved the problem.


    So this issue may be closed as far as I'm concerned. Thanks ryspredatorfor/connexion2000/Georgia the assistance.

  • Hi,


    Thank you for reporting back with your results.


    I now declare this topic closed.

This discussion has been closed.