0 Replies Latest reply on Oct 21, 2013 8:09 PM by shinjiman

    Intel 82579LM NIC driver memory leak in HCK for Windows 8.1

    shinjiman

      Hi I've got a motherboard with the Intel 82579LM NIC adapter and trying to do the HCK test for it. However it encountered the issues during the "System - Sleep and PNP (disable and enable) with IO before and after", and a bugcheck was thrown. I've installed the Windows debugger and trace the memory dump file, and noticed there's memory leak on the NIC driver, for both inbox and the latest network driver in the 18.7 driver pack.

       

      So is that there's the bug in the driver file, or the NIC itself got the issue so I need another one to do the same test?

       

      ============================================================

       

      Here's the bugcheck analysis for the inbox Windows 8.1 driver (e1i63x64.sys):

       

      *******************************************************************************

      *                                                                             *

      *                        Bugcheck Analysis                                    *

      *                                                                             *

      *******************************************************************************

       

       

      Use !analyze -v to get detailed debugging information.

       

       

      BugCheck C4, {62, ffffe00001d0bae0, ffffe000039f5a30, 1}

       

       

      Probably caused by : e1i63x64.sys

       

       

      Followup: MachineOwner

      ---------

       

       

      7: kd> !analyze -v

      *******************************************************************************

      *                                                                             *

      *                        Bugcheck Analysis                                    *

      *                                                                             *

      *******************************************************************************

       

       

      DRIVER_VERIFIER_DETECTED_VIOLATION (c4)

      A device driver attempting to corrupt the system has been caught.  This is

      because the driver was specified in the registry as being suspect (by the

      administrator) and the kernel has enabled substantial checking of this driver.

      If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will

      be among the most commonly seen crashes.

      Arguments:

      Arg1: 0000000000000062, A driver has forgotten to free its pool allocations prior to unloading.

      Arg2: ffffe00001d0bae0, name of the driver having the issue.

      Arg3: ffffe000039f5a30, verifier internal structure with driver information.

      Arg4: 0000000000000001, total # of (paged+nonpaged) allocations that weren't freed.

        Type !verifier 3 drivername.sys for info on the allocations

        that were leaked that caused the bugcheck.

       

       

      Debugging Details:

      ------------------

       

       

       

       

      BUGCHECK_STR:  0xc4_62

       

       

      IMAGE_NAME:  e1i63x64.sys

       

       

      DEBUG_FLR_IMAGE_TIMESTAMP:  51496739

       

       

      MODULE_NAME: e1i63x64

       

       

      FAULTING_MODULE: fffff80002974000 e1i63x64

       

       

      VERIFIER_DRIVER_ENTRY: dt nt!_MI_VERIFIER_DRIVER_ENTRY ffffe000039f5a30

      Symbol nt!_MI_VERIFIER_DRIVER_ENTRY not found.

       

       

      DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

       

       

      PROCESS_NAME:  System

       

       

      CURRENT_IRQL:  2

       

       

      ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

       

       

      LAST_CONTROL_TRANSFER:  from fffff801c28e66a8 to fffff801c23c70a0

       

       

      STACK_TEXT: 

      ffffd000`20c8d488 fffff801`c28e66a8 : 00000000`000000c4 00000000`00000062 ffffe000`01d0bae0 ffffe000`039f5a30 : nt!KeBugCheckEx

      ffffd000`20c8d490 fffff801`c28eac4a : fffff800`02974000 ffffe000`01d0ba20 00000000`00000016 00000000`ffffffff : nt!VerifierBugCheckIfAppropriate+0x3c

      ffffd000`20c8d4d0 fffff801`c24232e8 : 00000000`00000000 00000000`00001000 0000007f`00000001 ffffe000`0139a690 : nt!VfPoolCheckForLeaks+0x4a

      ffffd000`20c8d510 fffff801`c28d8060 : fffff801`c2523cc0 fffff801`c2523cc0 ffffe000`01d0ba20 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x4bd58

      ffffd000`20c8d5a0 fffff801`c274b6c6 : 00000000`00000000 ffffe000`01d0ba20 ffffc000`02be8b40 ffffe000`016027e0 : nt!VfDriverUnloadImage+0x34

      ffffd000`20c8d5d0 fffff801`c274b630 : 00000000`00000000 ffffe000`01d0ba20 ffffe000`016027e0 ffffe000`016027e0 : nt!MiUnloadSystemImage+0x7e

      ffffd000`20c8d650 fffff801`c274b578 : 00000000`00000000 ffffe000`00144420 ffffe000`016027e0 00000000`76697244 : nt!MmUnloadSystemImage+0x20

      ffffd000`20c8d680 fffff801`c2628f28 : 00000000`00000000 ffffe000`016027e0 ffffe000`00144420 ffffe000`01c78050 : nt!IopDeleteDriver+0x40

      ffffd000`20c8d6c0 fffff801`c22df05f : 00000000`00000000 ffffe000`01c78050 ffffe000`016027e0 ffffe000`01c78020 : nt!ObpRemoveObjectRoutine+0x64

      ffffd000`20c8d720 fffff801`c268c79f : ffffe000`01c78050 ffffe000`00144580 ffffd000`20c8d650 ffffe000`00000004 : nt!ObfDereferenceObject+0x8f

      ffffd000`20c8d760 fffff801`c2628f28 : ffffcf80`14ba4fd0 00000000`00000024 ffffe000`011e8880 ffffe000`019c6880 : nt!IopDeleteDevice+0x47

      ffffd000`20c8d790 fffff801`c22df05f : 00000000`00000000 00000000`00000000 ffffe000`01c78050 ffffe000`019c6870 : nt!ObpRemoveObjectRoutine+0x64

      ffffd000`20c8d7f0 fffff801`c232d705 : ffffe000`011ef490 ffffe000`012222d0 00000000`00000000 ffffffff`80000a30 : nt!ObfDereferenceObject+0x8f

      ffffd000`20c8d830 fffff801`c26956b1 : ffffe000`011e8880 ffffe000`011ef490 ffffc000`005a29a0 ffffe000`011e8880 : nt!PnpRemoveLockedDeviceNode+0x245

      ffffd000`20c8d890 fffff801`c269562a : 00000000`00000000 ffffc000`005a29a0 ffffe000`011ef490 00000000`3f051397 : nt!PnpDeleteLockedDeviceNode+0x4d

      ffffd000`20c8d8d0 fffff801`c26949c7 : ffffe000`011e8880 ffffd000`00000002 00000000`00000000 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0x9a

      ffffd000`20c8d950 fffff801`c268ea15 : ffffc000`0261fd00 00000000`00000001 ffffc000`00000000 ffffe000`ffffffff : nt!PnpProcessQueryRemoveAndEject+0x4ef

      ffffd000`20c8dab0 fffff801`c268ed4f : ffffc000`0261fda0 00000000`00000000 00000000`00000000 fffff801`c268ea30 : nt!PnpProcessTargetDeviceEvent+0x9d

      ffffd000`20c8daf0 fffff801`c22b33cd : fffff801`c268ea30 ffffc000`0133baf0 ffffd000`20c8dbd0 ffffe000`04120ea0 : nt!PnpDeviceEventWorker+0x31f

      ffffd000`20c8db50 fffff801`c235e664 : 29292929`29292929 ffffe000`0010f040 ffffe000`0010f040 ffffe000`000e4040 : nt!ExpWorkerThread+0x2b5

      ffffd000`20c8dc00 fffff801`c23cd6c6 : fffff801`c2568180 ffffe000`0010f040 fffff801`c25c0a80 29292929`29292929 : nt!PspSystemThreadStartup+0x58

      ffffd000`20c8dc60 00000000`00000000 : ffffd000`20c8e000 ffffd000`20c88000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

       

       

       

       

      STACK_COMMAND:  kb

       

       

      FOLLOWUP_NAME:  MachineOwner

       

       

      FAILURE_BUCKET_ID:  0xc4_62_VRF_LEAKED_POOL_IMAGE_e1i63x64.sys

       

       

      BUCKET_ID:  0xc4_62_VRF_LEAKED_POOL_IMAGE_e1i63x64.sys

       

       

      ANALYSIS_SOURCE:  KM

       

       

      FAILURE_ID_HASH_STRING:  km:0xc4_62_vrf_leaked_pool_image_e1i63x64.sys

       

       

      FAILURE_ID_HASH:  {59f6d737-59ca-a5da-318f-81cc8365781f}

       

       

      Followup: MachineOwner

      ---------

       

      ============================================================

       

      Here's the bugcheck analysis for the latest 18.7 Intel NIC driver package for Windows 8.1 (e1c64x64.sys):

       

      *******************************************************************************

      *                                                                             *

      *                        Bugcheck Analysis                                    *

      *                                                                             *

      *******************************************************************************

       

       

      Use !analyze -v to get detailed debugging information.

       

       

      BugCheck C4, {62, ffffe000020fcb50, ffffe00001d2fb40, 1}

       

       

      *** ERROR: Module load completed but symbols could not be loaded for e1c64x64.sys

      Probably caused by : e1c64x64.sys

       

       

      Followup: MachineOwner

      ---------

       

       

      7: kd> !analyze -v

      *******************************************************************************

      *                                                                             *

      *                        Bugcheck Analysis                                    *

      *                                                                             *

      *******************************************************************************

       

       

      DRIVER_VERIFIER_DETECTED_VIOLATION (c4)

      A device driver attempting to corrupt the system has been caught.  This is

      because the driver was specified in the registry as being suspect (by the

      administrator) and the kernel has enabled substantial checking of this driver.

      If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will

      be among the most commonly seen crashes.

      Arguments:

      Arg1: 0000000000000062, A driver has forgotten to free its pool allocations prior to unloading.

      Arg2: ffffe000020fcb50, name of the driver having the issue.

      Arg3: ffffe00001d2fb40, verifier internal structure with driver information.

      Arg4: 0000000000000001, total # of (paged+nonpaged) allocations that weren't freed.

        Type !verifier 3 drivername.sys for info on the allocations

        that were leaked that caused the bugcheck.

       

       

      Debugging Details:

      ------------------

       

       

       

       

      BUGCHECK_STR:  0xc4_62

       

       

      IMAGE_NAME:  e1c64x64.sys

       

       

      DEBUG_FLR_IMAGE_TIMESTAMP:  521491e0

       

       

      MODULE_NAME: e1c64x64

       

       

      FAULTING_MODULE: fffff80001a00000 e1c64x64

       

       

      VERIFIER_DRIVER_ENTRY: dt nt!_MI_VERIFIER_DRIVER_ENTRY ffffe00001d2fb40

      Symbol nt!_MI_VERIFIER_DRIVER_ENTRY not found.

       

       

      DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

       

       

      PROCESS_NAME:  System

       

       

      CURRENT_IRQL:  2

       

       

      ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

       

       

      LAST_CONTROL_TRANSFER:  from fffff800930f26a8 to fffff80092bd30a0

       

       

      STACK_TEXT: 

      ffffd000`38334488 fffff800`930f26a8 : 00000000`000000c4 00000000`00000062 ffffe000`020fcb50 ffffe000`01d2fb40 : nt!KeBugCheckEx

      ffffd000`38334490 fffff800`930f6c4a : fffff800`01a00000 ffffe000`020fca90 00000000`00000016 00000000`ffffffff : nt!VerifierBugCheckIfAppropriate+0x3c

      ffffd000`383344d0 fffff800`92c2f2e8 : 00000000`00000000 00000000`00001000 0000007f`00000001 ffffe000`0308b9a0 : nt!VfPoolCheckForLeaks+0x4a

      ffffd000`38334510 fffff800`930e4060 : fffff800`92d2fcc0 fffff800`92d2fcc0 ffffe000`020fca90 00000000`00000059 : nt! ?? ::FNODOBFM::`string'+0x4bd58

      ffffd000`383345a0 fffff800`92f576c6 : 00000000`00000000 ffffe000`020fca90 ffffc000`0278cf10 ffffe000`040aa690 : nt!VfDriverUnloadImage+0x34

      ffffd000`383345d0 fffff800`92f57630 : 00000000`00000000 ffffe000`020fca90 ffffe000`040aa690 ffffe000`040aa690 : nt!MiUnloadSystemImage+0x7e

      ffffd000`38334650 fffff800`92f57578 : 00000000`00000000 ffffe000`00144420 ffffe000`040aa690 00000000`76697244 : nt!MmUnloadSystemImage+0x20

      ffffd000`38334680 fffff800`92e34f28 : 00000000`00000000 ffffe000`040aa690 ffffe000`00144420 ffffe000`021f5050 : nt!IopDeleteDriver+0x40

      ffffd000`383346c0 fffff800`92aeb05f : 00000000`00000000 ffffe000`021f5050 ffffe000`040aa690 ffffe000`021f5020 : nt!ObpRemoveObjectRoutine+0x64

      ffffd000`38334720 fffff800`92e9879f : ffffe000`021f5050 ffffe000`00144580 ffffd000`38334650 ffffe000`00000004 : nt!ObfDereferenceObject+0x8f

      ffffd000`38334760 fffff800`92e34f28 : ffffcf80`06b52fd0 00000000`00000024 ffffe000`011e8880 ffffe000`03c524c0 : nt!IopDeleteDevice+0x47

      ffffd000`38334790 fffff800`92aeb05f : 00000000`00000000 00000000`00000000 ffffe000`021f5050 ffffe000`03c524b0 : nt!ObpRemoveObjectRoutine+0x64

      ffffd000`383347f0 fffff800`92b39705 : ffffe000`011f0d30 ffffdfff`feb3aa60 00000000`00000000 ffffffff`80001ad0 : nt!ObfDereferenceObject+0x8f

      ffffd000`38334830 fffff800`92ea16b1 : ffffe000`011e8880 ffffe000`011f0d30 ffffc000`02ddf720 ffffe000`011e8880 : nt!PnpRemoveLockedDeviceNode+0x245

      ffffd000`38334890 fffff800`92ea162a : 00000000`00000000 ffffc000`02ddf720 ffffe000`011f0d30 00000000`3f051397 : nt!PnpDeleteLockedDeviceNode+0x4d

      ffffd000`383348d0 fffff800`92ea09c7 : ffffe000`011e8880 ffffd000`00000002 00000000`00000000 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0x9a

      ffffd000`38334950 fffff800`92e9aa15 : ffffc000`02ec3d00 00000000`00000001 ffffc000`00000000 ffffe000`ffffffff : nt!PnpProcessQueryRemoveAndEject+0x4ef

      ffffd000`38334ab0 fffff800`92e9ad4f : ffffc000`02ec3d60 00000000`00000000 00000000`00000000 fffff800`92e9aa30 : nt!PnpProcessTargetDeviceEvent+0x9d

      ffffd000`38334af0 fffff800`92abf3cd : fffff800`92e9aa30 ffffc000`0235f7d0 ffffd000`38334bd0 ffffe000`02e1e240 : nt!PnpDeviceEventWorker+0x31f

      ffffd000`38334b50 fffff800`92b6a664 : 0f0f0f0f`0f0f0f0f ffffe000`022be880 ffffe000`022be880 ffffe000`000e4040 : nt!ExpWorkerThread+0x2b5

      ffffd000`38334c00 fffff800`92bd96c6 : ffffd000`20a5d180 ffffe000`022be880 ffffe000`02052880 ffffd000`38334d90 : nt!PspSystemThreadStartup+0x58

      ffffd000`38334c60 00000000`00000000 : ffffd000`38335000 ffffd000`3832f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

       

       

       

       

      STACK_COMMAND:  kb

       

       

      FOLLOWUP_NAME:  MachineOwner

       

       

      FAILURE_BUCKET_ID:  0xc4_62_VRF_LEAKED_POOL_IMAGE_e1c64x64.sys

       

       

      BUCKET_ID:  0xc4_62_VRF_LEAKED_POOL_IMAGE_e1c64x64.sys

       

       

      ANALYSIS_SOURCE:  KM

       

       

      FAILURE_ID_HASH_STRING:  km:0xc4_62_vrf_leaked_pool_image_e1c64x64.sys

       

       

      FAILURE_ID_HASH:  {370de743-33b3-1b47-20cc-a27211ff829f}

       

       

      Followup: MachineOwner

      ---------