New
#11
It is likely due to your NETGEAR WG111v3 Wireless-G USB Adapter; Wireless USB is a very finicky method to get wireless internet. If you are having trouble shutting down with it plugged in, try removing it before shutting down and see if it resolves the problem.Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:\Kingston\BSODDmpFiles\coreysbrodylan\Windows_NT6_BSOD_jcgriff2\020412-20623-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c3c0? 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 Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03009000 PsLoadedModuleList = 0xfffff800`0324e670 Debug session time: Sat Feb 4 14:16:58.555 2012 (GMT-7) System Uptime: 0 days 0:19:26.382 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list ........... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, fffffa8008899050, fffff80000b9c3d8, fffffa800a084c60} Probably caused by : usbehci.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: fffffa8008899050, Physical Device Object of the stack Arg3: fffff80000b9c3d8, Functional Device Object of the stack Arg4: fffffa800a084c60, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: fffffa800a084c60 DEVICE_OBJECT: fffffa8008899050 DRIVER_OBJECT: fffffa80087e18b0 IMAGE_NAME: usbehci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c00 MODULE_NAME: usbehci FAULTING_MODULE: fffff880045bb000 usbehci CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff800030f3cd2 to fffff80003085c40 STACK_TEXT: fffff800`00b9c388 fffff800`030f3cd2 : 00000000`0000009f 00000000`00000003 fffffa80`08899050 fffff800`00b9c3d8 : nt!KeBugCheckEx fffff800`00b9c390 fffff800`030915fc : fffff800`00b9c610 fffff800`00b9c610 00000000`00000000 00000000`0000000a : nt! ?? ::FNODOBFM::`string'+0x34a90 fffff800`00b9c430 fffff800`03091496 : fffff880`017985b0 00000000`000123e3 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c fffff800`00b9c4a0 fffff800`0309137e : 00000002`b6cf24c4 fffff800`00b9cb18 00000000`000123e3 fffff800`031ffee8 : nt!KiProcessExpiredTimerList+0xc6 fffff800`00b9caf0 fffff800`03091167 : fffff800`031fbed8 fffffa80`000123e3 fffffa80`08829a30 00000000`000000e3 : nt!KiTimerExpiration+0x1be fffff800`00b9cb90 fffff800`0307d96a : fffff800`031fbe80 fffff800`03209cc0 00000000`00000000 fffff880`04402db0 : nt!KiRetireDpcList+0x277 fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_IMAGE_usbehci.sys BUCKET_ID: X64_0x9F_IMAGE_usbehci.sys Followup: MachineOwner ---------