Random Daily BSOD latest is APC_INDEX_MISMATCH


  1. Posts : 4
    windows 7 pro x64
       #1

    Random Daily BSOD latest is APC_INDEX_MISMATCH


    I have a customer running an intel based Windows 7 Pro x86 system with 6gb of memory. Onboard video and no attached peripheral devices. Standard usb mouse and keyboard.
    Over the past month he has been getting BSOD at least once per week, and more recently it has become daily. Each time the BSOD is a different message in the dmp file.
    I have loaded all the latest drivers from the manufacturer and from intel directly as well. The BIOS has also been updated to the latest. McAfee AV was installed until yesterday when I removed it.
    Upon first boot this morning from a cold start, I received a BSOD showing 0x0000007f

    Attached are all the files from the SF Diagnostic.

    Please help me out :)
    Last edited by ROLSEN74; 30 Jan 2013 at 12:06.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    ROLSEN74, An APC index mismatch bugcheck is a very rare one. As far as I have noticed, it is caused by a third party security program, and removing them usually solves the issue.

    Code:
    96e1f29c  8b7ba998Unable to load image \SystemRoot\system32\drivers\mfehidk.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for mfehidk.sys
    *** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
     mfehidk+0x64998
    You have McAfee installed, which is a very common and widely found cause of BSODs. If it is present in the system, it make a lot of troubles. Not only BSOD, but also network troubles and a lot. Uninstall McAfee Using McAfee Removal Tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
    Download, install and update those, and then run full system scans with both of them, one by one.

    Free up the startup.

    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 the restart.

    Let us know the results.
      My Computer


  3. Posts : 15,026
    Windows 10 Home 64Bit
       #3

    Arc is right about McAfee, but in case this is a corporate PC I guess you'd have some restrictions on removing some programs?

    Also, to make use of all 6 GB RAM, you'll have to do a fresh install of the 64 bit Windows 7.
      My Computer


  4. Posts : 4
    windows 7 pro x64
    Thread Starter
       #4

    Thank you both for the response. I am currently running through the cleanup process for McAfee and in fact yesterday I had told them that McAfee was likely the culprit in one way or another. But, had nothing to prove it.
    They have McAfee deployed through sonicwall and personally I hate McAfee, we almost always use Vipre and in some cases Norton.
    I will let you know how things go after the cleanup and time will only tell if the BSOD is gone.

    I assume that the earlier dmp files also pointed to McAfee as well?

    Thanks again!
      My Computer


  5. Posts : 15,026
    Windows 10 Home 64Bit
       #5

    Yup, the code highlighted in red..
    Here's the description: Driver Reference Table - mfehidk.sys
      My Computer


  6. Posts : 4
    windows 7 pro x64
    Thread Starter
       #6

    Okay, so the BSOD is till persisting. I have removed McAfee using the removal tool, and run full scans of Security Esstials and MalwareBytes with nothing found. I let this system run over night as thats when the BSOD's had usually occurred. I ran who Crashed as well after the BSOD's and it showed cng.sys as the cause.
    I am uoloading the SF Diag scan results again.

    Thanks for the assist!
      My Computer


  7. Posts : 15,026
    Windows 10 Home 64Bit
       #7

    Upload a screenshot of your hard disk using CrystalDiskInfo:

    Make a hard drive test from the hard drive manufacturers website:

    Run Disk Check on your hard disk for file system errors and bad sectors on it:


    Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.


    The goal is to test all the RAM sticks and all the motherboard slots.

    Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

    If you get errors, stop the test and continue with the next step.

    1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
    *Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
    If this stick passes the test then go to step #3.

    2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
    *If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
    *If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
    3. Test the next stick of RAM (stick #2) in the next motherboard slot.
    *If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
    *If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
    4. If you find a stick that passes the test, test it in all the other motherboard slots.

    If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

    In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
       Information
    Errors are sometimes found after 8 passes.

       Tip
    Do this test overnight, before going to bed.

    If Memtest86+ does not find any errors with ram run Windows Memory Diagnostics for 7-8 passes following its tutorial: Memory Diagnostics Tool
      My Computer


  8. Posts : 4
    windows 7 pro x64
    Thread Starter
       #8

    Update:
    I ran everything suggested above and had memory tests and chkdsk's without error. But, the BSOD's continued.
    The disk had been wiped and OS reloaded 4 times over the course of the past 6 months and always had blue screens.

    I am replacing the motherboard and memory under warranty, and hopefully this will arrive today so I can put this one to bed.
      My Computer


  9. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #9

    You can change the hardware, but before doing that, check the software part one more time. Enable Driver Verifier to monitor the drivers.
    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.

       Tip



    Let us know the results, with the subsequent crash dumps, if any.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 11:53.
Find Us