I just bought my laptop for a few days and now I get this BSOD. When I use BlueScreenView to analyze the minidump, it shows that it's because of the ntoskrnl.exe. But the WinDbg shows the reason is cdd.dll. This happened when I just quit the game CoD4. So now, I'm very thankful if some one clear it out for me :) . The attached file is here:
Your iw3sp.exe caused these. That is the COD4 crack. You need to un-install it. As we cant support cracked software we would need a log showing its removal
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\012811-18392-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols *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.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02a67000 PsLoadedModuleList = 0xfffff800`02ca4e50 Debug session time: Thu Jan 27 12:24:50.045 2011 (GMT-5) System Uptime: 0 days 7:19:00.372 Loading Kernel Symbols ............................................................... ................................................................ .................................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff900c1c807a0, 0, fffff960006ddc51, 0} 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: fffff900c1c807a0, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff960006ddc51, 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 fffff80002d0f0e0 fffff900c1c807a0 FAULTING_IP: cdd!CddBitmapHw::Release+31 fffff960`006ddc51 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: iw3sp.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff8800db7b6b0 -- (.trap 0xfffff8800db7b6b0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff900c1c80020 rbx=0000000000000000 rcx=fffff900c1c5f900 rdx=fffffa8003fbd410 rsi=0000000000000000 rdi=0000000000000000 rip=fffff960006ddc51 rsp=fffff8800db7b840 rbp=0000000000000001 r8=0000000000000000 r9=0000000000000000 r10=00000000000042cf r11=fffff8800db7b860 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cdd!CddBitmapHw::Release+0x31: fffff960`006ddc51 483b9080070000 cmp rdx,qword ptr [rax+780h] ds:0e5c:fffff900`c1c807a0=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002b57f14 to fffff80002ad7740 STACK_TEXT: fffff880`0db7b548 fffff800`02b57f14 : 00000000`00000050 fffff900`c1c807a0 00000000`00000000 fffff880`0db7b6b0 : nt!KeBugCheckEx fffff880`0db7b550 fffff800`02ad582e : 00000000`00000000 fffff900`c00bf010 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42837 fffff880`0db7b6b0 fffff960`006ddc51 : 00000000`00000000 00000e5c`00000000 00001645`00000000 00000000`00000001 : nt!KiPageFault+0x16e fffff880`0db7b840 fffff960`000e5360 : 00000000`00000001 fffff900`c00bf010 00000000`00000001 fffff900`c1f21690 : cdd!CddBitmapHw::Release+0x31 fffff880`0db7b880 fffff960`000ed65d : 00000000`00000000 00000000`00000001 fffff900`c1f21690 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x358 fffff880`0db7b9d0 fffff960`000e4c00 : 00000000`00000e5c 00000000`00000000 fffff900`c1e67ce0 fffff960`00000000 : win32k!NtGdiCloseProcess+0x2c9 fffff880`0db7ba30 fffff960`000e4337 : fffffa80`07f18e00 00000000`00000001 fffffa80`03fbd410 00000000`00000000 : win32k!GdiProcessCallout+0x200 fffff880`0db7bab0 fffff800`02dbca01 : fffffa80`07f18e60 00000000`00000000 00000000`00000000 fffffa80`03fbd410 : win32k!W32pProcessCallout+0x6b fffff880`0db7bae0 fffff800`02d9485b : 00000000`00000000 00000000`00000001 fffffa80`0426c900 00000000`00000000 : nt!PspExitThread+0x561 fffff880`0db7bba0 fffff800`02ad6993 : fffffa80`0426c9f0 00000000`00000000 00000000`7efdb001 fffffa80`03fbd410 : nt!NtTerminateProcess+0x25b fffff880`0db7bc20 00000000`77a5017a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0008e308 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a5017a STACK_COMMAND: kb FOLLOWUP_IP: cdd!CddBitmapHw::Release+31 fffff960`006ddc51 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: 4bf4408a FAILURE_BUCKET_ID: X64_0x50_cdd!CddBitmapHw::Release+31 BUCKET_ID: X64_0x50_cdd!CddBitmapHw::Release+31 Followup: MachineOwner ---------
Quote