1 2 Previous Next 15 Replies Latest reply on Aug 8, 2011 5:55 AM by ketchup

    VSE 8.8 BSOD on Server 2008 R2

      We rolled out VSE 8.8 on Monday.  Starting Monday night our Backup Exec 2010 server (running on Windows Server 2008 R2) began crashing to a Blue Screen.  Here is the output of the memory.dmp as it was run through the debugger.  Anyone seen anything else like this? Interestingly enough, the crashes occurred at different times during the backup.  I have only stopped the crashes by completetly uninstalling Mcafee VSE 8.8 and the Mcafee Agent 4.5.

       

      *******************************************************************************
      *                                                                             *
      *                        Bugcheck Analysis                                   *
      *                                                                             *
      *******************************************************************************

      BAD_POOL_CALLER (c2)
      The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
      Arguments:
      Arg1: 0000000000000007, Attempt to free pool which was already freed
      Arg2: 0000000000001097, (reserved)
      Arg3: 0000000004090001, Memory contents of the pool block
      Arg4: fffffa8008fb0bd0, Address of the block of pool being deallocated

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

      Page 58f not present in the dump file. Type ".hh dbgerr004" for details
      Page 21fa06 not present in the dump file. Type ".hh dbgerr004" for details

      POOL_ADDRESS:  fffffa8008fb0bd0 Nonpaged pool

      FREED_POOL_TAG:  MFE0

      BUGCHECK_STR:  0xc2_7_MFE0

      DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

      PROCESS_NAME:  beremote.exe

      CURRENT_IRQL:  0

      LAST_CONTROL_TRANSFER:  from fffff80001bac60e to fffff80001a79740

      STACK_TEXT: 
      fffff880`0877d328 fffff800`01bac60e : 00000000`000000c2 00000000`00000007 00000000`00001097 00000000`04090001 : nt!KeBugCheckEx
      fffff880`0877d330 fffff880`07f9f4fe : 23080000`02100019 fffffa80`08fb0bd0 fffff880`3045464d fffffa80`09b096e0 : nt!ExDeferredFreePool+0x11eb
      fffff880`0877d3e0 fffff880`07f4fe1a : fffffa80`08fb0bd0 fffff880`07fb5628 fffffa80`09f2e1c0 fffff880`07fa65a0 : mfehidk!DEVICEDISPATCH::DispatchPassThrough+0x6cbe
      fffff880`0877d410 fffff880`07f50a6c : fffff880`07fb5628 fffffa80`09b096e0 00000000`00000000 fffffa80`090f5410 : mfehidk+0x13e1a
      fffff880`0877d440 fffff880`07f50c84 : 00000000`00000000 fffff880`0877d700 00000000`00000000 fffffa80`093707a0 : mfehidk+0x14a6c
      fffff880`0877d520 fffff880`07f53687 : 00000000`00000000 fffff880`0877d401 fffff880`0877d4f8 fffff880`07e60f05 : mfehidk+0x14c84
      fffff880`0877d5a0 fffff880`07f988ee : fffffa80`090f5410 fffffa80`09ca7750 fffffa80`09ca7750 fffff800`01d79f60 : mfehidk+0x17687
      fffff880`0877d6d0 fffff800`01d7a507 : 00000000`00000005 fffffa80`0e945b10 fffffa80`0e945b10 fffffa80`090f54a8 : mfehidk!DEVICEDISPATCH::DispatchPassThrough+0xae
      fffff880`0877d740 fffff800`01d70b84 : fffffa80`09ca8840 00000000`00000000 fffffa80`0e4ed850 fffff8a0`0000a001 : nt!IopParseDevice+0x5a7
      fffff880`0877d8d0 fffff800`01d75b4d : fffffa80`0e4ed850 fffff880`0877da30 fffff880`00000040 fffffa80`06a19750 : nt!ObpLookupObjectName+0x585
      fffff880`0877d9d0 fffff800`01d7c617 : 00000000`00000000 00000000`00000001 fffffa80`09aacb01 ffffffff`ffffffff : nt!ObOpenObjectByName+0x1cd
      fffff880`0877da80 fffff800`01d86360 : 00000000`0739e908 fffff8a0`80100080 fffff8a0`00e2e960 00000000`0739e918 : nt!IopCreateFile+0x2b7
      fffff880`0877db20 fffff800`01a78993 : 00000000`00007342 00000000`00000001 fffffa80`09aacb60 0000007f`ffffffff : nt!NtCreateFile+0x78
      fffff880`0877dbb0 00000000`772cfc0a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
      00000000`0739e888 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772cfc0a


      STACK_COMMAND:  kb

      FOLLOWUP_IP:
      mfehidk!DEVICEDISPATCH::DispatchPassThrough+6cbe
      fffff880`07f9f4fe 4883c428        add     rsp,28h

      SYMBOL_STACK_INDEX:  2

      SYMBOL_NAME:  mfehidk!DEVICEDISPATCH::DispatchPassThrough+6cbe

      FOLLOWUP_NAME:  MachineOwner

      MODULE_NAME: mfehidk

      IMAGE_NAME:  mfehidk.sys

      DEBUG_FLR_IMAGE_TIMESTAMP:  4d2e1e54

      FAILURE_BUCKET_ID:  X64_0xc2_7_MFE0_mfehidk!DEVICEDISPATCH::DispatchPassThrough+6cbe

      BUCKET_ID:  X64_0xc2_7_MFE0_mfehidk!DEVICEDISPATCH::DispatchPassThrough+6cbe

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

        • 1. VSE 8.8 BSOD on Server 2008 R2
          alexander_h

          What i could suggest you is to update all drivers, but if that is not helping you then you should try with any older version of VSe for example 8.7 p3(not causind BSOD)

          • 2. VSE 8.8 BSOD on Server 2008 R2
            psolinski

            We got BSoD once on one of our 2008R2 servers:

             

            MODULE_NAME: mfehidk

            FAULTING_MODULE: fffff80001657000 nt

            DEBUG_FLR_IMAGE_TIMESTAMP:  4d2e1e54

            POOL_ADDRESS:  fffffa80057134a0

            BUGCHECK_STR:  0xc2_7

            DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

            CURRENT_IRQL:  0

            LAST_CONTROL_TRANSFER:  from fffff800017fa60e to fffff800016c7740

             

            STACK_TEXT: 

            fffff880`054dd328 fffff800`017fa60e : 00000000`000000c2 00000000`00000007 00000000`00001097 00000000`04090013 : nt!KeBugCheckEx

            fffff880`054dd330 fffff880`014fb4fe : 130c0000`0210001a fffffa80`057134a0 00000000`3045464d fffffa80`05d1c8d0 : nt!ExDeleteNPagedLookasideList+0x704e

            fffff880`054dd3e0 fffff880`014abe1a : fffffa80`057134a0 fffff880`01511628 fffffa80`05fac1c0 fffff880`015025a0 : mfehidk!DEVICEDISPATCH::DispatchPassThrough+0x6cbe

            fffff880`054dd410 fffff880`014aca6c : fffff880`01511628 fffffa80`05d1c8d0 00000000`00000000 fffffa80`049ddd50 : mfehidk+0x13e1a

            fffff880`054dd440 fffff880`014acc84 : 00000000`00000000 fffff880`054dd701 00000000`00000000 fffffa80`04b963d0 : mfehidk+0x14a6c

            fffff880`054dd520 fffff880`014af687 : 00000000`00000000 fffff880`054dd801 00000000`00000001 fffff8a0`09f02030 : mfehidk+0x14c84

            fffff880`054dd5a0 fffff880`014f48ee : fffffa80`049ddd50 fffffa80`057a1c00 fffffa80`057a1c00 fffff800`019c7f60 : mfehidk+0x17687

            fffff880`054dd6d0 fffff800`019c8507 : 00000000`00000025 fffffa80`05383610 fffffa80`05383610 fffffa80`049ddde8 : mfehidk!DEVICEDISPATCH::DispatchPassThrough+0xae

            fffff880`054dd740 fffff800`019beb84 : fffffa80`04b91af0 00000000`00000000 fffffa80`0533f5f0 fffff880`054ddb01 : nt!SeUnlockSubjectContext+0x647

            fffff880`054dd8d0 fffff800`019c3b4d : fffffa80`0533f5f0 fffff880`054dda30 00000000`00000040 fffffa80`0360c4b0 : nt!SeQueryInformationToken+0x20b4

            fffff880`054dd9d0 fffff800`019ca617 : fffff8a0`746c6644 00000000`00000001 00000000`00000001 00000000`00000001 : nt!ObOpenObjectByName+0x1cd

            fffff880`054dda80 fffff800`019d4360 : 00000000`0402e7d8 fffff8a0`00100081 fffff8a0`0291d070 00000000`0402e7f0 : nt!SeUnlockSubjectContext+0x2757

            fffff880`054ddb20 fffff800`016c6993 : fffffa80`05027b30 00000000`00000001 fffffa80`05039a10 fffff800`019db254 : nt!NtCreateFile+0x78

            fffff880`054ddbb0 00000000`7712fc0a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x3a43

            00000000`0402e768 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7712fc0a

             

            STACK_COMMAND:  kb

             

            FOLLOWUP_IP:

            mfehidk!DEVICEDISPATCH::DispatchPassThrough+6cbe

            fffff880`014fb4fe 4883c428        add     rsp,28h

             

            SYMBOL_STACK_INDEX:  2

            SYMBOL_NAME:  mfehidk!DEVICEDISPATCH::DispatchPassThrough+6cbe

            FOLLOWUP_NAME:  MachineOwner

            IMAGE_NAME:  mfehidk.sys

            BUCKET_ID:  WRONG_SYMBOLS

             

            Followup: MachineOwner

            ---------

             

            0: kd> lmvm mfehidk

            start             end                 module name

            fffff880`01498000 fffff880`01529b80   mfehidk    (export symbols)       mfehidk.sys

                Loaded symbol image file: mfehidk.sys

                Image path: \SystemRoot\system32\drivers\mfehidk.sys

                Image name: mfehidk.sys

                Timestamp:        Wed Jan 12 21:34:12 2011 (4D2E1E54)

                CheckSum:         00098F72

                ImageSize:        00091B80

                Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

            • 3. VSE 8.8 BSOD on Server 2008 R2

              Nice to know it is not just us.  Sure we could try to update the server's driver, but considering that the faulting module is mfehidk.sys this defintely seems like a McAfee issue.

              • 4. VSE 8.8 BSOD on Server 2008 R2
                wwarren

                The alleged "faulting module" is the debugger's "best guess" after following a complex algorithm of looking for the first non-Microsoft driver in the stack.

                Sarcastic tone intended.

                 

                You should .zip up the dump, run our MER tool, and call it in to McAfee Support.

                Taking other measures like ensuring you have the latest drivers from vendors is always recommended - then seeing if the crash reoccurs. If that's not an option, we can work with what you have and see if root cause can be found.

                • 5. VSE 8.8 BSOD on Server 2008 R2
                  psolinski

                  Already there see: Service Request# 3-1418298821

                  • 6. VSE 8.8 BSOD on Server 2008 R2
                    alexander_h

                    i think that is a major problem with new vse 8.8 and in some cases vse8.7 p4

                    a have a couple of friends which have the same issue and every one is searching for work around you could try with vse p3 (i dont know for such problem with that version).

                    • 7. VSE 8.8 BSOD on Server 2008 R2

                      The bottom line is that the backup server was stable while running version 8.7.  We installed version 8.8 and the server began crashing that night, and every subsequent evening until version 8.8 was removed.  Maybe this is a weird Server 2008 R2 + Backup Exec 2010 R2 + version 8.8 = BSOD equation, but it definitely began with the install of 8.8.

                      • 8. VSE 8.8 BSOD on Server 2008 R2
                        alexander_h

                        i  think that in one Mcafee article there was info that this should resolved with McAfee agent 4.5 p3. But you should wait. for the moment you have to downgrade.

                        • 9. Re: VSE 8.8 BSOD on Server 2008 R2

                            The moment may have arrived.  I just had to rip McAfee VSE 8.8 and the agent off of my primary file server because it decided to BSOD on the mfehidk.sys this morning.  The file server is Windows Server 2008 R2 running in a VMWare vSphere 4.1 environment, so it is indeed on different "hardware" than my backup server.  Now my department gets to sit around nervously and take bets on what crashes next.  Yay!

                          1 2 Previous Next