Windows 10: Marvell Avastar Wireless-AC Network Controller driver causing crashes/BSOD

I have a Surface Pro 3. Overnight my Wi-Fi driver ceased to function, I've tried numerous solutions, including running a "sfc /scannow" command that changed the grayed out driver in the device list to Code 12 instead. In the end the fix was to uninstall and restart the computer.However, that introduced worse problems, as my computer now freezes and often eventually BSODs whenever it reaches anywhere near 100% CPU. Even entering my PIN at the start screen too hastily can cause a freeze. I've then updated it via DriverEasy and later manually through Windows' own updater, then going back to unins

:)

 

Marvell AVASTAR Wireless-AC Network Controller Error

I have a surface book and I am having an issue with the Marvell AVASTAR Wireless-AC Network Controller displaying the following error: Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in
memory. (Code 38)

 

Marvell AVASTAR Network Controller is Missing

My Surface Pro 3 was fully functional lately. Had no problems with it lately and all of a sudden, my internet won't work. Went through Device Manager and found out that there is no Marvell AVASTAR Network Controller. Only 8 WAN Miniports. I was able to see
the controller through hidden devices, and it said that the hardware is not connected to the computer. (Code 45)

I searched for a way to fix this and found that I can reinstall a rolled back version of the adapter using the drivers given by Microsoft. I uninstalled the Marvell controller and did as the site had said. After some reboots and an install, the Marvell driver
was completely gone from Device Manager. I have no known way of fixing this as I have tried for hours with no solution.

 

marvell avastar wireless

Hi

I went through the items above including running DISM and sfc /scannow

Marvell AVASTAR Wireless still shows up with code 37.

Note 1: when searching, I've found references to the issue that occurred during the 14915 and people had to back out of the build. Here's the reference

https://twitter.com/cepowell/status/771082379049828352

Note 2: that my system started with a fresh install of Creators Update on fully formatted Surface 1 Pro (Marvell AVASTAR was working). After going to 16215, it stopped working