This is a question I have been waiting for an answer to a couple of weeks.
for perfcap i had the exact same problem with a3 com air-connect wireless card and had to get updated driver from 3Com specifically for XP (even though the original was supposed to be)
in my problem I have had 3 different clients crash my machine to BSOD. There is no report on any driver being at fault just a system STOP : 0x0000007f
in the memory dump is this snippet
Probably caused by : Unknown_Image ( qbikhkXP!stricmp+24c60 )
Extended
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_d
TRAP_FRAME: f7c7656c -- (.trap f7c7656c)
ErrCode = 00000000
eax=000005ea ebx=867cb340 ecx=8676b958 edx=fffffffe esi=00000008 edi=f7c76c34
eip=f765ca01 esp=f7c765e0 ebp=f7c765fc iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
qbikhkXP!stricmp+0x31631:
f765ca01 c70200000000 mov dword ptr [edx],0x0 ds:0023:fffffffe=????????
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
LAST_CONTROL_TRANSFER: from f76579ac to f765ca01
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f7c765fc f76579ac f7c76c98 00000616 000001ff qbikhkXP!stricmp+0x31631
f7c76614 f764e0ba f7c76c98 00000616 851b4a58 qbikhkXP!stricmp+0x2c5dc
f7c76c70 f764df50 f7661cc0 85e48b74 857fd1e0 qbikhkXP!stricmp+0x22cea
f7c76ca8 f764dea0 f7661cc0 85c82a58 857fd1e0 qbikhkXP!stricmp+0x22b80
f7c76d34 f7649a62 f7661cc0 85e48b66 85e48b74 qbikhkXP!stricmp+0x22ad0
f7c76d68 f7657d8a 851b4a50 851b4a50 851b4a50 qbikhkXP!stricmp+0x1e692
f7c76d7c 80528545 851b4a50 00000000 867cb340 qbikhkXP!stricmp+0x2c9ba
f7c76dac 805b05c6 851b4a50 00000000 00000000 nt!ExpWorkerThread+0xed
f7c76ddc 80534de6 80528458 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
qbikhkXP!stricmp+31631
f765ca01 c70200000000 mov dword ptr [edx],0x0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: qbikhkXP!stricmp+31631
MODULE_NAME: qbikhkXP
IMAGE_NAME: qbikhkXP.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 40313899
STACK_COMMAND: .trap f7c7656c ; kb
BUCKET_ID: 0x7f_d_qbikhkXP!stricmp+31631
Followup: MachineOwner
I CAN say that each time it happens before the crash in the nat translations the PUBLIC WAN ip of the client is in there as well as the local IP(s)
After the crash I can use MSN Messenger without problem But internet access doesnt work until i do a repair on the connection (XP)
Paid support have not come up with an answer to this either.
Regards
JonO
Last edited by
jono659 on Mar 31 04 3:23 am, edited 4 times in total.