Windows 7 Help required BSOD Driver_IRQL_NOT_LESS_OR_EQUAL - Windows 7

abhijithbg

New Member
Joined
Oct 19, 2012
Hi,
I am using my system from 2 years. From past eight days I am observing BSOD.
I request your help to solve this problem.
I have attached dump in zipped format created by W7F diagnostic tool.
I have also attached image from CPU-Z about system.
Finally I attached report from PassMark RAMMon.
Image and HTML report is inside the Zip folder.

I am eagerly waiting for your help.

Thank you.
 

Attachments

  • W7F_19-10-2012.zip
    2.4 MB · Views: 464
  • CPUZ_Images.png
    CPUZ_Images.png
    412.5 KB · Views: 512
Code:
********************************************************************************                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


Use !analyze -v to get detailed debugging information.


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


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
[COLOR=#ff0000]Probably caused by : athrx.sys ( athrx+10a6e8 )[/COLOR]


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: fffff8800457c6e8, address which referenced memory


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




WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800040b90e0
 000000000000001c 


CURRENT_IRQL:  2


FAULTING_IP: 
[COLOR=#ff0000]athrx+10a6e8[/COLOR]
fffff880`0457c6e8 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:  fffff88002fcb810 -- (.trap 0xfffff88002fcb810)
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=fffff8800457c6e8 rsp=fffff88002fcb9a0 rbp=fffff800040265a0
 r8=000000000491a000  r9=0000000000000000 r10=000000000000004d
r11=fffffa80059f0128 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
athrx+0x10a6e8:
fffff880`0457c6e8 c7401c00000000  mov     dword ptr [rax+1Ch],0 ds:0002:00000000`0000001c=????????
Resetting default scope


LAST_CONTROL_TRANSFER:  from fffff80003e81aa9 to fffff80003e82540


STACK_TEXT:  
fffff880`02fcb6c8 fffff800`03e81aa9 : 00000000`0000000a 00000000`0000001c 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02fcb6d0 fffff800`03e80720 : 00000000`00000010 fffffa80`054ce050 fffff880`02fcb830 fffff800`043fd1bc : nt!KiBugCheckDispatch+0x69
fffff880`02fcb810 fffff880`0457c6e8 : fffffa80`059e3030 fffffa80`059f0128 fffffa80`00000008 fffff880`0000981c : nt!KiPageFault+0x260
[COLOR=#ff0000]fffff880`02fcb9a0 fffffa80`059e3030 : fffffa80`059f0128 fffffa80`00000008 fffff880`0000981c 00000000`00000001 : athrx+0x10a6e8[/COLOR]
fffff880`02fcb9a8 fffffa80`059f0128 : fffffa80`00000008 fffff880`0000981c 00000000`00000001 fffffa80`059e28a0 : 0xfffffa80`059e3030
fffff880`02fcb9b0 fffffa80`00000008 : fffff880`0000981c 00000000`00000001 fffffa80`059e28a0 00000000`00000000 : 0xfffffa80`059f0128
fffff880`02fcb9b8 fffff880`0000981c : 00000000`00000001 fffffa80`059e28a0 00000000`00000000 fffffa80`059e3030 : 0xfffffa80`00000008
fffff880`02fcb9c0 00000000`00000001 : fffffa80`059e28a0 00000000`00000000 fffffa80`059e3030 fffff880`02fcbc54 : 0xfffff880`0000981c
fffff880`02fcb9c8 fffffa80`059e28a0 : 00000000`00000000 fffffa80`059e3030 fffff880`02fcbc54 fffff880`0457501c : 0x1
fffff880`02fcb9d0 00000000`00000000 : fffffa80`059e3030 fffff880`02fcbc54 fffff880`0457501c fffffa80`059e3030 : 0xfffffa80`059e28a0




STACK_COMMAND:  kb


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


SYMBOL_STACK_INDEX:  3


SYMBOL_NAME:  athrx+10a6e8


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: athrx


[COLOR=#ff0000]IMAGE_NAME:  athrx.sys[/COLOR]


DEBUG_FLR_IMAGE_TIMESTAMP:  4b8db121


FAILURE_BUCKET_ID:  X64_0xD1_athrx+10a6e8


BUCKET_ID:  X64_0xD1_athrx+10a6e8


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

Drivers operating at the time:
Code:
start             end                 module name
fffff880`00ec7000 fffff880`00f1e000   ACPI     ACPI.sys     Tue Jul 14 09:19:34 2009 (4A5BC106)
fffff880`02c9a000 fffff880`02d23000   afd      afd.sys      Wed Dec 28 14:59:08 2011 (4EFA940C)
fffff880`03bd2000 fffff880`03be8000   AgileVpn AgileVpn.sys Tue Jul 14 10:10:24 2009 (4A5BCCF0)
fffff880`010ba000 fffff880`010d0000   amd_sata amd_sata.sys Sat Aug 14 09:35:02 2010 (4C65D6A6)
fffff880`010d0000 fffff880`010dd000   amd_xata amd_xata.sys Sat Aug 14 09:35:04 2010 (4C65D6A8)
fffff880`03ba5000 fffff880`03bba000   amdppm   amdppm.sys   Tue Jul 14 09:19:25 2009 (4A5BC0FD)
fffff880`00fbb000 fffff880`00fcf000   amdsata  amdsata.sys  Thu Oct 08 07:13:09 2009 (4ACCF655)
fffff880`010af000 fffff880`010ba000   amdxata  amdxata.sys  Thu Oct 08 07:13:10 2009 (4ACCF656)
fffff880`03428000 fffff880`03430000   ASMMAP64 ASMMAP64.sys Thu Jul 02 19:13:26 2009 (4A4C7A36)
fffff880`00e8d000 fffff880`00e96000   atapi    atapi.sys    Tue Jul 14 09:19:47 2009 (4A5BC113)
fffff880`00e96000 fffff880`00ec0000   ataport  ataport.SYS  Tue Jul 14 09:19:52 2009 (4A5BC118)
[COLOR=#ff0000]fffff880`0445f000 fffff880`045e8000   athrx    athrx.sys    Wed Mar 03 11:45:21 2010 (4B8DB121)[/COLOR]
fffff880`04a00000 fffff880`04a23000   AtiHdmi  AtiHdmi.sys  Thu Apr 08 17:42:30 2010 (4BBD88E6)
fffff880`03cd9000 fffff880`04383000   atikmdag atikmdag.sys Wed Mar 31 12:47:03 2010 (4BB2A997)
fffff880`03b1f000 fffff880`03b55000   atikmpag atikmpag.sys Wed Mar 31 12:23:32 2010 (4BB2A414)
fffff880`01609000 fffff880`01611000   AtiPcie  AtiPcie.sys  Wed May 06 01:00:22 2009 (4A005486)
fffff880`03bba000 fffff880`03bc2000   ATK64AMD ATK64AMD.sys Wed May 13 11:04:54 2009 (4A0A1CB6)
fffff960`008d0000 fffff960`00931000   ATMFD    ATMFD.DLL    Sat Feb 19 15:13:38 2011 (4D5F4372)
fffff880`00f8f000 fffff880`00f9b000   BATTC    BATTC.SYS    Tue Jul 14 09:31:01 2009 (4A5BC3B5)
fffff880`01611000 fffff880`01618000   Beep     Beep.SYS     Tue Jul 14 10:00:13 2009 (4A5BCA8D)
fffff880`02c83000 fffff880`02c94000   blbdrive blbdrive.sys Tue Jul 14 09:35:59 2009 (4A5BC4DF)
fffff880`05dc6000 fffff880`05de4000   bowser   bowser.sys   Wed Feb 23 16:15:06 2011 (4D6497DA)
fffff960`00630000 fffff960`00657000   cdd      cdd.dll      unavailable (00000000)
fffff880`013d6000 fffff880`01400000   cdrom    cdrom.sys    Tue Jul 14 09:19:54 2009 (4A5BC11A)
fffff880`00d23000 fffff880`00de3000   CI       CI.dll       Tue Jul 14 11:32:13 2009 (4A5BE01D)
fffff880`01450000 fffff880`01480000   CLASSPNP CLASSPNP.SYS Tue Jul 14 09:19:58 2009 (4A5BC11E)
fffff880`00cc5000 fffff880`00d23000   CLFS     CLFS.SYS     Tue Jul 14 09:19:57 2009 (4A5BC11D)
fffff880`03ba0000 fffff880`03ba4500   CmBatt   CmBatt.sys   Tue Jul 14 09:31:03 2009 (4A5BC3B7)
fffff880`014b6000 fffff880`01529000   cng      cng.sys      Thu Nov 17 15:26:35 2011 (4EC48CFB)
fffff880`00f86000 fffff880`00f8f000   compbatt compbatt.sys Tue Jul 14 09:31:02 2009 (4A5BC3B6)
fffff880`03bc2000 fffff880`03bd2000   CompositeBus CompositeBus.sys Tue Jul 14 10:00:33 2009 (4A5BCAA1)
The dmp file points to athrx.sys, which is an Atheros network adapter driver.
Try updating the driver first, http://www.atheros.cz and see what happens.
 
Hi GeneralHining,
Thank you very much for your reply and help.
I have updated Atheros network adapter driver.
I will update you about status of BSOD problem soon.
Thank you once again.
 
Back
Top Bottom