Defiance III with killer wireless, driver issues and BSOD windows 10

J

Jmdhainsworth

Active member
hi, my laptop is blue screening when i have the drivers installed for the killer 1535 wireless card, but without them i cannot download as it keeps disconnecting every few minutes, any help will be highly appreciated, as this issue is really frustrating
 
SpyderTracks

SpyderTracks

We love you Ukraine
Jmdhainsworth said:
hi, my laptop is blue screening when i have the drivers installed for the killer 1535 wireless card, but without them i cannot download as it keeps disconnecting every few minutes, any help will be highly appreciated, as this issue is really frustrating
Click to expand...

Where are you getting the latest drivers from?
 
J

Jmdhainsworth

Active member
yeah that made it alot worse :S, just uninstalling all stuff that came with it and just have drivers for gpu and stuff so i can atleast play games without it bluescreening :/
 
T

thisisevilevil

Enthusiast
http://www.killernetworking.com/driver-downloads/item/e2200-e2400-wireless try and fetch these.



http://www.killernetworking.com/images/drivers/ReleaseNotes/Killer_1.1.64.1737_Release_Notes.pdf
"8 Fixed Issues
Component Description
Killer Bandwidth Control Fixed BSOD_D1_bwcW10x64
Installer Fixed various upgrade issues.
Killer E2X Updated to W10 Aniversary Update WHQL Certified Driver
Killer 11AC Wifi Updated to W10 Aniversary Update WHQL Certified Driver
Killer Bandwidth Control Updated to W10 Aniversary Update WHQL Certified Driver
Killer 11AC Wifi Wi-Fi yellow bang( code43) after S3 mode (randomly)"
 
J

Jmdhainsworth

Active member
ill give it a shot, just uninstalled all the control centre ****e that comes with it, think one bsod were the keyboard drivers :(
 
T

thisisevilevil

Enthusiast
If it doesn't work with the new drivers: Go to C:\Windows\Minidumps copy all the dump files to your desktop. Add them to a .zip file. Upload to a fileupload service like filedropper.com and put the link in here.
 
J

Jmdhainsworth

Active member
also how can i get my bluetooth to work properly i have a bt wireless speaker system and want to connect it but when i search for devices it just comes up with unknown device and fails to connect every time
 
T

thisisevilevil

Enthusiast
Jmdhainsworth said:
also how can i get my bluetooth to work properly i have a bt wireless speaker system and want to connect it but when i search for devices it just comes up with unknown device and fails to connect every time
Click to expand...

Install the latest BT driver. Not sure if PCs keeps it up-to-date on their website, but you can get the latest one from here
 
Last edited:
J

Jmdhainsworth

Active member
cheers, with the new killer wireless driver, my internet downloading is terrible dropping to 200kbs when usually i get 9mbs Untitled.jpg
 
T

thisisevilevil

Enthusiast
Right.

I see 2 seperate issues here, they might be linked due to the way the Hotkey utility works.

Crash type #1:
ffff9980`62269a58 fffff802`a3e56572 : 00000000`0000001e ffffffff`c0000005 fffff802`72cfdcec 00000000`00000000 : nt!KeBugCheckEx
ffff9980`62269a60 fffff802`a3dd4aed : fffff802`a3fd9000 fffff802`a3c84000 0004f530`00820000 00000000`00200296 : nt!KiFatalExceptionHandler+0x22
ffff9980`62269aa0 fffff802`a3d171b1 : ffff9980`6226c000 00000000`00000000 ffff9980`62265000 00000000`00000000 : nt!RtlpExecuteHandlerForException+0xd
ffff9980`62269ad0 fffff802`a3d15f64 : ffff9980`6226a200 ffff9980`6226a700 ffff9980`6226a200 ffff9980`6226a9d8 : nt!RtlDispatchException+0x421
ffff9980`6226a1d0 fffff802`a3dd9902 : fffff802`a3fa8480 00001f80`00260240 00000000`00000002 fffff802`a3fa6d00 : nt!KiDispatchException+0x144
ffff9980`6226a8a0 fffff802`a3dd7bbd : 00000000`00000b88 00000000`00000000 00000000`00000001 fffff802`a3d1872b : nt!KiExceptionDispatch+0xc2
ffff9980`6226aa80 fffff802`72cfdcec : fffffc0b`480d0fc0 fffffc0b`8b834e70 ffff9980`6226ace0 fffff802`a3ea3003 : nt!KiGeneralProtectionFault+0xfd (TrapFrame @ ffff9980`6226aa80)
ffff9980`6226ac10 fffff802`6d139db2 : fffff802`72d03740 ffff9980`6226ad09 ffff9980`6226acd8 fffffc0b`47b1cc70 : nwifi!MP6ReturnNBL+0x30
ffff9980`6226ac40 fffff802`6d168a81 : 00000000`00000000 00000000`00000000 00000000`00000030 fffff802`a4385e13 : ndis!ndisCallReceiveCompleteHandler+0x258b2
ffff9980`6226ac80 fffff802`6d140153 : 00000000`00000000 fffffc0b`8b834e70 fffffc0b`8b834e70 ffff830d`7afcae00 : ndis!ndisInvokeNextReceiveCompleteHandler+0x101
ffff9980`6226ad60 fffff802`6e4fe597 : fffffc0b`4817ac70 00000000`00000000 ffff830d`7819d948 fffff802`6e4f4601 : ndis!NdisFReturnNetBufferLists+0x21d83
ffff9980`6226ade0 fffffc0b`4817ac70 : 00000000`00000000 ffff830d`7819d948 fffff802`6e4f4601 fffffc0b`715724a0 : bwcW10x64+0xe597
ffff9980`6226ade8 00000000`00000000 : ffff830d`7819d948 fffff802`6e4f4601 fffffc0b`715724a0 00000000`00000001 : 0xfffffc0b`4817ac70

TL;DR: The driver is messed up, and is causing the Native WiFi Miniport driver to mess up. Looking around on google, this is a pretty known issue and pretty much always point to a driver issue. Found 1 very recent thread for a specific dell laptop, where a BIOS update was needed to fix the issue. Same driver is loaded. Might be relevant for later, but we will leave this for now.

Crash type #2
STACK_TEXT:
fffff800`71e6dad8 fffff800`6ffde829 : 00000000`0000000a ffff9f8a`8b8aefe8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`71e6dae0 fffff800`6ffdce07 : ffff9f89`352847c0 00000000`00000001 ffff9f89`35284930 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`71e6dc20 fffff80d`e335180a : 00000000`00000000 ffffc60c`8b580310 00000000`0000000c ffff9f89`36c3ad3c : nt!KiPageFault+0x247
fffff800`71e6ddb0 00000000`00000000 : ffffc60c`8b580310 00000000`0000000c ffff9f89`36c3ad3c ffffc60c`8b59fb20 : HKKbdFltr+0x180a

Look at the driver dates, they are horribly outdated:
0: kd> lmDvmHKKbdFltr
Browse full module list
start end module name
fffff80d`e3350000 fffff80d`e335f000 HKKbdFltr T (no symbols)
Loaded symbol image file: HKKbdFltr.sys
Image path: \SystemRoot\system32\DRIVERS\HKKbdFltr.sys
Image name: HKKbdFltr.sys
Timestamp: Wed Jul 22 04:36:56 2015 (55AF0FD8)


TL;DR: Uninstall your Hotkey utility. I don't believe Clevo even supports this utility anymore, but I might be wrong. Even so, just remove it, to avoid any future issues with these BSoDs.

Please go ahead and do the following now:
a) Go to run (Win button + R), type in "SystemPropertiesAdvanced" -> Startup and recovery settings -> In "Write debugging information" set it to "Kernel Dump".
b) Right click your start menu button in the lower right corner and choose "Programs and features". Remove the hotkey utility + Killer wireless driver.
c) Go to run again (Win button + R), type "devmgmt.msc" -> Fold out "Network Adapters". Verify your killer network adapter is gone. If it's not gone, right click on it and press uninstall.
d) Reboot your laptop
e) Upon booting back into Windows, verify your hotkey utility is no longer loaded and running. Also head into devmgmt.msc again -> Navigate to "System Devices" and verify there's not mentions of hotkey in there. If there is, right click it and press "Uninstall"
f) Install the latest Killer Wireless driver I linked to earlier.
g) When the installation is finished, reboot your laptop once more

When this is done, please go ahead and share a DxDiag output from your system. Would like to verify that there is no traces of the hotkey utility on your system. Go to run (Win button + R) and type in "Dxdiag" -> Save all information. Send this file to us.

Let me know if you have any questions.
 
Last edited:
T

thisisevilevil

Enthusiast
do it like this:
a) Uninstall the Killer drivers once more from Programs & Features
b) Reboot laptop
c) Navigate to device manager by typing in "devmgmt.msc" in run. Go to Network Adapters -> If the killer network adapter is still present, right click it and press uninstall
d) Reboot laptop once more
e) Attempt to install the killer driver again

Also did you have the hotkey utility installed? If yes: Did you remove it? I don't see it pop up in your DxDiag so that's a good sign I guess.

There is a way to save this Win 10 install, but it might be faster just doing a reinstall in the end if this doesn't work. A Win10 reinstall shouldn't take more than 15-20 min with a decent speed USB Drive when installing on an SSD.

EDIT: BTW, before attempting the uninstall, please close all other running programs. Use Process Explorer if needed.
 
Last edited:
T

thisisevilevil

Enthusiast
Looking at the minidump, the NVIDIA Driver caused the BSoD. But we also have to remember that with minidumps we only get partial information, so in certain cases it can be misleading. I can also see you are using the latest NVIDIA Driver available:
5: kd> lmDvmnvlddmkm
Browse full module list
start end module name
fffff800`a2230000 fffff800`a3044000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\System32\DriverStore\FileRepository\nvcvi.inf_amd64_ef63d0fbe12509f4\nvlddmkm.sys
Image name: nvlddmkm.sys
Browse all global symbols functions data
Timestamp: Fri Jan 20 13:29:59 2017
CheckSum: 00DCBC4D
ImageSize: 00E14000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4


So let's rewind a bit: You did the reinstall, you installed the display and WiFi drivers only and from there, the system was running fine, no errors? So our previous issue with installing/uninstalling WiFi drivers is gone and that now works as expected?
 
You must log in or register to reply here.
Top