Windows 7 Multiple BSODs, files attached

[temp89]

Hello, my system is suffering from frequent BSODs shortly after startup. Trying to start something strenuous like a video-game is a sure-fire way to cause it but temperatures are fine. I have attached the Daignostic, CPU-Z and RAMMon files.

View attachment Seven Forums.rar

My RAM is in slots 3&4 instead of 1&2 so my CPU coller can fit but changing back does nothing.

 

[Trouble]

Hello and welcome to the forum.
Your problem is with
athrxusb.sys 7/29/2008 which is currently being used by your Belkin Wireless "G USB Network Adapter. You need to consider either updating, uninstalling or renaming. If you are unable to find a driver that is more recent than your currently installed pre-Windows 7 RTM version than you will likely need to obtain a different adapter with support for Windows 7.
DUMP FILE:

BugCheck 1E, {0, 0, 0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\[COLOR=#ff0000][U][B]athrxusb.sys[/B][/U][/COLOR], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR=#ff0000][U][B]athrxusb.sys[/B][/U][/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR=#ff0000][U][B]athrxusb.sys[/B][/U][/COLOR]
Probably caused by : nwifi.sys ( nwifi!Pt6RepackRecvNBL+103 )
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP: 
+0
00000000`00000000 ??              ???
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  0000000000000000
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  WerFault.exe
CURRENT_IRQL:  2
EXCEPTION_RECORD:  fffff88002f22518 -- (.exr 0xfffff88002f22518)
ExceptionAddress: fffff8800203e767 (nwifi!Pt6RepackRecvNBL+0x0000000000000103)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME:  fffff88002f225c0 -- (.trap 0xfffff88002f225c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800447fa30 rbx=0000000000000000 rcx=fffff880020766e0
rdx=fffffa80044e0f40 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800203e767 rsp=fffff88002f22750 rbp=0000000000000000
 r8=0000000000000000  r9=fb64c8ccac3c7127 r10=fffff88002074110
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nwifi!Pt6RepackRecvNBL+0x103:
fffff880`0203e767 450fb701        movzx   r8d,word ptr [r9] ds:fb64c8cc`ac3c7127=????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff800030b12ee to fffff800030b9590
STACK_TEXT:  
fffff880`02f21608 fffff800`030b12ee : 00000000`00000000 00000000`00000000 fffff880`02f21d80 fffff800`030e6524 : nt!KeBugCheck
fffff880`02f21610 fffff800`030df2dd : fffff800`032c7b7c fffff800`03201e68 fffff800`03049000 fffff880`02f22518 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f21640 fffff800`030e6950 : fffff800`03208a38 fffff880`02f216b8 fffff880`02f22518 fffff800`03049000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f21670 fffff800`030f38cf : fffff880`02f22518 fffff880`02f21d80 fffff880`00000000 fffffa80`044b07d0 : nt!RtlDispatchException+0x410
fffff880`02f21d50 fffff800`030b8c02 : fffff880`02f22518 00000000`00000000 fffff880`02f225c0 fffffa80`04df4010 : nt!KiDispatchException+0x16f
fffff880`02f223e0 fffff800`030b750a : fffffa80`0447fb20 fffff880`02f22838 00000000`00000000 fffff880`020f7bd4 : nt!KiExceptionDispatch+0xc2
fffff880`02f225c0 fffff880`0203e767 : 00000000`00000000 00000000`00000000 fffffa80`04df4010 fffff880`000005fc : nt!KiGeneralProtectionFault+0x10a
fffff880`02f22750 fffff880`0203f6c8 : fffffa80`0442e030 fffffa80`0377b43b fffffa80`0000243b fffffa80`04df4010 : nwifi!Pt6RepackRecvNBL+0x103
fffff880`02f22850 fffff880`016cd2b7 : fffffa80`037811a0 fffffa80`044b07d0 00000000`00000001 fffffa80`04458638 : nwifi!Pt6Receive+0x170
fffff880`02f228b0 fffff880`020c2202 : 00000000`00000000 fffff880`00dd7130 fffffa80`04255450 00000000`00000000 : ndis! ?? ::FNODOBFM::`string'+0xccef
fffff880`02f22900 00000000`00000000 : fffff880`00dd7130 fffffa80`04255450 00000000`00000000 fffffa80`00000001 : [COLOR=#ff0000][U][B]athrxusb[/B][/U][/COLOR]+0x11202
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nwifi!Pt6RepackRecvNBL+103
fffff880`0203e767 450fb701        movzx   r8d,word ptr [r9]
SYMBOL_STACK_INDEX:  7
SYMBOL_NAME:  nwifi!Pt6RepackRecvNBL+103
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nwifi
IMAGE_NAME:  nwifi.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc3b
FAILURE_BUCKET_ID:  X64_0x1E_nwifi!Pt6RepackRecvNBL+103
BUCKET_ID:  X64_0x1E_nwifi!Pt6RepackRecvNBL+103

Regards
Randy