Hi,

I've been getting some really weird crashes from a 2008 x64 server. When the crash occurs the whole machine stops outputing anything including video.

Only after a reboot do things come back to life - the event logs indicate some kind of issue with the SCSI card - but I've swapped the SCSI card from an identical machine and it still happens.

I've run the minidump though an analysis and it looks like it's pointing to a driver issue - however I'm wondering if it could be something else (faulty memory prehaps?).

Any help is really appreciated...



3: 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: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffffa6000843b9e, address which referenced memory

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


WRITE_ADDRESS: 0000000000000010

CURRENT_IRQL: 0

FAULTING_IP:
NDIS!_NULL_IMPORT_DESCRIPTOR <PERF> (NDIS+0x42b9e)+0
fffffa60`00843b9e ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80001671450

STACK_TEXT:
fffffa60`06f5fc88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopLockMountedDeviceForRemove+0x17


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
NDIS!_NULL_IMPORT_DESCRIPTOR <PERF> (NDIS+0x42b9e)+0
fffffa60`00843b9e ?? ???

SYMBOL_NAME: NDIS!_NULL_IMPORT_DESCRIPTOR <PERF> (NDIS+0x42b9e)+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NDIS

IMAGE_NAME: NDIS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 49e02df3

FAILURE_BUCKET_ID: X64_0xD1_NDIS!_NULL_IMPORT_DESCRIPTOR__PERF__(NDIS+0x42b9e)+0

BUCKET_ID: X64_0xD1_NDIS!_NULL_IMPORT_DESCRIPTOR__PERF__(NDIS+0x42b9e)+0

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

3: kd> lmvm NDIS
start end module name
fffffa60`00801000 fffffa60`009c4000 NDIS M (pdb symbols) c:\windows\symbols\SYS\NDIS.pdb
Loaded symbol image file: NDIS.SYS
Image path: \SystemRoot\system32\DRIVERS\NDIS.SYS
Image name: NDIS.SYS
Timestamp: Sat Apr 11 13:43:15 2009 (49E02DF3)
CheckSum: 000B4C34
ImageSize: 001C3000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

This error is usually caused by drivers but sometimes by faulty or mismatched memory. Please attach the minidump in your next post. We'll see if it will give a definitive driver for the cause of your crashes.

Hi, thanks for the assistance with this - unfortuanetely I can't attache the minidump here as it exceeds the max file size (it's 261kb) - so I've hosted it here...

2shared.com/file/6892458/77d7f621/Mini072909-01.html

from what I can tell now... NDIS.sys is relating to the Realtek NIC that we have on that machine, but I could be barking up the wrong tree.

Cheers

There is the option to Zip your dump(s). It should compress that file. We've seen many issues with Realtek drivers. It wouldn't hurt to update them through your motherboard manufacturer's site for your particular motherboard.