Windows 10: Wireless Network Driver Uninstall BSOD

Alright, so a bit of history here. This laptop started having BSOD issues after taking the free update to Windows 10. It was apparently due to network drivers so I had attempted to update a few of them, and thought the problem had gone away. I was wrong. I had the laptop plugged in via network cable, and am now learning the problems appear to have to do with the wireless network drivers. I didn't realize this until now as I generally use the laptop when I'm away from home, and haven't had a need for it until now.

-----

It started off with Driver Verifier's scans causing a blue screen, DRIVER_VERIFIER_DECTECTED_VIOLATION. Opening that, it was flagging ntoskrnl.exe, nwifi.sys, and I believe tcpip.sys. To prevent the laptop from hitting a BSOD I reset Driver Verifier's settings so it wouldn't run any scans, then went to work. (That should be the first three minidumps in the included attachment.)

I didn't have the Windows Debugging tools installed at the time, so I was using a program called "BlueScreenView" to dig into what could be an issue. I saw nwifi.sys in there, the NativeWiFi Miniport Driver. Alright, my WiFi drivers are Bigfoot Killer Wireless-N 1103 drivers. I saw that they're from 2011 (odd, WIndows says they're fully updated) so I check the website. I find drivers from 2013 with a higher version number, perfect. Searching for and downloading these drivers took some time, as the laptop would periodically BSOD with IRQL_UNEXPECTED_VALUE. (That would be the fourth and fifth minidumps.)

So here's where I hit the main issue. I did get the drivers. They require me to uninstall the previous Killer Network Manager suite in order to install the new version. Attempting to uninstall the previous suite version causes yet another BSOD, MEMORY_MANAGEMENT (the last three minidumps), which is where I am now. I have Windows Debugging tools installed now, and it's flagging "Ak27x64.sys" as the potential reason. Go figure, that's the wireless driver that's being uninstalled.

If I uninstall the driver manually through the Device Manager, it works just fine. However, the Killer Network Manager suite is determined to reinstall the driver before uninstalling the entire suite.

I could extract the driver from the installation archive (it has an option for that) and install it myself. However, I'm worried that the error itself means something worse than the uninstaller tripping over the driver. I'll probably attempt a Memtest in the near future, but hopefully someone here has ideas!

EDIT:
Ran a standard memtest, came back clean. That makes me think the un/installer was the issue, but maybe someone will see something else?

:)

 

Killer Wireless network causing bsod, can't uninstall (Killer Wireless n1102)

Recently upgraded to windows 10. first bsod fwpckw.sys occured when manager wanted to run a speed test and I let it. I restarted and tried to go on, but bsod(driver_irql, memory exception, memoryexecute_nomemory) started happening intermittently.

Tried uninstalling wireless manager software and install new version. Bsod. Tried uninstalling in safe mode. bsod. Took several BSODs to even get into safe mode, for a period restarting comp led to bsod.

uninstalled driver and tried to uninstall manager bsod. Now I don't even have access to internet on the laptop. No new drivers for windows 10 available, only a the manager suite.

What do?

 

memory management bsod

I uninstalled the driver for "killer e2400 gigabit ethernet controller" and "Killer wireless=n/a/ac 1525 wireless network adapter" (the only 2 drivers up there besides "bluetooth device").

Reinstalled them in safe mode (since my system BSOD'd every single time upon launch, and I just got a memory_management BSOD again, with WhoCrashed saying the probable cause being "ntoskrnl.exe", and "ntkrnlmp.exe" once as well.

Again thanks a lot for your help

 

What memtest have you performed exactly? The built-in feature?
What website have you checked exactly for updating drivers?

Code: *** WARNING: Unable to verify timestamp for bflwfx64.sys *** ERROR: Module load completed but symbols could not be loaded for bflwfx64.sys *** WARNING: Unable to verify timestamp for Ak27x64.sys *** ERROR: Module load completed but symbols could not be loaded for Ak27x64.sys 4: kd> lmvm bflwfx64 start end module name fffff800`79380000 fffff800`794d7000 bflwfx64 T (no symbols) Loaded symbol image file: bflwfx64.sys Image path: \SystemRoot\system32\DRIVERS\bflwfx64.sys Image name: bflwfx64.sys Timestamp: Tue Feb 14 20:28:54 2012 (4F3AB5F6) CheckSum: 0001A6A6 ImageSize: 00157000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 4: kd> lmvm Ak27x64 start end module name fffff800`7a600000 fffff800`7a8a2000 Ak27x64 (deferred) Image path: \SystemRoot\System32\drivers\Ak27x64.sys Image name: Ak27x64.sys Timestamp: Wed Dec 07 18:13:57 2011 (4EDF9ED5) CheckSum: 002AB75A ImageSize: 002A2000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

Yes, used the built in Windows 10 memtest, on the Standard setting.

Qualcomm Killer Wireless N1202/N1103 Driver Driver Details | Dell US

Downloaded the drivers from this page here, and installed them manually instead of using the installer that was giving me so much trouble. They're intended for the next model of laptop up from what I'm using, but the network card is the same, and they haven't been giving me any troubles yet. The "Ak27x64.sys" driver was replaced with "Akw8x64.sys". "Bflwfx64.sys" is also related to the bigfoot network drivers, but unlike the first driver, I haven't been able to find it in my device manager or any specific way of updating it by itself, so I assume it has to do with the function of the KIller Network Manager program itself rather than specifically the wireless function.

I haven't had any new BSODs yet thankfully (and I am on the wireless again), but the MEMORY_MANAGEMENT one has me worried.

EDIT: As an aside, Dell has stopped support of this hardware with Windows 10, so the Windows 8 drivers are likely as close as I'm going to get. The "Ak27x64.sys" driver to my best knowledge was a leftover driver from Windows 7, which I was using before the free upgrade to 10.

Product Support | Dell US

That's the support page for this model.

 

1 thing that is wrong, installing drivers from other sites then your manufacturers.
With laptops, the manufacturer alter the drivers so you are forced to only use their drivers. Other drivers won't work properly.
I recommend to check your manufacturers site, Alienware, for drivers.

A 2nd thing, I would recommend to run MemTest86+ to test the memory.
MemTest86+ is much better then the memory diagnostics test from Windows self.





Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

 

Alienware is owned by Dell, and the Support -> Drivers & Downloads link on the Alienware page send you to Dell support.
Attachment 50676


Now would be a good time to run Memtest86 I suppose. About to start some heavy cooking, so that'll give it time to do its thing. Thank you, I'll see what it tells me.

 

My bad about the site*Redface

As it looks like, as you say, they have indeed stopped support for your laptop.
Unfortunately, my guess would be that the solution is to revert back the OS.

 

It happens, no worries. I was surprised myself when it redirected me during the initial search. Wasn't expecting that!

So I came back to check the memtest86 run, and it looks like it had restarted the laptop on its own. I assumed from a quick read around that it would just continue to test until I told it to stop? I had gone through the settings to see what was adjustable, then left it on default and let it do its thing.

EDIT:
Ok, so I tried a second memtest86 run. This one I was trying to keep an eye on, and it seemed like it went for a longer period of time, then I walked into the room again just a couple minutes go to see it had restarted the laptop once more. I'm not sure what to make of that.

Regardless, I'll keep your suggestion in mind. So far I haven't had any BSODs (and they were rapid before I replaced that driver, usually within a couple minutes of startup), so I'm going to keep going with Windows 10 for now and see if that really was the issue. If it happens again, I have a USB with a bootable Windows 7 install on stand-by.

Thank you for the help! Very much appreciated.