Windows 10: BSOD Driver IRQL Not Less Or Equal L1C63x64.sys

Discus and support BSOD Driver IRQL Not Less Or Equal L1C63x64.sys in Windows 10 BSOD Crashes and Debugging to solve the problem; I am getting this error every time I try to open a browser window. I have seen others with the same question, and I have tried to resolve the issue... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Kyle D.N., Aug 19, 2020.

  1. KYLE D.N.
    Kyle D.N. Win User

    BSOD Driver IRQL Not Less Or Equal L1C63x64.sys


    I am getting this error every time I try to open a browser window. I have seen others with the same question, and I have tried to resolve the issue using the steps listed on their questions. Those steps do jot work for me.


    Any help would be very welcome.

    :)
     
    Kyle D.N., Aug 19, 2020
    #1
  2. JOY KEMPRAI
    Joy Kemprai Win User

    BSOD - driver_irql_not_less_or_equal (l1c63x64.sys)

    Hi Seung,

    Sorry for the inconvenience caused by BSOD - driver_irql_not_less_or_equal (l1c63x64.sys).

    Please let us know the make/model of your computer.

    The L1C63x64.sys is the Atheros LAN driver and I would suggest to uninstall and reinstall the Atheros LAN driver but install the latest Atheros LAN driver by visiting the manufacture's website and avoid using any LAN driver available though Windows Update.

    However the problem could also be with any VPN software and other software so make sure you have the latest version of each of these software.

    If the errors continue uninstall the VPN software and check if the issue persist.

    Hope this helps. Get back to us for further queries for BSOD - driver_irql_not_less_or_equal (l1c63x64.sys). We are happy to help!
     
    Joy Kemprai, Aug 19, 2020
    #2
  3. KLEEMC
    kleemc Win User
    BSOD - IRQL NOT LESS OR EQUAL / L1C63x64.sys

    I'm using Windows 10 on a desktop Core i7 PC. This windows was an upgrade from Win 7 but it was upgraded more than a year ago. I never had any issue but recently I had 3 blue screens in about 10 days. Today I had the 3rd one. The error message was

    BSOD - IRQL NOT LESS OR EQUAL

    What Failed - L1C63x64.sys

    I searched the web for solution. Many posts suggested issue with the graphics card. I updated the driver for my nVidia graphics card. But it still happened today. The minidump file shows the following data. I have no idea what to make of it
    and what other actions to take. I noticed : "PROCESS_NAME: Dropbox.exe" Does this mean Dropbox is causing the issue ?

    Appreciate advice. Thank you.

    --------------------------------------------------------------------------------------------------------------------------------------

    BugCheck D1, {0, 2, 0, fffff8003d426cb3}

    *** WARNING: Unable to verify timestamp for L1C63x64.sys

    *** ERROR: Module load completed but symbols could not be loaded for L1C63x64.sys

    Probably caused by : L1C63x64.sys ( L1C63x64+6cb3 )

    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: 0000000000000000, memory referenced

    Arg2: 0000000000000002, IRQL

    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation

    Arg4: fffff8003d426cb3, address which referenced memory

    Debugging Details:

    ------------------

    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING: 10.0.14393.576 (rs1_release_inmarket.161208-2252)

    SYSTEM_MANUFACTURER: Hewlett-Packard

    SYSTEM_PRODUCT_NAME: h9-1180d

    SYSTEM_SKU: H1M75AA#AB4

    BIOS_VENDOR: AMI

    BIOS_VERSION: 8.21

    BIOS_DATE: 10/20/2014

    BASEBOARD_MANUFACTURER: PEGATRON CORPORATION

    BASEBOARD_PRODUCT: 2AD5

    BASEBOARD_VERSION: 1.03

    DUMP_TYPE: 2

    DUMP_FILE_ATTRIBUTES: 0x8

    Kernel Generated Triage Dump

    BUGCHECK_P1: 0

    BUGCHECK_P2: 2

    BUGCHECK_P3: 0

    BUGCHECK_P4: fffff8003d426cb3

    READ_ADDRESS: fffff802595b9338: Unable to get MiVisibleState

    0000000000000000

    CURRENT_IRQL: 2

    FAULTING_IP:

    L1C63x64+6cb3

    fffff800`3d426cb3 488b08 mov rcx,qword ptr [rax]

    CPU_COUNT: 8

    CPU_MHZ: d40

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 3a

    CPU_STEPPING: 9

    CPU_MICROCODE: 6,3a,9,0 (F,M,S,R) SIG: 1B'00000000 (cache) 1B'00000000 (init)

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: AV

    PROCESS_NAME: Dropbox.exe

    ANALYSIS_SESSION_HOST: KL_HP_CORE_I7DT

    ANALYSIS_SESSION_TIME: 01-09-2017 12:46:09.0791

    ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

    TRAP_FRAME: ffffb080d71c4eb0 -- (.trap 0xffffb080d71c4eb0)

    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=fffff8003d426cb3 rsp=ffffb080d71c5040 rbp=ffff9f0ffd481e00

    r8=00000000000002c7 r9=ffff9f0ffd317000 r10=0000000000000000

    r11=ffffb080d71c5000 r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0 nv up ei pl nz na pe nc

    L1C63x64+0x6cb3:

    fffff800`3d426cb3 488b08 mov rcx,qword ptr [rax] ds:00000000`00000000=????????????????

    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80259367829 to fffff8025935c6f0

    STACK_TEXT:

    ffffb080`d71c4d68 fffff802`59367829 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

    ffffb080`d71c4d70 fffff802`59365e07 : ffffb080`d71c5110 fffff802`59a37e08 ffff9f00`00000b50 00000000`00000001 : nt!KiBugCheckDispatch+0x69

    ffffb080`d71c4eb0 fffff800`3d426cb3 : ffff9f00`008c6b10 de5cd2f8`2fe76307 ffff9f00`008c6cf3 ffff9f0f`fd481e00 : nt!KiPageFault+0x247

    ffffb080`d71c5040 ffff9f00`008c6b10 : de5cd2f8`2fe76307 ffff9f00`008c6cf3 ffff9f0f`fd481e00 00000000`00000018 : L1C63x64+0x6cb3

    ffffb080`d71c5048 de5cd2f8`2fe76307 : ffff9f00`008c6cf3 ffff9f0f`fd481e00 00000000`00000018 ffff9f00`008c6cf3 : 0xffff9f00`008c6b10

    ffffb080`d71c5050 ffff9f00`008c6cf3 : ffff9f0f`fd481e00 00000000`00000018 ffff9f00`008c6cf3 ffff9f00`028503e8 : 0xde5cd2f8`2fe76307

    ffffb080`d71c5058 ffff9f0f`fd481e00 : 00000000`00000018 ffff9f00`008c6cf3 ffff9f00`028503e8 ffff9f0f`fd44d030 : 0xffff9f00`008c6cf3

    ffffb080`d71c5060 00000000`00000018 : ffff9f00`008c6cf3 ffff9f00`028503e8 ffff9f0f`fd44d030 ffff9f0f`fd481e00 : 0xffff9f0f`fd481e00

    ffffb080`d71c5068 ffff9f00`008c6cf3 : ffff9f00`028503e8 ffff9f0f`fd44d030 ffff9f0f`fd481e00 00000000`00000000 : 0x18

    ffffb080`d71c5070 ffff9f00`028503e8 : ffff9f0f`fd44d030 ffff9f0f`fd481e00 00000000`00000000 ffff9f0f`fd317a20 : 0xffff9f00`008c6cf3

    ffffb080`d71c5078 ffff9f0f`fd44d030 : ffff9f0f`fd481e00 00000000`00000000 ffff9f0f`fd317a20 fffff800`3d426edb : 0xffff9f00`028503e8

    ffffb080`d71c5080 ffff9f0f`fd481e00 : 00000000`00000000 ffff9f0f`fd317a20 fffff800`3d426edb ffff9f0f`000000b7 : 0xffff9f0f`fd44d030

    ffffb080`d71c5088 00000000`00000000 : ffff9f0f`fd317a20 fffff800`3d426edb ffff9f0f`000000b7 00000000`00000000 : 0xffff9f0f`fd481e00

    STACK_COMMAND: kb

    THREAD_SHA1_HASH_MOD_FUNC: 6848407ae33d8b824e44a663bf3b11779613f277

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: c80863aa88b03eae30cc377f2fdfbe2d3f947016

    THREAD_SHA1_HASH_MOD: 6a0b43a94793034e39a5e317480a3872f9f5cf50

    FOLLOWUP_IP:

    L1C63x64+6cb3

    fffff800`3d426cb3 488b08 mov rcx,qword ptr [rax]

    FAULT_INSTR_CODE: 48088b48

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: L1C63x64+6cb3

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: L1C63x64

    IMAGE_NAME: L1C63x64.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 5158fbc5

    BUCKET_ID_FUNC_OFFSET: 6cb3

    FAILURE_BUCKET_ID: AV_L1C63x64!unknown_function

    BUCKET_ID: AV_L1C63x64!unknown_function

    PRIMARY_PROBLEM_CLASS: AV_L1C63x64!unknown_function

    TARGET_TIME: 2017-01-09T16:53:31.000Z

    OSBUILD: 14393

    OSSERVICEPACK: 576

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 784

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2016-12-09 04:23:02

    BUILDDATESTAMP_STR: 161208-2252

    BUILDLAB_STR: rs1_release_inmarket

    BUILDOSVER_STR: 10.0.14393.576

    ANALYSIS_SESSION_ELAPSED_TIME: 564

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:av_l1c63x64!unknown_function

    FAILURE_ID_HASH: {1c745e23-731f-42c8-af3a-346943adb42b}

    Followup: MachineOwner

    ---------
     
    kleemc, Aug 19, 2020
    #3
  4. BOOFIE
    boofie Win User

    BSOD Driver IRQL Not Less Or Equal L1C63x64.sys

    BSOD playing Overwatch, error L1C63x64.sys

    Hi all,
    I have been experiencing this BSOD: Driver IRQL Not Less or Equal, L1C63x64.sys for a few months now.
    When it happens, it is only when I am in the middle of gaming (Overwatch).
    After some research, I see that there are many of the same problems with my ethernet driver (Qualcomm Atheros AR8161). I have updated the driver via the Device Manager on my computer.
    I am hoping maybe there is a different fix other than having to replace my ethernet port/motherboard, because that seems like it is the next step.
    Thank you,
    -b
    Attachment 113147
     
    boofie, Aug 19, 2020
    #4
Thema:

BSOD Driver IRQL Not Less Or Equal L1C63x64.sys

Loading...

  1. BSOD Driver IRQL Not Less Or Equal L1C63x64.sys - Similar Threads - BSOD Driver IRQL

  2. Driver IRQL not less or equal dxgmms2.sys

    in Windows 10 Gaming
    Driver IRQL not less or equal dxgmms2.sys: I am getting one BSOD after another while working on my Windows 10 Pro PC. I also got these in the BSOD messages:Kernel Security Check FailureSystem Thread Exception Not HandledDriver IRQL not less or equalAnyone have any idea why?...

  3. Driver IRQL not less or equal dxgmms2.sys

    in Windows 10 Software and Apps
    Driver IRQL not less or equal dxgmms2.sys: I am getting one BSOD after another while working on my Windows 10 Pro PC. I also got these in the BSOD messages:Kernel Security Check FailureSystem Thread Exception Not HandledDriver IRQL not less or equalAnyone have any idea why?...

  4. Driver IRQL not less or equal dxgmms2.sys

    in Windows 10 BSOD Crashes and Debugging
    Driver IRQL not less or equal dxgmms2.sys: I am getting one BSOD after another while working on my Windows 10 Pro PC. I also got these in the BSOD messages:Kernel Security Check FailureSystem Thread Exception Not HandledDriver IRQL not less or equalAnyone have any idea why?...

  5. Driver Irql Not Equal Or Less - Qcamain10x64.sys

    in Windows 10 BSOD Crashes and Debugging
    Driver Irql Not Equal Or Less - Qcamain10x64.sys: For several months I've been intermittently receiving the blue screen of death with the stop code: "DRIVER_IRQL_NOT_LESS_OR_EQUAL" and what failed as "Qcamain10x64.sys" I haven't installed any new drivers lately and much of what I've read online has been around uninstalling...

  6. Stop code: Driver IRQL NOT LESS OR EQUAL / What failed: L1C63x64.sys

    in Windows 10 Drivers and Hardware
    Stop code: Driver IRQL NOT LESS OR EQUAL / What failed: L1C63x64.sys: I have been getting the "blue screen of death" for a few months now. It only seems to happen when I am on video calls over Zoom. Here is a link to the dump files: https://1drv.ms/u/s!Aq-2kr212YARjkU1HESRGUTASEJC?e=A2nRRs What can I do to fix this?...

  7. Driver IRQL not Less or Equal - l1c63x64.sys

    in Windows 10 BSOD Crashes and Debugging
    Driver IRQL not Less or Equal - l1c63x64.sys: So these BSODs have been bugging me for quite a while now. Sometimes they just appear completely at random. I just had a 2 month clean go, and then it came back 3 times in 2 days. At other times, they seem to link with windows update, which goes like this: I get a...

  8. BSOD fault=Driver IRLQ not Less or Equal - L1C63x64.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD fault=Driver IRLQ not Less or Equal - L1C63x64.sys: Have gotten a bunch of BSOD due to this problem last few days, cleared out minidump folder so there wouldn't be anything unrelated to this problem and used your program to capture the information to see what you guys could find that would help me. I seen a few others...

  9. Driver IRLQ not Less or Equal - L1C63x64.sys

    in Windows 10 BSOD Crashes and Debugging
    Driver IRLQ not Less or Equal - L1C63x64.sys: A couple of times a week my computer will freeze and the audio goes go into a loop, followed by a BSOD showing DRIVER_IRQL_NOT_LESS_OR_EQUAL blaming L1C63x64.sys (Atheros LAN). This generally happens when playing games, though I've had it once or twice while just watching a...

  10. bsod - driver less or equal L1C63x64

    in Windows 10 BSOD Crashes and Debugging
    bsod - driver less or equal L1C63x64: hi, im a complete luddite to be honest so need all the help possible... i play mostly one game, Hawken. I just upgraded from win7 pro to win10 pro. I used to get a different BSOD in win7 and only now and again. Now in 10 i get it 4/5/6 times a day, sometimes it just keeps...