Random BSOD Driver_IRQL_Not_Less_Or_Equal - L1C62x64.sys


  1. Posts : 3
    Windows 7 Home Premium x64
       #1

    Random BSOD Driver_IRQL_Not_Less_Or_Equal - L1C62x64.sys


    Hello, I'm getting BSOD at random times, like when i'm playing games, watching videos or just idling.

    I don't know if this is relevant, but tried to use my computer without my graphic card (it's a Nvidia GTX 650) for a month and I didn't get any BSOD. I got a new one thanks to my warranty, but the problem is the same as before.
      My Computer


  2. Posts : 81
    Windows 7 Ultimate X64
       #2

    Hello, and welcome to SevenForums!

    Your BSOD seems to be caused by your Atheros AR8171/8175 PCI-E Gigabit Ethernet Controller driver:

    Code:
    *******************************************************************************
    *                                                                             *
    *                        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: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff8800f006c9b, address which referenced memory
    
    Debugging Details:
    ------------------
    
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003309100
    GetUlongFromAddress: unable to read from fffff800033091c0
     0000000000000000 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    L1C62x64+6c9b
    fffff880`0f006c9b 488b08          mov     rcx,qword ptr [rax]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  uTorrent.exe
    
    TRAP_FRAME:  fffff8800c0d0ae0 -- (.trap 0xfffff8800c0d0ae0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=00000000000015f2
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800f006c9b rsp=fffff8800c0d0c70 rbp=fffffa80083cf3c8
     r8=0000000000000329  r9=fffffa8008293000 r10=fffffa8007fbb3a0
    r11=fffff8800c0d0c90 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    L1C62x64+0x6c9b:
    fffff880`0f006c9b 488b08          mov     rcx,qword ptr [rax] ds:00000000`00000000=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800030d1169 to fffff800030d1bc0
    
    STACK_TEXT:  
    fffff880`0c0d0998 fffff800`030d1169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0c0d09a0 fffff800`030cfde0 : fffff880`0f007301 00000000`00000001 fffffa80`087d5000 00000000`00000001 : nt!KiBugCheckDispatch+0x69
    fffff880`0c0d0ae0 fffff880`0f006c9b : fffffa80`07fbb1a0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
    fffff880`0c0d0c70 fffffa80`07fbb1a0 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`07fbb1a0 : L1C62x64+0x6c9b
    fffff880`0c0d0c78 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`07fbb1a0 fffffa80`083772f0 : 0xfffffa80`07fbb1a0
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    L1C62x64+6c9b
    fffff880`0f006c9b 488b08          mov     rcx,qword ptr [rax]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  L1C62x64+6c9b
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: L1C62x64
    
    IMAGE_NAME:  L1C62x64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  51e4eeac
    
    FAILURE_BUCKET_ID:  X64_0xD1_L1C62x64+6c9b
    
    BUCKET_ID:  X64_0xD1_L1C62x64+6c9b
    
    Followup: MachineOwner
    ---------
    You can try to reinstall the driver by following these steps:

    1) Hold CTRL+R on the keyboard.

    2) Type in "devmgmt.msc" (without quotes)

    3) Look for the device named something like "Atheros AR8171/8175 PCI-E Gigabit Ethernet Controller", it should be in the subset "Network Controllers".

    4) Right click it, and click "Uninstall". If it asks you if you want to delete the files, check the box under it.

    5) Restart your computer. If it is successful, it should say "Installing Device Driver Software" on the bottom task bar.

    Best of luck,

    PeregrineX
      My Computer


  3. Posts : 3
    Windows 7 Home Premium x64
    Thread Starter
       #3

    I did as you said but when I restarted my computer, I had to manually install the driver or else I couldn't access Internet.
    I can't say if it worked, so do I mark this thread as solved and create a new one if the BSOD comes back, or do I leave the thread as is and bump it back if the BSOD comes back ?
      My Computer


  4. Posts : 81
    Windows 7 Ultimate X64
       #4

    Sanya said:
    I did as you said but when I restarted my computer, I had to manually install the driver or else I couldn't access Internet.
    I can't say if it worked, so do I mark this thread as solved and create a new one if the BSOD comes back, or do I leave the thread as is and bump it back if the BSOD comes back ?
    Windows should install it whether or not it has internet.

    But, since you did reinstall it, use the computer for about an hour or so (or for the time the BSODs seemed to interval at), and then mark this question as "Solved".

    I'm glad I could help!

    PeregrineX
      My Computer


  5. Posts : 3
    Windows 7 Home Premium x64
    Thread Starter
       #5

    I'm sorry to bump this thread again, but I just got another BSOD with the same error code.
    I attached a new log archive to this post.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 08:53.
Find Us