Jump to content

BSOD on windows XP SP2 new laptop


moo2004

Recommended Posts

Hi,

Twice a day I get BSOD on my new Lenovo T61 laptop.

The error message is always 0X400000080 and for each crash a 'Dump' file is created.

I have searched for solution on MS Technet and could find one.

Can you assist?

Link to comment
Share on other sites


If you're talking about a bugcheck code of 0x00000080 (0x40000080 isn't a Windows bugcheck code, so if it's that you've got a 3rd party driver or program throwing it for sure), then it means:

Bug Check 0x80: NMI_HARDWARE_FAILURE
The NMI_HARDWARE_FAILURE bug check has a value of 0x00000080. This bug check indicates that a hardware malfunction has occurred.

Parameters
None

Cause
A variety of hardware malfunctions can cause the NMI_HARDWARE_FAILURE bug check. The exact cause is difficult to determine.

Resolving the Problem
Remove any hardware or drivers that have been recently installed. Make sure that all memory modules are of the same type.

Link to comment
Share on other sites

Looking at the 5 minidumps, it's not quite twice a day this occurs, the uptime varies from ~5 minutes to over 5 days.

The bugchecks are consistent, and all point to the network card driver e1e5132.sys (Intel PRO/1000 LAN adapter).

I'm guessing it is triggered by high network activity, or if the network cable is plugged in/out.

Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 2600.xpsp_sp2_gdr.070227-2254

Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0

Debug session time: Mon May 26 14:14:02.959 2008 (GMT+2)

System Uptime: 0 days 19:28:16.824

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: 8a550ad0

Arg2: 897439b8

Arg3: f78babb8

Arg4: 00000003

STACK_TEXT:

f78baaf4 ba769921 40000080 8a550ad0 897439b8 nt!KeBugCheckEx+0x1b

f78bab54 b9f321f8 8a550ad0 f78babb8 00000003 NDIS!ethFilterDprIndicateReceivePacket+0x5fd

f78bab70 b9f3c35c 89b0f970 f78babb8 00000003 e1e5132+0x21f8

f78bab90 b9f3ea7d 89b0f808 00000000 f78babb8 e1e5132+0xc35c

f78bacc8 b9f38341 01aa3000 00000003 00000001 e1e5132+0xea7d

f78bad04 b9f31371 00aa3000 f78bad28 ba75ef09 e1e5132+0x8341

f78bad10 ba75ef09 89b0f970 80560f00 f771f9c0 e1e5132+0x1371

f78bad28 804dcd22 89aa3ac8 89aa3ab4 00000000 NDIS!ndisMDpcX+0x21

f78bad50 804dcc07 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61

f78bad54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28

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

Debug session time: Tue Jun 3 15:59:16.799 2008 (GMT+2)

System Uptime: 5 days 20:19:51.374

BUGCODE_ID_DRIVER (40000080)

Arg1: 89b86ad0

Arg2: 8973e5d0

Arg3: 805562b8

Arg4: 00000001

STACK_TEXT:

805561f4 ba769921 40000080 89b86ad0 8973e5d0 nt!KeBugCheckEx+0x1b

80556254 b9f321f8 89b86ad0 805562b8 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5fd

80556270 b9f3c35c 8998c6e0 805562b8 00000001 e1e5132+0x21f8

80556290 b9f3ea7d 8998c578 00000000 805562b8 e1e5132+0xc35c

805563c8 b9f38341 0198a000 00000001 00000000 e1e5132+0xea7d

80556404 b9f31371 0098a000 80556428 ba75ef09 e1e5132+0x8341

80556410 ba75ef09 8998c6e0 80560f00 ffdff9c0 e1e5132+0x1371

80556428 804dcd22 8998aac8 8998aab4 00000000 NDIS!ndisMDpcX+0x21

80556450 804dcc07 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61

80556454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28

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

Debug session time: Thu Jun 5 12:40:24.022 2008 (GMT+2)

System Uptime: 0 days 4:07:17.444

BUGCODE_ID_DRIVER (40000080)

Arg1: 8a5615b8

Arg2: 89779508

Arg3: 805562b8

Arg4: 00000001

STACK_TEXT:

805561f4 ba769921 40000080 8a5615b8 89779508 nt!KeBugCheckEx+0x1b

80556254 b9f321f8 8a5615b8 805562b8 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5fd

80556270 b9f3c35c 8a57df50 805562b8 00000001 e1e5132+0x21f8

80556290 b9f3ea7d 89aedd08 00000000 805562b8 e1e5132+0xc35c

805563c8 b9f38341 019cd000 00000001 00000000 e1e5132+0xea7d

80556404 b9f31371 009cd000 80556428 ba75ef09 e1e5132+0x8341

80556410 ba75ef09 8a57df50 80560f00 ffdff9c0 e1e5132+0x1371

80556428 804dcd22 899cdac8 899cdab4 00000000 NDIS!ndisMDpcX+0x21

80556450 804dcc07 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61

80556454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28

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

Debug session time: Thu Jun 5 14:01:16.857 2008 (GMT+2)

System Uptime: 0 days 1:20:09.388

BUGCODE_ID_DRIVER (40000080)

Arg1: 8a587ad0

Arg2: 8977bf30

Arg3: f78babb8

Arg4: 00000001

STACK_TEXT:

f78baaf4 ba769921 40000080 8a587ad0 8977bf30 nt!KeBugCheckEx+0x1b

f78bab54 b9f6a1f8 8a587ad0 f78babb8 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5fd

f78bab70 b9f7435c 8a538198 f78babb8 00000001 e1e5132+0x21f8

f78bab90 b9f76a7d 89af1148 00000000 f78babb8 e1e5132+0xc35c

f78bacc8 b9f70341 019c5000 00000001 00000001 e1e5132+0xea7d

f78bad04 b9f69371 009c5000 f78bad28 ba75ef09 e1e5132+0x8341

f78bad10 ba75ef09 8a538198 80560f00 f771f9c0 e1e5132+0x1371

f78bad28 804dcd22 899c5ac8 899c5ab4 00000000 NDIS!ndisMDpcX+0x21

f78bad50 804dcc07 00000000 0000000e 00dfc434 nt!KiRetireDpcList+0x61

f78bad54 00000000 0000000e 00dfc434 00dfc436 nt!KiIdleLoop+0x28

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

Debug session time: Wed Jun 11 08:31:51.818 2008 (GMT+2)

System Uptime: 0 days 0:05:46.623

BUGCODE_ID_DRIVER (40000080)

Arg1: 89b5cad0

Arg2: 897858f0

Arg3: f78babb8

Arg4: 00000001

STACK_TEXT:

f78baaf4 ba769921 40000080 89b5cad0 897858f0 nt!KeBugCheckEx+0x1b

f78bab54 b9f321f8 89b5cad0 f78babb8 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5fd

f78bab70 b9f3c35c 89b9bd38 f78babb8 00000001 e1e5132+0x21f8

f78bab90 b9f3ea7d 89b62038 00000000 f78babb8 e1e5132+0xc35c

f78bacc8 b9f38341 019db000 00000001 00000001 e1e5132+0xea7d

f78bad04 b9f31371 009db000 f78bad28 ba75ef09 e1e5132+0x8341

f78bad10 ba75ef09 89b9bd38 80560f00 f771f9c0 e1e5132+0x1371

f78bad28 804dcd22 899dbac8 899dbab4 00000000 NDIS!ndisMDpcX+0x21

f78bad50 804dcc07 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61

f78bad54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28

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

1: kd> lmvm e1e5132

start end module name

b9f30000 b9f71000 e1e5132 T (no symbols)

Loaded symbol image file: e1e5132.sys

Image path: e1e5132.sys

Image name: e1e5132.sys

Timestamp: Sat Oct 13 01:11:05 2007 (470FFF09)

CheckSum: 00045D48

ImageSize: 00041000

Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0

No version information available in the minidump, but the date on the driver is 10/2007...

http://www-307.ibm.com/pc/support/site.wss...ocid=MIGR-67829

"Intel PRO/1000 LAN adapter software for Windows 2000, XP - ThinkPad R61, R61i, T60, T60p, T61, T61p, X61, X61s, X61 Tablet, X300

...

Version: 9.7.251.0 (Build 152228)

Release Date: 2007/12/18"

If the driver update doesn't help, then I would recommend checking if it has an option for TCP checksum offloading, and disable it.

(The option is located on the Advanced tab of the network card driver itself, different manufacturers refer to it as different things but it should have the word "offloading" in the property name.)

Link to comment
Share on other sites

Hi,

When I'm starting to think about it, it is very obvious the the NIC driver is cause.

Whenever I Undocked the laptop, or plugged out the Ethernet cable, the laptop crashed.

I'll inform you if one if the following helped me.

[edited]

Well, there is no new version for my NIC driver so I have disabled the checksum.

I have disabled the it in the following:

Offloading Receive TCP checksum

Offloading Transmit TCP checksum

:blink: {Problem still occurs}

Hi,

I still get BSOD.

This is what appears in the event log:

Event Type:	Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 18,06,2008
Time: 11:08:17
User: N/A
Computer: ****
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x40000080 (0x89bdc8c8, 0x8976ff30, 0xf78babb8, 0x00000001). A dump was saved in: C:\WINDOWS\Minidump\Mini061808-03.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I have attached three dump files from today

Minidump18_06.zip

Edited by moo2004
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...