Could use some help understanding this dump analysis

[ParadoxDenmark]

Heya,

I've been getting bluescreens while playing games these last couple of days. Did a clean driver sweep, and reinstalled fresh drivers for my devices.

Didn't work, though, so I figured out how to open the .dmp files Windows create when it bluescreens, just can't make much sense of it.

Hope someone here can point me in the right direction. Thanks.

This is the latest. Happened 30 minutes ago:

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960000e304e, Address of the instruction which caused the bugcheck
Arg3: fffff88007d480d0, 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:
win32k!TimersProc+142
fffff960`000e304e 488910 mov qword ptr [rax],rdx

CONTEXT: fffff88007d480d0 -- (.cxr 0xfffff88007d480d0)
rax=000000000301050e rbx=fffff900c221bc10 rcx=fffff900c2524628
rdx=fffff900c221bc70 rsi=000000007fffffff rdi=fffff900c221bc28
rip=fffff960000e304e rsp=fffff88007d48aa0 rbp=000000000000000f
r8=fffffa800909cbb8 r9=0000000000000000 r10=fffffffffffffffb
r11=0000000000000000 r12=0000000000000000 r13=fffff960003022c0
r14=0000000000000002 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
win32k!TimersProc+0x142:
fffff960`000e304e 488910 mov qword ptr [rax],rdx ds:002b:00000000`0301050e=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff960000e3a84 to fffff960000e304e

STACK_TEXT:
fffff880`07d48aa0 fffff960`000e3a84 : 00000000`00000000 fffff960`00302a90 00000000`00000004 00000000`00000001 : win32k!TimersProc+0x142
fffff880`07d48af0 fffff960`000745ec : fffffa80`0000007b 00000000`0000000f fffff880`00000001 ffffffff`8000038c : win32k!RawInputThread+0x9b4
fffff880`07d48bc0 fffff960`000f429a : fffffa80`00000002 fffff880`07d2df40 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x58
fffff880`07d48bf0 fffff800`03879953 : fffffa80`09093060 00000000`00000004 000007ff`fffd3000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffff880`07d48c20 000007fe`fd213d5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01dff858 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd213d5a


FOLLOWUP_IP:
win32k!TimersProc+142
fffff960`000e304e 488910 mov qword ptr [rax],rdx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!TimersProc+142

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4de066b5

STACK_COMMAND: .cxr 0xfffff88007d480d0 ; kb

FAILURE_BUCKET_ID: X64_0x3B_win32k!TimersProc+142

BUCKET_ID: X64_0x3B_win32k!TimersProc+142

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

 

[dphantom]

bad RAM? have you added or changed RAM lately?

 

[ParadoxDenmark]

Nope. Haven't changed any hardware since I bought it (2 years ago) and never had a bluescreen until about a week ago, when it happened the first time.

 

[pandemonium]

Nope. Haven't changed any hardware since I bought it (2 years ago) and never had a bluescreen until about a week ago, when it happened the first time.

On that note, have you cleaned the cake out? Creeping blue screens are a good indicator of hardware failure resulting from overheating (especially if you're gaming). Clean fans, PCB, heatsinks, etc on CPU and GPU and see if that helps.

 

[ParadoxDenmark]

Thanks for the replies.

I've updated all drivers and cleaned out all fans for dust.

Everything has always been running at default speed, since I bought it.

Installed and ran all the OCCT tests. The CPU test told me the CPU was getting too hit (at 90 degrees. It's an I7 920)

Ain't really any thermal grease left, either, and it's just the cooler that came with it.

Guess next step is fixing that. Maybe get a new cooler for it?