Tech Support Forum banner

Bsod (apc_index_mismatch)

4275 Views 14 Replies 2 Participants Last post by  VirGnarus
First off, here is my hardware info:
  • Windows 7, 64-bit SP1
  • Processor: Intel Core i5 @ 2.80 GHz
  • Video Card: ATI Radeon HD 4670 512MB
  • MotherBoard: MSI socket 1156
  • RAM: 4 GB DDR3 1333MHz, Corsair
  • Power Supply: Corsair 450W
i have a problem with my desktop, i get BSOD with APC INDEX MISMATCH.
I attached the dump file...please help me
I have the same problem on my laptop, the same bsod and i think that it's from daemon tools.


Not open for further replies.
1 - 15 of 15 Posts
Is this a continuing experience, or is it just this one instance? It's best to just continue using the PC till it occurs again. If it does occur again, generate a report as described here. If not, write it off as just an occasional PC fluke.
i found the solution, it's about "pfc.sys".

Padus ASPI Shell ("pfc.sys") filter driver. Comes with Nero 6.x/7.x.x if you choose to install it, comes with WinDVD Creator, it comes with DiscJuggler and it comes with NVIDIA Purevideo decoder.

My event viewer say that:

\SystemRoot\SysWow64\drivers\pfc.sys has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.

The driver \Driver\pfc failed to load for the device IDE\CdRomASUS_DRW-1612BL_________________________1.06____\6&34e5885f&0&0.0.0.

And the solution is:

This error is caused by DEP (Data Execution Prevention). To fix it ...

Right click the My Computer icon, select Properties, in the new dialog, click the Advanced tab, in the Performance group click the Settings button, now click the Data Execution Prevention tab, now select Turn on DEP for all programs and services except those I select:, now click the Add button at the bottom and browse to C:\Windows\SysWow64\drivers\pfc.sys (assuming Windows is installed in the Windows folder on your C: drive) and select Open, ensure there is a tick next to the file you just added in the list, then click Apply. Close all open windows and restart your PC, the problem should now be gone.
See less See more
That may be a different situation than the bsod, especially considering that - at least from what I see - there's nothing related to either pfc or the software mentioned listed in currently loaded modules from the crashdump. The error also isn't relevant to what's occurred there. However, that is something that should be resolved anyways, so congrats on finding it out.
· OS - Windows 7 x64 SP1
· Age of system (hardware): 2 months
· Age of OS installation - 20 days
· CPU: Intel Core i5 760 @ 2.80 Ghz
· Video Card: Radeon HD 4670 512MB
· MotherBoard: MSI
· Power Supply - Corsair 650W



The bugcheck type and its consistency has it appear that a particular driver is causing the problem. There's other items in the crashdumps that also point to it.

I would mainly assume that this is caused by a user-mode application or service that did something funky. That means any program that doesn't relate to getting your hardware to work. I could tell you exactly what it is, by minidumps don't provide user-mode data, only windows kernel data (and very, very little of it).

My first level of concern is a program called Tuneup Utilities that you have installed. These kind of programs typically cause more woe than wonder, and given that reports of it occur in the event log at similar times to the crashes, and it's the kind of program i would expect to be performing this kind of behavior caught on the bugchecks, I'm going to have to assume this is the case for now. Plus it's better to get rid of it than keep it.
i removed the tuneup utilities 2011, and i get BSOD again.
i think that the problem it's from Kaspersky Internet Security 2011.:rolleyes:
i attached the last crashed file with bsod.


i removed the tuneup utilities 2011, and i get BSOD again.
i think that the problem it's from Kaspersky Internet Security 2011.:rolleyes:
i attached the last crashed file with bsod.

problem solved :D thank you
Great to hear, mate. Was it in fact Kaspersky?
Kaspersky it's ok, the problem was: Tuneup Utilities 2011 and Universal Shield 4.4 by Everstrike Software
That program evaded me. Thanks for the heads-up. Glad to help.
1 - 15 of 15 Posts
Not open for further replies.