Intel Dual Band Wireless 8265 causing BSOD in Win10

[AZhur]

Hi, I have an 8265 wifi adapter. I experience BSOD's randomly on system boot up, maybe every 2- 3 or so. I see this same topic in earlier posts where someone had the same issue then stated it was resolved,

Here is the debug of mini dump file. It is flagging the Netwtw06.sys file as the probable cause.

Microsoft (R) Windows Debugger Version 10.0.16299.91 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 16299 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 16299.15.amd64fre.rs3_release.170928-1534

Machine Name:

Kernel base = 0xfffff801`d2c9c000 PsLoadedModuleList = 0xfffff801`d3002fd0

Debug session time: Sun Jan 7 16:10:30.213 2018 (UTC + 3:00)

System Uptime: 0 days 4:36:23.158

Loading Kernel Symbols

...............................................................

................................................................

................................................................

..............

Loading User Symbols

Loading unloaded module list

.............

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffff960631a00000, 2, fffff801d2e2566f, 2}

*** WARNING: Unable to verify timestamp for Netwtw06.sys

*** ERROR: Module load completed but symbols could not be loaded for Netwtw06.sys

Could not read faulting driver name

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : Netwtw06.sys ( Netwtw06+531eb9 )

Followup: MachineOwner

---------

4: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)

Invalid system memory was referenced. This cannot be protected by try-except.

Typically the address is just plain bad or it is pointing at freed memory.

Arguments:

Arg1: ffff960631a00000, memory referenced.

Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.

Arg3: fffff801d2e2566f, If non-zero, the instruction address which referenced the bad memory

address.

Arg4: 0000000000000002, (reserved)

Debugging Details:

------------------

Could not read faulting driver name

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.16299.192 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: Timi

SYSTEM_PRODUCT_NAME: TM1701

BIOS_VENDOR: INSYDE Corp.

BIOS_VERSION: XMAKB5R0P0200

BIOS_DATE: 09/07/2017

BASEBOARD_MANUFACTURER: Timi

BASEBOARD_PRODUCT: TM1701

BASEBOARD_VERSION: MP

DUMP_TYPE: 2

BUGCHECK_P1: ffff960631a00000

BUGCHECK_P2: 2

BUGCHECK_P3: fffff801d2e2566f

BUGCHECK_P4: 2

READ_ADDRESS: fffff801d3098380: Unable to get MiVisibleState

Unable to get NonPagedPoolStart

Unable to get NonPagedPoolEnd

Unable to get PagedPoolStart

Unable to get PagedPoolEnd

ffff960631a00000

FAULTING_IP:

nt!memcpy+af

fffff801`d2e2566f 660f7f41e0 movdqa xmmword ptr [rcx-20h],xmm0

MM_INTERNAL_CODE: 2

CPU_COUNT: 8

CPU_MHZ: 708

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 8e

CPU_STEPPING: a

CPU_MICROCODE: 6,8e,a,0 (F,M,S,R) SIG: 70'00000000 (cache) 70'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-9J1D3C6

ANALYSIS_SESSION_TIME: 01-07-2018 16:36:07.0613

ANALYSIS_VERSION: 10.0.16299.91 amd64fre

TRAP_FRAME: ffffb008f7dced90 -- (.trap 0xffffb008f7dced90)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000040000 rbx=0000000000000000 rcx=ffff960631a00020

rdx=00001dfb99dc0000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff801d2e2566f rsp=ffffb008f7dcef28 rbp=0000000000000000

r8=0000000000000000 r9=0000000000000800 r10=00000000ffffffff

r11=ffff960631a00000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na pe nc

nt!memcpy+0xaf:

fffff801`d2e2566f 660f7f41e0 movdqa xmmword ptr [rcx-20h],xmm0 ds:ffff9606`31a00000=????????????????????????????????

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff801d2e3b71d to fffff801d2e116e0

STACK_TEXT:

ffffb008`f7dceb18 fffff801`d2e3b71d : 00000000`00000050 ffff9606`31a00000 00000000`00000002 ffffb008`f7dced90 : nt!KeBugCheckEx

ffffb008`f7dceb20 fffff801`d2cebbbd : 00000000`00000002 ffff9606`31a00000 ffffb008`f7dced90 ffffb008`f7dcecc0 : nt!MiSystemFault+0x15151d

ffffb008`f7dcebc0 fffff801`d2e2074e : 00000000`00000000 ffffac80`03f95850 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x23d

ffffb008`f7dced90 fffff801`d2e2566f : fffff801`d313a48a 00000000`00000000 ffff9606`2a230830 ffff9606`31a00000 : nt!KiPageFault+0x40e

ffffb008`f7dcef28 fffff801`d313a48a : 00000000`00000000 ffff9606`2a230830 ffff9606`31a00000 ffff9606`2c6e34e0 : nt!memcpy+0xaf

ffffb008`f7dcef30 fffff801`d313a214 : 00000000`00040000 00000000`00040000 00000000`00c89848 ffffb008`f7dcf030 : nt!CcCopyBytesToUserBuffer+0x4a

ffffb008`f7dcef80 fffff801`d2cd2cbc : ffff9606`275c8260 00000000`00000000 00000000`00040000 ffff9606`29e58701 : nt!CcMapA...

[AZhur]

SSU report attached

[idata]

Hello Azhur,

We understand that you're experiencing random blue screen crashes on Windows 10*.

In the post you mentioned, the customer last action was a clean driver installation. Please try the https://www.intel.com/content/www/us/en/support/articles/000022173/network-and-i-o/wireless-networking.html following:

1. Download and save your driver of choice. You can:
   1. Get the latest system-specific driver from your computer manufacturer support (I tried to search the support site for your Xiaomi TIMI TM1701*, but wasn't able to find one).
   2. https://www.intel.com/content/www/us/en/support/network-and-i-o/wireless-networking/000005559.html Download the Latest Driver for Your Intel® Wireless Adapter.
2. Uninstall the Intel® PROSet/Wireless Software.
   1. Open Programs and Features (Uninstall a program) from the Control Panel.
   2. Select Uninstall or Change and then Remove.
   3. When prompted, choose to discard settings.
3. Uninstall your wireless driver. Windows* with an inbox driver may natively support some wireless adapters. You cannot uninstall an inbox driver. Proceed to the next step if you start seeing the same version of the driver installed automatically after it's uninstalled.
   1. Go to Device Manager.
   2. Expand the Network Adapters category.
   3. Right-click your Intel Wireless Adapter and choose to uninstall it.
   4. Make sure to select the option to Delete the driver software for this device.
4. Clear out your temporary files.
   1. Press the Windows* key and R key simultaneously to open the run box.
   2. Type in: cleanmgr.exe and press the Enter key or OK.
   3. Place a check mark next to Temporary Files. You can leave everything else checked or unchecked.
   4. Press OK and wait.
5. Reboot your computer.
6. Locate the driver you downloaded back in Step 1. Run as administrator and follow the wizard to completion.
7. (Optional Step) Apply the https://www.intel.com/content/www/us/en/support/network-and-i-o/wireless-networking/000024678.html Recommended Settings for Wireless Connectivity.

Do you remember if the issue started after a driver or Windows* update?

Best regards,

Eugenio F.

[AZhur]

Hi Eugenio,

I already try your instruction, it was mentioned in similar post about 8260.

it is doesn't help me.

I bought this PC in december, and it is work fine.

but then, after few windows and drivers updates - I have BSOD. now it is almost each time when I switch on my PC.

initial WIFI drivers for Dual Band Wireless 8265 delivered with PC - was 19.71.0

[idata]

Hello Azhur,

What is the exact stop error message that displays on your BSOD crashes?Could you uninstall our generic drivers and try using the system specific drivers provided by your computer manufacturer? After some digging, I was able to find the drivers page for your laptop:NOTE: Any links provided for third party tools or sites are offered for your convenience and should not be viewed as an endorsement by Intel® of the content, products, or services offered there.- http://en.miui.com/thread-318018-1-1.html Driver Collections for Mi Notebook Air* 12.5" and 13.3"You may also want to engage your computer manufacturer:- http://www.mi.com/us/support/ XIAOMI MI* SupportPlease let us know if these make a difference.Best regards,Carlos A.

[NKauf1]

Try reverting the drivers back to an older version and check if that works, might have to go a version or 2 or more back.

Newer Intel drivers do NOT seem to be fixing issues in some cases, but that is the new Intel, frustrating and disappointing... whether it be graphics drivers or networking drivers. Both of these drivers have been horrendous,

Have not looked at other drivers - chipset, storage etc. - who knows what else broken stuff is being released by Intel.

Have the standards fallen this low?

[idata]

Hello nkaufman,

The drivers posted through our Download Center for wireless adapters are generic versions. Since we only have two retail wireless adapter models , in most cases it's better to use the latest system specific drivers provided through your computer manufacturer, these are the only ones that account for OEM customizations.Best regards,Carlos A.

[NKauf1]

Yes Carlos, we do understand that.

Most of the users (try doing a poll) normally update drivers through their manufacturers who get their drivers from INTEL.

It is only when these drivers create ISSUES that people start looking for solutions. Manufacturers who typically have nothing to do with drivers would only pass along the information to INTEL or ask users to revert to older versions (was much easier to do till Windows 10 made it difficult. ). Unless of course in those rare instances where manufacturers customize drivers instead of just packaging them into an executable.

So, as owner of drivers that have been causing issues and as the organization that will be (in most cases) ultimately responsible for a FIX, it is INTEL to own up the issue, investigate and create a fix.

[idata]

Hello nkaufman,

Thanks for submitting your feedback. We'll make sure to pass it on to our business unit.

Azhur Did you have the chance to install the drivers provided by the OEM?

Best regards,

Eugenio F.

[AZhur]

Hi Eugenio,

I tried to delete latest drivers, using your procedures, but after PC reboot it is installed automatically.

So I can't install older version on top of new one

BR, Alex

[idata]

Hello Azhur,

Thanks for your reply.What driver version you get when the system reboots? The latest driver might persist if Intel® PROSet/Wireless Software is still installed or if temporary files are storing the driver.Please double check that Intel® PROSet/Wireless Software is uninstalled and temporary files are cleaned? If you've already done this, remove the drivers as instructed in one of our previous messages. However, install the driver provided by the OEM before you reboot.Please let us know the results.Best regards,Eugenio F.

[AZhur]

Hi,

when i delete drivers from device managers menu, and press refresh equipment configuration,

drivers itstalled automatictly with lower version then before.

I done this procedure 4-5 times, and finally - oldest one 19.50.1.6.

after that, I reboot PC and installed 19.71.1.1 provided by OEM Xiaomi.

but then I check device manager info and find a lot of errors 411

[idata]

Hello Azhur,

Thanks for the update.Checking Microsoft* Event Viewer documentation, https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc727035(v=ws.10) Event ID 411 is related to Task Scheduler Service. These kind of errors are usually solved by the system without end user interference.When these errors comes up, is your wireless connection affected? If so, have you noticed a pattern to it?Also, please let us know if the blue screen errors persisted.Best regards,Eugenio F.

[AZhur]

Hi Eugenio,

seems, 411 error have no any common with BSOD, I check timestamp for for it.

But, I still have blue screen time to time ( one time per day) even after OEM drivers installation

[idata]

Hello Azhur,

Thanks for your reply.Please allow us more time to investigate this issue. We'll let you know as soon as we have updates.Best regards,Eugenio F.

[idata]

Hello Azhur,

A new Intel wireless driver version will be released soon. Even though we don't have an ETA yet, we'll notify you as soon as it's available.The new driver might help to solve the issue.Best regards,Eugenio F.

[idata]

Hello Azhur,

The new version of Intel® PROSet/Wireless Software and Drivers for Windows® 10 (v20.30.1) was released yesterday.

Please try a https://www.intel.com/content/www/us/en/support/articles/000022173/network-and-i-o/wireless-networking.html clean driver installation with this new release and let us know if the blue screen error persists.

- https://downloadcenter.intel.com/download/27475/Wireless-Intel-PROSet-Wireless-Software-and-Drivers-for-Windows-10?v=t Intel® PROSet/Wireless Software and Drivers for Windows® 10 Version 20.30.1

- https://downloadcenter.intel.com/download/27493/Intel-Wireless-Bluetooth-for-Windows-10?product=89450 Intel® Wireless Bluetooth® for Windows® 10 Version 20.30.0

Best regards,

Eugenio F.

[idata]

Hello Azhur,

We haven't heard from you for a while now. Did you have the chance to install the latest drivers?

Best regards,

Eugenio F.

[AZhur]

Hi Eugenio,

I install latest drivers 3 days ago.

there is no Blue screen till now.

but I also have 2-3 days normal work with previous driver version.

so I keep monitoring situation and update you on next week.

[idata]

Hello Azhur,

Thanks for your reply. We'll be waiting for your next reply.Best regards,Eugenio F.

[AZhur]

Hi Eugenio,

So finnally I can confirm that now all works fine with latest drivers

BR, Alex