Intel Dual Band Wireless 8265 causing BSOD in Win10 - Page 2

AZhur · ‎01-12-2018

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

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...

idata · ‎02-27-2018

Hello Alex,

Thanks for confirming the solution.

It is good to know the blue screen crashes have stopped after updating the wireless drivers.

Let us know if there's anything else we can do for you.

Best regards,

Eugenio F.

idata · ‎02-27-2018

Hello Alex,

Thanks for confirming the solution. It is good to know the blue screen crashes stopped after the driver update.

Let us know if there's anything else we can do for you.

Best regards,

Eugenio F.

AKlim4 · ‎02-04-2018

Just wanted to chime in and report the same kind of issue, with referenced memory BSODs and blame put on the intel wireless link drivers.

This has started happening about 3-5 weeks ago. Current version installed is 20.10.2.2, however, I'll try 20.2.2 and see if it helps.

idata · ‎02-05-2018

Hello tohaklim,

Thanks for notifying us. Do you have an Intel® Dual Band Wireless-AC 8265 as well?

Also, have you test a https://www.intel.com/content/www/us/en/support/articles/000022173/network-and-i-o/wireless-networking.html clean driver installation? We recommend testing this with both the latest Intel generic driver and the OEM (Original Equipment Manufacturer) driver.

Best regards,

Eugenio F.

AKlim4 · ‎02-11-2018

Hi Eugenio. thanks for replying.

Yep, also an 8265. My OEM doesn't do much in terms of driver update/modification, hence it is close to stock Intel, if not stock.

The issue appears to be fixed on 22, no BSODs so far

idata · ‎02-12-2018

Hello tohaklim,

Thanks for the update. It is good to know the blue screen crashes have stopped after the driver update.

Please notify us if the issue persists.

Best regards,

Eugenio F.