Intel's Netwtw04.sys driver is causing BSOD on windows 10.

[SH2]

Hi,

I have an minidump of this crash as well. I am sharing it with you.

Please let me know about the issue.

Actually, this is a bug.

Thanks

Shashikant

[AlHill]

What wireless adapter are you using?

Doc

[SH2]

It's Wireless Wifi link adapter

[AlHill]

What model and manufacturer?

Doc

[SH2]

Protocol:802.11nSecurity type:WPA2-PersonalNetwork band:2.4 GHzNetwork channel:11Manufacturer:Intel CorporationDescription:Intel(R) Dual Band Wireless-AC 3165Driver version:18.40.0.12

I hope this will help.

[AlHill]

The latest driver is 19.50.1.

You can find it here: https://downloadcenter.intel.com/download/26653/Wireless-Intel-PROSet-Wireless-Software-and-Drivers-for-Windows-10?v=t Download Intel® PROSet/Wireless Software and Drivers for Windows® 10

Doc

[SH2]

Thanks Al Hill.

[idata]

Hello shashikant11,

Please try our latest driver as suggested by Al_Hill and let us know if the issue is resolved. Additionally you may want to run a RAM test, as faulty RAM is one of the top misdiagnosed BSOD triggers.

- https://www.lifewire.com/free-memory-test-programs-2626178 4 Free Memory Test Programs.

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. We do not offer support for any third party tool mentioned here.

Best regards,

Carlos A.

[idata]

Hello shashikant11,

We heaven't heard from you in a while, has your issue been resolved?Please let us know if you would like further assistance.Best regards,Carlos A.

[SH2]

Carlos A

Yes, It has been resolved. the driver was not updated. but I haven't got any update notification from intel to update the drivers.

nonetheless, the problem is resolved.

Shashikant

[idata]

shashikant11,

We're glad to hear that your problem has been resolved.Please keep in mind that our driver software will not automatically notify you when new drivers are released. This process is expected to be performed manually.However we do have a tool to help you keep the drivers for the Intel® components on your system up to date. If you're interested in this, feel free to give the http://www.intel.com/content/www/us/en/support/detect.html Intel® Driver Update Utility a try.Best regards,Carlos A.

[SH2]

Result of !analyze -v

KMODE_EXCEPTION_NOT_HANDLED (1e)

This is a very common bugcheck. Usually the exception address pinpoints

the driver/function that caused the problem. Always note this address

as well as the link date of the driver/image that contains this address.

Arguments:

Arg1: ffffffffc0000005, The exception code that was not handled

Arg2: fffff80c82926304, The address that the exception occurred at

Arg3: 0000000000000000, Parameter 0 of the exception

Arg4: ffffffffffffffff, Parameter 1 of the exception

Debugging Details:

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

Unable to load image Netwtw04.sys, Win32 error 0n2

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

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

ADDITIONAL_DEBUG_TEXT:

Use '!findthebuild' command to search for the target build information.

If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: fffff802cca92000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP:

Netwtw04+36304

fffff80c`82926304 8b8098000000 mov eax,dword ptr [rax+98h]

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get nt!MmPoolCodeStart

unable to get nt!MmPoolCodeEnd

ffffffffffffffff

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x1E

CURRENT_IRQL: 0

BAD_PAGES_DETECTED: 135c8

LAST_CONTROL_TRANSFER: from fffff802ccc5ff52 to fffff802ccbe07c0

STACK_TEXT:

fffff802`cf05d118 fffff802`ccc5ff52 : 00000000`0000001e ffffffff`c0000005 fffff80c`82926304 00000000`00000000 : nt+0x14e7c0

fffff802`cf05d120 00000000`0000001e : ffffffff`c0000005 fffff80c`82926304 00000000`00000000 ffffffff`ffffffff : nt+0x1cdf52

fffff802`cf05d128 ffffffff`c0000005 : fffff80c`82926304 00000000`00000000 ffffffff`ffffffff fffff80c`82a1da55 : 0x1e

fffff802`cf05d130 fffff80c`82926304 : 00000000`00000000 ffffffff`ffffffff fffff80c`82a1da55 fffff802`cf05d290 : 0xffffffff`c0000005

fffff802`cf05d138 00000000`00000000 : ffffffff`ffffffff fffff80c`82a1da55 fffff802`cf05d290 fffff802`ccbe6bbd : Netwtw04+0x36304

STACK_COMMAND: kb

SYMBOL_NAME: PAGE_NOT_ZERO

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware_ram

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

---------

*** Memory manager detected 79304 instance(s) of page corruption, target is likely to have memory corruption.