BSOD after putting in new wireless card. DMP included

[zzz]

My computer randomly blue screens ever since I put in a new wireless card (Belkin). I installed the new drivers. It is especially prone to crashing if I hit the repair wireless connection button. the dmp says it's due to ntoskrnl.exe. Reading up on this it might not be the wireless card's fault, just that now ntoskrnl.exe has an opportunity to access the net and it's crashing.

WinXP SP3
AMD Athlon 64 X2 dual core
MA790X UD4 motherboard
2046mb ram

Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat Jul 4 14:59:01.890 2009 (GMT+1)
System Uptime: 0 days 2:50:26.646
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 498c11d3

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
00000400

CURRENT_IRQL: 2

FAULTING_IP:
nt+1137b
804e837b 0108 add dword ptr [eax],ecx

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 804e2779 to 804e837b

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
bacdbc14 804e2779 8a64f378 000f5ca8 00000000 nt+0x1137b
bacdbc48 804e366a 00000000 00001000 bacdbd48 nt+0xb779
bacdbc68 804e468b 8a64f378 bacdbcb8 00001000 nt+0xc66a
bacdbcf0 804e48c5 00001000 00000000 00000001 nt+0xd68b
bacdbd34 804e70db 8a774aa8 80564820 8a77ea20 nt+0xd8c5
bacdbd7c 8053877d 8a774aa8 00000000 8a77ea20 nt+0x100db
bacdbdac 805cff70 8a774aa8 00000000 00000000 nt+0x6177d
bacdbddc 805460ee 8053868e 00000000 00000000 nt+0xf8f70
00000000 00000000 00000000 00000000 00000000 nt+0x6f0ee


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+1137b
804e837b 0108 add dword ptr [eax],ecx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+1137b

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

 

[raybay]

Looks like a bad card. Belkin is actually a number of companies making products under contract... so it is very difficult to track down the problem online... some with the same product ID will work, while others from another plant or country will not..
I would return the unit to the seller, and get another card... Then go to the Registry and remove all lines relevant to the Belkin install.
If it works without the Belkin, you have your answer.

 

[zzz]

is that what the mini dump says?

 

[raybay]

Well, you can read the minidump yourself... corrupted files and a stack dump...

If you want more information you can use, set it to report as a txt file instead of a dmp file.