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 closing games

25 Jan 2010   #1

Windows 7 Ultimate x86
 
 
BSOD when closing games

Hi! I had this problem about a month ago and I thought it was solved

I last played Dragon Age: Origins but when I close it (not only this particular game) when the desktop shows up I got a BSOD

The last problem was the cdd.dll and i replaced it with an uncorrupted one. But now it's at it again

Please analyze my dump for me if there are more problems than just this driver

thanks!

BTW thanks TimStitt for last time!
yeah it happened again

My System SpecsSystem Spec
.

25 Jan 2010   #2

Win 8 Release candidate 8400
 
 

[QUOTE=BlckThrn;528456]Hi! I had this problem a few months ago and I thought it was solved

I last played Dragon Age: Origins but when I close it (not only this particular game) when the desktop shows up I got a BSOD

The last problem was the cdd.dll and i replaced it with an uncorrupted one. But now it's at it again

Please analyze my dump for me if there are more problems than just this driver

thanks![/QUO

Hi and welcome

This crash was caused by cdd.dll.
I would
run a system file check.
type cmd in search>right click and run as admin>sfc /scannow
If you are overclocking STOP.


Ken J+


Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\012510-16140-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x83040000 PsLoadedModuleList = 0x8317f570
Debug session time: Mon Jan 25 09:05:35.969 2010 (GMT-5)
System Uptime: 0 days 6:24:53.766
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 830f32ca, b9c35a94, 0}

Probably caused by : cdd.dll ( cdd!CGuardMutex::Enter+d )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 830f32ca, The address that the exception occurred at
Arg3: b9c35a94, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+1a
830f32ca f00fba3000      lock btr dword ptr [eax],0

TRAP_FRAME:  b9c35a94 -- (.trap 0xffffffffb9c35a94)
ErrCode = 00000002
eax=00000000 ebx=8cf5d07e ecx=00000000 edx=00000001 esi=00000000 edi=85924940
eip=830f32ca esp=b9c35b08 ebp=b9c35b28 iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x1a:
830f32ca f00fba3000      lock btr dword ptr [eax],0   ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  daorigins.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 96c372c9 to 830f32ca

STACK_TEXT:  
b9c35b0c 96c372c9 fda14498 96c3a8d4 fda14498 nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x1a
b9c35b14 96c3a8d4 fda14498 00000000 00000000 cdd!CGuardMutex::Enter+0xd
b9c35b28 96c3b7c7 0043bfef fda14498 fd5e36e8 cdd!CddBitmap::RemoveFromCddBitmapList+0x28
b9c35b5c 96c31753 fda14498 b9c35bfc 96e6d304 cdd!CddBitmapHw::Release+0x7d
b9c35b68 96e6d304 fda14498 00000002 b9c35c20 cdd!DrvDeleteDeviceBitmapEx+0x39
b9c35bfc 96e6e718 00000001 00000000 8905144d win32k!SURFACE::bDeleteSurface+0x235
b9c35c10 96e70c0f 00000001 00000001 fd5e36e8 win32k!SURFREF::bDeleteSurface+0x14
b9c35c24 96e703af 0000073c 00000001 0000073c win32k!vCleanupSurfaces+0x43
b9c35c44 96e6c052 fe69eba8 00000000 00000000 win32k!NtGdiCloseProcess+0xc5
b9c35c64 96e6e937 fe69eba8 00000000 886003f0 win32k!GdiProcessCallout+0x151
b9c35c80 8325100a 85e43420 00000000 91b41496 win32k!W32pProcessCallout+0x5d
b9c35cfc 83258c63 00000000 ffffffff 0012fe90 nt!PspExitThread+0x46d
b9c35d24 8307579a ffffffff 00000000 0012fe9c nt!NtTerminateProcess+0x1fa
b9c35d24 77b864f4 ffffffff 00000000 0012fe9c nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012fe9c 00000000 00000000 00000000 00000000 0x77b864f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cdd!CGuardMutex::Enter+d
96c372c9 c7460401000000  mov     dword ptr [esi+4],1

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  cdd!CGuardMutex::Enter+d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cdd

IMAGE_NAME:  cdd.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bd992

FAILURE_BUCKET_ID:  0x8E_cdd!CGuardMutex::Enter+d

BUCKET_ID:  0x8E_cdd!CGuardMutex::Enter+d

Followup: MachineOwner
---------
My System SpecsSystem Spec
25 Jan 2010   #3

Windows 7 Ultimate x86
 
 

thanks for that

The results say they didn't find any integrity violations

any particular drivers I need to update? as far as i know all of 'em are up to date
My System SpecsSystem Spec
.


Reply

 BSOD when closing games





Thread Tools




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 09:18 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33