BSOD crashes APC Index Mismatch

I just bought a new PC preloaded with vista and was upgraded to windows 7 in store. At first, I was experiencing numerous crashes while the computer was sleeping and also had trouble recovering from sleep mode. I disabled sleep mode and that "fixed" that problem. Then I started to experience BSODs while running an online game. The BSOD screen said it was a APC Index Mismatch. I don't know how to view the minidump reports but have included them. Any insight or advice would be greatly appreciated.

Processor
Intel® Core™2 Quad Processor Q9300
2.50GHz, 6MB L2 Cache, 1333MHz Front Side Bus
Chipset
Intel® G33 Express Chipset
Standard memory
8 GB
Memory type
DDR2 SDRAM memory
Memory slots
4 DIMM (240-pin, DDR2) (occupied)
Internal drives
Internal hard disk drive
1 Terabyte
Hard disk controller
Serial ATA hard drive
Hard disk drive speed
5400 RPM
Optical drive type
SuperMulti DVD Burner with LightScribe Techn

Salamy said:

I just bought a new PC preloaded with vista and was upgraded to windows 7 in store. At first, I was experiencing numerous crashes while the computer was sleeping and also had trouble recovering from sleep mode. I disabled sleep mode and that "fixed" that problem. Then I started to experience BSODs while running an online game. The BSOD screen said it was a APC Index Mismatch. I don't know how to view the minidump reports but have included them. Any insight or advice would be greatly appreciated.

Processor
Intel® Core™2 Quad Processor Q9300
2.50GHz, 6MB L2 Cache, 1333MHz Front Side Bus
Chipset
Intel® G33 Express Chipset
Standard memory
8 GB
Memory type
DDR2 SDRAM memory
Memory slots
4 DIMM (240-pin, DDR2) (occupied)
Internal drives
Internal hard disk drive
1 Terabyte
Hard disk controller
Serial ATA hard drive
Hard disk drive speed
5400 RPM
Optical drive type
SuperMulti DVD Burner with LightScribe Techn

One of two things.

Driver incompatibility.
Overheating.

...And that's a rough guess. I probably shouldn't have even posted, got a major headache and going to sleep after this one.

Looks like at least two separate crash patterns:

1) Rt64win7.sys (your NIC driver) being unable to deal with power state transitions. The driver is relatively new, so I doubt you'll find updates but you might as well try. Otherwise, update the BIOS and chipset drivers and cross your fingers.

2) Something to do with a firewire device. Do you have firewire hardware plugged in? A video camera, card reader...?

Thanks, I hope the two problems were related, because I think I've solved one. I unplugged my M-Audio Firewire Solo unit, and no BSOD lately. This unit is an external soundcard, and it doesn't have any windows 7 specific drivers yet, it appeared to be working fine, but when I played an online game the RAM usage would gradually go crazy higher than I would have expected, and then I'd get the bsod.

Salamy said:

Thanks, I hope the two problems were related, because I think I've solved one. I unplugged my M-Audio Firewire Solo unit, and no BSOD lately. This unit is an external soundcard, and it doesn't have any windows 7 specific drivers yet, it appeared to be working fine, but when I played an online game the RAM usage would gradually go crazy higher than I would have expected, and then I'd get the bsod.

M-Audio.... drivers... promises... delays... incompetence... crashes... lack of updates or concern from M-Audio....

I'm sorry for the blathering. It's just that this is very painful for me personally, and I think I'm going to go cry some tears of quiet rage in a corner.

Hi, just found this topic as my computer is doing the same thing.... and guess what??? I have an M-Audio NRV10 firewire. Something is sounding suspect here....

SandraChung said:

I am also experiencing the APC_INDEX_MISMATCH. I have uninstalled programs, rolled back drivers, and used system restore to fix the problem, and it's happening with more and more regularity, on an at least daily basis. Attached is the latest one. I've changed the extension to TXT from dmp so I could upload it.

I have done all the websearch and nothing applies. Not running FireWire, nor have I added new hardware, so no new drivers. could you upload more DMP's if yoou have them?

Help?

Sandra

Hi and welcome

This is a "unusual" type of crash with little information. I found that your mirc client was involved.

If you have more of the DMP file can you upload them?


In the mean time there are a few things we can do.

First I would un-install MIRC, just to test if it is the cause.
second run a system file check to verify and repair your system files.
third you have some old drivers on you system that should be updated.

If the problem continues we can get more aggressive and use driver verifier. Before you can run driver verifier you need to backup the system as it will cause your computer to crash

OLD DRIVERS

Code:

secdrv.SYS        fffff880`0a2d3000    fffff880`0a2de000    0x0000b000    0x4508052e    9/13/2006 9:18:38 AM                        
ElbyCDFL.sys        fffff880`043ed000    fffff880`043fb000    0x0000e000    0x4581c093    12/14/2006 5:22:27 PM                        
WacomVKHid.sys        fffff880`043fb000    fffff880`043fcc80    0x00001c80    0x45d4e87e    2/15/2007 7:10:54 PM                        
wacommousefilter.sys        fffff880`04467000    fffff880`0446f000    0x00008000    0x45d5f401    2/16/2007 2:12:17 PM                        
SCDEmu.SYS        fffff880`03ad3000    fffff880`03ae5000    0x00012000    0x46b88d94    8/7/2007 11:19:48 AM                        
adfs.SYS        fffff880`06d90000    fffff880`06da8000    0x00018000    0x48640195    6/26/2008 4:52:37 PM                        
wacomvhid.sys        fffff880`04210000    fffff880`04212680    0x00002680    0x4877a389    7/11/2008 2:16:41 PM                        
ElRawDsk.sys        fffff880`03ca8000    fffff880`03cb2000    0x0000a000    0x488b65ed    7/26/2008 1:59:09 PM                        
NTIDrvr.sys        fffff880`04208000    fffff880`04210000    0x00008000    0x49c9a073    3/24/2009 11:09:39 PM                        
cpuz132_x64.sys        fffff880`075f4000    fffff880`075fc000    0x00008000    0x49cc0d03    3/26/2009 7:17:23 PM

Analysis

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\031710-28080-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03267000 PsLoadedModuleList = 0xfffff800`034a4e50
Debug session time: Tue Mar 16 19:21:01.930 2010 (GMT-4)
System Uptime: 0 days 7:38:26.569
Loading Kernel Symbols
...............................................................
................................................................
..........................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1, {77ba040a, 0, ffff, fffff88003eb52e0}

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

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

0: 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: 0000000077ba040a, address of system function (system call)
Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 000000000000ffff, Thread->KernelApcDisable
Arg4: fffff88003eb52e0, Previous KernelApcDisable

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


FAULTING_IP: 
+5f74952f0415da40
00000000`77ba040a ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1

PROCESS_NAME:  mirc.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800032d8469 to fffff800032d8f00

STACK_TEXT:  
fffff880`03eb50a8 fffff800`032d8469 : 00000000`00000001 00000000`77ba040a 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffff880`03eb50b0 fffff800`032d83a0 : fffffa80`09e887b0 00000000`00000001 fffffa80`0587cb60 fffff800`035ec094 : nt!KiBugCheckDispatch+0x69
fffff880`03eb51f0 00000000`77ba040a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`0008c998 fffff800`032d0840 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ba040a
fffff880`03eb56a0 fffff880`03eb56b8 : 00000000`00000000 fffff880`03eb57d8 fffff880`00000018 00000000`000000b0 : nt!KiCallUserMode
fffff880`03eb56a8 00000000`00000000 : fffff880`03eb57d8 fffff880`00000018 00000000`000000b0 fffff880`03eb5d70 : 0xfffff880`03eb56b8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSystemServiceExit+245
fffff800`032d83a0 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:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1_nt!KiSystemServiceExit+245

BUCKET_ID:  X64_0x1_nt!KiSystemServiceExit+245

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

I have suffered the BSOD for about 3 months and whilst surfing someone had stated that System Mechanic Pro may be the cause of the problem. I have since removed this progam about 3 weeks ago and have not suffered any APC Index Mismatch failures. I have also reported this to Iolo and they have sent an e-mail with details on clearing the registry and a new download. They also state that they hope to have a resolution in about two weeks. If you have SM Pro on your system, try removing it and see if your PC stablises.