4 Replies Latest reply on Dec 30, 2012 6:07 AM by Peter M

    mfehidk.sys Crash

      I wonder if you can pass this along to the developers? Tell them I will keep the DMP file for a while in case they need it.

      0: kd> !analyze -v
      *******************************************************************************
      * *
      * Bugcheck Analysis *
      * *
      *******************************************************************************

      DRIVER_POWER_STATE_FAILURE (9f)
      A driver is causing an inconsistent power state.
      Arguments:
      Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
      subsystem.
      Arg2: 0000000000000258, Timeout in seconds.
      Arg3: fffffa8003cff040, The thread currently holding on to the Pnp lock.
      Arg4: fffff80000b9c510

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


      DRVPOWERSTATE_SUBCODE: 4

      FAULTING_THREAD: fffffa8003cff040

      DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

      BUGCHECK_STR: 0x9F

      PROCESS_NAME: System

      CURRENT_IRQL: 2

      LAST_CONTROL_TRANSFER: from fffff80002c91052 to fffff80002c8fdda

      STACK_TEXT:
      fffff880`15112f80 fffff800`02c91052 : fffffa80`03cff040 fffffa80`03cff040 00000000`00000000 fffffa80`00000008 : nt!KiSwapContext+0x7a
      fffff880`151130c0 fffff800`02c931af : fffffa80`03cff040 00000000`00000000 00000000`00000013 fffff800`02e02e80 : nt!KiCommitThreadWait+0x1d2
      fffff880`15113150 fffff880`03f14fc7 : 00000000`00000000 fffff880`00000000 00000000`01b80700 fffffa80`09d25c00 : nt!KeWaitForSingleObject+0x19f
      fffff880`151131f0 fffff880`0df0ac16 : fffff880`0df17f68 fffff880`151133f8 fffff880`03f4a8f8 00000000`00000014 : mfehidk+0x2fc7
      fffff880`15113310 fffff880`0df085cd : 00000000`00000000 fffffa80`07367640 fffff880`151135c0 00000000`00000000 : mfeavfk+0x4c16
      fffff880`15113480 fffff880`03f2584e : 00000000`00000000 00000000`00000000 fffffa80`07367640 fffff880`151137f0 : mfeavfk+0x25cd
      fffff880`15113560 fffff880`03f1c232 : fffffa80`00faecc0 fffff880`151136d8 fffffa80`0a104000 00000000`0000000a : mfehidk+0x1384e
      fffff880`151135a0 fffff880`03f1c4ce : fffffa80`0979a960 fffff800`02dbd2dd fffffa80`0979a9f0 00000000`00000000 : mfehidk+0xa232
      fffff880`15113680 fffff880`03f375a5 : fffff8a0`00000000 fffffa80`0a75c040 00000000`00000000 fffffa80`0479a1b0 : mfehidk+0xa4ce
      fffff880`151137d0 fffff800`02f9d68f : 00000000`00000000 fffffa80`03cc74a0 00000000`00000000 fffffa80`0479a1b0 : mfehidk!DEVICEDISPATCH::DispatchPassThrough+0x5d
      fffff880`15113830 fffff800`02f83304 : 00000000`00000000 fffffa80`03cc74a0 00000000`0000000f fffff800`02ccc59e : nt!IopCloseFile+0x11f
      fffff880`151138c0 fffff800`02f9d181 : fffffa80`03cc74a0 fffffa80`00000001 fffff8a0`00001930 00000000`00000000 : nt!ObpDecrementHandleCount+0xb4
      fffff880`15113940 fffff800`02f9d094 : 00000000`00002310 fffffa80`03cc74a0 fffff8a0`00001930 00000000`00002310 : nt!ObpCloseHandleTableEntry+0xb1
      fffff880`151139d0 fffff800`02c89153 : fffffa80`03cff040 fffff880`15113aa0 fffffa80`05713190 00000000`00000000 : nt!ObpCloseHandle+0x94
      fffff880`15113a20 fffff800`02c856f0 : fffff880`01015bf1 00000000`00000000 00000000`00000000 fffffa80`05713000 : nt!KiSystemServiceCopyEnd+0x13
      fffff880`15113bb8 fffff880`01015bf1 : 00000000`00000000 00000000`00000000 fffffa80`05713000 fffffa80`05713100 : nt!KiServiceLinkage
      fffff880`15113bc0 fffff880`01009305 : fffffa80`057133d8 ffffffff`800025e8 ffffffff`80002500 fffffa80`05713100 : volsnap!VspRemoveLookupEntries+0xa1
      fffff880`15113c00 fffff880`01010e4d : fffffa80`05713190 00000000`00000000 fffffa80`04b594d0 00000000`00000001 : volsnap!VspCleanupFilter+0x475
      fffff880`15113cb0 fffff880`0144e54a : fffff880`02fd95d0 fffff880`02fd97c0 fffffa80`03cff040 00000000`00000000 : volsnap! ?? ::OKHAJAOM::`string'+0x19b
      fffff880`15113d30 fffff800`02c81d87 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsStorageDriverCallout+0x16
      fffff880`15113d60 fffff800`02c81d41 : 00000000`00000000 fffffa80`03cff040 fffff880`15114000 fffff800`02c9980a : nt!KySwitchKernelStackCallout+0x27
      fffff880`02fd94a0 fffff800`02c9980a : fffff8a0`69634d43 fffffa80`03cff040 00000000`00000000 fffff8a0`00140c30 : nt!KiSwitchKernelStackContinue
      fffff880`02fd94c0 fffff880`0145b3d5 : fffff880`0144e534 fffff880`02fd95d0 fffffa80`043f4400 fffff880`014ba700 : nt!KeExpandKernelStackAndCalloutEx+0x29a
      fffff880`02fd95a0 fffff880`015123ff : fffffa80`043f4401 fffffa80`09e31180 fffffa80`09e31180 00000000`00000000 : Ntfs!NtfsCallStorageDriver+0x31
      fffff880`02fd9600 fffff880`0151e20c : fffffa80`043f4450 fffff880`02fd9788 fffff880`02fd9790 00000000`00000001 : Ntfs!NtfsCommonPnp+0x16f
      fffff880`02fd96e0 fffff880`0120323f : fffffa80`04b59a68 fffffa80`04b594d0 fffff880`02fd9800 fffffa80`043f4450 : Ntfs!NtfsFsdPnp+0x1f0
      fffff880`02fd9780 fffff880`012016df : fffffa80`0a6ad630 fffff880`02fd9988 fffffa80`0a6ad600 fffffa80`04b594d0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
      fffff880`02fd9810 fffff880`03f375f1 : fffffa80`04b594d0 00000000`00000000 fffff8a0`00000000 00000000`000007ff : fltmgr!FltpDispatch+0xcf
      fffff880`02fd9870 fffff800`02ef5419 : fffffa80`049f6160 00000000`c00000bb fffff880`02fd9988 fffffa80`04b594d0 : mfehidk!DEVICEDISPATCH::DispatchPassThrough+0xa9
      fffff880`02fd98d0 fffff800`03073391 : fffffa80`049f6160 fffffa80`09e31030 fffffa80`05e15430 fffffa80`049f6160 : nt!IopSynchronousCall+0xc5
      fffff880`02fd9940 fffff800`0306de08 : fffffa80`05c51d90 fffffa80`049f6160 00000000`0000030a 00000000`00000308 : nt!IopRemoveDevice+0x101
      fffff880`02fd9a00 fffff800`03072ed7 : fffffa80`05e15430 00000000`00000000 00000000`00000003 fffff880`02fd9cb8 : nt!PnpSurpriseRemoveLockedDeviceNode+0x128
      fffff880`02fd9a40 fffff800`03072ff0 : 00000000`00000000 fffff8a0`0b632300 fffff8a0`0cf6a670 fffff880`02fd9b98 : nt!PnpDeleteLockedDeviceNode+0x37
      fffff880`02fd9a70 fffff800`03102f6f : 00000000`00000002 00000000`00000000 fffffa80`05e15430 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
      fffff880`02fd9ae0 fffff800`03103b2c : fffff880`02fd9cb8 fffffa80`0a248800 fffffa80`03cff000 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0x6cf
      fffff880`02fd9c20 fffff800`02feec48 : 00000000`00000000 fffffa80`0a248840 fffff8a0`0ae904e0 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c
      fffff880`02fd9c50 fffff800`02c97161 : fffff800`02ef4fc0 fffff8a0`0b6323b0 fffff800`02e2d5f8 fffffa80`03cff040 : nt! ?? ::NNGAKEGL::`string'+0x5abab
      fffff880`02fd9cb0 fffff800`02f2d166 : 00000000`00000000 fffffa80`03cff040 00000000`00000080 fffffa80`03cc74a0 : nt!ExpWorkerThread+0x111
      fffff880`02fd9d40 fffff800`02c68486 : fffff880`009eb180 fffffa80`03cff040 fffff880`009f5f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
      fffff880`02fd9d80 00000000`00000000 : fffff880`02fda000 fffff880`02fd4000 fffff880`02fd94a0 00000000`00000000 : nt!KxStartSystemThread+0x16


      STACK_COMMAND: .thread 0xfffffa8003cff040 ; kb

      FOLLOWUP_IP:
      mfehidk+2fc7
      fffff880`03f14fc7 488bcf mov rcx,rdi

      SYMBOL_STACK_INDEX: 3

      SYMBOL_NAME: mfehidk+2fc7

      FOLLOWUP_NAME: MachineOwner

      MODULE_NAME: mfehidk

      IMAGE_NAME: mfehidk.sys

      DEBUG_FLR_IMAGE_TIMESTAMP: 4a73695e

      FAILURE_BUCKET_ID: X64_0x9F_mfehidk+2fc7

      BUCKET_ID: X64_0x9F_mfehidk+2fc7

      Followup: MachineOwner
        • 1. RE: mfehidk.sys Crash
          Peter M
          You can do that now by contacting Technical Support Chat, linked in the link at top left. BSOD's involving mfehidk.sys have been the subject of several posts but I don't think anyone has found a permanent solution, although a forum search may come up with something.

          Technical Support is open 24/7 whereas now the weekend is upon us it is extremely unlikely any McAfee staff will put in an appearance here on the forums.
          • 2. Re: RE: mfehidk.sys Crash

            Hi

            I've had McAfee installed on my pc with XP Pro for some years.  Renewed subscription near end of July.  On 31 July noticed update going on in background.  Received note that update successful.  Then another to say restart necessary.  BSOD on restart with mfehidk.sys etc mentioned.

             

            Started contacting McAfee....   Had to use a notebook as in safemode could not use internet.  Was sent removal tool and then pc OK, but without McAfee.   Have had two sessions with tier two support working on pc remotely, reloading and each time they restart, BSOD appears.  Am concerned that so many crashes are affecting my machine as last attempt to start in safe mode was slow and difficult to get into.

             

            Another remote session was supposed to start this morning - with reassurances that they would phone at the time set (previous day call came through 7 hours late) and now two hours late and still no call.

             

            In spite of their courtesy and efforts, I'm wondering whether McAfee are anywhere close to sorting this problem out, as it seems to have been causing havoc for many months, judging by the hundreds of messages found when doing a net search...

             

            Has anyone had this problem and it has actually been resolved???

            • 3. Re: mfehidk.sys Crash

              I have windows 7 ultimate 64 bit, and constantly have BSOD with mfefirek.sys and mfehidk.sys as causes via analysis of memory.dmp. Any help would be appreciated.

              • 4. Re: mfehidk.sys Crash
                Peter M

                You need to give Technical Support Online Chat the opportunity to analyse as many cases as possible otherwise they'll never get to the bottom of this.  So I suggest contacting them.  Escalate the issue if necessary.

                 

                See the link under Useful Links at the top of this page.

                 

                That said, this is a very old thread and am assuming you are at least using the 2010 home products?

                 

                I think the issue is dealt with in the 2011 product release which is slowly filtering out to the various worldwide servers.

                 


                 

                 

                 

                Message was edited by: Ex_Brit on 30/12/12 7:07:19 EST AM