Windows 10: bsod - driver less or equal L1C63x64

This is the update to 4 days of support, locked pc for half a day (idiot support) - first it was Nvidia, most definately not Bullguard. Then it was BullGuard FW, then it wasnt! Now its network...they havnt got a clue...here is the support letter, bearing in mind this is after 4 diff sets of reportsa, 3 from them and a copy of the one following the instructions here...This is their explanation...

+++++++++++++++++++++++++++++++++++
First of all, on checking the minidump logs that you have sent us so far, the two crashes were related to the L1C63x64.sys driver.(Qualcomm Atheros Network driver).

BullGuard was indeed tested on Windows 10 platforms with fully compatible drivers and has passed all Microsoft compatibility tests. At this point, I would like to recommend a test with the BullGuard Firewall off and confirm whether or not the BlueScreen error persists.

If the problem is indeed solved once the Firewall is OFF, I can report this back to our Development team for further study along with the information already received and a set of our BullGuard diagnostic logs (note that these are needed in order to correlate and diagnose the behaviour of the application/drivers)

Browse to C:\Program Files\BullGuard Ltd\BullGuard\Support and run the application CollectLogs.bat. This will create a BullGuard Logs.7z file on your Desktop. Please attach the file to your reply e-mail.
++++++++++++++++++++++++++++++

Thery have had 4 sets of logs and even complied logs themselves in remote yesterday.

BullGuard are bloody useless and I still have the same problem. The only way my PC works properly is if BG is completely uninstalled using an avg uninstaller to clear everythinfg out my pc.

Now I am only reliant on windows defender, which isnt ideal *Sad

 

The network driver is blamed because it was the last driver that was active, but this does not mean it is the cause.

They better reproduce the problem fast and fix it, this isn't service a company should offer.

 

To make it a little bit more clear about the situation.

BullGuard wanted to access the internet.
BullGuard gave the network driver instructions for likely updating its definitions and the network driver is only following the instructions.
Windows saw this action and found it illegal.
Windows cannot find a solution for the problem and throws an error.
Last driver that was active was the network driver.

That is why the network driver is blamed, if I had to guess.

 

Essentially I have now been liasing with BG for a few weeks and getting nowhere. The problem is the BG driver 'BDNet' this is continually conflicting with my Nvidia driver and the network driver.

They have been taking control of my PC regularly running driver verification s/ware, collecting minidumps using their own error log reporting s/ware as well and finally after all this time I have managed a morning with NO BSOD at all!!!!! I have been dealing directly with the head of BullGuard development and it has still taken 3 or so weeks. This process started before I came to this site.

Its very useful and helpful to come here as I had to tell the engineer and correct him a few times in the correct direction of the error as he was convinced for 2 weeks that this was only a nvidia problem, then the penny dropped when I mentioned this site.

Thanks for the basic info that I was able to to pass on to get a start in problem solving this issue. I dont think this quick fix i have is the end of the matter but we will see....

*Smile

The problem is also the fact that the network driver is not all that happy working with BG and windows 10, so it returns the command and fails, there is no updated driver for the network card to work with Win10, and probably wont be.

 

You're welcome *Smile

Have they looked good at the dumps in the weeks that have passed?
It is very clear that BG is causing problems if they can look good at the dumps.

Just a small question, have you checked Atheros for network driver updates?

 

As you can see in the list, there are no windows 10 drivers at all, 32 or 64 bit...

Qualcomm ATHEROS Network drivers for Windows

I refuse to renew my MB after just 18months as well. The results have been generally poor whenm looking for a proper working solution. Its very frustrating when coders are too lazy to write the proper code and you are left with workaround of a workaround of a quickfix workaround...Surely its easier to just write new, and proper working code from scratch. Its not like its all new now is it :-O

I have marked this as solved as its probably as near as its ever likely to be...I will however come back again should the need arise. I do hope it doesnt!

*Shock

 

I forgot to check the network drivers.
Seeing it is a USB adapter from TP-Link and the driver is from 2011 please check here for driver updates
It is best to keep the drivers from a USB adapter up to date, this because USB adapters with outdated drivers cause crashes or instability.

Code: 0: kd> lmvm athurx start end module name fffff800`23e00000 fffff800`23fde000 athurx T (no symbols) Loaded symbol image file: athurx.sys Image path: \SystemRoot\System32\drivers\athurx.sys Image name: athurx.sys Timestamp: Wed Apr 20 12:07:45 2011 (4DAEB071) CheckSum: 001E1C78 ImageSize: 001DE000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

hey axe0

My problems have got a whole lot worse. I have now completely uninstalled BullGuard and I still crash with the same driver less or equal malarki, this time tho there is no number classification associated with the driver issue - and now that BG is completely removed in all capacity Im a bit dumbfounded...

Any help would be...helpful i guess...

 

Run the dm log collector, a single dump isn't enough.

 

yep sorry forgot that bit...*Redface

Attachment 51656

TVM *Smile

 

A driver from your gaming keyboard is the cause of all 3 crashes.
I have no more information then below, I suggest to check the manufacturer of the keyboard for driver updates.
Code: Gaming Keyboard 1 c:\windows\system32\drivers\gks16fltr.sys[/quote] Code: 0: kd> lmvm GKS16Fltr start end module name fffff801`81cd0000 fffff801`81cd3a00 GKS16Fltr T (no symbols) Loaded symbol image file: GKS16Fltr.sys Image path: \SystemRoot\system32\drivers\GKS16Fltr.sys Image name: GKS16Fltr.sys Timestamp: Tue Dec 20 02:26:10 2011 (4EEFE432) CheckSum: 0000A5F1 ImageSize: 00003A00 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

hi again,

Can you tell the manufacturer of the keyboard by looking at this file? I ask because I have been using two keyboards recently; a steelseries raw and a zalman. both have drivers...

 

Of course both keyboards have drivers *Tongue
Every device has drivers, without drivers a device is useless.

I noticed you have software called Gaming Keyboard, most likely related to each other but it doesn't tell me anything more.
As I stated, I do not have more data then I posted in my previous post.

 

they have both been removed! howevfer my zalman remains operational with just the win10 driver...I assume!

Thx again