VMware Cloud Community
BoostedG
Contributor
Contributor

Windows 2003 64-Bit guest Blue Screens & debug check says the Intel E1000 driver is the cause.

My Guest OS Windows 2003 Standard 64-Bit is running on VMware server 2.0 has blue screened twice, once last week and again today. The first debug simply indicated it was a device driver but did not indicate which device driver. Today after reviewing the crash dump. It says the cause is e1G5132e.sys. So I do a search and it's my virtual network card driver. Has anyone run into this before? Can I switch to the enhanced driver and hope it does not happen again. I checked though the knowledgebase and I could not find a similar post.

Below is the info from the WIndows Debug session. Any help would be greatly appreciated!

Probably caused by : e1G5132e.sys ( e1G5132e+a47 )

Followup: MachineOwner

-


0: kd> !analyze -v

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

  • *

  • Bugcheck Analysis *

  • *

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If kernel debugger is available get stack backtrace.

Arguments:

Arg1: 00000000000001ef, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, value 0 = read operation, 1 = write operation

Arg4: fffffadf968802bb, address which referenced memory

Debugging Details:

-


READ_ADDRESS: 00000000000001ef

CURRENT_IRQL: 2

FAULTING_IP:

+0

fffffadf`968802bb ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR: 0xD1

PROCESS_NAME: Idle

TRAP_FRAME: fffff800001176d0 -- (.trap 0xfffff800001176d0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000202

rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000

rip=fffffadf968802bb rsp=fffff80000117860 rbp=fffff80000117900

r8=00000000000c002f r9=fffffadf9ca85040 r10=0000000000000003

r11=0000000000000000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na pe cy

fffffadf`968802bb ?? ???

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8000102e5b4 to fffff8000102e890

STACK_TEXT:

fffff800`00117548 fffff800`0102e5b4 : 00000000`0000000a 00000000`000001ef 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

fffff800`00117550 fffff800`0102d547 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x74

fffff800`001176d0 fffffadf`968802bb : fffffadf`9687e6d6 fffffadf`8fe543ad 00000000`00000022 00000000`00000000 : nt!KiPageFault+0x207

fffff800`00117860 fffffadf`9687e6d6 : fffffadf`8fe543ad 00000000`00000022 00000000`00000000 fffffadf`9a4f700a : 0xfffffadf`968802bb

fffff800`00117868 fffffadf`8fe543ad : 00000000`00000022 00000000`00000000 fffffadf`9a4f700a 00000000`00000000 : 0xfffffadf`9687e6d6

fffff800`00117870 fffffadf`8f308a47 : fffffadf`0000003c fffff800`00117a10 fffffadf`00000001 00000000`00000003 : NDIS!ethFilterDprIndicateReceivePacket+0x8dd

fffff800`00117940 fffffadf`0000003c : fffff800`00117a10 fffffadf`00000001 00000000`00000003 fffffadf`9066b180 : e1G5132e+0xa47

fffff800`00117948 fffff800`00117a10 : fffffadf`00000001 00000000`00000003 fffffadf`9066b180 00000000`00000000 : 0xfffffadf`0000003c

fffff800`00117950 fffffadf`00000001 : 00000000`00000003 fffffadf`9066b180 00000000`00000000 00000000`00000000 : 0xfffff800`00117a10

fffff800`00117958 00000000`00000003 : fffffadf`9066b180 00000000`00000000 00000000`00000000 fffffadf`9a49e010 : 0xfffffadf`00000001

fffff800`00117960 fffffadf`9066b180 : 00000000`00000000 00000000`00000000 fffffadf`9a49e010 00000000`00000000 : 0x3

fffff800`00117968 00000000`00000000 : 00000000`00000000 fffffadf`9a49e010 00000000`00000000 00000000`00000000 : 0xfffffadf`9066b180

STACK_COMMAND: kb

FOLLOWUP_IP:

e1G5132e+a47

fffffadf`8f308a47 ?? ???

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: e1G5132e+a47

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: e1G5132e

IMAGE_NAME: e1G5132e.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0xD1_e1G5132e+a47

BUCKET_ID: X64_0xD1_e1G5132e+a47

Followup: MachineOwner

0 Kudos
2 Replies
AWo
Immortal
Immortal

Do you use the e1000 driver from the VMWare Tools?

Try to change to vmxnet3.


AWo

VCP 3 & 4

Author @ vmwire.net

\[:o]===\[o:]

=Would you like to have this posting as a ringtone on your cell phone?=

=Send "Posting" to 911 for only $999999,99!=

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
0 Kudos
BoostedG
Contributor
Contributor

I have not yet tried the vmxnet3 driver yet. For now I just shutdown the guest os and removed and re-added the e1000 driver, I am hoping that refreshing the driver will fix the problem. This serve has been running for over a year with no issues until now!

If I get another blue screen then I will try the vmnetx3 driver.

0 Kudos