Random bsod when just had a fresh install of windows 7 1 week ago

I have started up my pc from scrath (fresh insatll of windows7) 1 week ago, just had my 1st BSOD today. Could you help me about this and I dont know what has caused this.

Can you help me please?

Thanks,

Ryan.

Click on the button below ....



It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
Screenshots and Files - Upload and Post in Seven Forums

Your situation is essentially identical with what ArmedShadow had.

Follow my suggestion to him. Here .....

Getting a BSOD error at random points lately

Let us know the result.
______________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880110b92ec, fffff8800ae72950, 0}

Probably caused by : atikmdag.sys ( atikmdag+b12ec )

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

0: 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: fffff880110b92ec, Address of the instruction which caused the bugcheck
Arg3: fffff8800ae72950, 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+b12ec
fffff880`110b92ec 488b02          mov     rax,qword ptr [rdx]

CONTEXT:  fffff8800ae72950 -- (.cxr 0xfffff8800ae72950;r)
rax=fffff88011234620 rbx=0000000000000000 rcx=fffffa8009c69028
rdx=0000000000000000 rsi=fffff8800ae7394c rdi=fffff88011233ff0
rip=fffff880110b92ec rsp=fffff8800ae73330 rbp=fffff8800ae73461
 r8=000000004cb6ed8b  r9=0000000000000001 r10=0000000000000008
r11=0000000000000000 r12=fffffa800b422040 r13=0000000000000051
r14=0000000000000000 r15=fffffa8008f64c40
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
atikmdag+0xb12ec:
fffff880`110b92ec 488b02          mov     rax,qword ptr [rdx] ds:002b:00000000`00000000=????????????????
Last set context:
rax=fffff88011234620 rbx=0000000000000000 rcx=fffffa8009c69028
rdx=0000000000000000 rsi=fffff8800ae7394c rdi=fffff88011233ff0
rip=fffff880110b92ec rsp=fffff8800ae73330 rbp=fffff8800ae73461
 r8=000000004cb6ed8b  r9=0000000000000001 r10=0000000000000008
r11=0000000000000000 r12=fffffa800b422040 r13=0000000000000051
r14=0000000000000000 r15=fffffa8008f64c40
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
atikmdag+0xb12ec:
fffff880`110b92ec 488b02          mov     rax,qword ptr [rdx] ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880110b92ec

STACK_TEXT:  
fffff880`0ae73330 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0xb12ec


FOLLOWUP_IP: 
atikmdag+b12ec
fffff880`110b92ec 488b02          mov     rax,qword ptr [rdx]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atikmdag+b12ec

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53bd610a

STACK_COMMAND:  .cxr 0xfffff8800ae72950 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+b12ec

BUCKET_ID:  X64_0x3B_atikmdag+b12ec

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x3b_atikmdag+b12ec

FAILURE_ID_HASH:  {953e808a-0919-1ac0-1e92-05cd8644bf08}

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

0: kd> lmvm atikmdag
start             end                 module name
fffff880`11008000 fffff880`11fb1000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Wed Jul 09 21:04:34 2014 (53BD610A)
    CheckSum:         00F46306
    ImageSize:        00FA9000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Good news.

Let us know for any further issue.