Windows 8 and 8.1 Forums


Random BSODs (driver_irql_not_less_or_equal L1C63x64.sys)

  1. #1


    Posts : 5
    Windows 8.1 Pro

    Random BSODs (driver_irql_not_less_or_equal L1C63x64.sys)


    Hello. I get BSODs while playing video games (WoW, Dying Light, Heroes of the Storm...) and/or while downloading torrents. Sometimes I get 3 per one evening. Sometimes I don't see them by weeks. Tried to update drivers, windows updates. Does not help. Can you help me?
    On win7 I don't have BSOD. After install 8.1 I started to get this BSOD (driver_irql_not_less_or_equal L1C63x64.sys).
    Can you help me?

      My System SpecsSystem Spec

  2. #2


    Posts : 356
    Windows 8.1 Enterprise


    Hi,
    Your Atheros driver seems to be for windows 8 not 8.1
    Maybe I'm wrong but there is a newer version than the one you currently have installed.

    All of dump files you provided are about Atheros driver problem:

    Code:
    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.
    
    
    MODULE_NAME: L1C63x64 ( Qualcom Atheros AR8151 NDIS 6.30 )

    You can download for Windows 8.1 x64 from following site:
    https://www.atheros.cz/atheros-netwo...et=50&system=8

    On *top* of that page make sure you download for Windows 8.1 x64
    extract the file into new folder somewhere, open device manager, right click on Qualcom Atheros AR8151 and select update driver software.
    then tell him where you extracted downloaded driver like this:
    Attachment 60851
      My System SpecsSystem Spec

  3. #3


    Posts : 5
    Windows 8.1 Pro


    Quote Originally Posted by Addictive Gamer
    You can download for Windows 8.1 x64 from following site:
    https://www.atheros.cz/atheros-netwo...et=50&system=8

    On *top* of that page make sure you download for Windows 8.1 x64
    extract the file into new folder somewhere, open device manager, right click on Qualcom Atheros AR8151 and select update driver software.
    then tell him where you extracted downloaded driver like this:
    OK. Downloaded, uninstalled current driver and updated to this one. In archive there are two versions x86 and x86_64. Info about new installed driver:
    Attachment 60869

    Rebooted computer. Will see if update help. Thanks.
      My System SpecsSystem Spec

  4. #4


    Posts : 5
    Windows 8.1 Pro


    Did not help. Fresh dm log attached. I enabled uTP transfers in my torrent client, added torrent with many seeds (to fill my internet channel 50Mb/s) and played WoW. After 5-10 minutes of gameplay I get BSOD.
      My System SpecsSystem Spec

  5. #5


    Posts : 356
    Windows 8.1 Enterprise


    Hi,
    Last dump file is about the same problem, here is a comparison of few dumps, and all are showing the same problem where the memory address is invalid: (I've removed some content and mark important with red)

    Code:
    Dump 1:
    
    4: kd> !analyze
    BugCheck D1, {ffffcf811c058dd0, 2, 0, fffff801c1fc9101}
    
    Probably caused by : L1C63x64.sys ( L1C63x64+7101 ) 
    
    ---------
    
    
    4: kd> !pte ffffcf811c058dd0
                                               VA ffffcf811c058dd0
    PXE at FFFFF6FB7DBEDCF8    PPE at FFFFF6FB7DB9F020    PDE at FFFFF6FB73E04700    PTE at FFFFF6E7C08E02C0
    contains 0000000100041863  contains 0000000100040863  contains 000000006531D863  contains 7800DDD480000000
    pfn 100041    ---DA--KWEV  pfn 100040    ---DA--KWEV  pfn 6531d     ---DA--KWEV  not valid
                                                                                      PageFile:  0
                                                                                      Offset: 7800ddd4
                                                                                      Protect: 0
    4: kd> k
    Child-SP          RetAddr           Call Site
    ffffd000`251abfb8 fffff800`f2f645e9 nt!KeBugCheckEx
    ffffd000`251abfc0 fffff800`f2f62e3a nt!KiBugCheckDispatch+0x69
    ffffd000`251ac100 fffff800`49fbb101 nt!KiPageFault+0x23a
    ffffd000`251ac290 ffffe000`c0209a20 L1C63x64+0x7101
    ffffd000`251ac298 ffffe000`c0209000 0xffffe000`c0209a20
    ffffd000`251ac2a0 ffffe000`c02bdf48 0xffffe000`c0209000
    ffffd000`251ac2a8 ffffcf81`0000010e 0xffffe000`c02bdf48
    ffffd000`251ac2b0 ffffe000`c027e6c0 0xffffcf81`0000010e
    ffffd000`251ac2b8 00000000`000001c0 0xffffe000`c027e6c0
    ffffd000`251ac2c0 00000000`00000000 0x1c0
    
    
    Dump 2:
    0: kd> !analyze
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck D1, {ffffcf80df612e80, 2, 0, fffff801fea18101}
    
    
    Probably caused by : L1C63x64.sys ( L1C63x64+7101 )
    
    
    Followup: MachineOwner
    ---------
    
    
    0: kd> !pte ffffcf80df612e80
                                               VA ffffcf80df612e80
    PXE at FFFFF6FB7DBEDCF8    PPE at FFFFF6FB7DB9F018    PDE at FFFFF6FB73E037D8    PTE at FFFFF6E7C06FB090
    contains 0000000100071863  contains 0000000100070863  contains 0000000003413863  contains 78015893F0000000
    GetUlongFromAddress: unable to read from fffff801589db10c
    pfn 100071    ---DA--KWEV  pfn 100070    ---DA--KWEV  pfn 3413      ---DA--KWEV  not valid
                                                                                      PageFile:  0
                                                                                      Offset: 78015893
                                                                                      Protect: 0
    
    
    0: kd> k
    Child-SP          RetAddr           Call Site
    ffffd000`24834ce8 fffff801`587d47e9 nt!KeBugCheckEx
    ffffd000`24834cf0 fffff801`587d303a nt!KiBugCheckDispatch+0x69
    ffffd000`24834e30 fffff801`fea18101 nt!KiPageFault+0x23a
    ffffd000`24834fc0 ffffe001`58574a20 L1C63x64+0x7101
    ffffd000`24834fc8 ffffe001`58574000 0xffffe001`58574a20
    ffffd000`24834fd0 ffffe001`57a8a710 0xffffe001`58574000
    ffffd000`24834fd8 ffffcf80`00000075 0xffffe001`57a8a710
    ffffd000`24834fe0 ffffe001`57a6d980 0xffffcf80`00000075
    ffffd000`24834fe8 00000000`000001c0 0xffffe001`57a6d980
    ffffd000`24834ff0 00000000`00000000 0x1c0
    
    Dump 3:
    2: kd> !analyze
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck D1, {ffffcf80c0fb2e80, 2, 0, fffff80180fd4101}
    
    
    Probably caused by : L1C63x64.sys ( L1C63x64+7101 ) 
    
    
    Followup: MachineOwner
    ---------
    
    
    2: kd> !pte ffffcf80c0fb2e80
                                               VA ffffcf80c0fb2e80
    PXE at FFFFF6FB7DBEDCF8    PPE at FFFFF6FB7DB9F018    PDE at FFFFF6FB73E03038    PTE at FFFFF6E7C0607D90
    contains 000000010000C863  contains 00000002057CD863  contains 000000005A8AC863  contains 7802D11420000000
    GetUlongFromAddress: unable to read from fffff802d11df104
    pfn 10000c    ---DA--KWEV  pfn 2057cd    ---DA--KWEV  pfn 5a8ac     ---DA--KWEV  not valid
                                                                                      PageFile:  0
                                                                                      Offset: 7802d114
                                                                                      Protect: 0
    
    
    2: kd> k
    Child-SP          RetAddr           Call Site
    ffffd000`2844bce8 fffff802`d0fd84e9 nt!KeBugCheckEx
    ffffd000`2844bcf0 fffff802`d0fd6d3a nt!KiBugCheckDispatch+0x69
    ffffd000`2844be30 fffff801`80fd4101 nt!KiPageFault+0x23a
    ffffd000`2844bfc0 ffffe001`c9277a20 L1C63x64+0x7101
    ffffd000`2844bfc8 ffffe001`c9277000 0xffffe001`c9277a20
    ffffd000`2844bfd0 ffffe001`c930ba68 0xffffe001`c9277000
    ffffd000`2844bfd8 ffffcf80`000000da 0xffffe001`c930ba68
    ffffd000`2844bfe0 ffffe001`c92a01c0 0xffffcf80`000000da
    ffffd000`2844bfe8 00000000`000001c0 0xffffe001`c92a01c0
    ffffd000`2844bff0 00000000`00000000 0x1c0

    From the above it's clear that L1C63x64.sys which is Atheros driver is causing this fault, we can't blame some application because all the addresses begin with ffffd000 which isn't in user space, for example here is a list of processes according to the above output:

    Code:
    4: kd> !process
    GetPointerFromAddress: unable to read from fffff800ddde5000
    PROCESS ffffe00046850900
        SessionId: none  Cid: 0004    Peb: 00000000  ParentCid: 0000
        DirBase: 001aa000  ObjectTable: ffffc00041203000  HandleCount: <Data Not Accessible>
        Image: System
    
    0: kd> !process
    GetPointerFromAddress: unable to read from fffff801589db000
    PROCESS ffffe0015aa9d800
        SessionId: none  Cid: 0a94    Peb: 7f119000  ParentCid: 0c6c
        DirBase: cee17000  ObjectTable: ffffc000d8fe2680  HandleCount: <Data Not Accessible>
        Image: qbittorrent.ex
    
    2: kd> !process
    GetPointerFromAddress: unable to read from fffff801221eb000
    PROCESS ffffe0005d8bd900
        SessionId: none  Cid: 1b40    Peb: 7f6bb000  ParentCid: 0e8c
        DirBase: 1d54ba000  ObjectTable: ffffc000fdde79c0  HandleCount: <Data Not Accessible>
        Image: WinSCP.exe
    
    4: kd> !process
    GetPointerFromAddress: unable to read from fffff800f316b000
    PROCESS ffffe000bb704700
        SessionId: none  Cid: 0820    Peb: 7e884000  ParentCid: 18b4
        DirBase: 1ef369000  ObjectTable: ffffc0006dbc32c0  HandleCount: <Data Not Accessible>
        Image: Skype.exe
    So not only that the address is in kernel space but also process involved is a random networking process, so blaming particular program does not make any logic.


    So what we can try is to test another driver, following are your adapter details:

    PCI-E Ethernet NDIS 6.30 ( Windows 8 )
    PCI\VEN_1969&DEV_1083&SUBSYS_E0001458&REV_C0


    From same webpage as last time but for windows 8 and somewhat older that you had previously, difference being that it addresses exact VEN\DEV number and NDIS 6.30 But it's not for Windows 8.1

    https://www.atheros.cz/atheros-network-download.php?chipset=50&system=8

    ABOVE LINK

    In the above page download button is at the very bottom of the page, one that says:



    If you press CTRL + F on that page and search for
    PCI\VEN_1969&DEV_1083&SUBSYS_E0001458&REV_C0
    you will see your version is listed there.

    Can't say if that will really work but testing doesn't cost anything

    Try to reproduce BSOD as you did last time. and report results.


    If the above driver won't work...

    You can try to uninstall the driver and check the "Delete the driver software for this device" checkbox
    and update the driver from Windows update instead.

    For this to work you need to have this option enabled in:
    Control Panel\System and Security\System > Advanced system properties > hardware > device installation settings.
    Last edited by Addictive Gamer; 26 Apr 2015 at 17:01.
      My System SpecsSystem Spec

  6. #6


    Posts : 5
    Windows 8.1 Pro


    Hi
    From the above it's clear that L1C63x64.sys which is Atheros driver is causing this fault, we can't blame some application because all the addresses begin with ffffd000 which isn't in user space,
    So not only that the address is in kernel space but also process involved is a random networking process, so blaming particular program does not make any logic.
    I think it will be good idea to tell atheros about this problem. But I can't find support portal or forum from them. Thank for your detailed answer, will try older version.

    I tried 2.1.0.7 version you mentioned -- received BSOD. Tried version from windows update 2.1.0.16 -- received BSOD. May it be that problem in memory not in network driver?
    Fresh DM log attached.
    Last edited by Sayer; 27 Apr 2015 at 13:05. Reason: added some info
      My System SpecsSystem Spec

  7. #7


    Posts : 356
    Windows 8.1 Enterprise


    If you wish you can contact Atheros for drivers here https://www.qualcomm.com/contact

    Did you receive disc with drivers probably while buying PC?
      My System SpecsSystem Spec

  8. #8


    Posts : 5
    Windows 8.1 Pro


    Quote Originally Posted by Addictive Gamer View Post
    If you wish you can contact Atheros for drivers here https://www.qualcomm.com/contact
    I will try to contact Gigabyte and Atheros.

    Did you receive disc with drivers probably while buying PC?
    Yes.
    Last edited by Sayer; 06 May 2015 at 11:07. Reason: fix typo
      My System SpecsSystem Spec

Random BSODs (driver_irql_not_less_or_equal L1C63x64.sys)
Related Threads
Hi, I've had a random BSOD just while surfing the web. Here are the results from your analyzing tool. 59825 I haven't recently installed anything on the PC, nor updated any drivers. The PC is a laptop, store bought, no hardware modifications. Thanks for any help !
Hi, The BSOD is happening constantly. Driving me NUTS. I ran Whocrashed and it comes back with file path: C:\WINDOWS\system32\drivers\l1c63x64.sys product: Qualcomm Atheros Ar81xx series PCI-E Gigabit Ethernet Controller company: Qualcomm Atheros Co., Ltd.
Hi For the past month or so i have been randomly been getting this BSOD error and then my computer restarts. At first i ignored it but now its become a bit of nuisance. Specs: Windows 8.1 processor: Interl(R) Core (TM) i7-4700HQ CPU @ 2.40GHz RAM: 12.0GB System: 64.bit operating system...
Hi there, new member joining here. :) So I've been having some random unexpected BSODS in the past few weeks that I disregarded (which was stupid) until now. After looking through countless of threads of people having the same error, I still haven't found the fix for mine. The BSODs that...
My laptop keeps crashing with the error in the title, and looking through it with blue screen view, I've noticed that each one has something different for the primary reason, could someone look through the dmps to find the reason and hopefully a fix. I have attatched all of the crashes through the...
Solved Driver_IRQL_Not_Less_Or_Equal BSODs in BSOD Crashes and Debugging
Computer has been hanging semi-regularly, where the entire screen freezes and any sound playing at the time begins to repeat, necessitating a hard shutdown. BSODs only happen sometimes. Any help would be greatly appreciated.
Solved DRIVER_IRQL_NOT_LESS_OR_EQUAL random BSOD in BSOD Crashes and Debugging
Hi, I recently installed Windows 8 and I had to do a clean install three times within 4 days. Something always messed up, so I need a permanent solution. I installed only drivers for my graphics card, audio and touchpad. The crash says DRIVER_IRQL_NOT_LESS_OR_EQUAL and I forgot what was in the...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook