PCE-AC68 Windows 10 Drivers

[sfx2000]

When will ASUS get this driver right?

You mean Broadcom?

 

[bodean]

You mean Broadcom?

Both of them.
How do you prevent Windows 10 from updating the driver through windows update?

 

[sfx2000]

Broadcom has been a trainwreck throughout the Win10 experience...

Not just the PCE-AC68 device, there are others where performance has been less than reliable...

 

[snakebite3]

Both of them.
How do you prevent Windows 10 from updating the driver through windows update?

Advance system settings--->Hardware---->Device Installation Settings

 

[fusrahdo]

So damn frustrating trying to find what drivers work the best for windows 10.

 

[sglorbo]

So damn frustrating trying to find what drivers work the best for windows 10.

2115 drivers work for me.

http://dlcdnet.asus.com/pub/ASUS/wireless/PCE-AC68/UT_PCE_AC68_2115.zip

 

[fitasny]

I installed new drivers and I have instant BSOD (0x50) when I'm using qBittorent. The same situation repeats with .333, .317, .327.

EDIT:

I received the official response from ASUS POLAND Support and they suggest try these driver: http://www.necacom.net/index.php/br...-wireless-lan-drivers-version-7-35-308-0-whql

 

[fusrahdo]

I installed new drivers and I have instant BSOD (0x50) when I'm using qBittorent. The same situation repeats with .333, .317, .327.

EDIT:

I received the official response from ASUS POLAND Support and they suggest try these driver: http://www.necacom.net/index.php/br...-wireless-lan-drivers-version-7-35-308-0-whql

About to try out that broadcom driver too. It's just insane how much testing you have to do with both Broadcom and Asus drivers.

 

[bodean]

I installed new drivers and I have instant BSOD (0x50) when I'm using qBittorent. The same situation repeats with .333, .317, .327.

EDIT:

I received the official response from ASUS POLAND Support and they suggest try these driver: http://www.necacom.net/index.php/br...-wireless-lan-drivers-version-7-35-308-0-whql

how do they work?

 

[fusrahdo]

Does anyone know how to roll back drivers on Windows 10 a different way? The option isn't showing up for me to change the broadcom drivers.

 

[bodean]

I installed new drivers and I have instant BSOD (0x50) when I'm using qBittorent. The same situation repeats with .333, .317, .327.

EDIT:

I received the official response from ASUS POLAND Support and they suggest try these driver: http://www.necacom.net/index.php/br...-wireless-lan-drivers-version-7-35-308-0-whql

5GHZ doesnt connect with these, but 2.4ghz does. So no good

 

[CSM746]

I loaded the latest Asus support site .315 driver update, followed by the device properties screen "Update Driver" using Broadcom download for .333 from the Softpedia site. A .338 version of the driver was posted yesterday on Softpedia so I downloaded it, extracted it and did the "Update Driver" and it is running stable and fast.

 

[aehmkei]

Can someone please help me with the driver installation:

If I either install the official package UT_PCE_AC68_2108 or UT_PCE_AC68_2115 the "Asus utility" does not install.
I can see the option to uninstall the utility at "Start", "Asus" but have no option to launch it.
(it seems that only the driver will install - is there an separate installe for the utility tool?))
Therefore I have no option to set any region and can only use channels 36-48 with 5GHz.

Currently using Broadcom 338 with Win10 64bit.

Plz help, tank you very much.

Edit: Successfully installed the Asus utility by using file 2.0.8.8 .
File 2.1.1.5 does not contain the utility!!
Downside: Still not able to selec other channels than 36-48 in 5ghz

 

[kavika]

I loaded the latest Asus support site .315 driver update, followed by the device properties screen "Update Driver" using Broadcom download for .333 from the Softpedia site. A .338 version of the driver was posted yesterday on Softpedia so I downloaded it, extracted it and did the "Update Driver" and it is running stable and fast.

I can confirm that I was crashing repeatedly, immediately off fresh reboots, when using uTorrent. Installed the .338 from Softpedia, didn't even have to reboot, and no more crashes when running uTorrent. Still maxing out my traffic, too, so it's definitely the drivers that fixed it.

Strangely enough, this is the 2nd broadcom device I've had where the official Windows drivers consistently crapped out on me (the other was a wired network adapter a few years back). Microsoft needs to test their drivers under true load Not that hard, WHQL...

 

[kavika]

I can confirm that I was crashing repeatedly, immediately off fresh reboots, when using uTorrent. Installed the .338 from Softpedia, didn't even have to reboot, and no more crashes when running uTorrent. Still maxing out my traffic, too, so it's definitely the drivers that fixed it.

Strangely enough, this is the 2nd broadcom device I've had where the official Windows drivers consistently crapped out on me (the other was a wired network adapter a few years back). Microsoft needs to test their drivers under true load Not that hard, WHQL...

---

Strike that - I ran a bunch of speed tests, started uTorrent again, and got a BSOD. Different message with the BSOD, and it might have taken longer to produce, but still not completely stable.

Edit: And after some more boot -> torrent passes, keeps BOSDing immediately. Will try other drivers

 

[sfx2000]

Strangely enough, this is the 2nd broadcom device I've had where the official Windows drivers consistently crapped out on me (the other was a wired network adapter a few years back). Microsoft needs to test their drivers under true load Not that hard, WHQL...

Not part of the WHQL test suites, but it's implied that the vendor (in this case Broadcom) does their due diligence - the PCE-AC68 isn't the only Broadcom device out there that is having issues with Win10 - I've got a HP Stream11 with a Broadcom b/g/n bluetooth combo card that is inconsistent in behavior as well under Win10...

 

[mzaur8]

.338 seems to be working well for me also.

http://drivers.softpedia.com/get/NE...-Wireless-Driver-7353380-for-Windows-10.shtml

 

[bodean]

.338 seems to be working well for me also.

http://drivers.softpedia.com/get/NE...-Wireless-Driver-7353380-for-Windows-10.shtml

This driver, along with the 308, causes Windows 10 to get an error and reboot when running UTorrent. Back to the drawing board. Does anyone have any idea why this happens?

 

[Magnus Halvorsen]

I also get BSOD when using uTorrent. Tried qBittorrent as well, seems it works a tiny bit better, but still getting the BSOD quite regular. Seems like the .308 (page fault in nonpaged area) gives an other BSOD than .338 (don`t remember the errormsg) though.

Contacted ASUS support, not much help there either:
"The problem you describe is out of our support range. The problem could also be in the computer itselves or it's operating system.
Our latest driver shall work ok, there is no known issues there."

Since it works for some ppl, I put on beer for that it`s the combination of HW and win10. Nothing much else to do than to wait for a fix unless somebody have a suggestion...

 

[egilso]

I also get BSOD when using uTorrent. Tried qBittorrent as well, seems it works a tiny bit better, but still getting the BSOD quite regular. Seems like the .308 (page fault in nonpaged area) gives an other BSOD than .338 (don`t remember the errormsg) though.

Contacted ASUS support, not much help there either:
"The problem you describe is out of our support range. The problem could also be in the computer itselves or it's operating system.
Our latest driver shall work ok, there is no known issues there."

Since it works for some ppl, I put on beer for that it`s the combination of HW and win10. Nothing much else to do than to wait for a fix unless somebody have a suggestion...

Having tried all kinds of drivers for this card in Windows 10, every driver exept the 2.0.8.8 which I used with Windows 7 originally gives BSOD in utorrent.
That driver works ok, but I want to use other channels tha 36-48 for 5GHz operation. I know that is a driver issue, as I could easily use channels 36-112 with the non-eu-driver, that sadly made BSODs as well Using 80MHz channels, leaving only the 36-48 space is problematic if there's a neighbour, there is no room for us both. The drivers that BSOD make errors in the windows event log as well pointing at networkuxbroker.