BSOD referencing to mrxsmb.sys in XP PRO SP3 (debug info included)

[tazzmissionx]

Here is my situation. A client of mine is using accounting software that syncs data files between the computer and an offsite server. Once in a while when data is transferring to the offsite server, a 100000D1 BSOD appears that refers to mrxsmb.sys. I've ran hardware diagnostics and virus scans and everything checks out ok. There are no other issues with the computer. When I asked the maker of the accounting software, all they said that replacing the network card would probably solve the issue. Any ideas?

Here is the debug info.


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: babd001c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: b4d6d1ae, address which referenced memory

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


WRITE_ADDRESS: babd001c

CURRENT_IRQL: 2

FAULTING_IP:
mrxsmb!ParseTransactResponse+1d3
b4d6d1ae f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from b4d6cebe to b4d6d1ae

STACK_TEXT:
bacfb870 b4d6cebe bae87ad4 00000000 000000a8 mrxsmb!ParseTransactResponse+0x1d3
bacfb8f8 b4d6b857 015f9e28 000000a8 000000a8 mrxsmb!SmbTransactExchangeReceive+0x41b
bacfb92c b4d6c710 8a2f7848 000000a8 000000a8 mrxsmb!SmbCeReceiveInd+0x2b2
bacfb954 b4ddbb23 8a2f7848 8a235b78 00000e20 mrxsmb!VctIndReceive+0x22
bacfb98c b4ddbb5d 00000000 8a2c1eb4 8a235b78 rdbss!ReceiveEventHandler+0x5a
bacfb9b8 b4eee209 8a2c1eb4 8a235b78 00000e20 rdbss!RxTdiReceiveEventHandler+0x24
bacfb9f8 b4eedeed 8a133498 00000044 00000e20 netbt!RcvHandlrNotOs+0xfd
bacfba34 b4f1c34b 00000004 8992d202 00000e20 netbt!TdiReceiveHandler+0x323
bacfba98 b4f193e5 8992d2b8 00001850 8967ec58 tcpip!IndicateData+0x225
bacfbb20 b4f16ef5 8a2d3098 0100007f 0100007f tcpip!TCPRcv+0xbb0
bacfbb80 b4f23783 00000020 8a2d3098 b4f190b6 tcpip!DeliverToUser+0x18e
bacfbbfc b4f16836 b4f568f0 8a2d3098 bacfbd18 tcpip!DeliverToUserEx+0x985
bacfbcb4 b4f22ce6 8a2d3098 8a2bd540 89c7f1c0 tcpip!IPRcvPacket+0x6cb
bacfbd60 bac103e4 b4f56680 8a2d3098 b4f56690 tcpip!LoopXmitRtn+0x195
bacfbd7c 8053876d 8a2d3098 00000000 8a5bd8b8 TDI!CTEpEventHandler+0x32
bacfbdac 805cff64 b4f56680 00000000 00000000 nt!ExpWorkerThread+0xef
bacfbddc 805460de 8053867e 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
mrxsmb!ParseTransactResponse+1d3
b4d6d1ae f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: mrxsmb!ParseTransactResponse+1d3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: mrxsmb

IMAGE_NAME: mrxsmb.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48025c2a

FAILURE_BUCKET_ID: 0xD1_W_mrxsmb!ParseTransactResponse+1d3

BUCKET_ID: 0xD1_W_mrxsmb!ParseTransactResponse+1d3

 

[QHalo]

This is about the closest thing I could find so far.

http://support.microsoft.com/kb/954956/en-us