Apc Index Mismatch

Seymore4Head wrote:
I got this screen.
I rebooted and it seems fine.
Any thing you can add to the cause of the error?
http://imgur.com/a/Bxwo6
I just started using AHCI

The root cause is a driver-level issue.

https://docs.microsoft.com/en-us/win...index-mismatch

"you can use Static Driver Verifier, a static
analysis tool available in the Windows Driver Kit,
to detect problems in your code before you ship
your driver. Run Static Driver Verifier with the
CriticalRegions rule to verify that your source code
uses these system calls in correct sequence.
"

Well, obviously you're not going to do that.

I doubt this is the actual MSAHCI driver doing it.

So where else can we look ?

fltmc filters

That will show the filter drivers loaded in the storage stack.
But I don't know if a filter driver, can wedge into
the stuff described in that article.

You might consider reviewing the hardware in the
computer, and whether any weird storage drivers
are present. Chips that used in-box drivers are
probably not the problem - the Intel Southbridge
is probably using MSAHCI. But it could be some
other kind of unique storage device, has a private
driver. A driver you installed from a CD or mini-CD.
A driver that was intended for some other OS maybe
(and the INF was improperly encoded, to allow installation
just about anywhere).

Also, see if you can get a driver name, associated with
that dump. Maybe there is something recorded in Event Viewer ?
The fault might still be recorded against "msahci", but
it doesn't hurt to have a look.

Paul

On 8/9/2017 8:59 PM, Seymore4Head wrote:
I got this screen.
I rebooted and it seems fine.
Any thing you can add to the cause of the error?
http://imgur.com/a/Bxwo6
I just started using AHCI

This looks like a good idea

If you are not equipped to use the Windows debugger to work on this
problem, you can use some basic troubleshooting techniques.

Check the System Log in Event Viewer for additional error messages
that might help identify the device or driver that is causing this bug
check.

If a driver is identified in the bug check message, disable the
driver or check with the manufacturer for driver updates.

Confirm that any new hardware that is installed is compatible with
the installed version of Windows. For example, you can get information
about required hardware at Windows 10 Specifications.

For additional general troubleshooting information, see Blue Screen
Data.

This is a kernel internal error. This error occurs on exit from a system
call. A possible cause for this bug check is when a file system or
driver has a mismatched sequence of system calls to enter or leave
guarded or critical regions. For example, each call to
KeEnterCriticalRegion must have a matching call to
KeLeaveCriticalRegion. If you are developing a driver, you can use
Static Driver Verifier, a static analysis tool available in the Windows
Driver Kit, to detect problems in your code before you ship your driver.
Run Static Driver Verifier with the CriticalRegions rule to verify that
your source code uses these system calls in correct sequence.


https://docs.microsoft.com/en-us/win...index-mismatch

I got this screen.
I rebooted and it seems fine.
Any thing you can add to the cause of the error?
http://imgur.com/a/Bxwo6
I just started using AHCI

Seymore4Head wrote:
On Wed, 09 Aug 2017 20:59:03 -0700, Seymore4Head
wrote:

I got this screen.
I rebooted and it seems fine.
Any thing you can add to the cause of the error?
http://imgur.com/a/Bxwo6
I just started using AHCI

I have the event viewer, but what file should I look for?

As far as all the other advice, it is over my head.

Thanks

OK, tell us something unique about your hardware.

What kinda stuff you got plugged in ?

What kinda computer is it, make and model ?

Did you add PCI Express SATA cards ? (I have one
in my newest machine, to protect the motherboard.)

What port is the SATA drive plugged into ? Southbridge ?
(sometimes they're color coded, and the ones that
are a "different color" are the add-on chip
SATA interfaces).

Is there anything unique about the drive ? Is
it an Alien Spaceship drive with SATA port ?
Or a WD Green ?

Just for the record, I've never heard of that error
before. You have a good puzzle in hand.

*******

http://www.visualstudioextensibility.com/2016/10/

"Update Nov 9, 2016:

The BSOD crash APC_INDEX_MISMATCH was caused by an update
to the Trend Micro Antivirus+ 2016. The solution is to
update to Trend Micro Antivirus+ 2017, as explained in
their web page Getting stuck on Windows Startup Repair
after updating Trend Micro Security."

Naughty, AVs playing with driver stacks ?

*******

This is an example of someone else getting one of those.

"On Tue 20.12.2016 / 23:06:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122116-32500-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x1 (0x7F , 0x0, 0xFFF, 0xFFFFC680CD0ACCC0)

Error: APC_INDEX_MISMATCH

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft Windows Operating System

description: NT Kernel & System

Bug check description:

This indicates that there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem
is caused by another drivers that cannot be identified at this time.
"

Which means it might not be that easy to find. The individual
in that example, was getting audio problems just before the crash.

*******

Someone here gets that error while playing the game Overwatch.

https://www.sevenforums.com/bsod-hel..._or_equal.html

*******

This event viewer example, unfortunately, doesn't show an APC mismatch,
so isn't a perfect example of where to look. Using the date/time of
when the computer crashed, is going to make it easier to spot
any entry the computer might have created. For example, if
might have had a problem a few moments before the crash happened,
and there's a bread crumb there for you.

http://cdn.overclock.net/b/b0/b04e2e54_Image1.jpeg

Paul

On Wed, 09 Aug 2017 20:59:03 -0700, Seymore4Head
wrote:

I got this screen.
I rebooted and it seems fine.
Any thing you can add to the cause of the error?
http://imgur.com/a/Bxwo6
I just started using AHCI

I have the event viewer, but what file should I look for?

As far as all the other advice, it is over my head.

Thanks

Seymore4Head wrote:
On Wed, 09 Aug 2017 20:59:03 -0700, Seymore4Head
wrote:

I got this screen.
I rebooted and it seems fine.
Any thing you can add to the cause of the error?
http://imgur.com/a/Bxwo6
I just started using AHCI

Here are a few places that might be of interest to you. They mean
nothing to me.

http://imgur.com/a/o3wY0

BTW there are an extremely large number of amdkmdag events

amdkmdag is addressed here.

https://answers.microsoft.com/en-us/...a5d4cc7?auth=1

"DRM for video"

It has something to do with protected content and using
HDCP on the link between the video card and HD monitor.

That probably isn't causing the other problem.

*******

The BUGCHECK might be your APC Index Mismatch.
I don't really expect the system to be clever enough
to cough up a driver name, but you should review the
BUGCHECK entry anyway.

*******

As for NOVERT, if it runs in DOSBOX, can any side effects
escape to the hardware platform ? That doesn't seem likely
somehow. But I haven't used DOSBOX and don't know
how insulating it is.

*******

Are you using the same video driver, as on your original
Win7 install ?

Apparently DOSBOX uses DirectDraw to represent graphics
inside the box, even though the games themselves might not.

*******

This article claims a music player can be the culprit.

https://support.microsoft.com/en-us/...-or-in-windows

"When a MTP or WPD device connects to the computer for
the first time, the composite bus enumerator detects the
device and tries to install the WPD composite driver.
During the installation process, the third-party application
may run a USB device reset command. If the reset command
occurs in a certain period, the race condition occurs.
This certain period is after the MTP and USB driver or
the MTP and IP driver is installed and before the MTP
composite multiple transport driver is installed.
"

That doesn't sound like yours.

*******

And the Answers forum, expects you to enjoy long homework assignments.

https://answers.microsoft.com/en-us/...7-64a27f7262a7

I wish I had a strong sense that analysis will fix this one.
More likely, a lucky guess is what will fix it :-( As it doesn't
sound like the bugcheck records the right stuff to make an
instant answer possible.

Paul

On Thu, 10 Aug 2017 13:23:56 -0400, Paul
wrote:

Seymore4Head wrote:
On Wed, 09 Aug 2017 20:59:03 -0700, Seymore4Head
wrote:

I got this screen.
I rebooted and it seems fine.
Any thing you can add to the cause of the error?
http://imgur.com/a/Bxwo6
I just started using AHCI

I have the event viewer, but what file should I look for?

As far as all the other advice, it is over my head.

Thanks

OK, tell us something unique about your hardware.

What kinda stuff you got plugged in ?

What kinda computer is it, make and model ?

Did you add PCI Express SATA cards ? (I have one
in my newest machine, to protect the motherboard.)

What port is the SATA drive plugged into ? Southbridge ?
(sometimes they're color coded, and the ones that
are a "different color" are the add-on chip
SATA interfaces).

Is there anything unique about the drive ? Is
it an Alien Spaceship drive with SATA port ?
Or a WD Green ?

Just for the record, I've never heard of that error
before. You have a good puzzle in hand.

*******

http://www.visualstudioextensibility.com/2016/10/

"Update Nov 9, 2016:

The BSOD crash APC_INDEX_MISMATCH was caused by an update
to the Trend Micro Antivirus+ 2016. The solution is to
update to Trend Micro Antivirus+ 2017, as explained in
their web page Getting stuck on Windows Startup Repair
after updating Trend Micro Security."

Naughty, AVs playing with driver stacks ?

*******

This is an example of someone else getting one of those.

"On Tue 20.12.2016 / 23:06:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122116-32500-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x1 (0x7F , 0x0, 0xFFF, 0xFFFFC680CD0ACCC0)

Error: APC_INDEX_MISMATCH

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft Windows Operating System

description: NT Kernel & System

Bug check description:

This indicates that there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem
is caused by another drivers that cannot be identified at this time.
"

Which means it might not be that easy to find. The individual
in that example, was getting audio problems just before the crash.

*******

Someone here gets that error while playing the game Overwatch.

https://www.sevenforums.com/bsod-hel..._or_equal.html

*******

This event viewer example, unfortunately, doesn't show an APC mismatch,
so isn't a perfect example of where to look. Using the date/time of
when the computer crashed, is going to make it easier to spot
any entry the computer might have created. For example, if
might have had a problem a few moments before the crash happened,
and there's a bread crumb there for you.

http://cdn.overclock.net/b/b0/b04e2e54_Image1.jpeg

Paul
My machine is an I7
I have two SSD drives and a video card.
I also have a tuner card that is plugged in but I don't have the
drivers installed.

I have been using the same machine for a long time. The only thing
significant can think of is the when I got my second SSD drive I
reformatted and installed Win7 new again and it failed some updates
including the service pack. I ended up turning off updates.

When I changed my Bios to AHCI and that seemed to work fine, I turned
updates back on and it tried to install about 180 updates.
I did a fresh format and reinstalled Windows. I ran the first set of
updates and they installed fine including Sp1.

Last night when I went to bed an update started and it failed again
this morning when I booted up and reverted.

I tried using a program called NOVERT to get Doom 2 working with
steam. Steam is using some kind of dos box to run this old game on
Win7

On Wed, 09 Aug 2017 20:59:03 -0700, Seymore4Head
wrote:

I got this screen.
I rebooted and it seems fine.
Any thing you can add to the cause of the error?
http://imgur.com/a/Bxwo6
I just started using AHCI

Here are a few places that might be of interest to you. They mean
nothing to me.

http://imgur.com/a/o3wY0

BTW there are an extremely large number of amdkmdag events

On Thu, 10 Aug 2017 19:49:12 -0400, Paul
wrote:

Seymore4Head wrote:
On Wed, 09 Aug 2017 20:59:03 -0700, Seymore4Head
wrote:

I got this screen.
I rebooted and it seems fine.
Any thing you can add to the cause of the error?
http://imgur.com/a/Bxwo6
I just started using AHCI

Here are a few places that might be of interest to you. They mean
nothing to me.

http://imgur.com/a/o3wY0

BTW there are an extremely large number of amdkmdag events

amdkmdag is addressed here.

https://answers.microsoft.com/en-us/...a5d4cc7?auth=1

"DRM for video"

It has something to do with protected content and using
HDCP on the link between the video card and HD monitor.

That probably isn't causing the other problem.

*******

The BUGCHECK might be your APC Index Mismatch.
I don't really expect the system to be clever enough
to cough up a driver name, but you should review the
BUGCHECK entry anyway.

*******

As for NOVERT, if it runs in DOSBOX, can any side effects
escape to the hardware platform ? That doesn't seem likely
somehow. But I haven't used DOSBOX and don't know
how insulating it is.

*******

Are you using the same video driver, as on your original
Win7 install ?

Apparently DOSBOX uses DirectDraw to represent graphics
inside the box, even though the games themselves might not.

*******

This article claims a music player can be the culprit.

https://support.microsoft.com/en-us/...-or-in-windows

"When a MTP or WPD device connects to the computer for
the first time, the composite bus enumerator detects the
device and tries to install the WPD composite driver.
During the installation process, the third-party application
may run a USB device reset command. If the reset command
occurs in a certain period, the race condition occurs.
This certain period is after the MTP and USB driver or
the MTP and IP driver is installed and before the MTP
composite multiple transport driver is installed.
"

That doesn't sound like yours.

*******

And the Answers forum, expects you to enjoy long homework assignments.

https://answers.microsoft.com/en-us/...7-64a27f7262a7

I wish I had a strong sense that analysis will fix this one.
More likely, a lucky guess is what will fix it :-( As it doesn't
sound like the bugcheck records the right stuff to make an
instant answer possible.

Paul

I have the same video card and driver.
The problem hasn't showed up again.
Unless it does it again, I am not going to worry about it.


Thanks

On 8/11/2017 1:40 AM, Seymore4Head wrote:
On Thu, 10 Aug 2017 19:49:12 -0400, Paul
wrote:

Seymore4Head wrote:
On Wed, 09 Aug 2017 20:59:03 -0700, Seymore4Head
wrote:

I got this screen.
I rebooted and it seems fine.
Any thing you can add to the cause of the error?
http://imgur.com/a/Bxwo6
I just started using AHCI

Here are a few places that might be of interest to you. They mean
nothing to me.

http://imgur.com/a/o3wY0

BTW there are an extremely large number of amdkmdag events

amdkmdag is addressed here.

https://answers.microsoft.com/en-us/...a5d4cc7?auth=1

"DRM for video"

It has something to do with protected content and using
HDCP on the link between the video card and HD monitor.

That probably isn't causing the other problem.

*******

The BUGCHECK might be your APC Index Mismatch.
I don't really expect the system to be clever enough
to cough up a driver name, but you should review the
BUGCHECK entry anyway.

*******

As for NOVERT, if it runs in DOSBOX, can any side effects
escape to the hardware platform ? That doesn't seem likely
somehow. But I haven't used DOSBOX and don't know
how insulating it is.

*******

Are you using the same video driver, as on your original
Win7 install ?

Apparently DOSBOX uses DirectDraw to represent graphics
inside the box, even though the games themselves might not.

*******

This article claims a music player can be the culprit.

https://support.microsoft.com/en-us/...-or-in-windows

"When a MTP or WPD device connects to the computer for
the first time, the composite bus enumerator detects the
device and tries to install the WPD composite driver.
During the installation process, the third-party application
may run a USB device reset command. If the reset command
occurs in a certain period, the race condition occurs.
This certain period is after the MTP and USB driver or
the MTP and IP driver is installed and before the MTP
composite multiple transport driver is installed.
"

That doesn't sound like yours.

*******

And the Answers forum, expects you to enjoy long homework assignments.

https://answers.microsoft.com/en-us/...7-64a27f7262a7

I wish I had a strong sense that analysis will fix this one.
More likely, a lucky guess is what will fix it :-( As it doesn't
sound like the bugcheck records the right stuff to make an
instant answer possible.

Paul

I have the same video card and driver.
The problem hasn't showed up again.
Unless it does it again, I am not going to worry about it.


Thanks


Glad it appears to have sorted itself out. I'd consider a fallback
position - doing some standard maintenance, clean the dust out of
everywhere, replace the heat sink grease if that's needed, reseat cables
and RAM. I've got nothing else. Good luck.