BSOD on Boot

[magicboy]

When i booted up my computer yesterday i got a BSOD .I've attached the .dmp. I don't know if its still something to do with my wireless adapter as i updated it. Thanks.

 

[nickle]

You have a driver that corrupted pool memory. Your best course of action is to run driver verifier to see if it can isolate the culprit. You can do this by typing VERIFIER /FLAGS 1 in the search area of start menu and reboot. Then wait for another BSOD. This will monitor all activity within pool memory for any driver which is causing corruption. More information here http://www.microsoft.com/whdc/DevTools/tools/DrvVerifier.mspx and here Special Pool.

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


Loading Dump File [C:\Users\Nickle\AppData\Local\Temp\Rar$DI00.493\020810-22011-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03052000 PsLoadedModuleList = 0xfffff800`0328fe50
Debug session time: Mon Feb  8 12:28:46.698 2010 (GMT-5)
System Uptime: 0 days 0:00:26.150
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffff800032519d0, fffff800032519d0, fffff800832519d0}

Probably caused by : Pool_Corruption ( nt!ExFreePool+536 )

Followup: Pool_corruption
---------

1: 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: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff800032519d0, the pool entry being checked.
Arg3: fffff800032519d0, the read back flink freelist value (should be the same as 2).
Arg4: fffff800832519d0, the read back blink freelist value (should be the same as 2).

Debugging Details:
------------------


BUGCHECK_STR:  0x19_3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800031f5d6f to fffff800030c3f00

STACK_TEXT:  
fffff880`03b8a388 fffff800`031f5d6f : 00000000`00000019 00000000`00000003 fffff800`032519d0 fffff800`032519d0 : nt!KeBugCheckEx
fffff880`03b8a390 fffff880`018828ed : 00000000`00000000 00180000`00000000 fffff8a0`0015b830 fffffa80`00000000 : nt!ExFreePool+0x536
fffff880`03b8a480 fffff880`0184a52f : fffff880`01943960 fffff880`01967800 fffffa80`044b2490 00000000`00000004 : tcpip!IppEnumerateInterfaceAddresses+0xc5
fffff880`03b8a570 fffff880`0160302b : fffff880`01943960 fffffa80`00000000 00180000`00000000 fffffa80`042076e0 : tcpip!IppEnumerateAllAddresses+0xd5
fffff880`03b8a5d0 fffff880`03e53e29 : fffffa80`042076e0 fffff8a0`00000070 fffffa80`042060e0 00000000`022cf5d0 : NETIO!NsiEnumerateObjectsAllParametersEx+0x24f
fffff880`03b8a7b0 fffff880`03e558e8 : fffffa80`042060e0 fffffa80`04206010 00000000`00000000 fffffa80`04206048 : nsiproxy!NsippEnumerateObjectsAllParameters+0x305
fffff880`03b8a9a0 fffff880`03e559db : fffffa80`04b187f0 00000000`00000000 00000000`00000001 00000000`00000003 : nsiproxy!NsippDispatchDeviceControl+0x70
fffff880`03b8a9e0 fffff800`033dc3a7 : fffffa80`0711ff20 fffffa80`0711ff20 fffffa80`04206128 fffffa80`04206010 : nsiproxy!NsippDispatch+0x4b
fffff880`03b8aa10 fffff800`033dcc06 : 00000000`022cf450 00000000`00000bc4 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`03b8ab40 fffff800`030c3153 : fffffa80`06f92780 00000000`022cf438 fffff880`03b8abc8 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
fffff880`03b8abb0 00000000`779bff2a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`022cf4c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779bff2a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExFreePool+536
fffff800`031f5d6f cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExFreePool+536

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExFreePool+536

BUCKET_ID:  X64_0x19_3_nt!ExFreePool+536

Followup: Pool_corruption
---------

 

[usasma]

There's lot's of network related drivers deep in the stack text (tcpip; NETIO; nsiproxy)
As such, I'd suggest:
- downloading a new, Windows 7 compatible Wireless USB device driver (if none are available, please post back)
- uninstalling your current, outdated wireless USB drivers
- installing the freshly downloaded copy of the wireless USB drivers and monitoring for further BSOD's.