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 while exiting Steam app DotA2 ( cdd.dll )

01 Feb 2012   #1
nihihi

Windows 7 Ultimate x64
 
 
BSOD while exiting Steam app DotA2 ( cdd.dll )

Hello guys,

I've encountered this issue just now and want to make sure it is not anything too serious, there is not much to say save for the fact that as soon as I hit exit to desktop the BS appeared.

I'm running a custom made PC with the following Specs :

CPU : AMD Phenom II X4 960T Black Edition 3.0GHz box
HDD : Samsung 1 TB SATA-II 7200RPM 32MB rpm Spinpoint F3
RAM : KingMax Nano Gaming RAM 4GB DDR3 1600MHz ( dual channel, hand set on 1333 mhz to avoid perf. issues )
VIDEO :Gigabyte GeForce GTX 460 SE 1GB DDR5 256-bit

My power supply unit is a very competent Corsair series unit, so I do not believe that would be an issue. I've attached the performance monitor report along with your Utility tool report.

The operating system is a Windows 7 Ultimate on 64 bits, and the entire hardware is fairly new ( <2 months old ).

Thank you for your time.


My System SpecsSystem Spec
.
01 Feb 2012   #2
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Could not read faulting driver name Probably caused by : win32k.sys ( win32k+27c69d ) Followup: MachineOwner --------- Loading Dump File [F:\BSODDmpFiles\nihihi\Seven Forums\020112-18673-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`0305b000 PsLoadedModuleList = 0xfffff800`03298e50 Debug session time: Wed Feb 1 11:14:18.945 2012 (GMT-7) System Uptime: 0 days 4:34:16.365 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff900c2b607a0, 0, fffff9600070dc51, 0} Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Could not read faulting driver name Probably caused by : cdd.dll ( cdd!CddBitmapHw::Release+31 ) Followup: MachineOwner --------- 0: 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: fffff900c2b607a0, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff9600070dc51, 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 fffff800033030e0 fffff900c2b607a0 FAULTING_IP: cdd!CddBitmapHw::Release+31 fffff960`0070dc51 483b9080070000 cmp rdx,qword ptr [rax+780h] MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: hl.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff88008fcf6a0 -- (.trap 0xfffff88008fcf6a0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff900c2b60020 rbx=0000000000000000 rcx=fffff900c313cd30 rdx=fffffa800934d060 rsi=0000000000000000 rdi=0000000000000000 rip=fffff9600070dc51 rsp=fffff88008fcf830 rbp=0000000000000001 r8=0000000000000000 r9=0000000000000000 r10=0000000000001662 r11=fffff88008fcf850 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cdd!CddBitmapHw::Release+0x31: fffff960`0070dc51 483b9080070000 cmp rdx,qword ptr [rax+780h] ds:0001:fffff900`c2b607a0=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000314c1e4 to fffff800030ccf00 STACK_TEXT: fffff880`08fcf538 fffff800`0314c1e4 : 00000000`00000050 fffff900`c2b607a0 00000000`00000000 fffff880`08fcf6a0 : nt!KeBugCheckEx fffff880`08fcf540 fffff800`030cafee : 00000000`00000000 fffff900`c00bf010 fffff800`00000000 fffffa80`096a9b60 : nt! ?? ::FNODOBFM::`string'+0x42907 fffff880`08fcf6a0 fffff960`0070dc51 : 00000000`00000000 00001304`00000000 00000776`00000000 00000000`00000001 : nt!KiPageFault+0x16e fffff880`08fcf830 fffff960`00165080 : 00000000`00000001 fffff900`c00bf010 00000000`00000001 fffff900`c2169690 : cdd!CddBitmapHw::Release+0x31 fffff880`08fcf870 00000000`00000001 : fffff900`c00bf010 00000000`00000001 fffff900`c2169690 00000000`00000005 : win32k+0xc5080 fffff880`08fcf878 fffff900`c00bf010 : 00000000`00000001 fffff900`c2169690 00000000`00000005 00000000`00000000 : 0x1 fffff880`08fcf880 00000000`00000001 : fffff900`c2169690 00000000`00000005 00000000`00000000 00000000`00000000 : 0xfffff900`c00bf010 fffff880`08fcf888 fffff900`c2169690 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1 fffff880`08fcf890 00000000`00000005 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff900`c2169690 fffff880`08fcf898 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5 STACK_COMMAND: kb FOLLOWUP_IP: cdd!CddBitmapHw::Release+31 fffff960`0070dc51 483b9080070000 cmp rdx,qword ptr [rax+780h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: cdd!CddBitmapHw::Release+31 FOLLOWUP_NAME: MachineOwner MODULE_NAME: cdd IMAGE_NAME: cdd.dll DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bde94 FAILURE_BUCKET_ID: X64_0x50_cdd!CddBitmapHw::Release+31 BUCKET_ID: X64_0x50_cdd!CddBitmapHw::Release+31 Followup: MachineOwner ---------
  2. Loading Dump File [F:\BSODDmpFiles\nihihi\Seven Forums\012612-17316-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`03050000 PsLoadedModuleList = 0xfffff800`0328de50 Debug session time: Wed Jan 25 11:40:32.687 2012 (GMT-7) System Uptime: 0 days 4:12:13.123 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff900c25836b0, 0, fffff960002cc69d, 0} Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Could not read faulting driver name Probably caused by : win32k.sys ( win32k+27c69d ) Followup: MachineOwner --------- 2: 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: fffff900c25836b0, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff960002cc69d, 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 fffff800032f80e0 fffff900c25836b0 FAULTING_IP: win32k+27c69d fffff960`002cc69d 488b4f20 mov rcx,qword ptr [rdi+20h] MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: dwm.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff88008b0c920 -- (.trap 0xfffff88008b0c920) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000011 rbx=0000000000000000 rcx=fffff900c38a99f0 rdx=0000000002120045 rsi=0000000000000000 rdi=0000000000000000 rip=fffff960002cc69d rsp=fffff88008b0cab0 rbp=0000000000000001 r8=0000000000000000 r9=0000000000000410 r10=fffff80003050000 r11=000000000000001e r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc win32k+0x27c69d: fffff960`002cc69d 488b4f20 mov rcx,qword ptr [rdi+20h] ds:99f0:00000000`00000020=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800031411e4 to fffff800030c1f00 STACK_TEXT: fffff880`08b0c7b8 fffff800`031411e4 : 00000000`00000050 fffff900`c25836b0 00000000`00000000 fffff880`08b0c920 : nt!KeBugCheckEx fffff880`08b0c7c0 fffff800`030bffee : 00000000`00000000 fffff900`c38a99f0 fffffa80`35616c00 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x42907 fffff880`08b0c920 fffff960`002cc69d : 00000000`0000001b 00000000`02120045 00000000`02120045 00000000`00000001 : nt!KiPageFault+0x16e fffff880`08b0cab0 00000000`0000001b : 00000000`02120045 00000000`02120045 00000000`00000001 00000000`02120045 : win32k+0x27c69d fffff880`08b0cab8 00000000`02120045 : 00000000`02120045 00000000`00000001 00000000`02120045 fffff960`002cbbae : 0x1b fffff880`08b0cac0 00000000`02120045 : 00000000`00000001 00000000`02120045 fffff960`002cbbae fffff900`c38a99f0 : 0x2120045 fffff880`08b0cac8 00000000`00000001 : 00000000`02120045 fffff960`002cbbae fffff900`c38a99f0 00000000`00000000 : 0x2120045 fffff880`08b0cad0 00000000`02120045 : fffff960`002cbbae fffff900`c38a99f0 00000000`00000000 00000045`624d4653 : 0x1 fffff880`08b0cad8 fffff960`002cbbae : fffff900`c38a99f0 00000000`00000000 00000045`624d4653 00000000`0000001d : 0x2120045 fffff880`08b0cae0 fffff900`c38a99f0 : 00000000`00000000 00000045`624d4653 00000000`0000001d 00000000`00000001 : win32k+0x27bbae fffff880`08b0cae8 00000000`00000000 : 00000045`624d4653 00000000`0000001d 00000000`00000001 00000000`054ceee0 : 0xfffff900`c38a99f0 STACK_COMMAND: kb FOLLOWUP_IP: win32k+27c69d fffff960`002cc69d 488b4f20 mov rcx,qword ptr [rdi+20h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: win32k+27c69d FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc5e1 FAILURE_BUCKET_ID: X64_0x50_win32k+27c69d BUCKET_ID: X64_0x50_win32k+27c69d Followup: MachineOwner ---------
  1. Fairly inconclusive. Possible causes are Memory problems... Graphics card memory problems... CMOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...
  2. Also inconclusive. Same possible causes as 1.

Thanks to Dave76 for help understanding possible causes.



We will start with the most likely problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.
My System SpecsSystem Spec
Reply

 BSOD while exiting Steam app DotA2 ( cdd.dll )




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD's While Exiting Game, Exiting Chrome
I have recently gotten three BSODs, one was from exiting to desktop from Far Cry 3, (the 3/12 10:26 pm) the other was when the computer was afk and not being used (3/13 6:36 PM) and 3/13 10:26pm from exiting Google Chrome. Dump file uploaded. Please help, I really need to get rid of this, :l I...
BSOD Help and Support
BSOD playing Dota2
BSODs only happen during Dota2. I haven't played many other games I don't know if its computer games that cause the BSOD or just Dota2.
BSOD Help and Support
BSOD playing dota2
Hello. I had a few random BSOD playing this game and i had it one just one moment ago. The last BSOD before this one was almost 1 month ago probably. Files attached. Thanks!
BSOD Help and Support
BSOD while playing ME3 and DOTA2
Thanks for your time. To start off i have no idea what is causing the crashes. My only guess is that my computer is overheating but when i check the temp its usually at 56-57. i have run malwarebytes and M Security essentials anti virus and both have said that there is nothing
BSOD Help and Support
BSOD starting Grand theft auto IV as non steam game in steam.
I get a bsod when starting GTA 4, i think its something to do with avast however. Please help finding what is causeing the bsod. Zipped Files attached. Computer build is about a month old. Thanks.
BSOD Help and Support
explorer.exe crashes when exiting Steam games
This is what everything was like before this happened.. C drive on SATA0 Steam drive on SATA1 Now, I got a new hard drive, so C is on SATA0 New drive is on SATA1 Steam drive is on SATA2
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 07:47.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App