I Got A BSOD, Why?

We need this file

C:\Windows\Minidump\070514-20436-01.dmp

Copy/Paste to the desktop and upload the file

Find a free website that allows file upload and sharing
https://www.dropbox.com/

Or Google Drive.

Here's your dump


Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\amowat\Desktop\070514-20436-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03214000 PsLoadedModuleList = 0xfffff800`03457890
Debug session time: Sat Jul 5 15:56:13.835 2014 (GMT-4)
System Uptime: 0 days 3:17:25.069
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** 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, fffff880111a9dbb, fffff880027a2228, fffff880027a1a80}

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: fffff880111a9dbb, The address that the exception occurred at
Arg3: fffff880027a2228, Exception Record Address
Arg4: fffff880027a1a80, 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`111a9dbb 488b83a8060000 mov rax,qword ptr [rbx+6A8h]

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

CONTEXT: fffff880027a1a80 -- (.cxr 0xfffff880027a1a80)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000070000 rdi=0000000000000002
rip=fffff880111a9dbb rsp=fffff880027a2460 rbp=fffffa8009786060
r8=0000000000000002 r9=000000f4196ec000 r10=0000000000000000
r11=fffff880027a2690 r12=fffffa8008674bc0 r13=fffffa800857cc40
r14=fffffa800c52d740 r15=fffff880110e2000
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`111a9dbb 488b83a8060000 mov rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_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 fffff800034c1100
00000000000006a8

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

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff88000000001 to fffff880111a9dbb

STACK_TEXT:
fffff880`027a2460 fffff880`00000001 : fffff880`00000000 fffffa80`08674b00 00000000`00000000 fffffa80`0c52d740 : atikmdag+0xc7dbb
fffff880`027a2468 fffff880`00000000 : fffffa80`08674b00 00000000`00000000 fffffa80`0c52d740 fffff880`1120af6f : 0xfffff880`00000001
fffff880`027a2470 fffffa80`08674b00 : 00000000`00000000 fffffa80`0c52d740 fffff880`1120af6f 00000000`00000000 : 0xfffff880`00000000
fffff880`027a2478 00000000`00000000 : fffffa80`0c52d740 fffff880`1120af6f 00000000`00000000 fffff880`0494b181 : 0xfffffa80`08674b00


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 0xfffff880027a1a80 ; 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`110e2000 fffff880`11ff2000 atikmdag T (no symbols)
Loaded symbol image file: atikmdag.sys
Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
Image name: atikmdag.sys
Timestamp: Thu Apr 17 22:13:16 2014 (53508A3C)
CheckSum: 00EAEEE6
ImageSize: 00F10000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Cpu: OC

Probably a bad overclock then.

Run Prime95 and see if it errors out.

http://www.mersenne.org/download/