BSOD Errors

All 12 of your minidumps crash at Rtlnicxp.sys. Realtek 10/100/1000 NDIS 5.1 Driver.

If you still think it isn`t a problem with your Realtek driver, then that`s up to you.

Regards Howard

Thanks

Could you please share of how did you got through the idea that my dumps are crashing at realtek drivers. I am keen to get the steps that leads to the conclusion as that will help me in handling same queries in the future as well, movers I can share the same with other people queries in the forum..

It was really working with the new drivers that i just installed.

Thank you very much ...

Here is the output of 1 of your minidumps.

BugCheck 40000080, {81a42130, ff9dd698, f99a8ef4, 1}

Unable to load image Rtlnicxp.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for Rtlnicxp.sys
*** ERROR: Module load completed but symbols could not be loaded for Rtlnicxp.sys
Probably caused by : Rtlnicxp.sys ( Rtlnicxp+3412 )

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

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: 81a42130
Arg2: ff9dd698
Arg3: f99a8ef4
Arg4: 00000001

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


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x40000080

LAST_CONTROL_TRANSFER: from f93f1921 to 8053a9ae

STACK_TEXT:
f99a8dd4 f93f1921 40000080 81a42130 ff9dd698 nt!KeBugCheckEx+0x1b
f99a8e34 f9268412 81a42130 f99a8ef4 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5fd
WARNING: Stack unwind information not available. Following frames may be wrong.
f99a8fa8 f9269d86 81981000 81a42130 81981150 Rtlnicxp+0x3412
f99a8fd0 804e3179 81981164 81981150 00000000 Rtlnicxp+0x4d86
f99a8ff4 804e2e2d aa5a5a18 00000000 00000000 nt!KiRetireDpcList+0x46
f99a8ff8 aa5a5a18 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a
804e2e2d 00000000 00000009 bb835675 00000128 0xaa5a5a18


FOLLOWUP_IP:
Rtlnicxp+3412
f9268412 ?? ???

SYMBOL_STACK_INDEX: 2

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: Rtlnicxp+3412

MODULE_NAME: Rtlnicxp

IMAGE_NAME: Rtlnicxp.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41aed3f6

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0x40000080_Rtlnicxp+3412

BUCKET_ID: 0x40000080_Rtlnicxp+3412

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

If you do a Google search for Rtlnicxp.sys, you`ll see what I mean.

All 12 minidumps crash with exactly the same error.

I hope this helps.

Regards Howard

Re-Thanks

Thanks Howard that was helpful..

Surely appreciated.



Thanks and Regards
Sebastian Fernandez