my 5 month old laptop is suffering it's first bsod ,while trying out this scratches game. Here is the windbg dump output :
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\012911-17737-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Program Files\Debugging Tools for Windows (x64)*http://msdl.microsoft.com/download/symbols;srv*
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03215000 PsLoadedModuleList = 0xfffff800`03452e50
Debug session time: Sat Jan 29 01:24:32.781 2011 (UTC - 7:00)
System Uptime: 0 days 0:03:55.966
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000094, fffff96000685577, fffff88009efc778, fffff88009efbfe0}
Probably caused by : cdd.dll ( cdd!PresentWorkerThread+20b )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000094, The exception code that was not handled
Arg2: fffff96000685577, The address that the exception occurred at
Arg3: fffff88009efc778, Exception Record Address
Arg4: fffff88009efbfe0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION} Integer division by zero.
FAULTING_IP:
cdd!PresentWorkerThread+20b
fffff960`00685577 48f7f1 div rax,rcx
EXCEPTION_RECORD: fffff88009efc778 -- (.exr 0xfffff88009efc778)
ExceptionAddress: fffff96000685577 (cdd!PresentWorkerThread+0x000000000000020b)
ExceptionCode: c0000094 (Integer divide-by-zero)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffff88009efbfe0 -- (.cxr 0xfffff88009efbfe0)
rax=0000000000989680 rbx=fffffa8003de1b60 rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa8009246820 rdi=fffff900c0178020
rip=fffff96000685577 rsp=fffff88009efc9b0 rbp=0000000000000080
r8=0000000000026161 r9=fffff88009efca90 r10=0000000000000000
r11=fffffa8003de1b60 r12=0000000000000000 r13=0000000000000000
r14=0000000000000001 r15=fffff88002f67f40
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
cdd!PresentWorkerThread+0x20b:
fffff960`00685577 48f7f1 div rax,rcx
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7E
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION} Integer division by zero.
LAST_CONTROL_TRANSFER: from fffff80003529c06 to fffff96000685577
STACK_TEXT:
fffff880`09efc9b0 fffff800`03529c06 : fffff880`00000002 fffffa80`03de1b60 00000000`00000080 fffffa80`09246820 : cdd!PresentWorkerThread+0x20b
fffff880`09efcd40 fffff800`03263c26 : fffff880`02f63180 fffffa80`03de1b60 fffff880`02f6dfc0 fffff880`01416810 : nt!PspSystemThreadStartup+0x5a
fffff880`09efcd80 00000000`00000000 : fffff880`09efd000 fffff880`09ef7000 fffff880`09efcd40 00000000`00000000 : nt!KxStartSystemThread+0x16
FOLLOWUP_IP:
cdd!PresentWorkerThread+20b
fffff960`00685577 48f7f1 div rax,rcx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: cdd!PresentWorkerThread+20b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: cdd
IMAGE_NAME: cdd.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4ccf9aaa
STACK_COMMAND: .cxr 0xfffff88009efbfe0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_cdd!PresentWorkerThread+20b
BUCKET_ID: X64_0x7E_cdd!PresentWorkerThread+20b
Followup: MachineOwner
---------
Is this a cdd.dll problem or something else ? I already have the latest video driver from the manufacturer.
video card: ati mobility radeon hd5650
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\012911-17737-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Program Files\Debugging Tools for Windows (x64)*http://msdl.microsoft.com/download/symbols;srv*
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03215000 PsLoadedModuleList = 0xfffff800`03452e50
Debug session time: Sat Jan 29 01:24:32.781 2011 (UTC - 7:00)
System Uptime: 0 days 0:03:55.966
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000094, fffff96000685577, fffff88009efc778, fffff88009efbfe0}
Probably caused by : cdd.dll ( cdd!PresentWorkerThread+20b )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000094, The exception code that was not handled
Arg2: fffff96000685577, The address that the exception occurred at
Arg3: fffff88009efc778, Exception Record Address
Arg4: fffff88009efbfe0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION} Integer division by zero.
FAULTING_IP:
cdd!PresentWorkerThread+20b
fffff960`00685577 48f7f1 div rax,rcx
EXCEPTION_RECORD: fffff88009efc778 -- (.exr 0xfffff88009efc778)
ExceptionAddress: fffff96000685577 (cdd!PresentWorkerThread+0x000000000000020b)
ExceptionCode: c0000094 (Integer divide-by-zero)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffff88009efbfe0 -- (.cxr 0xfffff88009efbfe0)
rax=0000000000989680 rbx=fffffa8003de1b60 rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa8009246820 rdi=fffff900c0178020
rip=fffff96000685577 rsp=fffff88009efc9b0 rbp=0000000000000080
r8=0000000000026161 r9=fffff88009efca90 r10=0000000000000000
r11=fffffa8003de1b60 r12=0000000000000000 r13=0000000000000000
r14=0000000000000001 r15=fffff88002f67f40
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
cdd!PresentWorkerThread+0x20b:
fffff960`00685577 48f7f1 div rax,rcx
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7E
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION} Integer division by zero.
LAST_CONTROL_TRANSFER: from fffff80003529c06 to fffff96000685577
STACK_TEXT:
fffff880`09efc9b0 fffff800`03529c06 : fffff880`00000002 fffffa80`03de1b60 00000000`00000080 fffffa80`09246820 : cdd!PresentWorkerThread+0x20b
fffff880`09efcd40 fffff800`03263c26 : fffff880`02f63180 fffffa80`03de1b60 fffff880`02f6dfc0 fffff880`01416810 : nt!PspSystemThreadStartup+0x5a
fffff880`09efcd80 00000000`00000000 : fffff880`09efd000 fffff880`09ef7000 fffff880`09efcd40 00000000`00000000 : nt!KxStartSystemThread+0x16
FOLLOWUP_IP:
cdd!PresentWorkerThread+20b
fffff960`00685577 48f7f1 div rax,rcx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: cdd!PresentWorkerThread+20b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: cdd
IMAGE_NAME: cdd.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4ccf9aaa
STACK_COMMAND: .cxr 0xfffff88009efbfe0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_cdd!PresentWorkerThread+20b
BUCKET_ID: X64_0x7E_cdd!PresentWorkerThread+20b
Followup: MachineOwner
---------
Is this a cdd.dll problem or something else ? I already have the latest video driver from the manufacturer.
video card: ati mobility radeon hd5650
Last edited:
