We have SCCM 2012 R2 and Dell. Using the latest combo drivers on Dell, imaging Win7 x86/x64.
I've been seeing BSOD on shutdown on almost all desktops/laptops. They don't BSOD every time, maybe 20-30% of the time on 5-10% of all desktops/laptops.
Dump is below.
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\katiecc\Downloads\e7440_111214-8330-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`0305f000 PsLoadedModuleList = 0xfffff800`032a2890
Debug session time: Wed Nov 12 13:49:33.070 2014 (UTC - 8:00)
System Uptime: 0 days 0:07:08.907
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88000ec6cce, fffff8800a993308, fffff8800a992b60}
*** WARNING: Unable to verify timestamp for TeeDriverx64.sys
*** ERROR: Module load completed but symbols could not be loaded for TeeDriverx64.sys
Probably caused by : TeeDriverx64.sys ( TeeDriverx64+fc0d )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88000ec6cce, The address that the exception occurred at
Arg3: fffff8800a993308, Exception Record Address
Arg4: fffff8800a992b60, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
Wdf01000!FxIoQueue::CancelForQueue+252
fffff880`00ec6cce 4c897038 mov qword ptr [rax+38h],r14
EXCEPTION_RECORD: fffff8800a993308 -- (.exr 0xfffff8800a993308)
ExceptionAddress: fffff88000ec6cce (Wdf01000!FxIoQueue::CancelForQueue+0x0000000000000252)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000038
Attempt to write to address 0000000000000038
CONTEXT: fffff8800a992b60 -- (.cxr 0xfffff8800a992b60;r)
rax=0000000000000000 rbx=fffffa800cb2de50 rcx=fffffa80109c1500
rdx=0000000075657500 rsi=0000000000000000 rdi=fffffa80109c14a0
rip=fffff88000ec6cce rsp=fffff8800a993540 rbp=fffffa8010a59d30
r8=0000000000001000 r9=fffff88000e45160 r10=000000000000000c
r11=0000000000000000 r12=fffff88000edad40 r13=0000000000000301
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
Wdf01000!FxIoQueue::CancelForQueue+0x252:
fffff880`00ec6cce 4c897038 mov qword ptr [rax+38h],r14 ds:002b:00000000`00000038=????????????????
Last set context:
rax=0000000000000000 rbx=fffffa800cb2de50 rcx=fffffa80109c1500
rdx=0000000075657500 rsi=0000000000000000 rdi=fffffa80109c14a0
rip=fffff88000ec6cce rsp=fffff8800a993540 rbp=fffffa8010a59d30
r8=0000000000001000 r9=fffff88000e45160 r10=000000000000000c
r11=0000000000000000 r12=fffff88000edad40 r13=0000000000000301
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
Wdf01000!FxIoQueue::CancelForQueue+0x252:
fffff880`00ec6cce 4c897038 mov qword ptr [rax+38h],r14 ds:002b:00000000`00000038=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 0000000000000038
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330c100
GetUlongFromAddress: unable to read from fffff8000330c1c0
0000000000000038 Nonpaged pool
FOLLOWUP_IP:
TeeDriverx64+fc0d
fffff880`05117c0d ?? ???
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff88000ec665b to fffff88000ec6cce
STACK_TEXT:
fffff880`0a993540 fffff880`00ec665b : fffffa80`109c14a0 fffff880`0a993600 00000000`00000000 fffffa80`109c14a0 : Wdf01000!FxIoQueue::CancelForQueue+0x252
fffff880`0a9935b0 fffff880`00eb33d3 : 00000000`00000000 fffffa80`109c14a0 0000057f`ef63eb58 00000000`00001003 : Wdf01000!FxIoQueue::QueuePurge+0x28f
fffff880`0a993630 fffff880`05117c0d : fffffa80`109c14a0 fffffa80`109912d0 fffff880`0511c028 fffff880`0511c028 : Wdf01000!imp_WdfIoQueuePurge+0x10b
fffff880`0a993690 fffffa80`109c14a0 : fffffa80`109912d0 fffff880`0511c028 fffff880`0511c028 fffffa80`109901e0 : TeeDriverx64+0xfc0d
fffff880`0a993698 fffffa80`109912d0 : fffff880`0511c028 fffff880`0511c028 fffffa80`109901e0 fffff880`00e64e1a : 0xfffffa80`109c14a0
fffff880`0a9936a0 fffff880`0511c028 : fffff880`0511c028 fffffa80`109901e0 fffff880`00e64e1a fffffa80`109912d0 : 0xfffffa80`109912d0
fffff880`0a9936a8 fffff880`0511c028 : fffffa80`109901e0 fffff880`00e64e1a fffffa80`109912d0 fffff880`0510f0d8 : TeeDriverx64+0x14028
fffff880`0a9936b0 fffffa80`109901e0 : fffff880`00e64e1a fffffa80`109912d0 fffff880`0510f0d8 fffffa80`109912d0 : TeeDriverx64+0x14028
fffff880`0a9936b8 fffff880`00e64e1a : fffffa80`109912d0 fffff880`0510f0d8 fffffa80`109912d0 00000000`00000000 : 0xfffffa80`109901e0
fffff880`0a9936c0 fffff880`00e58288 : fffffa80`109901e0 00000000`00000000 00000000`00000005 fffff880`0a9937d8 : Wdf01000!FxPkgPnp::NotifyResourceObjectsDx+0x4a
fffff880`0a993730 fffff880`00e64e99 : 00000000`00000000 fffff880`0a9938b0 fffff880`00edb200 fffffa80`109901e0 : Wdf01000!FxPkgPnp::PowerGotoDxIoStopped+0x120
fffff880`0a993780 fffff880`00e5b0f8 : 00000000`0000031c fffff880`0a9938b0 00000000`ffff7fff fffffa80`109901e0 : Wdf01000!FxPkgPnp::PowerGotoDNotZeroIoStopped+0x9
fffff880`0a9937b0 fffff880`00e5ada6 : fffff880`00edb1c0 fffffa80`10990398 fffffa80`109901e0 fffffa80`109901e0 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1d8
fffff880`0a993910 fffff880`00e5b627 : 00000000`00000000 fffff880`0a9939f0 fffffa80`10990380 fffffa80`109901e0 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
fffff880`0a993980 fffff880`00e65dd3 : 00000000`00000000 fffffa80`109901e0 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1b3
fffff880`0a993a20 fffff880`00e476f2 : 00000000`00000002 0000057f`ef66efd8 fffffa80`109a8bb0 fffffa80`12b46402 : Wdf01000!FxPkgFdo::DispatchDeviceSetPower+0x117
fffff880`0a993a70 fffff880`00e4679a : fffffa80`12b46410 fffffa80`12b46410 fffffa80`12b46410 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x2aa
fffff880`0a993ad0 fffff880`00e46866 : fffffa80`12b46410 00000000`00000000 fffffa80`109a8bb0 fffffa80`109a8bb0 : Wdf01000!FxDevice::Dispatch+0x19a
fffff880`0a993b10 fffff800`031f0eb5 : 00000000`00000001 00000000`00000000 fffffa80`109a8bb0 fffffa80`12b464b8 : Wdf01000!FxDevice::DispatchWithLock+0xa6
fffff880`0a993b50 fffff800`0337073a : ffffffff`fa0a1f00 fffffa80`1235ab50 00000000`00000080 fffff8a0`00000002 : nt!PopIrpWorker+0x3c5
fffff880`0a993c00 fffff800`030c58e6 : fffff800`0324fe80 fffffa80`1235ab50 fffffa80`13004b50 fffffa80`13b9f010 : nt!PspSystemThreadStartup+0x5a
fffff880`0a993c40 00000000`00000000 : fffff880`0a994000 fffff880`0a98e000 fffff880`0a9932e0 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: TeeDriverx64+fc0d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: TeeDriverx64
IMAGE_NAME: TeeDriverx64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 51d31e10
STACK_COMMAND: .cxr 0xfffff8800a992b60 ; kb
FAILURE_BUCKET_ID: X64_0x7E_TeeDriverx64+fc0d
BUCKET_ID: X64_0x7E_TeeDriverx64+fc0d
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x7e_teedriverx64+fc0d
FAILURE_ID_HASH: {c079e5d7-83f0-230c-5936-8e6123aa32cd}
Followup: MachineOwner
---------