New
#1
Laptop BSOD
Ok, hopefully I"ve fixed the my desktop bsods...now for the laptop...
I've attached all relevant files...
Thanks in advance...
nucemgd
Ok, hopefully I"ve fixed the my desktop bsods...now for the laptop...
I've attached all relevant files...
Thanks in advance...
nucemgd
Your wifi driver. Probably caused by : athrx.sys. RE-install the newest version available
Ken J
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\111410-16832-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`03ea94c0? Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols *http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02c4e000 PsLoadedModuleList = 0xfffff800`02e8be50 Debug session time: Sun Nov 14 11:27:52.646 2010 (GMT-5) System Uptime: 0 days 2:54:38.472 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, fffffa8003c91060, fffff80003ea94d8, fffffa8003e8ac60} *** WARNING: Unable to verify timestamp for athrx.sys *** ERROR: Module load completed but symbols could not be loaded for athrx.sys Probably caused by : athrx.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: fffffa8003c91060, Physical Device Object of the stack Arg3: fffff80003ea94d8, Functional Device Object of the stack Arg4: fffffa8003e8ac60, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: fffffa8003e8ac60 DEVICE_OBJECT: fffffa8005e8b050 DRIVER_OBJECT: fffffa8005f02bf0 IMAGE_NAME: athrx.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4aca1ff5 MODULE_NAME: athrx FAULTING_MODULE: fffff88004810000 athrx CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002d2d273 to fffff80002cbe740 STACK_TEXT: fffff800`03ea9488 fffff800`02d2d273 : 00000000`0000009f 00000000`00000003 fffffa80`03c91060 fffff800`03ea94d8 : nt!KeBugCheckEx fffff800`03ea9490 fffff800`02cca29e : fffff800`03ea95c0 fffff800`03ea95c0 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0 fffff800`03ea9530 fffff800`02cc9dd6 : fffff800`02e6e700 00000000`000a3fcc 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66 fffff800`03ea95a0 fffff800`02cca4be : 00000018`65a8073f fffff800`03ea9c18 00000000`000a3fcc fffff800`02e3cc08 : nt!KiProcessExpiredTimerList+0xc6 fffff800`03ea9bf0 fffff800`02cc9cb7 : 00000004`fdb8abc1 00000004`000a3fcc 00000004`fdb8abeb 00000000`000000cc : nt!KiTimerExpiration+0x1be fffff800`03ea9c90 fffff800`02cc6eea : fffff800`02e38e80 fffff800`02e46c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277 fffff800`03ea9d40 00000000`00000000 : fffff800`03eaa000 fffff800`03ea4000 fffff800`03ea9d00 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_IMAGE_athrx.sys BUCKET_ID: X64_0x9F_IMAGE_athrx.sys Followup: MachineOwner ---------