View Single Post
12 Feb 2012  
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:\BSODDmpFiles\relaxedcrazyman\Windows_NT6_BSOD_jcgriff2\021212-23290-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500? Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e68000 PsLoadedModuleList = 0xfffff800`030ad670 Debug session time: Sun Feb 12 17:54:32.663 2012 (GMT-7) System Uptime: 0 days 0:40:03.740 Loading Kernel Symbols ............................................................... ................................................................ .................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, fffffa80048f2060, fffff80000b9c518, fffffa800937a410} *** WARNING: Unable to verify timestamp for NETw5s64.sys *** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys Probably caused by : NETw5s64.sys Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver is causing an inconsistent power state. Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: fffffa80048f2060, Physical Device Object of the stack Arg3: fffff80000b9c518, Functional Device Object of the stack Arg4: fffffa800937a410, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: fffffa800937a410 DEVICE_OBJECT: fffffa80070d7050 DRIVER_OBJECT: fffffa8005052920 IMAGE_NAME: NETw5s64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c04085e MODULE_NAME: NETw5s64 FAULTING_MODULE: fffff8800588d000 NETw5s64 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002f52cd2 to fffff80002ee4c40 STACK_TEXT: fffff800`00b9c4c8 fffff800`02f52cd2 : 00000000`0000009f 00000000`00000003 fffffa80`048f2060 fffff800`00b9c518 : nt!KeBugCheckEx fffff800`00b9c4d0 fffff800`02ef05fc : fffff800`00b9c600 fffff800`00b9c600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90 fffff800`00b9c570 fffff800`02ef0496 : fffffa80`09296168 fffffa80`09296168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c fffff800`00b9c5e0 fffff800`02ef037e : 00000005`98bdafe9 fffff800`00b9cc58 00000000`000259e4 fffff800`0305ef08 : nt!KiProcessExpiredTimerList+0xc6 fffff800`00b9cc30 fffff800`02ef0167 : 00000001`619dc1c4 00000001`000259e4 00000001`619dc188 00000000`000000e4 : nt!KiTimerExpiration+0x1be fffff800`00b9ccd0 fffff800`02edc96a : fffff800`0305ae80 fffff800`03068cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277 fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_IMAGE_NETw5s64.sys BUCKET_ID: X64_0x9F_IMAGE_NETw5s64.sys Followup: MachineOwner ---------
  2. Loading Dump File [F:\BSODDmpFiles\relaxedcrazyman\Windows_NT6_BSOD_jcgriff2\021212-27721-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e57000 PsLoadedModuleList = 0xfffff800`0309c670 Debug session time: Sun Feb 12 16:33:52.657 2012 (GMT-7) System Uptime: 0 days 0:21:07.734 Loading Kernel Symbols ............................................................... ................................................................ .................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C2, {7, 109b, 210008, fffffa80094f1610} Unable to load image \SystemRoot\system32\DRIVERS\NETw5s64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for NETw5s64.sys *** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys GetPointerFromAddress: unable to read from fffff80003106100 Probably caused by : NETw5s64.sys ( NETw5s64+1f9f15 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_CALLER (c2) The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc. Arguments: Arg1: 0000000000000007, Attempt to free pool which was already freed Arg2: 000000000000109b, (reserved) Arg3: 0000000000210008, Memory contents of the pool block Arg4: fffffa80094f1610, Address of the block of pool being deallocated Debugging Details: ------------------ POOL_ADDRESS: fffffa80094f1610 FREED_POOL_TAG: W3Rx BUGCHECK_STR: 0xc2_7_W3Rx CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: fzsftp.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80003001be9 to fffff80002ed3c40 STACK_TEXT: fffff880`0b2f5ef8 fffff800`03001be9 : 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`00210008 : nt!KeBugCheckEx fffff880`0b2f5f00 fffff880`016e7382 : fffffa80`049aefb0 fffff880`0589efc2 00000000`00000200 fffffa80`094f1630 : nt!ExDeferredFreePool+0x1201 fffff880`0b2f5fb0 fffff880`05a82f15 : fffff880`05a82e50 fffffa80`07afd5c0 fffffa80`049aefe0 fffff880`0589efc2 : ndis!NdisFreeNetBufferList+0x112 fffff880`0b2f5fe0 fffff880`05a82e50 : fffffa80`07afd5c0 fffffa80`049aefe0 fffff880`0589efc2 00000000`00000000 : NETw5s64+0x1f9f15 fffff880`0b2f5fe8 fffffa80`07afd5c0 : fffffa80`049aefe0 fffff880`0589efc2 00000000`00000000 fffffa80`043184c0 : NETw5s64+0x1f9e50 fffff880`0b2f5ff0 fffffa80`049aefe0 : fffff880`0589efc2 00000000`00000000 fffffa80`043184c0 fffffa80`07afd5c0 : 0xfffffa80`07afd5c0 fffff880`0b2f5ff8 fffff880`0589efc2 : 00000000`00000000 fffffa80`043184c0 fffffa80`07afd5c0 fffff880`0589aebd : 0xfffffa80`049aefe0 fffff880`0b2f6000 00000000`00000000 : fffffa80`043184c0 fffffa80`07afd5c0 fffff880`0589aebd fffff880`0b2f6064 : NETw5s64+0x15fc2 STACK_COMMAND: kb FOLLOWUP_IP: NETw5s64+1f9f15 fffff880`05a82f15 ?? ??? SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: NETw5s64+1f9f15 FOLLOWUP_NAME: MachineOwner MODULE_NAME: NETw5s64 IMAGE_NAME: NETw5s64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c04085e FAILURE_BUCKET_ID: X64_0xc2_7_W3Rx_NETw5s64+1f9f15 BUCKET_ID: X64_0xc2_7_W3Rx_NETw5s64+1f9f15 Followup: MachineOwner ---------
  1. This basically means your system sent a signal to a device driver to turn the device on or off, and the driver failed to respond or the device failed to enter the power state. This usually happens if a driver is not working as it should, needs to be updated, or is corrupted. In your case, the device in question is the network wireless adapter.

    If re-installing the driver and/or updating the driver does not resolve the problem, contact the manufacturer of the device or of the laptop for troubleshooting steps or to make the company aware of the problem so a new driver may be developed.
  2. Again, pointing to your network wireless adapter. Re-install and/or update the driver to the newest version. If you already have the newest version, re-install in case the current driver is corrupted.

Also, what antivirus are you running? Have you had another antivirus on the system that was originally installed? How did you remove it? Antivirus/firewall software can cause network adapter drivers to behave erratically, so this information would be helpful.
My System SpecsSystem Spec