topic Re: Wireless-AC 7265 BSOD Error in Wireless

Wireless-AC 7265 BSOD Error

idata — Wed, 13 Jan 2016 02:39:57 GMT

Hello all,

I've had some issues with my wireless AC 7265 adapter. I noticed it was intermittently losing connection or losing major speed. I made the changes recommended here:

and so far I haven't that issue occur again.

However, earlier today I had a BSoD (blue screen of death) error (Driver_IRQL_not_less_or_equal netwtw02.sys) that forced my laptop to shut down and lose my work. I am wondering if there is a fix in the works or if anyone else has had this issue. I have the most current driver installed (18.30.0.9).

For more information on this, see here: http://answers.microsoft.com/en-us/windows/forum/windows_10-performance/driverirqlnotlessorequal-netwtw02sys/8947ed87-1213-41ef-b46b-e61b6373f509 http://answers.microsoft.com/en-us/windows/forum/windows_10-performance/driverirqlnotlessorequal-netwtw02sys/8947ed87-1213-41ef-b46b-e61b6373f509

This is a brand new laptop and it has had a lot of driver issues so it has been a little frustrating.

Re: Wireless-AC 7265 BSOD Error

ASouz7 — Wed, 13 Jan 2016 21:55:25 GMT

AlexROG,

Thank you for the information, we are working on the drivers in order to improve its performance. We will publish a new version when they become available. In the mean time, we recommend that you use the drivers provided by your OEM. After using the OEM's driver you notice that the issue still persists, you can use our generic drivers version: 18.21.x found in our download center: https://downloadcenter.intel.com/download/25514/Intel-PROSet-Wireless-Software-for-Windows-10 Intel® PROSet/Wireless Software for Windows® 10 - File Name: Wriless_18.21.0_t64.exe. We are going to create a service ticket for you so you can send us the log files and Windows* event logs.

Another option as well, would be to clean uninstall all the current drivers installed and use Windows* Update to install the drivers.

Please check you provite messages in order to create a service ticket for you.

Re: Wireless-AC 7265 BSOD Error

Benjamin_S_Intel — Thu, 21 Jan 2016 20:58:14 GMT

I was seeing this same BSOD (DRIVER_IRQL_NOT_LESS_OR_EQUAL in netwtw02.sys) on my wireless AC 7265 adapter. I have a Lenovo Yoga 12 so I went to the Lenovo page and downloaded the wireless driver.

Driver Date: 9/24/2015

Driver Version: 18.21.0.2

With this driver installed I haven't seen the BSOD in a couple of days, hopefully it will continue this way.

Re: Wireless-AC 7265 BSOD Error

idata — Thu, 21 Jan 2016 21:00:34 GMT

I installed the same driver version. It was working fine for a couple days but today it started with BSOD error again.

Re: Wireless-AC 7265 BSOD Error

Benjamin_S_Intel — Thu, 21 Jan 2016 21:32:44 GMT

I just saw they posted a new driver two days ago. https://downloadcenter.intel.com/download/25683/Intel-PROSet-Wireless-Software-for-Windows-10 Download Intel® PROSet/Wireless Software for Windows® 10

I installed it and hopefully it will fix the issue. We'll see after a few days of use.

Driver Version: 18.32.0.5

Driver Date: 12/22/2015

Re: Wireless-AC 7265 BSOD Error

idata — Fri, 22 Jan 2016 04:27:35 GMT

I am still getting BSOD errors regardless of the driver, even 18.32.0.5 still causes it.

I'm starting to wonder if intel can fix this. All the drivers cause the problem. Does this mean it is a hardware defect? Should I return my laptop?

Re: Wireless-AC 7265 BSOD Error

Benjamin_S_Intel — Fri, 22 Jan 2016 06:39:56 GMT

It almost certainly a software defect. This bugcheck 0xD1 is caused by the kernel mode driver, netwtw02.sys. It's something Intel should be able to fix once they have a repro of the issue.

This explains more about the error: https://msdn.microsoft.com/en-us/library/windows/hardware/ff560244(v=vs.85).aspx https://msdn.microsoft.com/en-us/library/windows/hardware/ff560244(v=vs.85).aspx

Re: Wireless-AC 7265 BSOD Error

Benjamin_S_Intel — Fri, 22 Jan 2016 16:20:09 GMT

I opened up the C:\Windows\MEMORY.dmp file that is generated when the BSOD happens and it is showing a slightly different bugcheck. This is only the latest bugcheck, I know the predominant one's I have seen were the bugcheck 0xD1.

Here is the Windbg analysis... it is an access violation (0xC0000005) in the netwtw02.sys which causes the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bugcheck. I don't have the symbols for the .sys file so we can't tell exactly what lead up to this crash, but hopefully an Intel person will reach out and I can share the .dmp file so they can analyze and fix.

2: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)

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: fffff8001498ec98, The address that the exception occurred at

Arg3: ffffd00048fb9c28, Exception Record Address

Arg4: ffffd00048fb9440, Context Record Address

Debugging Details:

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

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

SYSTEM_SKU: LENOVO_MT_20DK_BU_Think_FM_ThinkPad S1 Yoga 12

SYSTEM_VERSION: ThinkPad S1 Yoga 12

BIOS_DATE: 07/24/2015

BASEBOARD_PRODUCT: 20DKS09J00

BASEBOARD_VERSION: SDK0E50510 WIN

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8001498ec98

BUGCHECK_P3: ffffd00048fb9c28

BUGCHECK_P4: ffffd00048fb9440

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

FAULTING_IP:

Netwtw02+1ec98

fffff800`1498ec98 66418900 mov word ptr [r8],ax

EXCEPTION_RECORD: ffffd00048fb9c28 -- (.exr 0xffffd00048fb9c28)

ExceptionAddress: fffff8001498ec98 (Netwtw02+0x000000000001ec98)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 0000000000000001

Parameter[1]: 0000000000000000

Attempt to write to address 0000000000000000

CONTEXT: ffffd00048fb9440 -- (.cxr 0xffffd00048fb9440)

rax=0000000000000000 rbx=0000000000000001 rcx=ffffe000bc8f8b70

rdx=ffffd00048fb9f00 rsi=0000000000000000 rdi=ffffd00048fba000

rip=fffff8001498ec98 rsp=ffffd00048fb9e68 rbp=ffffd00048fb9f70

r8=0000000000000000 r9=000000000000002f r10=fffff80294c693c0

r11=fffff80294415001 r12=fffff80014ccc000 r13=ffffd00048fba040

r14=ffffe000bc6797e4 r15=0000000000000000

iopl=0 nv up ei ng nz na po nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286

Netwtw02+0x1ec98:

fffff800`1498ec98 66418900 mov word ptr [r8],ax ds:002b:00000000`00000000=????

Resetting default scope

CPU_COUNT: 4

CPU_MHZ: 8f7

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3d

CPU_STEPPING: 4

DEFAULT_BUCKET_ID: NULL_DEREFERENCE

PROCESS_NAME: System

CURRENT_IRQL: 0

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

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 0000000000000000

WRITE_ADDRESS: 0000000000000000

FOLLOWUP_IP:

Netwtw02+1ec98

fffff800`1498ec98 66418900 mov word ptr [r8],ax

BUGCHECK_STR: AV

ANALYSIS_VERSION: 10.0.10240.9 amd64fre

LAST_CONTROL_TRANSFER: from fffff80014972f20 to fffff8001498ec98

STACK_TEXT:

ffffd000`48fb9e68 fffff800`14972f20 : 00000000`00000000 ffffd000`48fb9f70 00000000`00000000 ffffd000`48fb9ff0 : Netwtw02+0x1ec98

ffffd000`48fb9e70 fffff800`14aee45d : 00000000`001c0001 fffff800`149737e7 ffffe000`bc90aa40 00000000`00000000 : Netwtw02+0x2f20

ffffd000`48fb9fc0 fffff800`149fdf57 : ffffe000`bc679174 00000000`00000025 00000000`00000000 fffff800`149f9195 : Netwtw02+0x17e45d

ffffd000`48fb9ff0 fffff800`14a37be6 : ffffd000`48fba180 fffff800`149f7ff5 00000000`00000000 00000000`00000000 : Netwtw02+0x8df57

ffffd000`48fba020 fffff800`14b05f51 : 00000000`00000000 ffffe000`bcac74e0 ffffe000`bc5b1470 ffffe000`bdb9cba0 : Netwtw02+0xc7be6

ffffd000`48fba160 fffff800`14b006b4 : ffffd000`48fba3a0 ffffe000`bc8f8b70 ffffd000`48fba3a0 ffff035d`53ed399d : Netwtw02+0x195f51

ffffd000`48fba250 fffff800`14b046f7 : fffff800`14c732d8 00000000`00000000 ffffd000`48fba3a0 00000000`00000020 : Netwtw02+0x1906b4

ffffd000`48fba280 fffff800`14b09925 : ffffe000`bc8f8b70 ffffe000`bf338f00 fffff800`00000006 ffffe000`bc5a7510 : Netwtw02+0x1946f7

ffffd000`48fba310 fffff800`14b07d85 : ffffe000`bc597e08 ffffe000`bf338f00 00000000`00000010 00000000`00000010 : Netwtw02+0x199925

ffffd000`48fba480 fffff800`14a5f41d : 00000000`00000001 ffffe000`bdb92fa0 00000000`00000030 ffffe000`bf338f00 : Netwtw02+0x197d85

ffffd000`48fba520 fffff800`1497ef8e : ffffe000`00000001 ffffe000`bc6797dc fffff800`14c32838 00000000`00000000 : Netwtw02+0xef41d

ffffd000`48fba590 fffff800`14a22b06 : ffffe000`bf338f00 00000000`00002605 ffffd000`48fba6f0 fffff800`14c39780 : Netwtw02+0xef8e

ffffd000`48fba5f0 fffff800`14991ec7 : ffffe000`bc6790f0 ffffe000`bc65da00 ffffd000`48fba810 fffff800`11941c7f : Netwtw02+0xb2b06

ffffd000`48fba780 fffff800`126f1b3f : 00000000`00000001 ffffe000`bc7971a0 00000000`e440001d fffff802`944576eb : Netwtw02+0x21ec7

ffffd000`48fba850 fffff800`1268f6e5 : ffffe000`bc7971a0 fffff800`150a9aa0 ffffe000`bc6ba080 ffffe000`bfb0b560 : ndis!ndisMRawInvokeOidRequest+0x9b

ffffd000`48fba890 fffff800`15028358 : 00000000`000000f8 fffff800`150a9aa0 ffffe000`bc6ba080 fffff800`150a9f90 : ndis!ndisMpHookInvokeOidRequestHandler+0x15

ffffd000`48fba8c0 fffff800`15035706 : 00000000`00000000 ffffe000`b978eb78 ffffe000`bc6ba460 fffff800`150a9fb0 : wdiwifi!CCtlPlane::SendWdiCommand+0x2b8

ffffd000`48fba940 fffff800`15035575 : 00000000`0000001d ffffe000`0000006d ffffe000`bfb0b560 fffff802`9445b84d : wdiwifi!DeviceCommandScheduler::OnIssueNext...

Re: Wireless-AC 7265 BSOD Error

Benjamin_S_Intel — Thu, 28 Jan 2016 16:07:54 GMT

So far no BSOD seen. That's about a week since upgrading to 18.32.0.5 driver version.

Re: Wireless-AC 7265 BSOD Error

TLi19 — Sat, 30 Jan 2016 18:53:59 GMT

I am using AC 3165 but have the same DRIVER_IRQL_NOT_LESS_THAN_EQUAL BSOD. 18.32.0 is significant more stable than the 18.21.0 version but BSOD still happens. The only version I know that is stable is 18.12.0.

Re: Wireless-AC 7265 BSOD Error

ASouz7 — Mon, 01 Feb 2016 23:33:44 GMT

Thomas5267,

What is your system information?

Is this Wireless adapter the one that came installed by factory ?

Re: Wireless-AC 7265 BSOD Error

ASouz7 — Mon, 01 Feb 2016 23:41:24 GMT

AlexROG,

Please try driver version 18.32.0 foound in this link: https://downloadcenter.intel.com/download/25683/Intel-PROSet-Wireless-Software-for-Windows-10 Download Intel® PROSet/Wireless Software for Windows® 10 File name: Wireless_18.32.0_PROSet64_Win10.exe

Re: Wireless-AC 7265 BSOD Error

TLi19 — Wed, 03 Feb 2016 00:56:42 GMT

It is a brand new MSI GE62 6QC Apache I bought a month ago. The wireless adapter is installed by factory and not an add-on afterwards.

The specs are as follows:

Windows 10 Home

i7 6700HQ

2x 2133 Hz 8 GB DDR4 by Hyundai Electronics

GTX960M graphics card

Killer E2400 NIC

Intel 3165 Wireless card

128 GB Toshiba SSD

1 TB HGST HDD

I am pretty sure this is not a hardware failure of RAM or CPU. I did 10 hours of Prime 95 Small FFT, 24 hours of memtest86, 10 hours of memtest86+, and 10 iterations of the IntelBurnTest on the maximum setting when I bought this computer just to make sure it is stable. No error were returned by these tests.

I am pretty sure this is a driver issue. I had no problems with 18.12.0 but a huge amount of BSOD with 18.21.0. I have some BSOD with 18.32.0 but it is miles ahead of 18.21.0. Every time I change drivers I first uninstall the Intel software from Programs and Features and then uninstall the drivers in Device Manager. I then reboot and install the different version of driver and reboot again before using it.

I have noticed a few peculiarities with the BSODs:

I never had BSOD when I was back home using my home wireless network. I am not sure whether I was using 18.12.0 or 18.21.0 at that time. 18.12.0 was always stable for me even in my dorm room where 18.21.0 would BSOD like crazy.
When I was using 18.21.0, almost every time when there is a change in wireless signal strength (as indicated by the wireless icon on the taskbar) there will be a bluescreen (DRIVER_IRQL_NOT_LESS_THAN_EQUAL). The network strength first dip down, then after a few seconds later it goes back up. If a BSOD is going to happen, it will happen within 5 seconds of the signal strength going back up. My guess is that this has something to do with AP roaming. At home, I was using a single access point setup and there is no AP that I can access nearby. However, in my dorm building there are multiple AP with the same SSID. I suspect the BSODs are partly triggered by roaming between AP with same SSID. For your information, the home network is encrypted using the normal WPA2 and the dorm wireless network is encrypted using WPA2 Enterprise with CCMP.
In the System section of Event Viewer in Windows, there are events from Netwtw02 with event ID 7001 and 7002. The event description for event ID 7001 is:

"The description for Event ID 7001 from source Netwtw02 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\NDMP3

Intel(R) Dual Band Wireless-AC 3165

The specified resource type cannot be found in the image file"

It is the same for event ID 7002 with 7001 replaced with 7002. I do not know whether this is related to the BSODs.

Hope this helps.

Re: Wireless-AC 7265 BSOD Error

ASouz7 — Wed, 03 Feb 2016 21:31:16 GMT

thomas5267,

Thank you for the information. We are going to investigate it an will get back to you as soon as possible.

Re: Wireless-AC 7265 BSOD Error

SCorn2 — Fri, 05 Feb 2016 20:13:22 GMT

Hi,

I got a BSOD in Windows 10 with the 18.32.0.5 driver on the Wireless-AC 7260 card.

My Dell laptop is about a year old and it's the first time I've ever had a BSOD in either Windows 8.1 or Windows 10.

I believe this version of the driver was delivered via a Windows update, although I normally update the Intel drivers myself.

Simon

Background information:

Intel(R) Dual Band Wireless-AC 7260

System Model: Dell XPS13 9333

This is the output from Windbg:

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

Microsoft (R) Windows Debugger Version 6.3.9600.17200 X86

Loading Dump File [C:\Windows\Minidump\013116-6890-01.dmp]

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

************* Symbol Path validation summary **************

Response Time (ms) Location

Deferred srv*C:\symbols*http://msdl.microsoft.com/downloads/symbols http://msdl.microsoft.com/downloads/symbols

Symbol search path is: srv*C:\symbols*http://msdl.microsoft.com/downloads/symbols http://msdl.microsoft.com/downloads/symbols

Executable search path is:

Windows 8 Kernel Version 10586 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 10586.63.amd64fre.th2_release.160104-1513

Machine Name:

Kernel base = 0xfffff801`d128e000 PsLoadedModuleList = 0xfffff801`d156cc70

Debug session time: Sun Jan 31 11:03:14.268 2016 (UTC + 0:00)

System Uptime: 0 days 23:25:44.076

Loading Kernel Symbols

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.

Run !sym noisy before .reload to track down problems loading symbols.

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

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

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

Loading User Symbols

Loading unloaded module list

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

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {98, 2, 0, fffff8004c38ff64}

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

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

Probably caused by : Netwbw02.sys ( Netwbw02+4ff64 )

Followup: MachineOwner

---------

0: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If kernel debugger is available get stack backtrace.

Arguments:

Arg1: 0000000000000098, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, value 0 = read operation, 1 = write operation

Arg4: fffff8004c38ff64, address which referenced memory

Debugging Details:

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

READ_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get nt!MmPagedPoolEnd

unable to get nt!MmNonPagedPoolStart

unable to get nt!MmSizeOfNonPagedPoolInBytes

0000000000000098

CURRENT_IRQL: 2

FAULTING_IP:

Netwbw02+4ff64

fffff800`4c38ff64 8b8098000000 mov eax,dword ptr [rax+98h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

TRAP_FRAME: ffffd0002cd45500 -- (.trap 0xffffd0002cd45500)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000000000000 rcx=ffffe000ff77c900

rdx=ffffe00103524700 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8004c38ff64 rsp=ffffd0002cd45698 rbp=ffffd0002cd45710

r8=ffffd0002cd45770 r9=0000000000000000 r10=0000000000000001

r11=ffffd0002cd45470 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na po nc

Netwbw02+0x4ff64:

fffff800`4c38ff64 8b8098000000 mov eax,dword ptr [rax+98h] ds:00000000`00000098=????????

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff801d13db2e9 to fffff801d13d0770

STACK_TEXT:

ffffd000`2cd453b8 fffff801`d13db2e9 : 00000000`0000000a 00000000`00000098 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

ffffd000`2cd453c0 fffff801`d13d9ac7 : ffffe001`031ee398 00000000`00000000 ffffd000`2cd45770 ffffe001`03432a10 : nt!KiBugCheckDispatch+0x69

ffffd000`2cd45500 fffff800`4c38ff64 : fffff800`4c37d395 00000000`000001a7 fffff800`4c37da29 ffffe001`00000000 : nt!KiPageFault+0x247

ffffd000`2cd45698 fffff800`4c37d395 : 00000000`000001a7 fffff800`4c37da29 ffffe001`00000000 fffff800`4c4ff7f3 : Netwbw02+0x4ff64

ffffd000`2cd456a0 00000000`000001a7 : fffff800`4c37da29 ffffe001`00000000 fffff800`4c4ff7f3 00000000`00001a70 : Netwbw02+0x3d395

ffffd000`2cd456a8 fffff800`4c37da29 : ffffe001`00000000 fffff800`4c4ff7f3 00000000`00001a70 ffffd000`2cd45700 : 0x1a7

ffffd000`2cd456b0 ffffe001`00000000 : ff...

Re: Wireless-AC 7265 BSOD Error

SCorn2 — Tue, 01 Mar 2016 12:50:17 GMT

Another BSOD in Windows 10 with the 18.32.0.5 driver on the Wireless-AC 7260 card.

This is the output from Windbg:

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

Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64

Loading Dump File [C:\Windows\Minidump\030116-6453-01.dmp]

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

************* Symbol Path validation summary **************

Response Time (ms) Location

Deferred srv*C:\symbols*http://msdl.microsoft.com/downloads/symbols http://msdl.microsoft.com/downloads/symbols

Symbol search path is: srv*C:\symbols*http://msdl.microsoft.com/downloads/symbols http://msdl.microsoft.com/downloads/symbols

Executable search path is:

Windows 10 Kernel Version 10586 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 10586.103.amd64fre.th2_release.160126-1819

Machine Name:

Kernel base = 0xfffff803`af21b000 PsLoadedModuleList = 0xfffff803`af4f9cf0

Debug session time: Tue Mar 1 09:20:20.390 2016 (UTC + 0:00)

System Uptime: 0 days 9:34:29.210

Loading Kernel Symbols

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.

Run !sym noisy before .reload to track down problems loading symbols.

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

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

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

Loading User Symbols

Loading unloaded module list

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

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 133, {1, 1e00, 0, 0}

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

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

Probably caused by : Netwbw02.sys ( Netwbw02+39676 )

Followup: MachineOwner

---------

0: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

DPC_WATCHDOG_VIOLATION (133)

The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL

or above.

Arguments:

Arg1: 0000000000000001, The system cumulatively spent an extended period of time at

DISPATCH_LEVEL or above. The offending component can usually be

identified with a stack trace.

Arg2: 0000000000001e00, The watchdog period.

Arg3: 0000000000000000

Arg4: 0000000000000000

Debugging Details:

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

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.103.amd64fre.th2_release.160126-1819

SYSTEM_MANUFACTURER: Dell Inc.

SYSTEM_PRODUCT_NAME: XPS13 9333

SYSTEM_SKU: 060A

BIOS_VENDOR: Dell Inc.

BIOS_VERSION: A08

BIOS_DATE: 08/31/2015

BASEBOARD_MANUFACTURER: Dell Inc.

BASEBOARD_PRODUCT: 0D13CR

BASEBOARD_VERSION: A00

DUMP_TYPE: 2

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: 0

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

CPU_COUNT: 4

CPU_MHZ: a22

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 45

CPU_STEPPING: 1

CPU_MICROCODE: 6,45,1,0 (F,M,S,R) SIG: 1D'00000000 (cache) 1D'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: System

CURRENT_IRQL: d

ANALYSIS_SESSION_HOST: DELL-LAPTOP-01

ANALYSIS_SESSION_TIME: 03-01-2016 11:17:30.0801

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER: from fffff803af376bbb to fffff803af35d480

STACK_TEXT:

fffff803`b1176d48 fffff803`af376bbb : 00000000`00000133 00000000`00000001 00000000`00001e00 00000000`00000000 : nt!KeBugCheckEx

fffff803`b1176d50 fffff803`af23a037 : fffff803`b1176e00 00000000`00000001 ffffe001`b6fbe010 fffff803`af538180 : nt! ?? ::FNODOBFM::`string'+0xadbb

fffff803`b1176de0 fffff803`af9e99c5 : 00000000`00400a02 fffff803`af538180 ffffe001`b596aaa0 00000000`0000a101 : nt!KeClockInterruptNotify+0xa7

fffff803`b1176f40 fffff803`af303ea7 : ffffe001`b7e39800 fffff803`af26f9ec fffff803`b1176f50 00000000`00000010 : hal!HalpTimerClockIpiRoutine+0x15

fffff803`b1176f70 fffff803`af35e8aa : fffff803`afa343b0 ffffe001`b596aaa0 fffff801`8af40000 ffffe001`b586ed00 : nt!KiCallInterruptServiceRoutine+0x87

fffff803`b1176fb0 fffff803`af35ecd7 : 00000000`3c3f61c6 00000000`3c396b2f ffffe001`b596aaa0 fffff801`8b129b46 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea

ffffd000`22de13a0 fffff803`af23d107 : 00000000`00000000 fffff801`8af78e50 ffffe001`b5969aa0 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37

ffffd000`22de1530 fffff803`af22f132 : 00000000`00000002 ffffffff`00000000 40030001`0...

Re: Wireless-AC 7265 BSOD Error

JDeen — Tue, 01 Mar 2016 22:46:52 GMT

Just to add to the thread, this was the only google thread that turned up searching some terms of the memory dump.

I'm having SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)

With exactly the same wireless-AC 7265

Interestingly almost exactly the same laptop as Simon above here, Dell XPS 13 9343

Could this be a Dell thing?

Anyway, the driver was from November so I updated it to 18.32.05 (same as above), let's see what happens....

Re: Wireless-AC 7265 BSOD Error

Benjamin_S_Intel — Tue, 01 Mar 2016 23:12:01 GMT

I don't see any reason to suspect Dell. My repro was on a Lenovo system. The faulting module is an Intel driver, it is all but guaranteed to be a driver bug.

By teh way, I haven't had any BSOD's since I upgraded to 18.32.0.5.

Re: Wireless-AC 7265 BSOD Error

ASouz7 — Sat, 05 Mar 2016 00:01:25 GMT

zambamingi Jocham SimonCornforth

We have released version 18.33.0 on our download center. Please check it out. This new version contains a lot of fixes.

Here you can find the link to it: https://downloadcenter.intel.com/product/83635/Intel-Dual-Band-Wireless-AC-7265 Drivers & Software

Re: Wireless-AC 7265 BSOD Error

JL2 — Sun, 06 Mar 2016 21:48:19 GMT

Hello I found this thread through a Google search and I've been having the same issues.

This is the fourth BSOD in a month. I was using a previous version of the driver but even after updating to the most recent version I'm still getting the same BSOD.

I'm currently using Windows 10 with Wireless-AC 7260 version 18.33.0.1.

Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64

Loading Dump File [C:\Windows\Minidump\030616-3875-01.dmp]

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

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 10586 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 10586.122.amd64fre.th2_release_inmarket.160222-1549

Machine Name:

Kernel base = 0xfffff802`efc79000 PsLoadedModuleList = 0xfffff802`eff57cf0

Debug session time: Sun Mar 6 15:25:19.604 2016 (UTC - 5:00)

System Uptime: 0 days 0:25:45.310

Loading Kernel Symbols

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.

Run !sym noisy before .reload to track down problems loading symbols.

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

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

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

Loading User Symbols

Loading unloaded module list

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

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {8, 2, 0, fffff802efc21675}

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

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

Probably caused by : Netwbw02.sys ( Netwbw02+926ad )

Followup: MachineOwner

---------

0: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

IRQL_NOT_LESS_OR_EQUAL (a)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: 0000000000000008, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, bitfield :

bit 0 : value 0 = read operation, 1 = write operation

bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)

Arg4: fffff802efc21675, address which referenced memory

Debugging Details:

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

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.122.amd64fre.th2_release_inmarket.160222-1549

SYSTEM_MANUFACTURER: ASUSTeK COMPUTER INC.

SYSTEM_PRODUCT_NAME: K501LX

SYSTEM_SKU: ASUS-NotebookSKU

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: K501LX.206

BIOS_DATE: 09/16/2015

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: K501LX

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 2

BUGCHECK_P1: 8

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff802efc21675

READ_ADDRESS: fffff802efff7520: Unable to get MiVisibleState

0000000000000008

CURRENT_IRQL: 2

FAULTING_IP:

hal!HalPutScatterGatherList+18b35

fffff802`efc21675 4d8b6d08 mov r13,qword ptr [r13+8]

CPU_COUNT: 4

CPU_MHZ: 95a

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3d

CPU_STEPPING: 4

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

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

ANALYSIS_SESSION_HOST: ASUS24

ANALYSIS_SESSION_TIME: 03-06-2016 15:28:00.0315

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

TRAP_FRAME: fffff802f1b0c5a0 -- (.trap 0xfffff802f1b0c5a0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000001

rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000

rip=fffff802efc21675 rsp=fffff802f1b0c730 rbp=000000000000001c

r8=ffffe000355a5990 r9=ffffe00037aa2336 r10=ffffe000355a5990

r11=ffffe00038f8cbd0 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl nz na ...