1. #1

    BSOD caused by driver: ntoskrnl.exe and L1C62x64.sys

    SysnativeFileCollectionApp.zip
    OS - Windows 7
    x86 x64
    What was original installed OS on system? Windows 7
    The OS is OEM version (came pre-installed on system)
    Age of system (hardware) = 8 years
    Age of OS installation - have you re-installed the OS? 8 years...have not re-installed

    CPU = Intel I7
    Video Card = Nividia GeForce 310M
    MotherBoard - Laptop
    Power Supply -Laptop

    System Manufacturer = Dell
    Exact model number (if laptop, check label on bottom)

    Laptop or Desktop? Laptop


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2
    Sysnative Staff
    BSOD Kernel Dump Analyst
    Contributor

    Join Date
    May 2015
    Location
    The Netherlands
    Age
    21
    Posts
    505
    • specs System Specs
      • Manufacturer:
        Custom build
      • Motherboard:
        Gigabyte B150-HD3P-CF
      • CPU:
        Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
      • Memory:
        16GB DDR4 Crucial Ballistix Sport LT BLS8G4D240F
      • Graphics:
        Intel(R) HD Graphics 530
      • Sound Card:
        (1) Intel(R) Display Audio (2) Realtek HD Audio
      • Hard Drives:
        Crucial MX200 500GB & 2x Toshiba DT01ACA300
      • Power Supply:
        Corsair RM550x
      • Case:
        Fractal Design Define S
      • Cooling:
        Cooler Master TX3 i
      • Display:
        24" Liyama ProLite XB2483HSU-B2 & 24" Dell Ultrasharp U2414H
      • Operating System:
        Windows 10 Pro

    Re: BSOD caused by driver: ntoskrnl.exe and L1C62x64.sys

    Hi yeto,

    Welcome to Sysnative

    Please check Networx and Juniper for software updates and check Toshiba for BIOS updates.

    Code:
    5: kd> !dpx
    Start memory scan  : 0xfffff88010fad208 ($csp)
    End memory scan    : 0xfffff88010fb0000 (Stack Base)
    
                   rsp : 0xfffff88010fad208 : 0xfffff8000350fecb : nt!KipFatalFilter+0x1b
                   r10 : 0xfffff88010faf4d0 : 0xfffff88001867b80 : tcpip!TcpTlConnectionSendCalloutRoutine
                   r11 : 0xfffff88010fad2f8 : 0xfffff800034a699d : nt!RtlpExecuteHandlerForException+0xd
    0xfffff88010fad208 : 0xfffff8000350fecb : nt!KipFatalFilter+0x1b
    0xfffff88010fad280 : 0xfffff88010fad3c0 : 0xfffff80003487308 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    0xfffff88010fad288 : 0xfffff800034a6f24 : nt!_C_specific_handler+0x8c
    0xfffff88010fad2b8 : 0xfffff800034a6a7b : nt!KeQueryCurrentStackInformation+0x4b
    0xfffff88010fad2d8 : 0xfffff800034a6e98 : nt!_C_specific_handler
    0xfffff88010fad2e0 : 0xfffff8000368df24 : "nt!BBTBuffer <PERF> (nt+0x282f24)"
    0xfffff88010fad2e8 : 0xfffff80003487308 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    0xfffff88010fad2f8 : 0xfffff800034a699d : nt!RtlpExecuteHandlerForException+0xd
    0xfffff88010fad318 : 0xfffff8000340b000 : "nt!KdpReport <PERF> (nt+0x0)"
    0xfffff88010fad320 : 0xfffff88010fad3c0 : 0xfffff80003487308 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    0xfffff88010fad328 : 0xfffff800034a5775 : nt!RtlDispatchException+0x415
    0xfffff88010fad338 : 0xfffff88010fad378 : 0xfffff8000340b000 : "nt!KdpReport <PERF> (nt+0x0)"
    0xfffff88010fad348 : 0xfffff8000340b000 : "nt!KdpReport <PERF> (nt+0x0)"
    0xfffff88010fad378 : 0xfffff8000340b000 : "nt!KdpReport <PERF> (nt+0x0)"
    0xfffff88010fad398 : 0xfffff8000368df24 : "nt!BBTBuffer <PERF> (nt+0x282f24)"
    0xfffff88010fad3c0 : 0xfffff80003487308 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    0xfffff88010fad3c8 : 0xfffff8000340b000 : "nt!KdpReport <PERF> (nt+0x0)"
    0xfffff88010fad3d0 : 0xfffff8000368df24 : "nt!BBTBuffer <PERF> (nt+0x282f24)"
    0xfffff88010fad3f0 : 0xfffff800034a6e98 : nt!_C_specific_handler
    0xfffff88010fad4a8 : 0xfffff88010faf4d0 : 0xfffff88001867b80 : tcpip!TcpTlConnectionSendCalloutRoutine
    0xfffff88010fad508 : 0xfffff880018688ba : tcpip!TcpTlConnectionSend+0x7a
    0xfffff88010fad518 : 0xfffff88004da1697 : dxgmms1!VidSchiProcessIsrCompletedPacket+0x1eb
    0xfffff88010fad5a8 : 0xfffff88004da119e : dxgmms1!VidSchDdiNotifyInterruptWorker+0x1ea
    0xfffff88010fad8e8 : 0xfffff8800170f3d2 : ndis!ndisSendNBLToFilter+0x42
    0xfffff88010fad8f8 : 0xfffff8800533e000 : L1C62x64
    0xfffff88010fad908 : 0xfffff8800533e000 : L1C62x64
    0xfffff88010fad918 : 0xfffff8800170d000 : "ndis!IsPM62Supported <PERF> (ndis+0x0)"
    0xfffff88010fad920 : 0xfffff8800177d79c : "ndis!__PchSym_ <PERF> (ndis+0x7079c)"
    0xfffff88010fad928 : 0xfffff8800170d000 : "ndis!IsPM62Supported <PERF> (ndis+0x0)"
    0xfffff88010fad930 : 0xfffff88001775354 : ndis!__PchSym_+0x444
    0xfffff88010fad938 : 0xfffff88002eec000 : jnprns
    0xfffff88010fad948 : 0xfffff88002eec000 : jnprns
    0xfffff88010fad958 : 0xfffff88002eec000 : jnprns <-- Juniper driver
    0xfffff88010fad968 : 0xfffff8800170d000 : "ndis!IsPM62Supported <PERF> (ndis+0x0)"
    0xfffff88010fad970 : 0xfffff88001775354 : ndis!__PchSym_+0x444
    0xfffff88010fad978 : 0xfffff88002eb0000 : "pacer!PcFilterSendNetBufferListsComplete <PERF> (pacer+0x0)"
    0xfffff88010fad980 : 0xfffff88002ec3048 : "pacer!PcgTimerUnitAssignmentIndex <PERF> (pacer+0x13048)"
    0xfffff88010fad988 : 0xfffff8800170d000 : "ndis!IsPM62Supported <PERF> (ndis+0x0)"
    0xfffff88010fad990 : 0xfffff88001775330 : ndis!__PchSym_+0x420
    0xfffff88010fad998 : 0xfffff8800170d000 : "ndis!IsPM62Supported <PERF> (ndis+0x0)"
    0xfffff88010fad9a0 : 0xfffff8800177d7a8 : "ndis!__PchSym_ <PERF> (ndis+0x707a8)"
    0xfffff88010fad9a8 : 0xfffff88001803000 : "tcpip!WfpAleInitializeAleEpoch <PERF> (tcpip+0x0)"
    0xfffff88010fad9b0 : 0xfffff880019a4ed4 : "tcpip!LowMemoryEvent <PERF> (tcpip+0x1a1ed4)"
    0xfffff88010fada08 : 0xfffff800034b6cfd : nt!KiDispatchException+0x17d
    0xfffff88010fada68 : 0xfffff96000088d94 : win32k!FreeThreadBufferWithTag
    0xfffff88010fadb48 : 0xfffff88004da1697 : dxgmms1!VidSchiProcessIsrCompletedPacket+0x1eb
    0xfffff88010fadbd8 : 0xfffff88004da119e : dxgmms1!VidSchDdiNotifyInterruptWorker+0x1ea
    0xfffff88010fadec0 : 0xfffff800039f5888 : hal!HalpAllocateAdapterCallback
    0xfffff88010faded8 : 0xfffff800034a34e5 : nt!RtlGetExtendedContextLength+0x19
    0xfffff88010fae048 : 0xfffff800039f3e08 : hal!HalpDmaSyncMapBuffers+0x1b0
    0xfffff88010fae098 : 0xfffff8000347a00e : nt!KiExceptionDispatch+0xce
    0xfffff88010fae278 : 0xfffff8000347890a : nt!KiGeneralProtectionFault+0x10a
    0xfffff88010fae280 : 0x0000000000000001 :  Trap @ fffff88010fae280
    .....

    Code:
    fffff880`10612688  fffffa80`0a26b850
    fffff880`10612690  fffffa80`06fc03d0
    fffff880`10612698  fffffa80`0a26b9b0
    fffff880`106126a0  fffffa80`0a26b850
    fffff880`106126a8  fffff880`02f3f2cc*** WARNING: Unable to verify timestamp for networx.sys
    *** ERROR: Module load completed but symbols could not be loaded for networx.sys
     networx+0x62cc
    fffff880`106126b0  00000000`00000001
    fffff880`106126c0  00000000`01024d58
    fffff880`106126c8  fffff880`02ecb3aa afd!AfdAllocateMdlChain32+0xfa
    fffff880`106126d0  00000000`00000001
    fffff880`106126d8  00000000`00000000
    fffff880`106126e0  fffffa80`095e8e00
    fffff880`106126e8  00000000`00000000
    fffff880`106126f0  fffffa80`0a26b850
    fffff880`106126f8  fffff880`02f3ab6c networx+0x1b6c
    fffff880`10612700  fffffa80`0a26b9b0
    fffff880`10612708  00000000`00000000
    fffff880`10612710  fffffa80`06fc03d0
    fffff880`10612718  00000000`00695676
    fffff880`10612720  fffffa80`049c8b80
    fffff880`10612728  fffff880`02f449f0 networx+0xb9f0
    fffff880`10612730  00000000`00000000
    fffff880`10612738  fffffa80`0a144e30
    fffff880`10612740  00000000`00000000

  3. #3

    Re: BSOD caused by driver: ntoskrnl.exe and L1C62x64.sys

    Thank you for your reply.

    I can just delete the Networx software as I don't use it anyway.

    Related to the Juniper software how would I update? I see the following in "uninstall a program". Juniper Networks Setup Client 64-bit Activex Control and Juniper Networks Setup Client Activex Control. I don't recognize this software. Is this something I can delete? I am not sure what it does.

    Thank you for your help,
    yeto

  4. #4
    Sysnative Staff
    BSOD Kernel Dump Analyst
    Contributor

    Join Date
    May 2015
    Location
    The Netherlands
    Age
    21
    Posts
    505
    • specs System Specs
      • Manufacturer:
        Custom build
      • Motherboard:
        Gigabyte B150-HD3P-CF
      • CPU:
        Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
      • Memory:
        16GB DDR4 Crucial Ballistix Sport LT BLS8G4D240F
      • Graphics:
        Intel(R) HD Graphics 530
      • Sound Card:
        (1) Intel(R) Display Audio (2) Realtek HD Audio
      • Hard Drives:
        Crucial MX200 500GB &amp; 2x Toshiba DT01ACA300
      • Power Supply:
        Corsair RM550x
      • Case:
        Fractal Design Define S
      • Cooling:
        Cooler Master TX3 i
      • Display:
        24&quot; Liyama ProLite XB2483HSU-B2 &amp; 24&quot; Dell Ultrasharp U2414H
      • Operating System:
        Windows 10 Pro

    Re: BSOD caused by driver: ntoskrnl.exe and L1C62x64.sys

    It looks to me like those programs are part of something that already has been removed, it should be safe to remove the programs.

  5. #5
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    9,369
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1803 x64

    Re: BSOD caused by driver: ntoskrnl.exe and L1C62x64.sys

    Please check for updates for your Atheros NIC driver.

Similar Threads

  1. [SOLVED] BSOD 0x7f UNEXPECTED_KERNEL_MODE_TRAP caused by ntoskrnl.exe - Windows 7 x64
    By xOrrangee in forum BSOD, Crashes, Kernel Debugging
    Replies: 8
    Last Post: 07-23-2015, 06:42 PM
  2. [SOLVED] BSOD 0x7f UPEXPECTED_KERNEL_TRAP_MODE caused by ntoskrnl.exe - Windows 8.1 x64
    By error01671 in forum BSOD, Crashes, Kernel Debugging
    Replies: 14
    Last Post: 06-08-2015, 05:23 AM
  3. [SOLVED] KERNEL_DATA_INPAGE_ERROR Caused By Driver: ntoskrnl.exe - Windows 8.1 x64
    By velozity in forum BSOD, Crashes, Kernel Debugging
    Replies: 2
    Last Post: 01-21-2015, 03:43 AM
  4. [SOLVED] BSOD 0x7f UNEXPECTED_KERNEL_MODE_TRAP caused by ntoskrnl.exe Windows 8.1
    By Renault925 in forum BSOD, Crashes, Kernel Debugging
    Replies: 3
    Last Post: 11-11-2014, 04:32 PM
  5. [SOLVED] [Win7 x64] BSOD 0x7f UNEXPECTED_KERNEL_MODE_TRAP caused by ntoskrnl.exe
    By JX24 in forum BSOD, Crashes, Kernel Debugging
    Replies: 3
    Last Post: 06-17-2014, 04:27 PM

Log in

Log in