Not Less or Equal crash

Hi and welcome,
Your 2 dumps blame on athrx.sys as the cause. It is your Atheros network adapter so I would recommend you to reinstall or update it if possible.
Atheros, Wireless LAN, WLAN, 2.4/5-GHz, 802.11a/b/g, 802.11b/g, 802.11n, Radio-on-a-Chip, Overview, Networking, Products and Technology

And you have many out date drivers which may cause BSOD in your windows.
So update these drivers (pay attention to year 2008 and below it because win7 was officially release at 2009)

Code:

wacommousefilter.sys Fri Feb 16 10:12:17 2007 --> Wacom(tablet) Mouse Filter
sisraid4.sys Wed Oct 01 14:56:04 2008 -->    SiS AHCI Stor Miniport Driver
SiSRaid2.sys Wed Sep 24 11:28:20 2008 -->    SiS RAID Stor Miniport Driver
nfrd960.sys  Tue Jun 06 14:11:48 2006 --> IBM ServeRAID Controller Driver
lsi_fc.sys   Tue Dec 09 14:46:09 2008 -->  LSI Logic Fusion-MPT FC Driver (StorPort)
iirsp.sys    Tue Dec 13 13:47:54 2005 --> Intel Raid StorPort Driver
ElRawDsk.sys Sat Jul 26 10:59:09 2008 --> RawDisk Driver by EldoS Corporation
Afc.sys      Tue Jul 11 22:48:20 2006 --> Arcsoft(R) ASPI Shell (CD/DVD program)

arc.sys      Thu May 24 14:27:55 2007 --> Adaptec RAID Storport Driver
adpu320.sys  Tue Feb 27 16:04:15 2007 --> Adaptec .NET Ultra320 Driver
adpahci.sys  Tue May 01 10:30:09 2007 --> Adaptec Windows SATA Storport Driver
adp94xx.sys  Fri Dec 05 15:54:42 2008 -->    Adaptec HostRAID SAS Driver

Your ATI driver : http://www.amd.com/us/products/Pages/graphics.aspx
AtiHdmi.sys  Fri Jun 05 01:31:42 2009 
atikmdag.sys Thu Jul 02 10:45:07 2009
AtiPcie.sys  Tue May 05 08:00:22 2009

Log

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {1c, 2, 1, fffff8800496c6e8}

Unable to load image \SystemRoot\system32\DRIVERS\athrx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+10a6e8 )

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

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: 000000000000001c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800496c6e8, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310c0e0
 000000000000001c 

CURRENT_IRQL:  2

FAULTING_IP: 
athrx+10a6e8
fffff880`0496c6e8 c7401c00000000  mov     dword ptr [rax+1Ch],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880037c4810 -- (.trap 0xfffff880037c4810)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000009920 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800496c6e8 rsp=fffff880037c49a0 rbp=fffff800030795a0
 r8=000000000491a000  r9=0000000000000000 r10=fffffa800503bc90
r11=fffffa800504e128 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
athrx+0x10a6e8:
fffff880`0496c6e8 c7401c00000000  mov     dword ptr [rax+1Ch],0 ds:0002:00000000`0000001c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ed3ca9 to fffff80002ed4740

STACK_TEXT:  
fffff880`037c46c8 fffff800`02ed3ca9 : 00000000`0000000a 00000000`0000001c 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`037c46d0 fffff800`02ed2920 : 00000000`00000000 fffffa80`04c12050 00000000`00000000 fffff800`02e2b1bc : nt!KiBugCheckDispatch+0x69
fffff880`037c4810 fffff880`0496c6e8 : fffffa80`05041030 fffffa80`0504e128 fffffa80`00000008 fffff880`0000981c : nt!KiPageFault+0x260
fffff880`037c49a0 fffffa80`05041030 : fffffa80`0504e128 fffffa80`00000008 fffff880`0000981c 00000000`00000001 : athrx+0x10a6e8
fffff880`037c49a8 fffffa80`0504e128 : fffffa80`00000008 fffff880`0000981c 00000000`00000001 fffffa80`050207c0 : 0xfffffa80`05041030
fffff880`037c49b0 fffffa80`00000008 : fffff880`0000981c 00000000`00000001 fffffa80`050207c0 00000000`00000000 : 0xfffffa80`0504e128
fffff880`037c49b8 fffff880`0000981c : 00000000`00000001 fffffa80`050207c0 00000000`00000000 fffffa80`05041030 : 0xfffffa80`00000008
fffff880`037c49c0 00000000`00000001 : fffffa80`050207c0 00000000`00000000 fffffa80`05041030 fffff880`037c4c54 : 0xfffff880`0000981c
fffff880`037c49c8 fffffa80`050207c0 : 00000000`00000000 fffffa80`05041030 fffff880`037c4c54 fffff880`0496501c : 0x1
fffff880`037c49d0 00000000`00000000 : fffffa80`05041030 fffff880`037c4c54 fffff880`0496501c fffffa80`05041030 : 0xfffffa80`050207c0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athrx+10a6e8
fffff880`0496c6e8 c7401c00000000  mov     dword ptr [rax+1Ch],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  athrx+10a6e8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athrx

IMAGE_NAME:  athrx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b8db121

FAILURE_BUCKET_ID:  X64_0xD1_athrx+10a6e8

BUCKET_ID:  X64_0xD1_athrx+10a6e8

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

Code:

iirsp    iirsp.sys    Tue Dec 13 16:47:54 2005
nfrd960  nfrd960.sys  Tue Jun 06 17:11:48 2006
Afc      Afc.sys      Wed Jul 12 01:48:20 2006
adpu320  adpu320.sys  Tue Feb 27 19:04:15 2007
adpahci  adpahci.sys  Tue May 01 13:30:09 2007
arc      arc.sys      Thu May 24 17:27:55 2007

Although not shown as a direct cause of your problem now, these old drivers should be updated. If not directly involved now, these old drivers have more than a great potential for problems in the future; BSOD or otherwise