Hi i hav two BSOD and now it is ok.

As I have seen, the absolute majority of the APC_INDEX_MISMATCH BSODs are caused by third party antivirus programs. But we cannot say it for your situation, at least till now.

As now it is OK, you may not pay that much importance to the issue right now, but if the BSODs continue to occur, then it would require a high level of attention.

For the time being, free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Dont worry, it will not loss anything. All the programs will be installed in your computer, you will be able to call them from Start > All programs whenever you need them.
__________________________________________________________

Code:

BugCheck 1, {775bdc2a, 0, ffff, fffff8800427bb60}

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

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

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

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


FAULTING_IP: 
+1
00000000`775bdc2a c3              ret

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x1

PROCESS_NAME:  vsserv.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80003290e69 to fffff800032918c0

STACK_TEXT:  
fffff880`0427b928 fffff800`03290e69 : 00000000`00000001 00000000`775bdc2a 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0427b930 fffff800`03290da0 : fffffa80`0b4ec060 00000000`00000001 fffffa80`0b511640 fffff800`03587894 : nt!KiBugCheckDispatch+0x69
fffff880`0427ba70 00000000`775bdc2a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`0264ead8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775bdc2a


STACK_COMMAND:  kb

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

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiSystemServiceExit+245

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  556356e8

IMAGE_VERSION:  6.1.7601.18869

FAILURE_BUCKET_ID:  X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245

BUCKET_ID:  X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245

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
---------

Nice. Now wait and see how it goes. Inform us for any further BSOD.