BSODing lately...

[hadesflames]

I set important computer specs and what not in my profile. If it's required for me to post it here, please ask what you need and I'll send it. Attached are the last three minidumps available in the minidump directory. I BSODed 3 times today alone, they weren't in the minidump directory unfortunately.

EDIT:

I was literally just watching a video (matroska video) on wmp as it happened. I wouldn't blame codecs so much, as the same codecs work just fine on my desktop, and the other two times, they happened as I was simply browsing the web or chatting on my IM client. (basically, it happens whenever the computer wants to piss me off)

 

[hadesflames]

Has anyone had a look?

 

[Capt.Jack Sparrow]

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:

000.fcl      Fri Sep 26 18:41:22 2008

Bugcheck:

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

 

[hadesflames]

The hardware passes all tests, that driver is removed.

I've attached the latest one (minutes ago) hopefully it's a bit specific.

 

[Capt.Jack Sparrow]

Hello there,

I believe you have ran the Prime95 test and MemTest86+ 7 to 8 passes. If that's done lets enable Driver Verifier follow this tutorial to enable it.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

The latest dump file didn't have any information in it. I created a little tool to find more information about your computer. Follow this link http://captaindbg.com/sf-diagnostic-tool-v4/ run all the options and upload the files here.

Bugcheck:

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff880209b5d50, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ed7402, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800031030e0
 fffff880209b5d50 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerExpiration+f2
fffff800`02ed7402 48894808        mov     qword ptr [rax+8],rcx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880009fcaa0 -- (.trap 0xfffff880009fcaa0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880209b5d48 rbx=0000000000000000 rcx=fffff880009b5d48
rdx=00000000000000be rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ed7402 rsp=fffff880009fcc30 rbp=00000000001265be
 r8=fffffa800bdcac20  r9=00000000000000c0 r10=00000000000000be
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe cy
nt!KiTimerExpiration+0xf2:
fffff800`02ed7402 48894808        mov     qword ptr [rax+8],rcx ds:fffff880`209b5d50=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ecac69 to fffff80002ecb700

STACK_TEXT:  
fffff880`009fc958 fffff800`02ecac69 : 00000000`0000000a fffff880`209b5d50 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`009fc960 fffff800`02ec98e0 : 0000002b`c0e01111 0000002b`cb020e7d fffff880`009b2180 fffff880`009b5500 : nt!KiBugCheckDispatch+0x69
fffff880`009fcaa0 fffff800`02ed7402 : 00000000`00006e7b 00000000`0000837f 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`009fcc30 fffff800`02ed6cc7 : 00000007`f6d45ec0 00000007`001265be 00000007`f6d45ebe 00000000`000000be : nt!KiTimerExpiration+0xf2
fffff880`009fccd0 fffff800`02ed3eea : fffff880`009b2180 fffff880`009bd0c0 00000000`00000001 fffff800`00000000 : nt!KiRetireDpcList+0x277
fffff880`009fcd80 00000000`00000000 : fffff880`009fd000 fffff880`009f7000 fffff880`009fcd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTimerExpiration+f2
fffff800`02ed7402 48894808        mov     qword ptr [rax+8],rcx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiTimerExpiration+f2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd34

FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+f2

BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+f2

Followup: MachineOwner
---------

Hope this helps,
Captain

 

[hadesflames]

Here you go:

http://envisionportal.net/sf.zip