Windows 7: Random BSOD after playing games

BlckThrn · 16 Dec 2009

this always happens to me when I close or exit a game. the last game I played was CoD MW2 and it suddenly happened...sigh...

Please help! I attached the dump and some screenshots of bluescreenview

Very much appreciated!

TimStitt · 16 Dec 2009

Hi BlckThrn,

Sometimes when games are installed, they can overwrite windows files.

I think this is what has happened to you. The cdd.dll driver is the Canonical Display Driver in windows. Grab the original from your installation disk and replace.

EDIT: Windows Installation disk.. not the game

BlckThrn · 16 Dec 2009

Quote: Originally Posted by TimStitt

Hi BlckThrn,

Sometimes when games are installed, they can overwrite windows files.

I think this is what has happened to you. The cdd.dll driver is the Canonical Display Driver in windows. Grab the original from your installation disk and replace.

EDIT: Windows Installation disk.. not the game

Ok thanks I'll try that. But is that the only reason?

Thanks again!

BTW how can I get the .dll file from the installation disk? the file itself isn't there...

TimStitt · 16 Dec 2009

"But is that the only reason?" - probably not

. It could also be corrupted; however I think this is the most likely. You may also consider running an 'sfc /scannow' from an elevated CMD prompt to check all windows system files.

I have the 64bit version so my cdd.dll may be different to yours, mine is the 6.1.7600.16385 version. I'd be curious to know what version you are running and what version other 32bit users have.

BlckThrn · 16 Dec 2009

Quote: Originally Posted by TimStitt

"But is that the only reason?" - probably not

. It could also be corrupted; however I think this is the most likely. You may also consider running an 'sfc /scannow' from an elevated CMD prompt to check all windows system files.

I have the 64bit version so my cdd.dll may be different to yours, mine is the 6.1.7600.16385 version. I'd be curious to know what version you are running and what version other 32bit users have.

sfc /scannow didn't find anything wrong

I have the same version of cdd.dll but only in a 32-bit version of Windows 7.

I'll try the replacing the old cdd.dll by the original one on the installation disk but I don't know how to grab it from there. Any help on this?

zigzag3143 · 16 Dec 2009

Quote: Originally Posted by BlckThrn

this always happens to me when I close or exit a game. the last game I played was CoD MW2 and it suddenly happened...sigh...

Please help! I attached the dump and some screenshots of bluescreenview

Very much appreciated!

Hi and welcome

this crash was probably caused by CDD.sys the dvd/cd driver. I woukd

update the druver
run a system file check
type cmd in search>right click and run as admin>sfc /scannow

if you are overclocking stop
if running a raid update its dtiver

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\121609-17812-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 = 0x82c49000 PsLoadedModuleList = 0x82d88570
Debug session time: Wed Dec 16 04:46:53.052 2009 (GMT-5)
System Uptime: 0 days 3:22:24.896
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 82cfc2ca, 92efca94, 0}

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

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

1: 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: 82cfc2ca, The address that the exception occurred at
Arg3: 92efca94, 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
82cfc2ca f00fba3000      lock btr dword ptr [eax],0

TRAP_FRAME:  92efca94 -- (.trap 0xffffffff92efca94)
ErrCode = 00000002
eax=00000000 ebx=8cb5507e ecx=00000000 edx=00000001 esi=00000000 edi=87dbfb30
eip=82cfc2ca esp=92efcb08 ebp=92efcb28 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:
82cfc2ca 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:  iw4sp.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 96b772c9 to 82cfc2ca

STACK_TEXT:  
92efcb0c 96b772c9 fdccbd78 96b7a8d4 fdccbd78 nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x1a
92efcb14 96b7a8d4 fdccbd78 00000000 00000000 cdd!CGuardMutex::Enter+0xd
92efcb28 96b7b7c7 0043bfef fdccbd78 ffac7008 cdd!CddBitmap::RemoveFromCddBitmapList+0x28
92efcb5c 96b71753 fdccbd78 92efcbfc 969ad304 cdd!CddBitmapHw::Release+0x7d
92efcb68 969ad304 fdccbd78 00000002 92efcc20 cdd!DrvDeleteDeviceBitmapEx+0x39
92efcbfc 969ae718 00000001 00000000 2e051929 win32k!SURFACE::bDeleteSurface+0x235
92efcc10 969b0c0f 00000001 00000001 ffac7008 win32k!SURFREF::bDeleteSurface+0x14
92efcc24 969b03af 00000ca8 00000001 00000ca8 win32k!vCleanupSurfaces+0x43
92efcc44 969ac052 fdf33258 00000000 00000000 win32k!NtGdiCloseProcess+0xc5
92efcc64 969ae937 fdf33258 00000000 88122330 win32k!GdiProcessCallout+0x151
92efcc80 82e5a00a 859caa48 00000000 ba97a40f win32k!W32pProcessCallout+0x5d
92efccfc 82e61c63 00000000 ffffffff 000ce51c nt!PspExitThread+0x46d
92efcd24 82c7e79a ffffffff 00000000 000ce528 nt!NtTerminateProcess+0x1fa
92efcd24 771364f4 ffffffff 00000000 000ce528 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
000ce528 00000000 00000000 00000000 00000000 0x771364f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cdd!CGuardMutex::Enter+d
96b772c9 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
---------

TimStitt · 16 Dec 2009

The version numbers are the same, that's interesting. Lets hope it's corrupt and replacing it fixes your issue.

Also did you try running the game in compatibility mode for XP?

I'll get back to you shortly with the location of the driver on the Windows 7 disk. I just have to find it myself

BlckThrn · 16 Dec 2009

Quote: Originally Posted by TimStitt

The version numbers are the same, that's interesting. Lets hope it's corrupt and replacing it fixes your issue.

Also did you try running the game in compatibility mode for XP?

I'll get back to you shortly with the location of the driver on the Windows 7 disk. I just have to find it myself

yeah I hope so too.

I tried almost everything...
...compatibilities to driver updates and such

TimStitt · 16 Dec 2009

It looks like this version of the driver came with KB974431, I have downloaded this MSU in x86 and extracted the driver for you, see attached.

BSOD's are commonly caused by faulty RAM and faulty drivers. We are looking at one driver issue now, this driver is the one shown in the dump file posted above. It's also possible that another driver on your system is causing this to crash. So perhaps checking the websites of your hardware manufacturers and updating nay available is also good policy. Lastly, run it in compatibility mode.

EDIT: I forgot to zip the attachment, you should see it now.

TimStitt · 16 Dec 2009

As an after thought. Try it with Aero disabled. Aero wasn't around when the game came out (I think)

Here's how http://www.howtogeek.com/howto/windo...-a-video-game/

Windows 7: Random BSOD after playing games

Random BSOD after playing games problems?