BSOD Debug

**rotiro3** · 11-08-2007, 03:19 PM

Hi can someone please tell me what this minidump means? Thanks James.

BugCheck 40000080, {89b43ad0, 89228440, 805502b8, 1}

Unable to load image e1e5132.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e1e5132.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e5132.sys

Probably caused by : hardware ( e1e5132+21f8 )

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

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

BUGCODE_ID_DRIVER (40000080)
This is the NDIS Driver Bugcheck for Windows 2000 and Windows XP.
For Windows Server 2003 and later, see 0x7C, BUGCODE_NDIS_DRIVER.
DESCRIPTION
The meaning of the bug check parameters cannot be determined by examining the
parameters alone. You must also examine the text of a DbgPrint message.
For details, see either the debugger documentation or the DDK documentation.
Arguments:
Arg1: 89b43ad0
Arg2: 89228440
Arg3: 805502b8
Arg4: 00000001

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

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x40000080

PROCESS_NAME: Idle

MISALIGNED_IP:
nt!KeForceResumeThread+1
804f9deb 5d pop ebp

LAST_CONTROL_TRANSFER: from ba587921 to 804f9deb

STACK_TEXT:
805501f4 ba587921 40000080 89b43ad0 89228440 nt!KeForceResumeThread+0x1
80550254 b8e051f8 89b43ad0 805502b8 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5fd
WARNING: Stack unwind information not available. Following frames may be wrong.
80550270 b8e0f32c 89508a78 805502b8 00000001 e1e5132+0x21f8
80550290 b8e11a4d 8950a5c0 00000000 805502b8 e1e5132+0xc32c
805503c8 b8e0b341 0149f000 00000001 00000000 e1e5132+0xea4d
80550404 b8e04371 0049f000 80550428 ba57cf09 e1e5132+0x8341
80550410 ba57cf09 89508a78 8055b0a0 ffdff9c0 e1e5132+0x1371
80550428 805450bf 8949fac8 8949fab4 00000000 NDIS!ndisMDpcX+0x21
ffdff980 00000000 bacd4000 0055a3f5 00000000 nt!WmiTraceMessageVa+0x26

STACK_COMMAND: kb

FOLLOWUP_IP:
e1e5132+21f8
b8e051f8 ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: e1e5132+21f8

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

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

0: kd> lmvm hardware
start end module name

**inh** · 11-08-2007, 03:51 PM

Somethings wrong with your wireless card

**Arrow** · 11-08-2007, 04:37 PM

Try updating the driver

**rotiro3** · 11-08-2007, 05:33 PM

Hi how do you tell it is the wireless card from the log I have updated the driver but receive the same result. IBM T61 XP service pack 2 thanks James.

**Enforcer** · 11-08-2007, 06:16 PM

Might be wired network card, the sys file e1e5132.sys is for an Intel PRO/1000 LAN adapter

might also be for some other Intel LAN cards

**rotiro3** · 11-08-2007, 06:25 PM

You guys are right on it looks to be a network or wireless card issue because it happens when I unplug the network cable or plug it back in but I have the latest Lan and Wlan drivers so I don't know what else to try any ideas thanks James.

**DarquePervert** · 11-08-2007, 06:40 PM

I started to respond to this at work, but got distracted by... well... work!

Here's how I'd handle it:

1 - Go into the BIOS and disable the adapter if it's onboard. If it's a PCI card, then physically remove it from the PC.
2 - Boot the PC into SAFE MODE
3 - Go into Device Manager and remove any instances of the Intel NICs listed.
4 - Search the registry for any references to the Intel NIC and delete them. Exercise extreme caution oin the registry!
5 - search your system for the file e1e5132.sys and delete them all.
6 - Reboot the PC to make sure you don't get a BSOD.
6 - Shut down the PC, and renstall or re-enable the NIC.
7 - Reboot the computer and install the latest drivers for the NIC.
8 - Reboot again.

If you get a BSOD after this, then the NIC is faulty and needs to stay disabled and replaced. If the NIC or motherboard is still under warranty, I'd look into getting it replaced.

Good luck...

**inh** · 11-09-2007, 05:16 AM

I figured on wireless because i saw NDIS and remember good ol' netstumbler and the NDIS option.. shoulda said 'network card' just to be safe =P

Do what DP said in the post above mine =]

**rotiro3** · 11-09-2007, 04:38 PM

I did the steps above and so far so good but I wont' know for a couple of days but so far I have tried to make it blue screen but it has not. If this works you are the man thanks.