BSOD Occuring Daily

[ShamrockRig]

Hi there, ive been getting blue screens daily, usually i would look through the files and sort it myself but i simple dont have the time to read through log after log. Cheers
Devlin

 

[Arc]

Hi mate, it appears that you are using a RC version of the display driver. Let us see the situation with a stable WHQL installed?

Uninstall your installed version of the display driver.

• How-To Uninstall AMD Catalyst Drivers From A Windows Based System

Then clean up any possible leftover.

• http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html

Then install version 14.9 WHQL only.

• Download AMD Catalyst 14.9 WHQL Driver

Now let us know for any further BSOD.
____________________________________

.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8800f0d72ec, fffff8800d5c2a90, 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: fffff8800f0d72ec, Address of the instruction which caused the bugcheck
Arg3: fffff8800d5c2a90, 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`0f0d72ec 488b02          mov     rax,qword ptr [rdx]

CONTEXT:  fffff8800d5c2a90 -- (.cxr 0xfffff8800d5c2a90;r)
rax=fffff8800f252620 rbx=0000000000000000 rcx=fffffa8005a63028
rdx=0000000000000000 rsi=fffff8800d5c3a8c rdi=fffff8800f251ff0
rip=fffff8800f0d72ec rsp=fffff8800d5c3470 rbp=fffff8800d5c35a1
 r8=00000000a29efa48  r9=0000000000000001 r10=0000000000000008
r11=0000000000000000 r12=fffffa800521a900 r13=0000000000000051
r14=0000000000000000 r15=fffffa8004e8b240
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210282
atikmdag+0xb12ec:
fffff880`0f0d72ec 488b02          mov     rax,qword ptr [rdx] ds:002b:00000000`00000000=????????????????
Last set context:
rax=fffff8800f252620 rbx=0000000000000000 rcx=fffffa8005a63028
rdx=0000000000000000 rsi=fffff8800d5c3a8c rdi=fffff8800f251ff0
rip=fffff8800f0d72ec rsp=fffff8800d5c3470 rbp=fffff8800d5c35a1
 r8=00000000a29efa48  r9=0000000000000001 r10=0000000000000008
r11=0000000000000000 r12=fffffa800521a900 r13=0000000000000051
r14=0000000000000000 r15=fffffa8004e8b240
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210282
atikmdag+0xb12ec:
fffff880`0f0d72ec 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:  plugin-contain

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800f0d72ec

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


FOLLOWUP_IP: 
atikmdag+b12ec
fffff880`0f0d72ec 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:  53a4efa7

STACK_COMMAND:  .cxr 0xfffff8800d5c2a90 ; 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`0f026000 fffff880`0ffcf000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Sat Jun 21 08:06:23 2014 (53A4EFA7)
    CheckSum:         00F44F2A
    ImageSize:        00FA9000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4