BSOD - kmode exception not handled (netwew02.sys)

Phateis · Apr 11, 2014

Hello there, I just got an Asus Q501LA notebook and while connecting to a wireless network I get a BSOD with this message kmode exception not handled (netwew02.sys) Any help would be greatly appreciated.

https://www.dropbox.com/s/htt2n7dxnrrtrl2/DSASUS-Fri_04_11_2014__65552_11.zip

lifetec · Apr 11, 2014

All 5 dumpfiles blame Probably caused by : NETwew02.sys .
The netwew02.sys is the driver for Intel® Wireless WiFi Link Driver - Intel® Wireless WiFi Link Adapter (Windows 8 only AFAIK).
Your netwew02.sys drivers is from Tue Feb 18 17:43:42 2014(53038dbe) 003565c4 None NETwew02.sys
Where did you get this driver from?
According to Asussupportsite of your model ASUSTeK Computer Inc. -Support- Drivers and Download Q501LA you must first uninstall the older driver before you install the new driver.

You are also using a AirPcap a wifi capture adapter for windows with drivers from 2011, who according to WinPcap site are not compatible with windows 8. There is a new version 4.1.3 which added windows 8 support.
It could be that these 2 drivers are interfering and give problems
Hopefully updating the winPcap driver to windows 8 version will solve the BSOD.
Another possibility is that your netwew driver is corrupted, uninstalling it and reinstall may solve this.
Or that your version is not compatible with your system, take the version of the above Asussupportsite.

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000094, fffff88004eefb1e, 0, fffff8800098f180}
*** WARNING: Unable to verify timestamp for NETwew02.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwew02.sys
Probably caused by : NETwew02.sys ( NETwew02+c9b1e )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
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: ffffffffc0000094, The exception code that was not handled
Arg2: fffff88004eefb1e, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: fffff8800098f180, Parameter 1 of the exception
Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {UITZONDERING}  Integer: deling door nul.
FAULTING_IP: 
NETwew02+c9b1e
fffff880`04eefb1e 48f7f1          div     rax,rcx
EXCEPTION_PARAMETER2:  fffff8800098f180
BUGCHECK_STR:  0x1E_c0000094
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  2
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
DPC_STACK_BASE:  FFFFF880009BFFB0
LAST_CONTROL_TRANSFER:  from fffff8000318c902 to fffff8000306c440
STACK_TEXT:  
fffff880`009b6e18 fffff800`0318c902 : 00000000`0000001e ffffffff`c0000094 fffff880`04eefb1e 00000000`00000000 : nt!KeBugCheckEx
fffff880`009b6e20 fffff800`030d847d : fffff880`009b7470 00000000`00000002 fffff880`009b6f90 fffff880`01d61607 : nt!KiFatalExceptionHandler+0x22
fffff880`009b6e60 fffff800`03100364 : 00000000`00000000 fffff880`009b6f90 fffffa80`00008910 fffff880`009b3000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`009b6e90 fffff800`030da1d6 : fffff880`009b7d98 fffff880`009b7ad0 fffff880`009b7d98 fffffa80`09014c80 : nt!RtlDispatchException+0x458
fffff880`009b75a0 fffff800`0306b842 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x455
fffff880`009b7c60 fffff800`03068c34 : 00000000`00000004 fffff880`04ef251c 00000000`00000037 fffff880`009b7e70 : nt!KiExceptionDispatch+0xc2
fffff880`009b7e40 fffff880`04eefb1e : fffffa80`090f7a18 00000000`00000000 fffffa80`0f795250 00000000`00000000 : nt!KiDivideErrorFault+0xf4
fffff880`009b7fd0 fffffa80`090f7a18 : 00000000`00000000 fffffa80`0f795250 00000000`00000000 00000002`624e62aa : NETwew02+0xc9b1e
fffff880`009b7fd8 00000000`00000000 : fffffa80`0f795250 00000000`00000000 00000002`624e62aa fffff880`04eef87b : 0xfffffa80`090f7a18

STACK_COMMAND:  kb
FOLLOWUP_IP: 
NETwew02+c9b1e
fffff880`04eefb1e 48f7f1          div     rax,rcx
SYMBOL_STACK_INDEX:  7
SYMBOL_NAME:  NETwew02+c9b1e
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: NETwew02
IMAGE_NAME:  NETwew02.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  53038dbe
FAILURE_BUCKET_ID:  0x1E_c0000094_NETwew02+c9b1e
BUCKET_ID:  0x1E_c0000094_NETwew02+c9b1e
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:0x1e_c0000094_netwew02+c9b1e
FAILURE_ID_HASH:  {637e7b5f-d09c-dc26-28a2-cf0a16de941d}
Followup: MachineOwner

Please update these older drivers. Linksare included to assist in looking up the source of the drivers. If unable tofind an update, please remove (un-install) the program responsible for thatdriver. DO NOT manually delete/rename the driver as it may make the systemunbootable! :
Note: first check the support/driver downloadsite of your OEM model or system for the latest windows 8.0 drivers.

ASMMAP64 fffff880`07466000 fffff880`0746e000 Thu Jul 02 11:13:26 2009 (4a4c7a36) 0000ceab ASMMAP64.sys
Driver Description: LENOVO ATK Hotkey ATK0101 ACPI UTILITY (also found in Asus systems)
Driver Update Site: Lenovo Support - Home (US)

atkwmiacpi64 fffff880`04073000 fffff880`0407c000 Wed Sep 07 03:44:52 2011 (4e66cc94) 000056b5 atkwmiacpi64.sys
Driver Description: ATK WMIACPI Utility
Driver Update Site: http://support.asus.com/download/download.aspx

AiCharger fffff880`04ce3000 fffff880`04ce5880 Fri Sep 23 04:04:40 2011 (4e7be938) 0000a877 AiCharger.sys
Driver Description: Asus Charger Driver
Likely BSOD cause - haven't seen recently (15Jan2013)
Driver Update Site: ASUSTeK Computer Inc. -Support- Drivers and Download P6T

WPRO_41_2001 fffff880`18d92000 fffff880`18d9e000 Mon Nov 07 22:04:48 2011 (4eb847f0) 00015adc WPRO_41_2001.sys
Driver Description: CACE Technologies WinPcap Packet Driver
Driver Update Site: WinPcap · Download

Phateis · Apr 11, 2014

Thanks lifetec, I will try these solutions and report back.

BSOD - kmode exception not handled (netwew02.sys)

Phateis

New Member

My Computer

System One

lifetec

New Member

My Computer

System One

Phateis

New Member

My Computer

System One