BSOD when turning off counter strike global offensive

[wixxen2012]

HELP! bluescreen happens when i turn off counter strike global offensive. i remembered that there was written cdd.dll. I used SF Diagnostic Tool and this is files which it had made.

 

[ICIT2LOL]

Hello and welcome wixxen mate that is a lot of dump files and there is one that caufght my notice - a memory issue

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff900c391a770, 0, fffff960006d6d15, 0}
*** WARNING: Unable to verify checksum for cdd.dll
Could not read faulting driver name
Probably caused by : memory_corruption
Followup: memory_corruption
---------
5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff900c391a770, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960006d6d15, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
 
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ae0e0
GetUlongFromAddress: unable to read from fffff800030ae198
 fffff900c391a770 
FAULTING_IP: 
cdd!DrvAssociateSharedSurface+51
fffff960`006d6d15 399f50070000    cmp     dword ptr [rdi+750h],ebx
MM_INTERNAL_CODE:  0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x50
PROCESS_NAME:  dwm.exe
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
TRAP_FRAME:  fffff880056ae920 -- (.trap 0xfffff880056ae920)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff960006d6cc4 rbx=0000000000000000 rcx=fffff900c24ddce8
rdx=0000000040002dc0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960006d6d15 rsp=fffff880056aeab0 rbp=fffff900c24ddce8
 r8=fffffffff5121998  r9=0000000000000040 r10=0000000003a7f600
r11=fffff880056aeb08 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cdd!DrvAssociateSharedSurface+0x51:
fffff960`006d6d15 399f50070000    cmp     dword ptr [rdi+750h],ebx ds:00000000`00000750=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002ef7024 to fffff80002e76700
STACK_TEXT:  
fffff880`056ae7b8 fffff800`02ef7024 : 00000000`00000050 fffff900`c391a770 00000000`00000000 fffff880`056ae920 : nt!KeBugCheckEx
fffff880`056ae7c0 fffff800`02e747ee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x427f7
fffff880`056ae920 fffff960`006d6d15 : 00000000`00000734 00000000`00000000 ffffffff`f5121912 00000000`00000020 : nt!KiPageFault+0x16e
fffff880`056aeab0 fffff960`00265e6d : 00000000`00000000 fffff900`c1e64f30 00000000`03a7f6a0 00000040`00000280 : cdd!DrvAssociateSharedSurface+0x51
fffff880`056aeb10 fffff960`002892d9 : 00000000`00000001 fffff880`056aec60 00000000`03a7f6a0 00000000`00007f6f : win32k!GreSetRedirectionSurfaceSignaling+0x125
fffff880`056aeb60 fffff800`02e75953 : fffffa80`0b987b60 fffffa80`0b987140 fffffa80`0b9b47b0 fffffa80`00000000 : win32k!NtGdiHLSurfSetInformation+0x209
fffff880`056aebe0 000007fe`fdb64efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03a7f5d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fdb64efa
 
STACK_COMMAND:  kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !cdd
    fffff960006d6009-fffff960006d600a  2 bytes - cdd!PresentWorkerThread+c9d
 [ 6d 9e:cd 9c ]
    fffff960006d62f0-fffff960006d62f1  2 bytes - cdd!PresentWorkerThread+f84 (+0x2e7)
 [ 3c 9b:9c 99 ]
    fffff960006d6a60-fffff960006d6a61  2 bytes - cdd!TriggerGdiModeReset+30 (+0x770)
 [ bc 94:1c 93 ]
    fffff960006d6ad6-fffff960006d6ad7  2 bytes - cdd!TriggerGdiModeReset+a6 (+0x76)
 [ 30 94:90 92 ]
    fffff960006d6b1e-fffff960006d6b1f  2 bytes - cdd!TriggerGdiModeReset+ee (+0x48)
 [ 0e 93:6e 91 ]
10 errors : !cdd (fffff960006d6009-fffff960006d6b1f)
MODULE_NAME: [COLOR=red]memory_corruption[/COLOR]
IMAGE_NAME:  [COLOR=red]memory_corruption[/COLOR]
FOLLOWUP_NAME:  [COLOR=red]memory_corruption[/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP:  0
MEMORY_CORRUPTOR:  LARGE
FAILURE_BUCKET_ID:  [COLOR=red]X64_MEMORY_CORRUPTION_LARGE[/COLOR]
BUCKET_ID:  X64_[COLOR=red]MEMORY_CORRUPTION_LARGE[/COLOR]
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_memory_corruption_large
FAILURE_ID_HASH:  {6332b0e4-cf0e-2392-6ba8-f96ca91b7f36}
Followup: memory_corruption
---------

So I reckon you should run the memtest and make sure it is for at least 8 PASSES!! - no less

It takes a long time to do but I think you should start there.
MEMTEST
The memtest you will need to make a bootable disk / stick and set the BIOS to boot from the optical (disk) or USB and it will take a fair time to run- some leave it overnight..
But one thing is very important you must let the test run for at least 8 passes any less and the findings are no good. Now if errors come up straight away then you can stop it - see my pics. Now if there are errors and you have more than one stick of RAM in then you will need to test each stick ie remove the sticks and replace stick 1 in slot 1 and test no errors do the same in slot 2 with stick 1 no errors then repeat the process with stick 2 - that will show up the faulty stick - the other thing is it could be a faulty slot but most unusual.
It is a very lengthy and tedious process but worth it if you have errors.
Memtest86+ - Advanced Memory Diagnostic Tool