Windows 7 NETIO.SYS related BSOD

[Landon]

So I 2 weeks ago I did a fresh installation of windows 7 to try and get rid of persistent BSOD's, and it seemed to work until today when this morning I got a blue screen within 15 minutes of turning on the computer while surfing the web. I though okay maybe its because of the cold humid weather, and its just a cold boot issue or something, but boom 10 minutes later it BSOD on me again while surfing the web. The first bluescreen said BAD_POOL_HEADER, but I couldn't read anything else in time, and I didn't change my dump settings till after the 2nd BSOD so I don't have the crash dump for the 1st one. The second one was:

DRIVER_IRQL_NOT_LESS_OR_EQUAL
Stop 0x000000D1
NETIO.SYS

Below are the results of running the windows debugger on the memory dump. I would attach the dump itself but it is 430mb so that isn't exactly feasible, and I can't find the mini-dumps. Where should I look? All I could find was the memory.dmp in the c:\windows folder.

Also in the windows debugger log below I noticed this line: "*** ERROR: Module load completed but symbols could not be loaded for RTL8192cu.sys". So I am not sure I have the symbol path correct.

Anyway here is the results of the debugger tool:

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`0325a000 PsLoadedModuleList = 0xfffff800`0349e670
Debug session time: Fri Mar 22 09:22:31.820 2013 (UTC - 5:00)
System Uptime: 0 days 0:02:26.757
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, fffffa8005d68cc0, fffffa8005d68da0, 40e0016}
*** ERROR: Module load completed but symbols could not be loaded for RTL8192cu.sys
Probably caused by : nwifi.sys ( nwifi!EtwEx_tidActivityInfoTransfer+98 )
Followup: MachineOwner
---------
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa8005d68cc0, The pool entry we were looking for within the page.
Arg3: fffffa8005d68da0, The next pool entry.
Arg4: 00000000040e0016, (reserved)
Debugging Details:
------------------

BUGCHECK_STR: 0x19_20
POOL_ADDRESS: fffffa8005d68cc0 Nonpaged pool
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
TAG_NOT_DEFINED_c000000f: FFFFF88003399FB0
LAST_CONTROL_TRANSFER: from fffff80003403cae to fffff800032cfc40
STACK_TEXT:
fffff880`03392518 fffff800`03403cae : 00000000`00000019 00000000`00000020 fffffa80`05d68cc0 fffffa80`05d68da0 : nt!KeBugCheckEx
fffff880`03392520 fffff880`0110bce2 : 00000000`00000001 fffff880`051a8eb0 fffffa80`72697377 00000000`00000000 : nt!ExDeferredFreePool+0x12da
fffff880`033925d0 fffff880`051a8d9c : fffffa80`06d58800 00000000`00000000 fffffa80`05ed6580 fffffa80`06a0d280 : ndis!NdisFreeNetBuffer+0xf2
fffff880`03392600 fffff880`051a4f58 : fffffa80`0d25bb20 00000000`00000000 fffffa80`05ed6580 fffffa80`0aac0280 : nwifi!EtwEx_tidActivityInfoTransfer+0x98
fffff880`03392630 fffff880`051a8860 : 00000000`00000000 00000000`00000000 fffffa80`05ed6580 00000000`00000000 : nwifi!Dot11SendCompletion+0x44
fffff880`03392660 fffff880`03fbf1bb : fffffa80`0cdd7a78 00000000`00000001 00000000`00000000 fffffa80`05d71440 : nwifi!Pt6SendComplete+0x28
fffff880`03392690 fffff880`011c321d : fffffa80`0a5671a0 00000000`00000000 00000000`00000001 fffffa80`0a5a9000 : vwififlt!FilterSendNetBufferListsComplete+0x10b
fffff880`033926e0 fffff880`026b9964 : fffffa80`05d68b90 00000000`00000001 fffffa80`0c22c730 fffffa80`0a5a9000 : ndis!NdisMSendNetBufferListsComplete+0x6d
fffff880`03392720 fffff880`026fa1c8 : fffffa80`0c22c730 00000000`00000000 fffffa80`0ad74b80 fffffa80`0d14c010 : RTL8192cu+0x1a964
fffff880`03392750 fffff880`026fa38f : 00000000`00000000 fffffa80`0a7c3201 fffffa80`0c237520 fffffa80`0a5a9000 : RTL8192cu+0x5b1c8
fffff880`03392780 fffff880`02727b3e : fffffa80`0a5a9000 fffffa80`0a5a9000 00000000`fffffffe 00000000`00001008 : RTL8192cu+0x5b38f
fffff880`033927c0 fffff880`026bb884 : 00000000`00000000 00000000`00000000 fffffa80`0a7c3200 fffffa80`0ad71a88 : RTL8192cu+0x88b3e
fffff880`03392860 fffff880`00ea65c0 : fffffa80`0ad74b80 00000000`00000000 fffffa80`0aa7ee30 fffffa80`08b181a0 : RTL8192cu+0x1c884
fffff880`033928d0 fffff880`00ea7838 : fffffa80`0aa7ee40 fffffa80`0aa7ee30 00000000`00000001 fffffa80`0aa7ee40 : Wdf01000!FxRequestBase::CompleteSubmitted+0x170
fffff880`03392950 fffff880`00ea84b8 : 00000000`00000002 fffffa80`05ea23f0 00000000`00000000 00000000`00000000 : Wdf01000!FxIoTarget::RequestCompletionRoutine+0x1c0
fffff880`033929c0 fffff800`032bb7a5 : 00000000`00000000 00000000`c0000016 fffffa80`05cbb6b0 fffff800`0340430d : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c
fffff880`033929f0 fffff800`032d36d1 : fffffa80`0d14c1bb 00000000`00000000 00000000`00000000 00000000`00000050 : nt!IopUnloadSafeCompletion+0x55
fffff880`03392a30 fffff880`04a13631 : fffffa80`08b18050 fffffa80`0ad74d00 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`03392b20 fffff880`04a13b0f : fffffa80`05ee5a02 fffffa80`0d14c010 00000000`ffffffff fffffa80`08b18eb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff880`03392c00 fffff880`04a1166f : fffffa80`08b18eb0 fffffa80`08b181a0 fffffa80`08b19050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`03392c60 fffff880`04a02f89 : fffffa80`08b18050 00000000`00000000 fffffa80`08b18e02 fffffa80`08b18eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`03392ca0 fffff800`032da3fc : fffff880`0336a180 fffffa80`08b18eb0 fffffa80`08b18ec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`03392cd0 fffff800`032c794a : fffff880`0336a180 fffff880`033750c0 00000000`00000000 fffff880`04a02db0 : nt!KiRetireDpcList+0x1bc
fffff880`03392d80 00000000`00000000 : fffff880`03393000 fffff880`0338d000 fffff880`03392d40 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND: kb
FOLLOWUP_IP:
nwifi!EtwEx_tidActivityInfoTransfer+98
fffff880`051a8d9c 488bcb mov rcx,rbx
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nwifi!EtwEx_tidActivityInfoTransfer+98
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nwifi
IMAGE_NAME: nwifi.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc3b
FAILURE_BUCKET_ID: X64_0x19_20_nwifi!EtwEx_tidActivityInfoTransfer+98
BUCKET_ID: X64_0x19_20_nwifi!EtwEx_tidActivityInfoTransfer+98
Followup: MachineOwner
---------

Any help or suggestions would be greatly appreciated this is my work computer, and my home gaming/entertainment center (I work from home). I spend a lot of time on it and need it working stable. Thanks.

 

[usasma]

Please provide this information so we can provide a complete analysis: Link Removed It'll collect the minidumps also (minidumps are in C:\Windows\Minidump )

The only 3rd party driver listed in the stack in your post is rtl8192cu.sys - a driver component of your Realtek RTL8192C Wireless USB 2.0 Adapter

I do not recommend using wireless USB network devices. Especially in Win7/Win8 systems.
These wireless USB devices have many issues with Win7(and I suspect with Win8) - using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7/Win8 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

I suggest removing the wireless adapter and it's associated software to see if that stops the BSOD's.
If it does, then you can either use a long wire or an "inside the case" wireless card to replace it.

If that doesn't stop the BSOD's, then the requested reports should help us find any other problem issues with the system.

Good luck!

 

[Landon]

Please provide this information so we can provide a complete analysis: Link Removed It'll collect the minidumps also (minidumps are in C:\Windows\Minidump )

The only 3rd party driver listed in the stack in your post is rtl8192cu.sys - a driver component of your Realtek RTL8192C Wireless USB 2.0 Adapter


I suggest removing the wireless adapter and it's associated software to see if that stops the BSOD's.
If it does, then you can either use a long wire or an "inside the case" wireless card to replace it.

If that doesn't stop the BSOD's, then the requested reports should help us find any other problem issues with the system.

Good luck!

Thank you for responding. I suspected it may be the wireless adapter, but was unaware of any systematic or inherent problems with those types of devices. I have already removed the device and uninstalled the drivers for it, and am now using an Ethernet cable to connect. If another BSOD occurs I will re-post here.

One thing that strike me as odd though is that the wireless adapter I was using was the Belkin N300 wireless adapter, Link Removed. Why would windows see this as a Realtek RTL8192C Wireless USB 2.0 Adapter?

 

[usasma]

Wireless adapter suppliers purchase the devices and the "chipset" for these devices in bulk from manufacturer's and then package them with their own branding.