Jump to content

How to fix DRIVER_IRQL_NOT_LESS_OR_EQUAL error?


menzobomhof

Recommended Posts


Update the Atheros WIFI driver:

********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high.  This is usuallycaused by drivers using improper addresses.If kernel debugger is available get stack backtrace.Arguments:Arg1: 0000000000000000, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000008, value 0 = read operation, 1 = write operationArg4: 0000000000000000, address which referenced memoryDebugging Details:------------------READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80013bdb150GetUlongFromAddress: unable to read from fffff80013bdb208 0000000000000000 Nonpaged poolCURRENT_IRQL:  2FAULTING_IP: +67d6f56256b600000000`00000000 ??              ???PROCESS_NAME:  SystemCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTBUGCHECK_STR:  AVANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64freDPC_STACK_BASE:  FFFFD000207F8FB0TRAP_FRAME:  ffffd000207f88f0 -- (.trap 0xffffd000207f88f0)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=ffffe00003e1a030 rbx=0000000000000000 rcx=ffffe00003e1a030rdx=ffffd00024385e02 rsi=0000000000000000 rdi=0000000000000000rip=0000000000000000 rsp=ffffd000207f8a88 rbp=ffffd000207f8c89 r8=ffffe0000420b498  r9=ffffd00024387098 r10=ffffe00003ffb260r11=fffff80002965328 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0         nv up ei ng nz na po nc00000000`00000000 ??              ???Resetting default scopeLAST_CONTROL_TRANSFER:  from fffff800139e77e9 to fffff800139dbca0FAILED_INSTRUCTION_ADDRESS: +67d6f56256b600000000`00000000 ??              ???STACK_TEXT:  ffffd000`207f8a88 fffff800`0299840e : 00000002`00000000 00000002`00000000 00000000`00000000 fffff800`02b463c2 : 0x0ffffd000`207f8a90 fffff800`02989274 : ffffe000`03e14030 fffff800`00000000 ffffd000`207f8b30 fffff800`0183e16c : athwnx!ath_gpio_handle_intr+0x36ffffd000`207f8ae0 fffff800`02b0bf4b : ffffe000`03e14030 00000000`00000000 00000001`0000005c 00000000`0005d057 : athwnx!ath_handle_intr+0x60cffffd000`207f8b50 fffff800`02ad4eba : ffffe000`03e10030 ffffd000`207c7100 0000001e`44a2da41 00000005`4e4b304e : athwnx!Hw11DpcDispatcher+0x27ffffd000`207f8b80 fffff800`008fc797 : ffffe000`03e04030 00000000`00000000 ffffd000`207f8bf8 00000000`00000000 : athwnx!MPHandleInterrupt+0x3affffd000`207f8bc0 fffff800`138e8d10 : ffffd000`207f8e70 ffffd000`207f8df0 ffffd000`207f8e70 ffffe000`001de118 : ndis!ndisInterruptDpc+0x2a247ffffd000`207f8cf0 fffff800`138e89f0 : 80000000`00a00121 ffffd000`207c7180 80000000`00a00121 ffffd000`2345dc80 : nt!KiExecuteAllDpcs+0x1b0ffffd000`207f8e40 fffff800`139dedd5 : 80000000`00a00121 ffffd000`207c7180 ffffd000`227c5d20 ffffd000`21333640 : nt!KiRetireDpcList+0xd0ffffd000`207f8fb0 fffff800`139debd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5ffffd000`227c5c60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinueSYMBOL_NAME:  athwnx!ath_gpio_handle_intr+36IMAGE_NAME:  athwnx.sysFAILURE_BUCKET_ID:  AV_CODE_AV_NULL_IP_athwnx!ath_gpio_handle_intrBUCKET_ID:  AV_CODE_AV_NULL_IP_athwnx!ath_gpio_handle_intr    Loaded symbol image file: athwnx.sys    Image path: \SystemRoot\system32\DRIVERS\athwnx.sys    Image name: athwnx.sys    Timestamp:        Mon Apr 01 07:32:05 2013 (51591BD5)
Link to comment
Share on other sites

Hi Andre,

Thanks! :)

I dont know what Atheros is, but I installed the right driver of my tp-link wireless adapter which I downloaded from their website, and that did the job.

I rebooted my pc once and it didnt give the error, so I guess its solved now :)

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...