Now it is different one.
Uninstall the display driver using DDU. Then install it again. See how it goes.
(Because it may be caused by an improper installation of the display driver. I guess you updated the driver directly).
_________________________________________
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff8800f16ae53, fffff88008a39750, 0}
Probably caused by : atikmdag.sys ( atikmdag+99e53 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8800f16ae53, Address of the instruction which caused the bugcheck
Arg3: fffff88008a39750, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
atikmdag+99e53
fffff880`0f16ae53 48395810 cmp qword ptr [rax+10h],rbx
CONTEXT: fffff88008a39750 -- (.cxr 0xfffff88008a39750;r)
rax=0000000000000001 rbx=fffffa8000000000 rcx=38f3591c51f40000
rdx=000000000000008f rsi=0000000000000002 rdi=fffffa800d910894
rip=fffff8800f16ae53 rsp=fffff88008a3a130 rbp=0000000000000000
r8=000000000000004e r9=0000000000000000 r10=0000000000000000
r11=fffff88008a3a070 r12=fffff8800f2d8768 r13=0000000000000010
r14=fffff88008a3a950 r15=fffff8800f2d8518
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
atikmdag+0x99e53:
fffff880`0f16ae53 48395810 cmp qword ptr [rax+10h],rbx ds:002b:00000000`00000011=????????????????
Last set context:
rax=0000000000000001 rbx=fffffa8000000000 rcx=38f3591c51f40000
rdx=000000000000008f rsi=0000000000000002 rdi=fffffa800d910894
rip=fffff8800f16ae53 rsp=fffff88008a3a130 rbp=0000000000000000
r8=000000000000004e r9=0000000000000000 r10=0000000000000000
r11=fffff88008a3a070 r12=fffff8800f2d8768 r13=0000000000000010
r14=fffff88008a3a950 r15=fffff8800f2d8518
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
atikmdag+0x99e53:
fffff880`0f16ae53 48395810 cmp qword ptr [rax+10h],rbx ds:002b:00000000`00000011=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: CCC.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8800f16ae53
STACK_TEXT:
fffff880`08a3a130 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x99e53
FOLLOWUP_IP:
atikmdag+99e53
fffff880`0f16ae53 48395810 cmp qword ptr [rax+10h],rbx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: atikmdag+99e53
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53508a3c
STACK_COMMAND: .cxr 0xfffff88008a39750 ; kb
FAILURE_BUCKET_ID: X64_0x3B_atikmdag+99e53
BUCKET_ID: X64_0x3B_atikmdag+99e53
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x3b_atikmdag+99e53
FAILURE_ID_HASH: {206680b8-57f0-a1ea-2da9-767bbc84f557}
Followup: MachineOwner
---------
1: kd> lmvm atikmdag
start end module name
fffff880`0f0d1000 fffff880`0ffe1000 atikmdag T (no symbols)
Loaded symbol image file: atikmdag.sys
Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
Image name: atikmdag.sys
Timestamp: Fri Apr 18 07:43:16 2014 (53508A3C)
CheckSum: 00EAEEE6
ImageSize: 00F10000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4