Random BSODs on Relative's laptop

RaidenRaccoon · 11 May 2015

A family member's laptop keeps BSOD-ing on them at random. The DMP before the most recent crash I was able to look at myself with the Debugging Tools for Windows. But the only thing I was able to read was: 'Probably caused by: ntkrnlmp.exe'

That was before I got DM Log to collect everything else from this last crash.
The laptop is running Windows 7 Home Premium x64, with a 1.7GHz i5 (3317U I think) and 6GB DDR3 RAM and is mainly used for web browsing and creating text documents.

I recently ran a monthly malware check up on the laptop in between these last 2 crashes. Pretty sure an infection can be ruled out.

SGT Oddball · 12 May 2015

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8004eb5a10, Physical Device Object of the stack
Arg3: fffff800044743d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa8005211c60, The blocked IRP
Debugging Details:
------------------

DRVPOWERSTATE_SUBCODE:  3
IMAGE_NAME:  pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f
MODULE_NAME: pci
FAULTING_MODULE: fffff88000e00000 pci
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
CURRENT_IRQL:  2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
DPC_STACK_BASE:  FFFFF8000447AFB0
STACK_TEXT:  
fffff800`04474388 fffff800`02f30b92 : 00000000`0000009f 00000000`00000003 fffffa80`04eb5a10 fffff800`044743d8 : nt!KeBugCheckEx
fffff800`04474390 fffff800`02ecbcfc : fffff800`044744c0 fffff800`044744c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`04474430 fffff800`02ecbb96 : fffffa80`05153168 fffffa80`05153168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`044744a0 fffff800`02ecba7e : 0000000f`b4ab58fd fffff800`04474b18 00000000`00069915 fffff800`0303f528 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04474af0 fffff800`02ecb867 : 00000002`9a075fc3 00000002`00069915 00000002`9a075fa5 00000000`00000015 : nt!KiTimerExpiration+0x1be
fffff800`04474b90 fffff800`02eb7bca : fffff800`0303ce80 fffff800`0304acc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04474c40 00000000`00000000 : fffff800`04475000 fffff800`0446f000 fffff800`04474c00 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
IMAGE_VERSION:  6.1.7601.17514
FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_athrx_IMAGE_pci.sys
BUCKET_ID:  X64_0x9F_3_POWER_DOWN_athrx_IMAGE_pci.sys
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_power_down_athrx_image_pci.sys
FAILURE_ID_HASH:  {63286d57-77cf-1e15-b72d-d3aa435fb827}
Followup: MachineOwner
---------

It's looking like Atheros network adapter driver - Driver Reference Table - athrx.sys

The installed version is very old, see if you can find a newer one.

RaidenRaccoon · 24 May 2015

Updated the driver via Windows Update several days ago.

The laptop had another crash 2 days ago. The BSOD stated 'DRIVER_POWER_STATE_FAILURE'