Hello there,
The dump files were very vague. So we have to run couple of test. Run a Hardware Diagnostic (RAM, Hard drive and GPU)
http://captaindbg.com/hardware-diagnostic/
Reinstall your Display drivers as well. What security software are you using?
Remove Duplex Driver (
sptd.sys Mon Oct 12 02:25:14 2009)
It's notorious for crashes on Windows 7. Follow this article and uninstall it
http://www.duplexsecure.com/faq
Update the following drivers:
Code:
000.fcl Fri Sep 26 18:41:22 2008
Bugcheck:
Code:
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002e89a56, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880098ca030, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt!KiCommitThreadWait+296
fffff800`02e89a56 f0480fba2b00 lock bts qword ptr [rbx],0
CONTEXT: fffff880098ca030 -- (.cxr 0xfffff880098ca030)
rax=0000000000008000 rbx=55e8746c66446144 rcx=00000000000000e9
rdx=00000000000007ff rsi=fffffa800c185120 rdi=0000000000000000
rip=fffff80002e89a56 rsp=fffff880098caa00 rbp=0000000000000000
r8=fffff80002e12000 r9=0000000000000000 r10=0000000000000001
r11=fffffa8006cc79c0 r12=0000000000000000 r13=0000000000000000
r14=55e8746c66444224 r15=00000000000000e9
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt!KiCommitThreadWait+0x296:
fffff800`02e89a56 f0480fba2b00 lock bts qword ptr [rbx],0 ds:002b:55e8746c`66446144=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002e8bd0f to fffff80002e89a56
STACK_TEXT:
fffff880`098caa00 fffff800`02e8bd0f : 00000000`00000000 80000000`00000001 00000000`000000e9 80000000`00000001 : nt!KiCommitThreadWait+0x296
fffff880`098caa90 fffff880`048db5b3 : fffffa80`0c185000 fffffa80`00000006 fffff880`098cac00 00000000`00000700 : nt!KeWaitForSingleObject+0x19f
fffff880`098cab30 fffff960`001be47e : 00000000`746c6644 fffff880`00000000 00000000`00000000 00000000`000007ea : dxgkrnl!DxgkWaitForVerticalBlankEvent+0x53f
fffff880`098cabf0 fffff800`02e81953 : fffffa80`0c185060 fffffa80`0c165bb0 000007fe`00000000 fffffa80`0c165bb0 : win32k!NtGdiDdDDIWaitForVerticalBlankEvent+0x12
fffff880`098cac20 000007fe`feda138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`027bfad8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`feda138a
FOLLOWUP_IP:
dxgkrnl!DxgkWaitForVerticalBlankEvent+53f
fffff880`048db5b3 f04183842428130000ff lock add dword ptr [r12+1328h],0FFFFFFFFh
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgkrnl!DxgkWaitForVerticalBlankEvent+53f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d3fa1a0
STACK_COMMAND: .cxr 0xfffff880098ca030 ; kb
FAILURE_BUCKET_ID: X64_0x3B_dxgkrnl!DxgkWaitForVerticalBlankEvent+53f
BUCKET_ID: X64_0x3B_dxgkrnl!DxgkWaitForVerticalBlankEvent+53f
Followup: MachineOwner
---------
Hope this helps,
Captain
Microsoft MVP