Crash Dump Analysis - Please advise

The following is a windows crash dump file on a computer that recently crashing, showing the "blue screen of death". The file nwfs.sys refers to a file that is associated with Novell Netware. In order to fix this problem, do you advise uninstalling novell and installing the most recent version?

Please advise.



Use !analyze -v to get detailed debugging information.
BugCheck 50, {e3e82218, 0, bb47add3, 1}

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

Could not read faulting driver name
Probably caused by : nwfs.sys ( nwfs+1add3 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: e3e82218, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bb47add3, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: unable to read from 804807d8
unable to read from 80480188
unable to read from 80480068
unable to read from 80471de0
unable to read from 80480080
unable to read from 80480184
unable to read from 80471de4
unable to read from 80480244
unable to read from 80480778
e3e82218

FAULTING_IP:
nwfs+1add3
bb47add3 ?? ???

MM_INTERNAL_CODE: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 00000014 to bb47add3

TRAP_FRAME: baea54d0 -- (.trap ffffffffbaea54d0)
ErrCode = 00000000
eax=f97d6004 ebx=f9b58218 ecx=f9b5a304 edx=e3e82204 esi=00000003 edi=f97d6804
eip=bb47add3 esp=baea5544 ebp=baea57ec iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nwfs+0x1add3:
bb47add3 ?? ???
Resetting default scope

STACK_TEXT:
baea5540 00000014 f9826cc4 baea57dc f998fd68 nwfs+0x1add3


FOLLOWUP_IP:
nwfs+1add3
bb47add3 ?? ???

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nwfs+1add3

MODULE_NAME: nwfs

IMAGE_NAME: nwfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3970855f

STACK_COMMAND: .trap ffffffffbaea54d0 ; kb

BUCKET_ID: 0x50_nwfs+1add3

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

 

Might be a bug in the Novell software, I'd check for patches on their website if possible. But, if its intermittant could be a hardware error. I'd keep a few debug files to see if the probably caused by file is consistant if the problem continues. If it is consistent you might want to ask novell and send them your debug file.