BSOD coming out of standby

[vanaaken]

We have a user who just reently when they bring there laptop (X61 with XP Pro SP3) out of standby it flashes up a BSOD before rebooting have examined the minidump and have the following output:

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

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


READ_ADDRESS: 00000000

CURRENT_IRQL: 2

FAULTING_IP:
KUSBusByTCPMasterBus+49d4
eb0389d4 8b11 mov edx,dword ptr [ecx]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from eb03a6b5 to eb0389d4

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f7ab0c04 eb03a6b5 00000001 28cda8c0 829897c4 KUSBusByTCPMasterBus+0x49d4
f7ab0c18 ee606ddd 829897c0 829897a0 861d64e8 KUSBusByTCPMasterBus+0x66b5
f7ab0c44 ee6072f5 ee608408 82989780 00000000 TDI!TdiNotifyPnpClientList+0x12d
f7ab0c68 ee60770e 00000000 00938950 00000000 TDI!TdiExecuteRequest+0x19b
f7ab0ca4 ee607989 82989780 0000000c f7ab0cf4 TDI!TdiHandleSerializedRequest+0x1c4
f7ab0cb4 aa2cda5f 82989780 85f75d50 85f91c18 TDI!TdiDeregisterNetAddress+0xf
f7ab0cf4 aa2cdb74 28cda8c0 00ffffff 86ddff10 tcpip!DHCPActivityDone+0x29
f7ab0d2c aa2df895 85f91c18 aa2dc27d 00000000 tcpip!IPpSetNTEAddr+0xb4
f7ab0d60 ee6053e4 8287aac0 8287aac0 8287aad0 tcpip!IPDelNTE+0x4f
f7ab0d7c 8053877d 8287aac0 00000000 86dc2640 TDI!CTEpEventHandler+0x32
f7ab0dac 805cff72 8287aac0 00000000 00000000 nt!MiTrimPte+0x1fe
f7ab0ddc 805460ee 8053868e 00000001 00000000 nt!IopQueryReconfiguration+0x25
f7ab0df8 00000000 00000000 00000000 00001f80 nt!ExpRemovePoolTracker+0x7b


STACK_COMMAND: kb

FOLLOWUP_IP:
KUSBusByTCPMasterBus+49d4
eb0389d4 8b11 mov edx,dword ptr [ecx]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: KUSBusByTCPMasterBus+49d4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: KUSBusByTCPMasterBus

IMAGE_NAME: KUSBusByTCPMasterBus.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 484c9304

FAILURE_BUCKET_ID: 0xD1_KUSBusByTCPMasterBus+49d4

BUCKET_ID: 0xD1_KUSBusByTCPMasterBus+49d4

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

Does anyone know what is causing this? Have done a search on KUSBusByTCPMasterbus but very little comes up.

[K0LO]

I don't know the cause, but due to the fact that it is triggered by resuming from suspend, my first suspicion would be bad RAM. Can you run MemTest86+ on the machine to check the RAM, or can you swap RAM modules as a test?