BSOD at random times - APC Index Mismatch

[NLE9]

I have been getting random BSOD's titled APC Index Mismatch. I can not attribute it to any specific activity. Please advise best route to correct this.

Thanks for the help!

Neil EricksonView attachment 201762

View attachment 201763

 

[writhziden]

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


Loading Dump File [D:\Kingston\BSODDmpFiles\NLE9\Windows_NT6_BSOD_jcgriff2\030712-41153-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03000000 PsLoadedModuleList = 0xfffff800`03245670
Debug session time: Wed Mar  7 00:10:10.396 2012 (UTC - 7:00)
System Uptime: 0 days 18:49:23.457
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1, {74852e09, 0, ffff, fffff88004871ca0}

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

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

2: 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->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: 0000000074852e09, address of system function (system call)
Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 000000000000ffff, Thread->KernelApcDisable
Arg4: fffff88004871ca0, Previous KernelApcDisable

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


FAULTING_IP: 
+6533356466343934
00000000`74852e09 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1

[COLOR="Red"]PROCESS_NAME:  SZServer.exe[/COLOR]

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000307c1e9 to fffff8000307cc40

STACK_TEXT:  
fffff880`04871a68 fffff800`0307c1e9 : 00000000`00000001 00000000`74852e09 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffff880`04871a70 fffff800`0307c120 : 00000000`74852450 ef000000`89707867 00000000`c0000001 00000980`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`04871bb0 00000000`74852e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`07bcf0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74852e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSystemServiceExit+245
fffff800`0307c120 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:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245

BUCKET_ID:  X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245

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

Remove STOPzilla. It caused the latest crash and is questionable software. Actually, it caused all the crashes included in your reports.

If you are looking for similar software that will not cause problems on your system, I would recommend starting a thread in System Security - Windows 7 Forums after removing STOPzilla.

 

[NLE9]

Thank you for your review

Thanks for the suggestion. I will remove it. I installed Stopzilla because of a fake AV that had totally taken control of my computer and even worked in Safe mode! Stopzilla would run prior to windows starting and was able to remove it as well as other things it found that improved the operation of my computer.

Too bad it is causing the BSOD.

Thanks for your help with this.

 

[writhziden]

You're welcome. I'm glad STOPzilla helped your computer in the past, but it is definitely hurting the performance now. Let us know how the system responds after removing STOPzilla.