Wireless-AC 7265 BSOD Error

[idata]

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.

[Benjamin_S_Intel]

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.

[ASouz7]

• 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

[SCorn2]

18.33.0.1 seems to have done the trick for me (so far at least). I've had it installed for a few weeks and haven't had an Intel-related BSOD since then.

Intel(R) Dual Band Wireless-AC 7260

System Model: Dell XPS13 9333

Windows 10

[ASouz7]

SimonCornforth,

Thanks for letting us know that this version worked for you.

[SCorn2]

I upgraded from 18.33.0.1 to 18.33.0.2 (which is distributed as part of 15.40.18.4380 win64_154018.4380.exe) a few weeks ago and since then have been getting about one BSOD a week from 18.33.0.2

Card:Intel(R) Dual Band Wireless-AC 7260

System Model: Dell XPS13 9333

OS:Windows 10

Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

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 10 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:

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

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.63.amd64fre.th2_release.160104-1513

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: 98

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8004c38ff64

READ_ADDRESS: fffff801d160c520: Unable to get MiVisibleState

0000000000000098

CURRENT_IRQL: 2

FAULTING_IP:

Netwbw02+4ff64

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

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: AV

PROCESS_NAME: System

ANALYSIS_SESSION_HOST: DELL-LAPTOP-01

ANALYSIS_SESSION_TIME: 02-05-2016 19:41:10.0457

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

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

[JDeen]

I've been using the 18.33.01 drivers for a while now, however still the occasionally crash.

In fact it always happens when I wake the laptop from sleep!! (frequently when I change places...) Any thoughts?

Here is the latest memorydump:

KERNEL_SECURITY_CHECK_FAILURE (139)

A kernel component has corrupted a critical data structure. The corruption

could potentially allow a malicious user to gain control of this machine.

Arguments:

Arg1: 0000000000000002, Stack cookie instrumentation code detected a stack-based

buffer overrun.

Arg2: ffffd0004e91ae20, Address of the trap frame for the exception that caused the bugcheck

Arg3: ffffd0004e91ad78, Address of the exception record for the exception that caused the bugcheck

Arg4: 0000000000000000, Reserved

Debugging Details:

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

Page 340 not present in the dump file. Type ".hh dbgerr004" for details

Page 340 not present in the dump file. Type ".hh dbgerr004" for details

Page 340 not present in the dump file. Type ".hh dbgerr004" for details

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 10586.212.amd64fre.th2_release_sec.160328-1908

SYSTEM_MANUFACTURER: Dell Inc.

SYSTEM_PRODUCT_NAME: XPS 13 9343

SYSTEM_SKU: 0665

BIOS_VENDOR: Dell Inc.

BIOS_VERSION: A07

BIOS_DATE: 11/11/2015

BASEBOARD_MANUFACTURER: Dell Inc.

BASEBOARD_PRODUCT: 0F5KF3

BASEBOARD_VERSION: A00

DUMP_TYPE: 1

BUGCHECK_P1: 2

BUGCHECK_P2: ffffd0004e91ae20

BUGCHECK_P3: ffffd0004e91ad78

BUGCHECK_P4: 0

TRAP_FRAME: ffffd0004e91ae20 -- (.trap 0xffffd0004e91ae20)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=fffff80133c77850 rbx=0000000000000000 rcx=0000000000000002

rdx=ffffe000197cf010 rsi=0000000000000000 rdi=0000000000000000

rip=fffff801339c4875 rsp=ffffd0004e91afb8 rbp=ffffe00019324010

r8=ffffe000197cf010 r9=0000000fffffffff r10=fffffd8000002190

r11=ffffd0004e91af30 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz ac po nc

Netwtw02+0x24875:

fffff801`339c4875 cd29 int 29h

Resetting default scope

EXCEPTION_RECORD: ffffd0004e91ad78 -- (.exr 0xffffd0004e91ad78)

ExceptionAddress: fffff801339c4875 (Netwtw02+0x0000000000024875)

ExceptionCode: c0000409 (Security check failure or stack buffer overrun)

ExceptionFlags: 00000001

NumberParameters: 1

Parameter[0]: 0000000000000002

Subcode: 0x2 FAST_FAIL_STACK_COOKIE_CHECK_FAILURE

CPU_COUNT: 4

CPU_MHZ: a22

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)

BUGCHECK_STR: 0x139

PROCESS_NAME: System

CURRENT_IRQL: 2

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR: c0000409

EXCEPTION_PARAMETER1: 0000000000000002

DEFAULT_BUCKET_ID: STACK_COOKIE_CHECK_FAILURE

WATSON_BKT_EVENT: BEX

ANALYSIS_SESSION_HOST: JOCHEM-XPS13

ANALYSIS_SESSION_TIME: 04-23-2016 00:42:19.0388

ANALYSIS_VERSION: 10.0.10586.567 x86fre

LAST_CONTROL_TRANSFER: from fffff800083532e9 to fffff80008348760

FAULTING_THREAD: 0000000000000000

STACK_TEXT:

ffffd000`4e91aaf8 fffff800`083532e9 : 00000000`00000139 00000000`00000002 ffffd000`4e91ae20 ffffd000`4e91ad78 : nt!KeBugCheckEx

ffffd000`4e91ab00 fffff800`08353610 : ffffe000`17f9f040 00000000`00000001 ffffe000`1929f000 fffff801`33c65838 : nt!KiBugCheckDispatch+0x69

ffffd000`4e91ac40 fffff800`083527f3 : ffffe000`1929f00c ffffe000`1929f00c ffffe000`0f01c7e4 00000000`00000000 : nt!KiFastFailDispatch+0xd0

ffffd000`4e91ae20 fffff801`339c4875 : fffff801`33b43389 ffffe000`0f01c174 fffff801`33ca8098 ffffd000`4e91b0b0 : nt!KiRaiseSecurityCheckFailure+0xf3

ffffd000`4e91afb8 fffff801`33b43389 : ffffe000`0f01c174 fffff801`33ca8098 ffffd000`4e91b0b0 ffffe000`193246ea : Netwtw02+0x24875

ffffd000`4e91afc0 37324142`37424350 : 42435055`202d2046 ff004637`32414237 ffffe000`0e3cd288 fffff800`089d31ce : Netwtw02+0x1a3389

ffffd000`4e91b1f0 42435055`202d2046 : ff004637`32414237 ffffe000`0e3cd288 fffff800`089d31ce 00000000`00000000 : 0x37324142`37424350

ffffd000`4e91b1f8 ff004637`32414237 : ffffe000`0e3cd288 fffff800`089d31ce 00000000`00000000 fffff801`00000000 : 0x42435055`202d2046

ffffd000`4e91b200 ffffe000`0e3cd288 : fffff800`089d31ce 00000000`00000000 fffff801`00000000 fffff801`33c65838 : 0xff004637`32414237

ffffd000`4e91b208 fffff800`089d31ce : 00000000`00000000 fffff801`00000000 fffff801`33c65838 ffffe000`0f0a1b01 : 0xffffe000`0e3cd288

ffffd000`4e91b210 6c667065`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!KeQueryPerformanceCounter+0x6e

ffffd000`4e91b240 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff26ce`0c12efac : 0x6c667065`00000000

THREAD_SHA1_HASH_MOD_FUNC: bcf090c7d52dc5a526cc31286b2f204b81e6ffa0

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ad8ae251b4e751bee862f4ea...

[ASouz7]

Jocham,

Have you tried driver version 18.40.x as it contain many fixes that might hel you get rid of this situation. Inte recommends to use the computer manufacturer latest driver version first. You may find their contact information here: http://www.intel.com/content/www/us/en/support/topics/OEMs.html Computer Manufacturer Support Websites

Alternatively, you can use our generic drivers found in our donwload center. Here is the link to it: https://downloadcenter.intel.com/product/83635/Intel-Dual-Band-Wireless-AC-7265 Downloads for Intel® Dual Band Wireless-AC 7265 - Junt make to download the drivers according to your you OS version and architecture.

[SCorn2]

I reported on 17-04-2016 that I was getting about one Netwbw02.sys-related crash a week on 18.33.0.2 (which is distributed as part of 15.40.18.4380 win64_154018.4380.exe). Since that date I haven't had any Netwbw02.sys-related crashes.

Card:Intel(R) Dual Band Wireless-AC 7260

System Model: Dell XPS13 9333

OS:Windows 10

[ASouz7]

SimonCornforth,

Thanks for letting us know. Please keep us informed should you our assistance. We will be more than glad to assist you.

[JL2]

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

Copyright (c) Microsoft Corporation. All rights reserved.

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

[ASouz7]

JL624,

Is there an specific task you are trying to do that causes the BSOD or does it happen out of the blue?

[JL2]

Hi Aleki,

This happens randomly out of the blue. I'd be in the middle of watching a video on Youtube or just reading a post on Chrome.

[ASouz7]

JL624,

Is this wireless adapter the one the was installed by factory?

[JL2]

Yes, it is the factory installed wireless adapter.

[Alek_S_Intel]

JL624,

Please check your private messages.

[RLazo]

Dell Inspiron 13z touch

same trouble .... even with 18.40.0 driver

randomly collapsing .. i really cant work.

this is a dissaster

[RLazo]

version 18.21.0 is working fine until now - I think the issue /in my case at least/ is somehow connected to Connectify software or just creating a hot spot in general.

all the newer drivers are crushing.

[SWang72]

Hello,

I have the exact same problem for 20 laptops in corporate environment. Can we get the driver working for version 18.4 for Wireless AC-7265 Win7 x64? The latest driver wont install on Win7

Here is my post in Lenovo page

https://forums.lenovo.com/t5/ThinkPad-X-Series-Laptops/Lenovo-X1-20BT-Carbon-Random-BSOD-Wireless-Driver-18-2-Unable-to/m-p/3311883/highlight/false# M69748 Lenovo X1 20BT Carbon - Random BSOD - Wireless Dri... - Lenovo Community

[Benjamin_S_Intel]

After a long time of not seeing any BSOD's with 18.32.0.5 driver, I just hit a bugcheck 0x133. I'll try latest driver from Intel.com, https://downloadcenter.intel.com/download/25833/Intel-PROSet-Wireless-Software-and-Drivers-for-Windows-10?product=83635 Download Intel® PROSet/Wireless Software and Drivers for Windows® 10.

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

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

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 10240.16841.amd64fre.th1_st1.160408-1853

SYSTEM_SKU: LENOVO_MT_20DK_BU_Think_FM_ThinkPad S1 Yoga 12

SYSTEM_VERSION: ThinkPad S1 Yoga 12

BIOS_VENDOR: LENOVO

BIOS_VERSION: JEET69WW (1.18 )

BIOS_DATE: 07/24/2015

BASEBOARD_MANUFACTURER: LENOVO

BASEBOARD_PRODUCT: 20DKS09J00

BASEBOARD_VERSION: SDK0E50510 WIN

DUMP_TYPE: 1

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

CPU_COUNT: 4

CPU_MHZ: 8f7

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)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

STACK_TEXT:

fffff803`4ef03c18 fffff803`4d00b44e : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx

fffff803`4ef03c20 fffff803`4ceeec06 : ffffe001`5e382000 00000000`000bddf4 00000000`00000002 fffff803`4d1ed180 : nt! ?? ::FNODOBFM::`string'+0x2334e

fffff803`4ef03cb0 fffff803`4cee996d : 00000000`00000000 00000000`0000138a 00000000`00000000 00000000`00000004 : nt!KiUpdateRunTime+0x56

fffff803`4ef03d10 fffff803`4ce1baa6 : 00002a05`3cfdd46a fffff803`4eef5400 fffff803`4eef4ef0 00000000`00000000 : nt!KeClockInterruptNotify+0x53d

fffff803`4ef03f40 fffff803`4cf5e7d7 : fffff803`4ce652e0 00000000`00000008 fffff803`4ef03f50 00000000`00000010 : hal!HalpTimerClockInterrupt+0x56

fffff803`4ef03f70 fffff803`4cfda89a : fffff803`4ce652e0 ffffe001`5e59f530 00000000`00000000 ffffe001`5a359501 : nt!KiCallInterruptServiceRoutine+0x87

fffff803`4ef03fb0 fffff803`4cfdacc7 : ffffe606`efa7fb7a 00000000`0000000a fffff800`0000400d 400d0000`e10f0c00 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea

fffff803`4eef4ef0 fffff803`4cee7e78 : ffffe001`5a359501 ffffe001`62669300 ffffe001`5e437b70 fffff800`5962e090 : nt!KiInterruptDispatchNoLockNoEtw+0x37

fffff803`4eef5080 fffff803`4cf5ea32 : 00000000`00000002 fffff800`00000000 ffffe001`00000000 ffffe001`5e437b70 : nt!KxWaitForSpinLockAndAcquire+0x18

fffff803`4eef50b0 fffff800`595dd044 : ffffe001`63c6a5b0 ffffe001`5e437b70 ffffe001`5a359540 ffffe001`63c6a5b0 : nt!KeAcquireSpinLockRaiseToDpc+0x32

fffff803`4eef50e0 fffff800`5969eedd : ffffe001`00000000 fffff800`598e1880 ffffe001`629b82a0 fffff800`575cf035 : Netwtw02+0x5d044

fffff803`4eef5110 fffff800`595d32c0 : 00000000`00000000 ffffe001`62669300 00000000`00000000 fffff800`59608293 : Netwtw02+0x11eedd

fffff803`4eef5190 fffff800`59633d13 : fffff803`4eef5400 fffff803`4eef5330 ffffe001`5a359540 ffffe001`5e437b70 : Netwtw02+0x532c0

fffff803`4eef51e0 fffff800`59632ba6 : 00000000`0001aabe fffff803`4eef5330 fffff800`5985d0f8 fffff800`5985d0f8 : Netwtw02+0xb3d13

fffff803`4eef5230 fffff800`59635217 : 00000000`0000002a fffff800`5985d110 00000000`00000018 fffff803`4eef5430 : Netwtw02+0xb2ba6

fffff803`4eef53c0 fffff800`5982bc13 : fffff803`4eef55b0 ffffe001`00000000 fffff800`59844838 fffff800`5982003c : Netwtw02+0xb5217

fffff803`4eef5550 fffff800`5982dfc8 : 00000000`00000008 ffffe001`5e6bdeb0 ffffd001`03aea004 00000000`00000004 : Netwtw02+0x2abc13

fffff803`4eef55a0 fffff800`59829406 : ffffd001`03ab4084 00000000`000000ff ffffe001`5e6bdd98 fffff803`4ce1a854 : Netwtw02+0x2adfc8

fffff803`4eef55e0 fffff800`59829f4d : ffffe001`5e56c440 0000000a`a074fa37 00000000`00000001 ffffe001`5e43e2ff : Netwtw02+0x2a9406

fffff803`4eef5680 fffff800`5981f86a : ffffe001`00000001 ffffe001`5e45d3c0 ffffe001`5e515980 00000000`80000000 : Netwtw02+0x2a9f4d

fffff803`4eef5710 fffff800`575b8424 : 00000000`00000000 00000000`00000000 ffffe001`5e6f9b90 fffff800`56a636f1 : Netwtw02+0x29f86a

fffff803`4eef5780 fffff803`4cee8c65 : fffff803`4eef5b20 fffff803`4cf12437 00000100`00010100 00000002`ffffffff : ndis!ndisInterruptDpc+0x1c4

fffff803`4eef58c0 fffff803`4cee8340 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x275

fffff803`4eef5a10 fffff803`4cfdc22a : fffff803`4d1ed180 fffff803`4d1ed180 fffff803`4d263740 ffffe001`63932800 : nt!KiRetireDpcList+0xe0

fffff803`4eef5c60 00000000`00000000 : fffff803`4eef6000 fffff803`4eef0000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 86c25b02910e3eb78ff372a61b597deae6054951

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 560a522e15efbd6cacb4f399ebd7b85ebd84cdb4

THREAD_SHA1_HASH_MOD: 77786a92300b36f9e6d0ec053718e14584cf4d0e

FOLLOWUP_IP:

Netwtw02+5d044

fffff800`595dd044 884308 mov byte ptr [rbx+8],al

FAULT_INSTR_CODE: f084388

SYMBOL_STACK_INDEX: a

SYMBOL_NAME: Netwtw02+5d044

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Netwtw02

IMAGE_NAME: Netwtw02.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5679a9da

BUCKET_ID_FUNC_OFFSET: 5d044

FAILURE_BUCKET_ID: 0x133_DPC_Netwtw02!Unknown_Function

BUCKET_ID: 0x133_DPC_Netwtw02!Unknown_Function

PRIMARY_PROBLEM_CLASS: 0x133_DPC_Netwtw02!Unknown_Function

TARGET_TIME: 2016-06-15T19:01:20.000Z

OSBUILD: 10240

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-04-09 00:48:24

BUILDDATESTAMP_STR: 160408-1853

BUILDLAB_STR: th1_st1

BUILDOSVER_STR: 10.0.10240.16841.amd64fre.th1_st1.160408-1853

ANALYSIS_SESSION_ELAPSED_TIME: 46dc

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x133_dpc_netwtw02!unknown_function

FAILURE_ID_HASH: {572b67dd-625a-961a-890f-5e687563ff62}

Followup: MachineOwner