BlueScreen 6.1.7601.2.1.0.768.3 Problem

Additional information is required.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

I've just had a look through your recent crashes and your Broadcom network adapter is looking the most likely culprit for your crashes - Driver Reference Table - bcmwl664.sys

Try finding a newer/alternative driver for it.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80069e2a10, fffff80000b9a3d8, fffffa800a162780}
Probably caused by : pci.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffffa80069e2a10, 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: fffffa800a162780, 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:  FFFFF80000BA0FB0
STACK_TEXT:  
fffff800`00b9a388 fffff800`030f1b92 : 00000000`0000009f 00000000`00000003 fffffa80`069e2a10 fffff800`00b9a3d8 : nt!KeBugCheckEx
fffff800`00b9a390 fffff800`0308ccfc : fffff800`00b9a4f0 fffff800`00b9a4f0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9a430 fffff800`0308cb96 : fffffa80`0b387248 fffffa80`0b387248 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9a4a0 fffff800`0308ca7e : 00000431`233e9d95 fffff800`00b9ab18 00000000`01c2d333 fffff800`032008e8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9aaf0 fffff800`0308c867 : 00000163`7b0e69c4 00000163`01c2d333 00000163`7b0e6941 00000000`00000032 : nt!KiTimerExpiration+0x1be
fffff800`00b9ab90 fffff800`03078bca : fffff800`031fde80 fffff800`0320bcc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9ac40 00000000`00000000 : fffff800`00b9b000 fffff800`00b95000 fffff800`00b9ac00 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_bcmwl664_IMAGE_pci.sys
BUCKET_ID:  X64_0x9F_3_POWER_DOWN_bcmwl664_IMAGE_pci.sys
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_power_down_bcmwl664_image_pci.sys
FAILURE_ID_HASH:  {03ad8a78-2fdb-fcb3-4095-637363008d10}
Followup: MachineOwner
---------

My apologies pman - I completely forgot about it, but Sgt Oddball is correct. The issue lies with the wireless Broadcom driver. An updated driver should sort the issue for you.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80073efa10, fffff80000b9a3d8, fffffa800ab36240}

Probably caused by : pci.sys

Followup: MachineOwner
---------
irp is active with 4 stacks 2 is current (= 0xfffffa800ab36358)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0  0 fffffa800a5ee050 00000000 00000000-00000000    
	      Unable to load image \SystemRoot\system32\DRIVERS\bcmwl664.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bcmwl664.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmwl664.sys
 \Driver\BCM43XX
			Args: 00015400 00000000 00000005 00000003
 [ 16, 2]   0 e1 fffffa800a4e22b0 00000000 fffff80003324210-fffffa800adac760 Success Error Cancel pending
	       \Driver\vwifibus	nt!PopSystemIrpCompletion
			Args: 00015400 00000000 00000005 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800adac760    

			Args: 00000000 00000000 00000000 00000000