topic Dual Band Wireless-N 7260: As expected DPC issues continue over generations of products this time with a premium: BSOD in Wireless

Dual Band Wireless-N 7260: As expected DPC issues continue over generations of products this time with a premium: BSOD

UUSRD — Wed, 24 Dec 2014 12:04:41 GMT

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

* *

* Bugcheck Analysis *

* *

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

DPC_WATCHDOG_VIOLATION (133)

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

or above.

Arguments:

Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending

component can usually be identified with a stack trace.

Arg2: 0000000000000501, The DPC time count (in ticks).

Arg3: 0000000000000500, The DPC time allotment (in ticks).

Arg4: 0000000000000000

Debugging Details:

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

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: System

CURRENT_IRQL: d

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

LAST_CONTROL_TRANSFER: from fffff8007e00c3c8 to fffff8007dfcfaa0

STACK_TEXT:

ffffd001`4f646c88 fffff800`7e00c3c8 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx

ffffd001`4f646c90 fffff800`7df1c2a1 : 00000000`4deffffe 00000000`000587c7 ffffe000`14eaf0e8 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2c418

ffffd001`4f646d20 fffff800`7de177b5 : ffffd001`00400a02 00000000`00000001 fffff801`dba9baa0 00000000`00009201 : nt!KeClockInterruptNotify+0x91

ffffd001`4f646f40 fffff800`7df604b3 : ffff3e2f`0d011e6b 00000000`00000008 fffff801`dd0f6538 00000000`00000000 : hal!HalpTimerClockIpiRoutine+0x15

ffffd001`4f646f70 fffff800`7dfd0f2a : fffff800`7de63d00 00000000`00000004 00000000`ffffffff 00000000`00000001 : nt!KiCallInterruptServiceRoutine+0xa3

ffffd001`4f646fb0 fffff800`7dfd130f : 00000000`0005ca00 fffff6fb`78001a18 00000000`00000200 fffff6f0`00343000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea

ffffd001`4f636040 fffff800`7dfc2055 : 00000022`00000000 00000000`00000013 00000000`ffffffff 00000007`00000000 : nt!KiInterruptDispatchLBControl+0x11f

ffffd001`4f6361d0 fffff800`7dfbee88 : ffffd001`4f63656d fffff801`0000007e 00000000`00054de8 ffffe000`00000042 : nt!output_l+0xed

ffffd001`4f636490 fffff801`dd078b76 : 00000000`00000001 fffff801`00057b3e fffff801`dd23de00 00000000`00054de8 : nt!snprintf+0x78

ffffd001`4f636510 00000000`00000001 : fffff801`00057b3e fffff801`dd23de00 00000000`00054de8 01d01f64`fd6c999a : NETwbw02+0xeb76

ffffd001`4f636518 fffff801`00057b3e : fffff801`dd23de00 00000000`00054de8 01d01f64`fd6c999a fffff801`dd0809e2 : 0x1

ffffd001`4f636520 fffff801`dd23de00 : 00000000`00054de8 01d01f64`fd6c999a fffff801`dd0809e2 00000000`00000000 : 0xfffff801`00057b3e

ffffd001`4f636528 00000000`00054de8 : 01d01f64`fd6c999a fffff801`dd0809e2 00000000`00000000 00000000`00000000 : NETwbw02+0x1d3e00

ffffd001`4f636530 01d01f64`fd6c999a : fffff801`dd0809e2 00000000`00000000 00000000`00000000 00000000`00000000 : 0x54de8

ffffd001`4f636538 fffff801`dd0809e2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x01d01f64`fd6c999a

ffffd001`4f636540 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : NETwbw02+0x169e2

STACK_COMMAND: kb

FOLLOWUP_IP:

NETwbw02+eb76

fffff801`dd078b76 ?? ???

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: NETwbw02+eb76

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETwbw02

IMAGE_NAME: NETwbw02.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53ce3d14

FAILURE_BUCKET_ID: 0x133_DPC_NETwbw02+eb76

BUCKET_ID: 0x133_DPC_NETwbw02+eb76

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x133_dpc_netwbw02+eb76

FAILURE_ID_HASH: {5d48de34-be45-f4d2-0132-2bd563b4ee8a}

Followup: MachineOwner

Re: Dual Band Wireless-N 7260: As expected DPC issues continue over generations of products this time with a premium: BSOD

Jose_H_Intel1 — Fri, 26 Dec 2014 21:08:31 GMT

What is your operating system and driver version?

Similar incidents are caused by fast startup or antivirus software.

http://www.eightforums.com/tutorials/6320-fast-startup-turn-off-windows-8-a.html http://www.eightforums.com/tutorials/6320-fast-startup-turn-off-windows-8-a.html

Re: Dual Band Wireless-N 7260: As expected DPC issues continue over generations of products this time with a premium: BSOD

UUSRD — Thu, 29 Jan 2015 11:30:54 GMT

My operating system is Windows 8.1 64-bit. I have came across different antivirus software. If the driver is not stable enough to survive across multiple hibernations (Windows fast startup) then it should not have being published as stable.

Re: Dual Band Wireless-N 7260: As expected DPC issues continue over generations of products this time with a premium: BSOD

jbenavides — Thu, 29 Jan 2015 17:32:18 GMT

Hello Fjtorsol,

Recent driver versions have improved this behavior. Follow these steps to get a clean install of the driver:

1. Download and save https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=24656 Intel® PROSet/Wireless Software for Windows 8.1*, 17.14.0:

The recommended download file for your system is the Intel PROSet/Wireless WiFi Software (includes Drivers): wireless_17.14.0_e164.exe

2. Go to Windows Device manager - Network Adapters, right click the Intel® Dual Band Wireless-N 7260 and Uninstall it, tick the option "Delete the driver software for this device".

3. Install the new driver you downloaded.

4. Go to the adapter properties in Device Manager, in the Power Management tab, and make sure there is a check-mark on the option "Allow the computer to turn off this device to save power".

Re: Dual Band Wireless-N 7260: As expected DPC issues continue over generations of products this time with a premium: BSOD

UUSRD — Fri, 13 Mar 2015 13:48:51 GMT

Yesterday I resumed my computer from sleep and after trying to connect to a low signal (distant) wireless router I got a BSOD.

Driver version: 17.14.0 (17.13.11.5)

This is the analysis from the memory dump:

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

* *

* Bugcheck Analysis *

* *

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

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.

Some common problems are exception code 0x80000003. This means a hard

coded breakpoint or assertion was hit, but this system was booted

/NODEBUG. This is not supposed to happen as developers should never have

hardcoded breakpoints in retail code, but ...

If this happens, make sure a debugger gets connected, and the

system is booted /DEBUG. This will let us see why this breakpoint is

happening.

Arguments:

Arg1: ffffffffc0000005, The exception code that was not handled

Arg2: fffff80224122cc4, The address that the exception occurred at

Arg3: ffffd0012ebd4868, Exception Record Address

Arg4: ffffd0012ebd4070, Context Record Address

Debugging Details:

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

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%08lx hace referencia a la memoria en 0x%08lx. La memoria no se pudo %s.

FAULTING_IP:

nt!KeSetEvent+14

fffff802`24122cc4 f6017f test byte ptr [rcx],7Fh

EXCEPTION_RECORD: ffffd0012ebd4868 -- (.exr 0xffffd0012ebd4868)

ExceptionAddress: fffff80224122cc4 (nt!KeSetEvent+0x0000000000000014)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 0000000000000000

Parameter[1]: ffffffffffffffff

Attempt to read from address ffffffffffffffff

CONTEXT: ffffd0012ebd4070 -- (.cxr 0xffffd0012ebd4070;r)

rax=0000000000000000 rbx=ffffe0010b0a71a0 rcx=7707a25611f14c05

rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000001

rip=fffff80224122cc4 rsp=ffffd0012ebd4aa0 rbp=ffffe0010b0a8320

r8=0000000000000000 r9=fffff80224084000 r10=000000000000001c

r11=ffffd0013262a000 r12=0000000000000000 r13=0000000000000001

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl zr na po nc

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

nt!KeSetEvent+0x14:

fffff802`24122cc4 f6017f test byte ptr [rcx],7Fh ds:002b:7707a256`11f14c05=??

Last set context:

rax=0000000000000000 rbx=ffffe0010b0a71a0 rcx=7707a25611f14c05

rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000001

rip=fffff80224122cc4 rsp=ffffd0012ebd4aa0 rbp=ffffe0010b0a8320

r8=0000000000000000 r9=fffff80224084000 r10=000000000000001c

r11=ffffd0013262a000 r12=0000000000000000 r13=0000000000000001

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl zr na po nc

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

nt!KeSetEvent+0x14:

fffff802`24122cc4 f6017f test byte ptr [rcx],7Fh ds:002b:7707a256`11f14c05=??

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%08lx hace referencia a la memoria en 0x%08lx. La memoria no se pudo %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff802243e7138

unable to get nt!MmNonPagedPoolStart

unable to get nt!MmSizeOfNonPagedPoolInBytes

ffffffffffffffff

FOLLOWUP_IP:

ndis!ndisDereferenceMiniport+10e

fffff800`ede90d8e ebbb jmp ndis!ndisDereferenceMiniport+0xcb (fffff800`ede90d4b)

BUGCHECK_STR: AV

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

LAST_CONTROL_TRANSFER: from fffff800ede90d8e to fffff80224122cc4

STACK_TEXT:

ffffd001`2ebd4aa0 fffff800`ede90d8e : 00000000`00000000 fffff802`00000000 fffff800`ede92d00 ffffe001`0b0a71a0 : nt!KeSetEvent+0x14

ffffd001`2ebd4b60 fffff800`edf28325 : ffffe001`13d329c0 00000000`00000080 ffffe001`0bf434f0 ffffe001`0b0a71a0 : ndis!ndisDereferenceMiniport+0x10e

ffffd001`2ebd4ba0 fffff800`ede92e2e : ffffe001`13d32b18 fffff800`edf06940 00000000`00000080 ffffe001`13d32b18 : ndis!ndisMQueuedFinishClose+0xc1

ffffd001`2ebd4bd0 fffff802`2415c280 : ffffe001`0b4d5880 ffffe001`0b4d5880 ffffd001`2ebd4c90 fffff802`241d7d7d : ndis!ndisWorkerThread+0x8e

ffffd001`2ebd4c00 fffff802`241dafc6 : ffffd001`32715180 ffffe001`0b4d5880 ffffd001`327212c0 dffbc004`66edfe70 : nt!PspSystemThreadStartup+0x58

ffffd001`2ebd4c60 00000000`00000000 : ffffd001`2ebd5000 ffffd001`2ebcf000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: ndis!ndisDereferenceMiniport+10e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ndis

IMAGE_NAME: ndis.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 54d01043

IMAGE_VERSION: 6.3.9600.17672

STACK_COMMAND: .cxr 0xffffd0012ebd4070 ; kb

BUCKET_ID_FUNC_OFFSET: 10e

FAILURE_BUCKET_ID: AV_ndis!ndisDereferenceMiniport

BUCKET_ID: AV_ndis!ndisDereferenceMiniport

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_ndis!ndisdereferenceminiport

FAILURE_ID_HASH: {55ed5713-e6dc-98f4-6dfb-c82e3fdb5920}

Followup: MachineOwner

---------

Re: Dual Band Wireless-N 7260: As expected DPC issues continue over generations of products this time with a premium: BSOD

jbenavides — Fri, 13 Mar 2015 18:18:05 GMT

Hello Fjtorsol,

The new BSOD is different than the one reported originally. This time it is reported for ndis.sys, which is a Windows* component.

Since the issue happened connecting to a distant router when coming back from sleep, it is advised to perform the following:

- Apply the settings from the document "http://www.intel.com/support/wireless/sb/CS-030709.htm?wapkw=wifi+recommended+settings What are the Recommended Settings for 802.11n Connectivity?"

- Check the Power options, in the advanced settings of the Power plan and make sure the Wireless Adapter is set to maximum performance.

- Have you tried disabling Fast Startup?

- Check your system for viruses.

- Please check your system for Windows updates.

If the issue persists, let us know the PC manufacture and model, also if this adapter was installed from factory in the PC, or if it it a custom upgrade.

Re: Dual Band Wireless-N 7260: As expected DPC issues continue over generations of products this time with a premium: BSOD

UUSRD — Sat, 14 Mar 2015 11:53:11 GMT

Yes I know it is the NDIS system driver but the timing and relation it has with network management seem to matter.

Why everyone suggests to try disabling fast boot are these drivers not hibernation-proof? Remember that the BSOD took place after sleep.

System is updated.

SFC and DISM checks are ok.

No viruses were found with different tests.

I have jet to try the power settings change for the PCI-e link but given the laptop was connected to A/C power it was working at "moderate power saving".