Windows 10: BSOD After Windows 10 Upgrade error e22w8x64.sys and L1C63x64.sys

Hey guys first time poster but i dont know where else to turn.

After the upgrade from 8.1 I started seeing a BSOD with the error e22w8x64.sys but it wasn't that common. Now thought its as soon as I try to install a game, open multiple browser tabs or try to watch a YouTube video so u can imagine how frustrating it is!
I seen that it may be an error with my build in Killer network card E2200 so I tried a work around and thought i fixed the problem by installing a Qualcomm generic ethernet driver.
But now the problem still remains but I am getting a new error code L1C63x64.sys!

Its driving me to the point of insanity - im almost ready to dump the MSI board and buy one with an intel ethernet driver to get around this pain!

:)

 

Blue screen error in Windows 10

fffff800`39253328 fffff801`00ba6c9fUnable to load image \SystemRoot\system32\DRIVERS\L1C63x64.sys, Win32 error 0n2

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

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

L1C63x64+0x6c

Loaded symbol image file: L1C63x64.sys

Image path: \SystemRoot\system32\DRIVERS\L1C63x64.sys

Image name: L1C63x64.sys

Browse all global symbols functions data

Timestamp: Tue Jul 16 02:56:31 2013 (51E4EE9F)

Update Qualcomm Atheros AR8151 PCI-E Gigabit Ethernet Controller (NDIS 6.30) to the latest driver available and see if that helps.

 

BSOD UNEXPECTED_STORE_EXCEPTION Win10

I did as instructed and it worked for a couple of days but I just had another BSoD with the error DRIVER_IRQL_NOT_LESS_OR_EQUAL related to L1C63x64.sys

 

Hi TheGolfingPablo,

Welcome to the 10forums.

This thread will likely be moved to the right section by a moderator.

Right now, it looks like an Anti-Virus is causing this problem.
This is because it is making an illegal action with the internet, but because it is trying to communicate with the internet the network driver is being blamed in the first sight.
Although, the network driver might need an update
Code: 1: kd> lmvm L1C63x64 start end module name fffff800`63e00000 fffff800`63e23000 L1C63x64 T (no symbols) Loaded symbol image file: L1C63x64.sys Image path: \SystemRoot\system32\DRIVERS\L1C63x64.sys Image name: L1C63x64.sys Timestamp: Tue Jul 16 08:56:31 2013 (51E4EE9F) CheckSum: 0002426B ImageSize: 00023000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] Do you have more then 1 AV installed? I see drivers from Agnitum and Bullguard.
Having more then 1 AV installed gives performance issues, BSOD's and other problems.

 

Do you have more then 1 AV installed? I see drivers from Agnitum and Bullguard.
Having more then 1 AV installed gives performance issues, BSOD's and other problems.[/quote] Hi, thanks for the prompt reply! - I definitely have Bullguard as an AV Software but have never heard of the other one called Agnitum. Its not within my programs folder to allow me to uninstall it.

Whenever I ran device manager it kept telling me the driver was up to date - so I think you are definitely on the right track with some other source causing the BSODs.

Does this help? - I'm happy to try anything including relinquishing my subscription to another AV provider in order to remove this Rogue program or even turn away from Bullguard (as reliable as it has been for me).

I should also mention that I reset my windows 10 installation and that too didn't resolve the issue.

Thanks.

 

Hey man, just to post an update. I decided to uninstall the normally very reliable BullGuard program and voila - no more BSOD's (yet!), he adds with a gulp.

I installed Norton protection with a free 30 day trial and things seem to be working fine - even when I updated by Killer Network driver to include all its E2200 features. This excites me greatly!

I'll still keep an eye on things over the next few days but as the BSODs were so common before and I haven't had any whatsoever since the change in AV software I'm feeling hopeful!

The only downside is that I had already bought the license for Bullguard and it still has over a year to run and now I have to subscribe to the Norton service - but I guess £29.99 is a lot cheaper than swapping out the motherboard which I was thinking I had to do!

I'll not close the thread just yet, but like I say, its looking good!

Thanks a million for your help dude!

 

I just see I made a mistake, the driver from Agnitum that caused the problem is a part of BullGuard.

Did you uninstall BullGuard when upgrading to windows 10?
Not removing your current AV when upgrading could cause BSOD's and several other problems.
This is the reason why it is recommended to uninstall the AV and install again after the upgrade to windows 10.

 

This sounds like exactly what happened then. - No I didn't uninstall anything - I simply upgraded the OS and kept everything I had previous.

I will stick with Norton for now (as long as things stay stable) - although I still prefer Bullguard.

I am planning on some more upgrades over the next few months which will see me purchase the Asus x99 Deluxe MOBO and the 5920c CPU as well as new RAM obviously. I will also be upgrading my SSD to a larger capacity one and moving away from mechanical drives. With this in mind I could probably install Bullguard once again onto this fresh system without any issues.

Thanks!