Wireless
Participate in insightful discussions regarding issues related to Intel® Wireless Adapters and technologies
7368 Discussions

BSOD on wake in Netwtw06.sys after driver update

idata
Employee
8,853 Views

After updating my Wifi driver to 20.0.2.3 (2-3 weeks ago), I've twice gotten a blue screen crash on resume from sleep. As this driver version is the first to include the KRACK vulnerability fix, it is not reasonable to roll back to an older version. An inspection of the last memory dump reveals the following:

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: ffff8009f4c00000, memory referenced.

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

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

address.

Arg4: 0000000000000002, (reserved)

Debugging Details:

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

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 15063.0.amd64fre.rs2_release.170317-1834

SYSTEM_MANUFACTURER: LENOVO

SYSTEM_PRODUCT_NAME: 20FQS04X00

SYSTEM_SKU: LENOVO_MT_20FQ_BU_Think_FM_ThinkPad X1 Carbon 4th

SYSTEM_VERSION: ThinkPad X1 Carbon 4th

BIOS_VENDOR: LENOVO

BIOS_VERSION: N1FET55W (1.29 )

BIOS_DATE: 09/08/2017

BASEBOARD_MANUFACTURER: LENOVO

BASEBOARD_PRODUCT: 20FQS04X00

BASEBOARD_VERSION: SDK0J40697 WIN

DUMP_TYPE: 1

BUGCHECK_P1: ffff8009f4c00000

BUGCHECK_P2: 2

BUGCHECK_P3: fffff80032d896af

BUGCHECK_P4: 2

READ_ADDRESS: ffff8009f4c00000 Nonpaged pool

FAULTING_IP:

nt!memcpy+af

fffff800`32d896af 660f7f41e0 movdqa xmmword ptr [rcx-20h],xmm0

MM_INTERNAL_CODE: 2

CPU_COUNT: 4

CPU_MHZ: af8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 4e

CPU_STEPPING: 3

CPU_MICROCODE: 6,4e,3,0 (F,M,S,R) SIG: BA'00000000 (cache) BA'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 10.0.16299.15 amd64fre

TRAP_FRAME: ffffcb80e41c3ec0 -- (.trap 0xffffcb80e41c3ec0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000040000 rbx=0000000000000000 rcx=ffff8009f4c00020

rdx=0000377d57080000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff80032d896af rsp=ffffcb80e41c4058 rbp=0000000000000000

r8=0000000000000000 r9=0000000000000800 r10=00000000ffffffff

r11=ffff8009f4c00000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na pe nc

nt!memcpy+0xaf:

fffff800`32d896af 660f7f41e0 movdqa xmmword ptr [rcx-20h],xmm0 ds:ffff8009`f4c00000=????????????????????????????????

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80032db3156 to fffff80032d7d580

STACK_TEXT:

ffffcb80`e41c3c28 fffff800`32db3156 : 00000000`00000050 ffff8009`f4c00000 00000000`00000002 ffffcb80`e41c3ec0 : nt!KeBugCheckEx

ffffcb80`e41c3c30 fffff800`32c9e6c6 : 00000000`00000002 ffff8009`f4c00000 ffffcb80`e41c3ec0 ffff8009`d7e8d500 : nt!MiSystemFault+0x116c36

ffffcb80`e41c3cd0 fffff800`32d86d72 : ffff8009`00000005 ffff8009`00000001 00000000`00000000 ffffcb80`e41c3f30 : nt!MmAccessFault+0xae6

ffffcb80`e41c3ec0 fffff800`32d896af : fffff800`3309960a 00000000`00040000 00000000`00000000 ffff8009`00000005 : nt!KiPageFault+0x132

ffffcb80`e41c4058 fffff800`3309960a : 00000000`00040000 00000000`00000000 ffff8009`00000005 ffff8009`eb7c7190 : nt!memcpy+0xaf

ffffcb80`e41c4060 fffff800`330993a4 : 00000000`00040000 00000000`00040000 00000000`00f3ef48 ffffcb80`e41c4160 : nt!CcCopyBytesToUserBuffer+0x4a

ffffcb80`e41c40b0 fffff800`32c5588b : ffff8009`f11081f0 00000000`00000000 ffff8009`00040000 00000000`00000001 : nt!CcMapAndCopyFromCache+0x114

ffffcb80`e41c4150 fffff802`b07d4032 : ffffa08d`00000002 00000000`00000001 ffffa08d`00f3ef48 ffffa08d`00000000 : nt!CcCopyReadEx+0x12b

ffffcb80`e41c41e0 fffff802`b07cc5e3 : ffff8009`d7e50180 ffffcb80`e41c4470 ffffa08d`fa82fc00 00000000`000000ff : NTFS!NtfsCachedRead+0x1a6

ffffcb80`e41c4250 fffff802`b07cb93e : ffff8009`ea73bad8 ffff8009`e4b70880 ffffa08d`fa82fc90 00000000`00000001 : NTFS!NtfsCommonRead+0xad3

ffffcb80`e41c4440 fffff802`ae60563d : ffff8009`eb629b00 ffff8009`e4b70880 ffff8009`dc0c3df0 ffff8009`e4b70c68 : NTFS!NtfsFsdRead+0x1ee

ffffcb80`e41c44f0 fffff802`ae6034d6 : ffffcb80`e41c4580 00000000`00000001 00000000`00000000 ffffcb80`e1cc0180 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x18d

ffffcb80`e41c4560 fffff800`330a672f : ffff8009`eb7c7190 ffff8009`e4b70880 ffff8009`e4b70cb0 00000000`00000001 : FLTMGR!FltpDispatch+0xb6

ffffcb80`e41c45c0 fffff800`330a5499 : ffff8009`00000001 ffff8009`eb7c7104 ffff8009`eb7c71e0 ffffcb80`e41c4870 : nt!IopSynchronousServiceTail+0x1af

ffffcb80`e41c4680 fffff800`32d88413 : 00000000`00000100 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x6a9

ffffcb80`e41c4780 fffff800`32d80760 : fffff802`b5f73ea9 fffff802`b5e27a60 00000000`00000100 fffff802`b5e27ac8 : nt!KiSystemServiceCopyEnd+0x13

ffffcb80`e41c4988 fffff802`b5f73ea9 : fffff802`b5e27a60 00000000`00000100 fffff802`b5e27ac8 fffff802`b5e27a98 : nt!KiServiceLinkage

ffffcb80`e41c4990 fffff802`b5f74188 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00f3ef48 : Netwtw06+0x533ea9

ffffcb80`e41c4a30 fffff800`32c2fe9b : ffff8009`00f3ef48 ffff8009`dcbc12f0 ffff8009`dcbcd060 ffff8009`e2333040 : Netwtw06+0x534188

ffffcb80`e41c4a90 fffff800`32c4f168 : 00000000`00000100 ffff8009`ed89d640 fffff800`32c2fda0 00000000`00000000 : nt!IopProcessWorkItem+0xfb

ffffcb80`e41c4b00 fffff800`32cedeb7 : 00000000`00000001 00000000`00000080 ffff8009`d7e8d500 ffff8009`ed89d640 : nt!ExpWorkerThread+0xd8

ffffcb80`e41c4b90 fffff800`32d82a06 : fffff800`311fa180 ffff8009`ed89d640 fffff800`32cede70 ffffcb80`e41c4d29 : nt!PspSystemThreadStartup+0x47

ffffcb80`e41c4be0 00000000`00000000 : ffffcb80`e41c5000 ffffcb80`e41be000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

THREAD_SHA1_HASH_MOD_FUNC: e8a4222b200fd5e09a45e55f7343347a90e99999

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 3008069a119e51096ddb4b95f9511eca7af74429

THREAD_SHA1_HASH_MOD: acd05c535281c782b7d45b17bb5c152018f5e1ee

FOLLOWUP_IP:

Netwtw06+533ea9

fffff802`b5f73ea9 33d2 xor edx,edx

FAULT_INSTR_CODE: 4489d233

SYMBOL_STACK_INDEX: 11

SYMBOL_NAME: Netwtw06+533ea9

MODULE_NAME: Netwtw06

IMAGE_NAME: Netwtw06.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 59d213eb

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 533ea9

FAILURE_BUCKET_ID: ...

11 Replies
idata
Employee
2,101 Views

Hi simtrip,

 

 

We understand that you are having some BSODs after upgrading the driver to the latest Intel PROSet/Wireless WiFi Software 20.0.2.3.

 

 

We recommend you to perform a clean installation of the drivers, please follow the next steps:

 

1.Get the latest https://downloadcenter.intel.com/product/72252/Intel-PROSet-Wireless-Software Intel® PROSet/Wireless Software.

 

 

2. Uninstall the Intel® PROSet/Wireless Software.a. Open Programs and Features (Uninstall a program) from the Control Panel.

 

b. Select Uninstall or Change and then Remove.

 

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

 

a. Go to Device Manager.

 

b. Expand the Network Adapters category.

 

c. Right-click your Intel Wireless Adapter and choose to uninstall it.

 

d. Make sure to select the option to Delete the driver software for this device.

 

 

4. Clear out your temporary files.

 

a. Press the Windows* key and R key simultaneously to open the run box.

 

b. Type in: cleanmgr.exe and press the Enter key or OK.

 

c. Place a checkmark next to Temporary Files. You can leave everything else checked or unchecked.

 

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

 

 

If that does not work Please download and run the https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility Intel® System Support Utility. Run the scan selecting "Everything." Save this report and upload.

 

 

To enable attachments, make sure to select the option to "use advanced editor" while replying.

 

 

We look forward to hearing back from you.

 

 

Regards,

 

Junior M.
GBös
Beginner
2,101 Views

I'm not the OP, but I had a very similar issue with a Lenovo X1 Yoga on Windows 10. It so far didn't reoccur after I followed your instructions.

0 Kudos
idata
Employee
2,101 Views

Hello Boeg,

 

 

Thanks for your reply.

 

 

It is good to know that the BSOD crashes stopped after a clean wireless driver installation. Other users have also report good results installing the driver provided by the OEM (Original Equipment Manufacturer).

 

 

Best regards,

 

Eugenio F.
0 Kudos
BPlas
Beginner
2,101 Views

HI,

I have the same error ; can please confirm which driver to install?

Microsoft (R) Windows Debugger Version 10.0.16299.15 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [D:\temp\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be 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

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

Machine Name:

Kernel base = 0xfffff803`fac97000 PsLoadedModuleList = 0xfffff803`faffdfd0

Debug session time: Sat Jan 27 20:59:35.012 2018 (UTC + 1:00)

System Uptime: 2 days 1:19:09.718

Loading Kernel Symbols

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

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

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

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

Loading User Symbols

Loading unloaded module list

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

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffb98485d4fff0, 2, fffff803fae20810, 2}

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

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

Followup: MachineOwner

---------

5: 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: ffffb98485d4fff0, memory referenced.

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

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

address.

Arg4: 0000000000000002, (reserved)

Debugging Details:

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

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 16299.15.amd64fre.rs3_release.170928-1534

SYSTEM_MANUFACTURER: HP

SYSTEM_PRODUCT_NAME: HP ZBook Studio G3

SYSTEM_SKU: Y6J44EA# ABH

BIOS_VENDOR: HP

BIOS_VERSION: N82 Ver. 01.23

BIOS_DATE: 12/19/2017

BASEBOARD_MANUFACTURER: HP

BASEBOARD_PRODUCT: 80D4

BASEBOARD_VERSION: KBC Version 11.72

DUMP_TYPE: 1

BUGCHECK_P1: ffffb98485d4fff0

BUGCHECK_P2: 2

BUGCHECK_P3: fffff803fae20810

BUGCHECK_P4: 2

READ_ADDRESS: ffffb98485d4fff0 Nonpaged pool

FAULTING_IP:

nt!memcpy+250

fffff803`fae20810 660f7f4110 movdqa xmmword ptr [rcx+10h],xmm0

MM_INTERNAL_CODE: 2

CPU_COUNT: 8

CPU_MHZ: a20

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: C2'00000000 (cache) C2'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: NL222

ANALYSIS_SESSION_TIME: 01-27-2018 23:12:28.0217

ANALYSIS_VERSION: 10.0.16299.15 amd64fre

TRAP_FRAME: ffff8b0eea046e10 -- (.trap 0xffff8b0eea046e10)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=ffffb98485d50000 rbx=0000000000000000 rcx=ffffb98485d4ffe0

rdx=ffffecfcd1480000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff803fae20810 rsp=ffff8b0eea046fa8 rbp=0000000000000000

r8=0000000000000000 r9=0000000000000800 r10=0000000000000001

r11=ffffb98485d40000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na pe nc

nt!memcpy+0x250:

fffff803`fae20810 660f7f4110 movdqa xmmword ptr [rcx+10h],xmm0 ds:ffffb984`85d4fff0=????????????????????????????????

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff803fae3671d to fffff803fae0c6e0

STACK_TEXT:

ffff8b0e`ea046b98 fffff803`fae3671d : 00000000`00000050 ffffb984`85d4fff0 00000000`00000002 ffff8b0e`ea046e10 : nt!KeBugCheckEx

ffff8b0e`ea046ba0 fffff803`face6bbd : 00000000`00000002 ffffb984`85d4fff0 ffff8b0e`ea046e10 ffff8b0e`ea046d40 : nt!MiSystemFault+0x15151d

ffff8b0e`ea046c40 fffff803`fae1b74e : 00000000`00000000 ffff9000`0460ad00 00000000`00000000 ffff9000`00000000 : nt!MmAccessFault+0x23d

ffff8b0e`ea046e10 fffff803`fae20810 : fffff803`fb13548a 00000000`00000000 ffffb984`74f2bde0 ffffb984`85d40000 : nt!KiPageFault+0x40e

ffff8b0e`ea046fa8 fffff803`fb13548a : 00000000`00000000 ffffb984`74f2bde0 ffffb984`85d40000 ffffb984`6...

0 Kudos
idata
Employee
2,101 Views

Hello BartP,

 

 

What driver should be installed will depend on your wireless and laptop (or motherboard model).

 

 

We recommend installing the drivers provided by your laptop OEM (Original Equipment Manufacturer) on their support site. Please make sure you perform a clean installation of the drivers as instructed here:

 

 

- https://www.intel.com/content/www/us/en/support/articles/000022173/network-and-i-o/wireless-networking.html Clean Installation of Wireless Drivers

 

 

For your specific laptop model, the drivers can be downloaded here:

 

 

- https://support.hp.com/us-en/drivers/selfservice/hp-zbook-studio-g3-mobile-workstation/8934839 Drivers Downloads for HP ZBook Studio G3*

 

 

NOTE: Links to third party sites are being offered for your convenience and should not be viewed as an endorsement by Intel of the content, products, or services offered there.

 

 

Best regards,

 

Eugenio F.
0 Kudos
BPlas
Beginner
2,101 Views

OK, but the windows update has Intel drivers.

I installed the Intel computing improvement program on pc too.

What is the best approach?

0 Kudos
idata
Employee
2,101 Views

Hello BartP,

 

 

In this case, we recommend to manually update your wireless driver instead of using the Intel® Driver & Support Assistant. This tool will install the latest generic drivers instead of your https://support.hp.com/us-en/drivers/selfservice/hp-zbook-studio-g3-mobile-workstation/8934839 system OEM drivers.

 

 

If a Windows 10* update installs a different driver version that doesn't work properly, you may temporarily block that driver from reinstalling. Here's how:

 

 

- https://support.microsoft.com/en-us/help/3073930/how-to-temporarily-prevent-a-driver-update-from-reinstalling-in-window How to temporarily prevent a driver update from reinstalling in Windows 10

 

 

NOTE: Links to third party sites are being offered for your convenience and should not be viewed as an endorsement by Intel of the content, products, or services offered there.

 

 

Best regards,

 

Eugenio F.
0 Kudos
idata
Employee
2,101 Views

Hi simtrip,

We would like to know if you read our previous post. If you have any other questions, we'll be waiting for your response.

Regards,

 

Junior M.

 

0 Kudos
idata
Employee
2,101 Views

I have read the previous post, and performed the suggested actions. However, since this was an issue that was not reliably reproducible, it is not easy for me to verify whether the issue at root has actually been resolved. I'll leave this issue dormant for now, and come back to it later if the system stays stable.

0 Kudos
idata
Employee
2,101 Views

Hi simtrip,

 

 

Thanks for the reply. Please let us know any update regarding this situation.

 

 

Regards,

 

Junior M.
0 Kudos
idata
Employee
2,101 Views

Hi simtrip,

 

 

We haven't heard back from you in a while. Have you been able to resolve this issue?

 

 

Regards,

 

Junior M.

 

0 Kudos
Reply