Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


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

  • Please log in to reply
1 reply to this topic

#1 yeto


  • Members
  • 10 posts
  • Local time:02:11 PM

Posted 25 August 2017 - 03:23 PM

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 Q720
· Video Card = Nividia GeForce 310M
· MotherBoard - Laptop
· Power Supply -Laptop

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

· Laptop or Desktop? Laptop

Attached Files

Edited by yeto, 25 August 2017 - 10:20 PM.

BC AdBot (Login to Remove)


#2 joseibarra


  • Members
  • 1,286 posts
  • Gender:Male
  • Location:Downstairs
  • Local time:01:11 PM

Posted 26 August 2017 - 07:33 AM

When a BSOD implicates core Windows system files like ntoskrnl.exe (win32k.sys, ntdll.dll, etc.) those are extremity unlikely to be the cause of the crash.  If those files were afflicted millions of systems all over the world would be crashing and they're not. 


Many third party programs like WhoCrashed and BlueScreenView will implicate core Windows system files too but those tools are wrong about as often as they might be right about the cause of the crash. 


BlueScreenView even says:  However, be aware that the driver detection mechanism is not 100% accurate...


That is when the Windows debugging tools come in handy.


Is there anything in particular you know you can do to get the system to crash(watching videos, playing games, etc.) because if you make an adjustment and that failure condition is resolved you will know you are on the right track.


In your case analysis implicates your Atheros network driver:


kd> lmvm L1C62x64
start             end                 module name
fffff880`04faa000 fffff880`04fbf000   L1C62x64 T (no symbols)           
    Loaded symbol image file: L1C62x64.sys
    Image path: \SystemRoot\system32\DRIVERS\L1C62x64.sys
    Image name: L1C62x64.sys
    Timestamp:        Fri Nov 13 04:47:36 2009 (4AFD2B38)
    CheckSum:         0001CC1E
    ImageSize:        00015000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4


You can see the timestamp is from 2009 so that is pretty old.


Your system is a Toshiba Satellite P500 so you should hop out to the Toshiba Support site and see if there is a later version of the Atheros LAN driver for you to install and that link is here:




You can see that they have later versions of the Atheros LAN driver:



I would go with the one with the latest version - looks like Version:


Before updating the drivers it would be a good idea to make a manual System Restore point so that in case something goes wrong or things get worse you can undo the adjustment.


If you have more crashes after that upload those new crash dump files.


Your motherboard BIOS (1.90) is also quite out of date but I would not update that unless you know a later version fixes a specific problem.

Edited by joseibarra, 26 August 2017 - 07:40 AM.

The mediocre teacher tells. The good teacher explains. The superior teacher demonstrates.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users