Blue Scren DRIVER_IRQL_NOT_LESS_OR_EQUAL Problem

System healt Report and Windows Nt6 File I play 1-2 hours and then suddenly switches off pc blue screen comes and nothing to do, is

If it helps to be happy

I have me too ;s

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\mamilan\Windows_NT6_BSOD_jcgriff2\011612-19624-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c67000 PsLoadedModuleList = 0xfffff800`02eac670
Debug session time: Mon Jan 16 02:09:02.177 2012 (UTC - 7:00)
System Uptime: 0 days 0:30:07.145
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {6c, 2, 0, fffff880056f675b}

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+c975b )

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

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f16100
 000000000000006c 

CURRENT_IRQL:  2

FAULTING_IP: 
athrx+c975b
fffff880`056f675b 03416c          add     eax,dword ptr [rcx+6Ch]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80004033190 -- (.trap 0xfffff80004033190)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000006a8d2f8a rbx=0000000000000000 rcx=0000000000000000
rdx=000000000000804c rsi=0000000000000000 rdi=0000000000000000
rip=fffff880056f675b rsp=fffff80004033320 rbp=fffffa80053528e0
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
athrx+0xc975b:
fffff880`056f675b 03416c          add     eax,dword ptr [rcx+6Ch] ds:00000000`0000006c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ce31e9 to fffff80002ce3c40

STACK_TEXT:  
fffff800`04033048 fffff800`02ce31e9 : 00000000`0000000a 00000000`0000006c 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`04033050 fffff800`02ce1e60 : fffff800`02e84268 00000000`00000000 fffffa80`05277c68 fffffa80`06e6c1a0 : nt!KiBugCheckDispatch+0x69
fffff800`04033190 fffff880`056f675b : fffffa80`07480030 00000000`00000000 00000000`00000000 00000000`00000007 : nt!KiPageFault+0x260
fffff800`04033320 fffffa80`07480030 : 00000000`00000000 00000000`00000000 00000000`00000007 fffffa80`07386a70 : athrx+0xc975b
fffff800`04033328 00000000`00000000 : 00000000`00000000 00000000`00000007 fffffa80`07386a70 fffff800`02d919e8 : 0xfffffa80`07480030


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athrx+c975b
fffff880`056f675b 03416c          add     eax,dword ptr [rcx+6Ch]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  athrx+c975b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athrx

IMAGE_NAME:  athrx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c9fdcaa

FAILURE_BUCKET_ID:  X64_0xD1_athrx+c975b

BUCKET_ID:  X64_0xD1_athrx+c975b

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

If you are overclocking any hardware, please stop.
Crashes were all the same and due to your wireless driver. This could mean the wireless driver is corrupted and needs to be re-installed. The dirver is athrx.sys for your wireless network adapter.

You may use the following sites as references for finding drivers. We recommend finding the manufacturer of the driver and downloading drivers directly from the manufacturer or software developer. If you have trouble finding a driver or driver manufacturer, let us know and we will do our best to assist you. If you need help, please provide the device name, manufacturer, and the driver .sys file that you are looking for.

1. Driver Reference is a good site to find the driver .sys files, their descriptions, and the site most likely to contain an update.
2. Driver Search Methods provides driver manufacturers and links to their homepages.
3. AR9002WB-1NG provides the Atheros driver for Windows 7. Click the Click for Download link.

There are a few methods for updating drivers.

1. Installing and updating drivers in 7
2. Driver Install - Add Hardware Wizard
3. Driver Install - Device Manager

To fully re-install a driver, use the following steps.

1. Click Start Menu
2. Right Click My Computer/Computer
3. Click Manage
4. Click Device Manager from the list on the left
5. Find the device you are trying to uninstall by expanding the appropriate set of devices
6. Right click the device
7. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
8. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer
10. Install the latest driver for the device once Windows starts.

Alternatively:

1. Login as an adminstrative user.
2. Click Start Menu
3. Click Control Panel
4. Click Hardware and Sound
5. Click Device Manager (the last link under Devices and Printers)
6. Find the device you are trying to uninstall by expanding the appropriate set of devices
7. Right click the device
8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
10. Restart your computer
11. Install the latest driver for the device once Windows starts.

If re-installing your wireless driver does not resolve the crashes, the problem may be due to your antivirus software since it is network related.

Uninstall ESET security using the steps for the ESET Uninstaller and replace with Microsoft Security Essentials to run with Windows firewall.