Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD when turning off counter strike global offensive

30 Apr 2015   #1

Windows 7 Ultimate x64
BSOD when turning off counter strike global offensive

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.

My System SpecsSystem Spec
02 May 2015   #2

Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10

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                                    *
*                                                                             *
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.
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
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
fffff960`006d6d15 399f50070000    cmp     dword ptr [rdi+750h],ebx
PROCESS_NAME:  dwm.exe
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
fffff960`006d6d15 399f50070000    cmp     dword ptr [rdi+750h],ebx ds:00000000`00000750=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002ef7024 to fffff80002e76700
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
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: memory_corruption
IMAGE_NAME:  memory_corruption
FOLLOWUP_NAME:  memory_corruption
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.
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
My System SpecsSystem Spec

 BSOD when turning off counter strike global offensive

Thread Tools

Similar help and support threads
Thread Forum
BSOD playing Counter Strike: Global Offensive
It doesn't happen all the time, but sometimes when I am playing, my computer will randomly start struggling to play the game. It has happened maybe 6 times but my computer recovers without getting a BSOD and I can play normally for the rest of the day. Today, it wasn't able to recover and I got a...
BSOD Help and Support
BSOD playing Counter Strike Global Offensive Error 116
Hi there, for the past week and more, my computer has experienced BSOD's when playing CSGO, it can happen at random times, I can play for hours with no issues, or 15 minutes into playing I'll crash and always with the error code 0x00000116 which I know has to do with video. I've updated my GPU...
BSOD Help and Support
BSOD playing Counter-Strike: Global Offensive
Interals: Intel Core i5-4670K 3.4GHz Quad-Core Processor Asus Z87-A ATX LGA1150 Motherboard G.Skill Ripjaws X Series 8GB (1 x 8GB) DDR3-1600 Memory GeFore 8800 GTS 512 MB This is a brand new custom build. Its only a few days old now and I just recently started playing CS:GO on it....
BSOD Help and Support
BSOD just after exiting Counter Strike Global Offensive
How do I go about fixing this issue?
BSOD Help and Support
BSOD playing Counter Strike:Global Offensive
Hello Seven Forums, I've never had BSOD (Bad Pool Call) problems until I began playing Counter Strike:Global Offensive. BSOD occurs whenever I play the game for anywhere between 5-20 minutes (sometimes a little longer). All fans are working properly and no temps are higher than normal. I also...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 00:33.
Twitter Facebook Google+