Bluescreens when gaming

[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.

Haven't installed any new hardware since I bought it, two years ago.

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_I 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_COMMAN .cxr 0xfffff88007d480d0 ; kb

FAILURE_BUCKET_I X64_0x3B_win32k!TimersProc+142

BUCKET_I X64_0x3B_win32k!TimersProc+142

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


Moved from PC Gaming

Anandtech Moderator
KeithTalent

 

[Zenoth]

If your hardware (any) is over-clocked then try running your system under default factory frequencies and voltages, at least as part of the elimination process of the potential causes of your issues. If everything was already running under default settings (hardware-wise, not the game) then try tempering with the graphics drivers options in the control panel (be it for NVIDIA or AMD's control panel). First, run under default control panel settings, and see if it helps. Then try to "force" a few configurations that you think might help. If not then, perhaps try to simply uninstall and re-install the game, since it could be a corrupted file (we never know).

There's a number of possibilities. I for one unfortunately can't really understand the technicalities behind that crash log you posted, perhaps an engineer behind Windows' coding or the game's coding could read it properly. If it's not related to the hardware, or the graphics drivers, or anything directly related to running the game itself outside of the main Windows files then I don't really know what to suggest beyond perhaps checking for hard-drive's sectors integrity (check disk) but I bet that by itself would be quite irrelevant.

 

[ShawnD1]

Update your motherboard and video drivers. My computer was doing all kinds of random crashing crap until I downloaded drivers from the website. The ones that came on the CD were total garbage!

With that out of the way, reset your mobo to stock settings for the sake of testing.

Now that your drivers are up to date and everything is running stock, run the OCCT power supply test.
http://www.ocbase.com/perestroika_en/index.php?Download

If it crashes during the PSU test, get back to us and we'll try to figure out which piece of hardware is busted. If it doesn't crash, then see if the game still crashes and get back to us.

-if it can pass the CPU test and it can pass the GPU test, but fails the PSU test, it means the PSU is broken
-failing the GPU test by itself could mean the GPU is broken
-failing the CPU test could mean the CPU or the RAM is broken, depending on how it crashes. blue screen is often memory error. black screen crash and reset is often CPU error.

It can be a lot of things.

 

[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?

 

[Xonim]

The stock fan on an i7 920 should be fine - mine idles around 33C, 48ish under full load (stock hs/f with AS5 paste), and there's plenty of reports of people reaching 3.2GHz+ with stock cooling. If you have some AS5 paste handy, I'd start with that and see if that fixes the problem. Give it a few days to set, hopefully that's the problem.

If it doesn't, then you have AS5 for when you try a different cooler. Whether or not the heat is the cause of the bsod's, I couldn't tell you, but you definitely want to bring that temp down regardless.

I'd also get a voltage monitoring program and see if it fluctuates a lot. I had a PSU that was causing tons of bsod's right before it died. The voltage was anything but stable, which, I'm assuming, is what was causing the crashes.

Good luck!

 

[ShawnD1]

I'd also get a voltage monitoring program and see if it fluctuates a lot. I had a PSU that was causing tons of bsod's right before it died. The voltage was anything but stable, which, I'm assuming, is what was causing the crashes.

Good luck!

OCCT has a built in one, and it shows the report after every kind of stress test.

Same thing happened to me. Running the PSU test would have crazy voltage fluctuations. Sometimes it shows a CPU spike from 1.4V to maybe 3V. Sometimes the 12V graph drops to about 5V. It's not really a mystery why the thing would crash when it's doing stuff like that.

In the OCCT voltage graphs, the thing to look at on the top is the voltage ripple, expressed as a percent.

 

[ParadoxDenmark]

Just applied thermal paste to the CPU. Temperature has dropped 30 degrees Celcius, and it can now pass the test.

Will try run it awhile with this, and see if it works. Otherwise, I'll check on the voltage, like suggested.

I'll report back regardless, of course, since someone else might be experiencing the same issues.

 

[ParadoxDenmark]

Having tested it for a few days, it seems like the bluescreens were caused by the CPU getting too hot. Haven't had any issues since I applied the thermal grease.