*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80076caa10, fffff80000b9a3d8, fffffa800ae9dbd0}
Probably caused by : pci.sys
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80076c5a10, fffff80000b9a3d8, fffffa800b060960}
Probably caused by : pci.sys
Followup: MachineOwner
Why do you need to use a tool? I've given you the support page with all the drivers available. Also using apps to find drivers is a lazy way to update your machine and invariably they get it wrong anyway.Also can you suggest any tool to scan and update drivers, preferably free one..
This could be why your seeing issues. These types of driver must be updated using only the driver supplied by the manufacturer. GPU drivers are the only exception to this rule.atheros from qualcom site
This is probably why your seeing a bsod.and atheros from qualcom site..
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80076dda10, fffff80000b9a3d8, fffffa800918f4a0}
Probably caused by : pci.sys
Followup: MachineOwner
---------
0: kd> !analyze -v;r;kv;lmtsmn;.bugcheck;!peb;!sysinfo cpuinfo;!sysinfo machineid; !sysinfo cpuspeed; !sysinfo smbios
*******************************************************************************
* *
* 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: fffffa80076dda10, Physical Device Object of the stack
Arg3: fffff80000b9a3d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa800918f4a0, The blocked IRP
FAILURE_ID_HASH_STRING: km:x64_0x9f_3_power_down_athrx_image_pci.sys