BSOD at different times, cant pinpoint the cause (Kernal Power 41)

Hi i have been getting a weird BSOD and there is no distinct line during the blue screen that i can give you as it seems to be a little different to many BSOD's

Here is some of the information i can give you

At the time of the particular Blue screen which was 10:18 PM i got the following errors in Event Viewer under System Tab, there where no errors at the time under Application tab

Critical 6/23/2014 10:18:15 PM Kernel-Power 41 (63)
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Error 6/23/2014 10:18:19 PM BugCheck 1001 None

Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff8800f2dcdbb, 0xfffff880054aa228, 0xfffff880054a9a80). A dump was saved in:

Error 6/23/2014 10:18:19 PM EventLog 6008 None
Description:
The previous system shutdown at 10:17:16 PM on ‎6/‎23/‎2014 was unexpected.

I also have a minidump file of it in my Minidump folder but i cannot attach it here because i apparently dont have permission to do so even though i went through the properties to allow full access

EDIT: ive uploaded the minidump now

Welcome to the forum scocuzza,

Please upload your MSINFO32 file.
MSINFO32:

• Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter.
• Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
• Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\admin\Downloads\062314-9968-01\062314-9968-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
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03265000 PsLoadedModuleList = 0xfffff800`034a8890
Debug session time: Tue Jun 24 08:17:50.490 2014 (UTC + 6:00)
System Uptime: 0 days 7:26:10.302
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
.....................
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800f2dcdbb, fffff880054aa228, fffff880054a9a80}

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

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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800f2dcdbb, The address that the exception occurred at
Arg3: fffff880054aa228, Exception Record Address
Arg4: fffff880054a9a80, Context Record Address

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+c7dbb
fffff880`0f2dcdbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h]

EXCEPTION_RECORD:  fffff880054aa228 -- (.exr 0xfffff880054aa228)
ExceptionAddress: fffff8800f2dcdbb (atikmdag+0x00000000000c7dbb)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000000006a8
Attempt to read from address 00000000000006a8

CONTEXT:  fffff880054a9a80 -- (.cxr 0xfffff880054a9a80)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000078000 rdi=0000000000000002
rip=fffff8800f2dcdbb rsp=fffff880054aa460 rbp=fffffa800897a960
 r8=0000000000000002  r9=000000f41a500000 r10=0000000000000000
r11=fffff880054aa690 r12=fffffa8008981b40 r13=fffffa8007c52840
r14=fffffa800acf4600 r15=fffff8800f215000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
atikmdag+0xc7dbb:
fffff880`0f2dcdbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000000006a8

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003512100
GetUlongFromAddress: unable to read from fffff800035121c0
 00000000000006a8 Nonpaged pool

FOLLOWUP_IP: 
atikmdag+c7dbb
fffff880`0f2dcdbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88000000001 to fffff8800f2dcdbb

STACK_TEXT:  
fffff880`054aa460 fffff880`00000001 : fffff880`00000000 fffffa80`08981b00 00000000`00000000 fffffa80`0acf4600 : atikmdag+0xc7dbb
fffff880`054aa468 fffff880`00000000 : fffffa80`08981b00 00000000`00000000 fffffa80`0acf4600 fffff880`0f33df6f : 0xfffff880`00000001
fffff880`054aa470 fffffa80`08981b00 : 00000000`00000000 fffffa80`0acf4600 fffff880`0f33df6f 00000000`00000000 : 0xfffff880`00000000
fffff880`054aa478 00000000`00000000 : fffffa80`0acf4600 fffff880`0f33df6f 00000000`00000000 fffff880`04610181 : 0xfffffa80`08981b00


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atikmdag+c7dbb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53508a3c

STACK_COMMAND:  .cxr 0xfffff880054a9a80 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_atikmdag+c7dbb

BUCKET_ID:  X64_0x7E_atikmdag+c7dbb

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

2: kd> lmvm atikmdag
start             end                 module name
fffff880`0f215000 fffff880`10125000   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 08:13:16 2014 (53508A3C)
    CheckSum:         00EAEEE6
    ImageSize:        00F10000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your BSODs were caused by the latest ATI Drivers, you may consider reverting to an older version of the driver to see if that helps.

To perform a clean install of a driver, follow this tutorial:

• How to Clean Left Over Driver Files with Driver Sweeper

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• How to Repair Windows 7 System Files with System File Checker

Scan with Kaspersky TDSSKiller:

• Anti-rootkit utility TDSSKiller

ESET online scanner:

• Free Online Virus Scanner | ESET

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• How to Run Disk Check in Windows 7