E1i63x64 cause VM Hung.

[getvc]

Hi,

After VM hung, MS provided the dump anaylisys as below. Seems like it's realated to e1i63x64.sys module.

I've checked the file in the google, seems it's intel network driver file. Is it possible this driver file cause VMware Tools offine and VM Panic?

e1000e driver with intel network card.

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

* *

* Bugcheck Analysis *

* *

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

NMI_HARDWARE_FAILURE (80)

This is typically due to a hardware malfunction. The hardware supplier should

be called.

Arguments:

Arg1: 00000000004f4454

Arg2: 0000000000000000

Arg3: 0000000000000000

Arg4: 0000000000000000

Debugging Details:

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

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x80

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DPC_STACK_BASE: FFFFF80084B5CFB0

LAST_CONTROL_TRANSFER: from fffff88000b725de to fffff88000b714fa

STACK_TEXT:

fffff800`84b56700 fffff880`00b725de : 00000000`00000000 fffffa80`01ef6780 00000000`00000000 00000000`00000000 : e1i63x64!INTERRUPT::IntSetItrMode+0x32a

fffff800`84b56770 fffff880`00b72248 : fffffa80`01ef6780 fffffa80`00000000 00000001`00000000 00000001`00000000 : e1i63x64!INTERRUPT::MsgIntDpcTxRxProcessing+0x25e

fffff800`84b567f0 fffff880`00b70ce8 : 00000000`00000000 00000001`00000000 fffff880`00b70d20 fffffa80`0384b910 : e1i63x64!INTERRUPT::MsgIntMessageInterruptDPC+0x138

fffff800`84b56850 fffff880`00eed2ff : fffff800`85b72100 fffff880`01ea0000 fffffa80`018b6b00 fffff800`85b74f80 : e1i63x64!INTERRUPT::MiniportMessageInterruptDPC+0x28

fffff800`84b56890 fffff880`00eed41c : fffffa80`0384baf8 00000000`ffffffff fffffa80`0384b910 00001480`22092c7f : NDIS!ndisMiniportDpc+0xff

fffff800`84b56920 fffff800`858fcdf1 : fffff800`85b74f00 fffff800`85b75c20 fffff800`84b56ab0 fffff880`01eadd68 : NDIS!ndisInterruptDpc+0x9c

fffff800`84b569b0 fffff800`858fca30 : fffffa80`02ec1620 fffff800`85b72180 00001480`2207c137 fffff800`84b56b4c : nt!KiExecuteAllDpcs+0x191

fffff800`84b56af0 fffff800`858fdb0a : fffff800`85b72180 fffff800`85b72180 00000000`00183de0 fffff800`85bcc880 : nt!KiRetireDpcList+0xd0

fffff800`84b56c60 00000000`00000000 : fffff800`84b57000 fffff800`84b51000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND: kb

FOLLOWUP_IP:

e1i63x64!INTERRUPT::IntSetItrMode+32a

fffff880`00b714fa eb78 jmp e1i63x64!INTERRUPT::IntSetItrMode+0x3a4 (fffff880`00b71574)

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: e1i63x64!INTERRUPT::IntSetItrMode+32a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: e1i63x64

IMAGE_NAME: e1i63x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4f4eec1a

BUCKET_ID_FUNC_OFFSET: 32a

FAILURE_BUCKET_ID: 0x80_e1i63x64!INTERRUPT::IntSetItrMode

BUCKET_ID: 0x80_e1i63x64!INTERRUPT::IntSetItrMode

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x80_e1i63x64!interrupt::intsetitrmode

FAILURE_ID_HASH: {86d422f3-2310-9268-16b4-6a050cd7eec2}

Followup: MachineOwner

---------

Best Regards,