I seem to have an issue that appears definitely related to WSAM. If I connect to WSAM and my PC goes to sleep due to inactivity the PC then does a BSOD. The PC is a Toshiba R930 laptop and to prove the point I installed a separate HD and did a factory restore to default. I then tested through setting the PC timeout to 1 minute in the following sequence.
1. Boot
2. Login
3. Go to sleep
4. Wake PC
5. login to WSAM
6. Go to sleep
7. Wait for upto 30 min at an unresponsive black screen for the final BSOD
This i also then repeated after updating all the drivers on the PC to the very latest version. Same results.
I also tried using the wireless and wired network interfaces as the windbg seems to think its related to the network interface. I think however its probably the TDI driver with WSAM thats causing the crash.
Unfortunately the BSOD has corrupted my main drive a couple of times now resulting in significant waste of time reinstallling backup images.
I've attached the output of windbg. If anyone has any other suggestions I'd be grateful for the insight. I've also lodged this as a bug with my company who will lodge it as a case for Juniper.
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`0325f000 PsLoadedModuleList = 0xfffff800`0349ce50
Debug session time: Sun Apr 19 07:07:31.848 2015 (UTC + 10:00)
System Uptime: 0 days 9:12:07.785
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`fffdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa800ca32a20, fffff80000ba2748, fffffa8012f4a8a0}
*** ERROR: Symbol file could not be found. Defaulted to export symbols for win32k.sys -
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: fffffa800ca32a20, Physical Device Object of the stack
Arg3: fffff80000ba2748, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa8012f4a8a0, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ad98dc1
MODULE_NAME: pci
FAULTING_MODULE: fffff88000e13000 pci
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: mscorsvw.exe
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
DPC_STACK_BASE: FFFFF80000BA2FB0
STACK_TEXT:
fffff800`00ba26f8 fffff800`0333e1b3 : 00000000`0000009f 00000000`00000003 fffffa80`0ca32a20 fffff800`00ba2748 : nt!KeBugCheckEx
fffff800`00ba2700 fffff800`032db6a6 : fffff800`00ba2830 fffff800`00ba2830 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
fffff800`00ba27a0 fffff800`032daa26 : fffffa80`10a5e270 00000000`0020672a 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00ba2810 fffff800`032db57e : 0000004d`21b2df7e fffff800`00ba2e88 00000000`0020672a fffff800`0344c7c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00ba2e60 fffff800`032dad97 : fffffa80`100102c2 fffff800`0020672a 00000000`00000000 00000000`00000029 : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`032d5765 : 00000000`00000000 fffffa80`0d8c5b60 00000000`00000000 fffff880`018bdc50 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`032d557c : 00000000`0000085c fffff800`03220895 fffff800`03245460 fffff880`02fb4c60 : nt!KxRetireDpcList+0x5
fffff880`02fb4ba0 fffff800`0331ab13 : fffff800`032cbb20 fffff800`032cbb8c fffffa80`0d8c5b60 00000000`0000012c : nt!KiDispatchInterruptContinue
fffff880`02fb4bd0 fffff800`032cbb8c : fffffa80`0d8c5b60 00000000`0000012c fffff880`02fb4bb8 fffffa80`0d811a50 : nt!KiDpcInterruptBypass+0x13
fffff880`02fb4be0 00000000`6ddce2f7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x1fc
00000000`0042bf44 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6ddce2f7
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 6.1.7600.20551
FAILURE_BUCKET_ID: X64_0x9F_3_POWER_DOWN_e1c62x64_IMAGE_pci.sys
BUCKET_ID: X64_0x9F_3_POWER_DOWN_e1c62x64_IMAGE_pci.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x9f_3_power_down_e1c62x64_image_pci.sys
FAILURE_ID_HASH: {1663ca0d-5f22-0abf-dc14-18870713acfc}
Followup: MachineOwner
---------
0: kd> !irp fffffa8012f4a8a0
Irp is active with 4 stacks 3 is current (= 0xfffffa8012f4aa00)
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
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
>[ 16, 2] 0 e1 fffffa80100e6050 00000000 fffff8000351af60-fffffa801308ff20 Success Error Cancel pending
*** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
\Driver\e1cexpress nt!PopSystemIrpCompletion
Args: 00014400 00000000 00000004 00000002
[ 0, 0] 0 0 00000000 00000000 00000000-fffffa801308ff20
Args: 00000000 00000000 00000000 00000000
Thanks
