BSOD after few mins of gaming

Ok mate some odd dumps and I would suggest running these first after reseating abd cleaning the sticks and slots

https://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

https://www.sevenforums.com/tutorials/433-disk-check.html< if necessary include the /f and /r in the command line as per Option2 (insafe mode)



if no go then

http://www.superantispyware.com/

http://www.malwarebytes.org/products/malwarebytes_free/

http://www.bleepingcomputer.com/download/adwcleaner/

ADW download frombleeping computer delete any rubbish found with the malware scans

(NB If one is runningKaspersky security it may rant about ADW - just ignore it or disable Kasperskywhile the ADW is being used)


SLOT CLEANING

Now as for the slots toclean them use a strip of old credit card (or any card thin enough some arebetter than others ) about 1/2 inch wide nip the corners off one end - preferably round them offhold a piece of thin lint free cloth over theend dab on some form of alcohol - isopropyl alcohol (what we swab the skin withbefore an injection) is good and GENTLYswipe along the slots.

This can also be done for the GPU slot/s andalso the contacts of the sticks or cards - not the stick but some lint freecloth of course. See my pic for the sick but please be very gentle doing it ifyou are in any doubt - please ask before doing it but I use this all the timeand have yet to damage anything

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Code:

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff96000233490, Address of the instruction which caused the bugcheck
Arg3: fffff88003c64b60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.
FAULTING_IP: 
win32k!GreSetDwmSoftwareCursorIntersectionDevice+0
fffff960`00233490 fff3            push    rbx
CONTEXT:  fffff88003c64b60 -- (.cxr 0xfffff88003c64b60;r)
rax=fffff900c01f7010 rbx=0000000000000000 rcx=fffff900c010a010
rdx=fffffa80092cc950 rsi=fffff900c0119010 rdi=fffff900c010a010
rip=fffff96000233490 rsp=fffff88003c65538 rbp=fffff900c072d1a8
 r8=0000000000000004  r9=fffff9600030f848 r10=fffff900c0854030
r11=fffff900c2534680 r12=0000000000000000 r13=00000000000001ba
r14=0000000000000002 r15=000000000000019a
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
win32k!GreSetDwmSoftwareCursorIntersectionDevice:
fffff960`00233490 fff3            push    rbx
Last set context:
rax=fffff900c01f7010 rbx=0000000000000000 rcx=fffff900c010a010
rdx=fffffa80092cc950 rsi=fffff900c0119010 rdi=fffff900c010a010
rip=fffff96000233490 rsp=fffff88003c65538 rbp=fffff900c072d1a8
 r8=0000000000000004  r9=fffff9600030f848 r10=fffff900c0854030
r11=fffff900c2534680 r12=0000000000000000 r13=00000000000001ba
r14=0000000000000002 r15=000000000000019a
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
win32k!GreSetDwmSoftwareCursorIntersectionDevice:
fffff960`00233490 fff3            push    rbx
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff96000233490
STACK_TEXT:  
fffff880`03c65538 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!GreSetDwmSoftwareCursorIntersectionDevice

FOLLOWUP_IP: 
win32k!GreSetDwmSoftwareCursorIntersectionDevice+0
fffff960`00233490 fff3            push    rbx
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  win32k!GreSetDwmSoftwareCursorIntersectionDevice+0
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: win32k
IMAGE_NAME:  win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  54163648
IMAGE_VERSION:  6.1.7600.17633
STACK_COMMAND:  .cxr 0xfffff88003c64b60 ; kb
FAILURE_BUCKET_ID:  X64_0x3B_win32k!GreSetDwmSoftwareCursorIntersectionDevice+0
BUCKET_ID:  X64_0x3B_win32k!GreSetDwmSoftwareCursorIntersectionDevice+0
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x3b_win32k!gresetdwmsoftwarecursorintersectiondevice+0
FAILURE_ID_HASH:  {6f9975a7-9fb5-617d-62fc-469008e56574}
Followup: MachineOwner
---------

Well done ! it was really a simple fix eh> for a change