BSOD Physical Memory Dump Crash

[Rote]

A very good day to all the experts out here. I've encountered an issue with my pc and would like to seek help.

I've just purchased a Samsung Evo 840 250 G SSD and have cloned my os over to it (was using Corsair Force 3 120G SSD). Prior to this, my PC would encounter occasional BSODs relating to memory dump crash. It usually happens when I'm watching youtube videos on full screen. Once in a while, I'll get them when I'm gaming as well.

After cloning and setting my new SSD as the primary drive, the same issue persists. Am I looking at faulty drivers or is it a hardware issue I'm facing here? I've uploaded my log file, do take a look!

Would love all the help I can get!

 

[Arc]

Hi Rote.

Upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

We need to see it before we suggest anything to you.

Also, is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .
_________________________________________

*** 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, fffff8800f4e9dbb, fffff880087df228, fffff880087dea80}

[COLOR=Red]Probably caused by : atikmdag.sys[/COLOR] ( 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: fffff8800f4e9dbb, The address that the exception occurred at
Arg3: fffff880087df228, Exception Record Address
Arg4: fffff880087dea80, 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`0f4e9dbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h]

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

CONTEXT:  fffff880087dea80 -- (.cxr 0xfffff880087dea80;r)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000070000 rdi=0000000000000002
rip=fffff8800f4e9dbb rsp=fffff880087df460 rbp=fffffa800ae3e960
 r8=0000000000000002  r9=000000f411950000 r10=0000000000000000
r11=fffff880087df690 r12=fffffa800ae3e840 r13=fffffa800a325d40
r14=fffffa80073f5010 r15=fffff8800f422000
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`0f4e9dbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Last set context:
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000070000 rdi=0000000000000002
rip=fffff8800f4e9dbb rsp=fffff880087df460 rbp=fffffa800ae3e960
 r8=0000000000000002  r9=000000f411950000 r10=0000000000000000
r11=fffff880087df690 r12=fffffa800ae3e840 r13=fffffa800a325d40
r14=fffffa80073f5010 r15=fffff8800f422000
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`0f4e9dbb 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 fffff800032ae100
GetUlongFromAddress: unable to read from fffff800032ae1c0
 00000000000006a8 Nonpaged pool

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

BUGCHECK_STR:  0x7E

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

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800f4e9dbb

STACK_TEXT:  
fffff880`087df460 00000000`00000000 : fffffa80`0ae7dd90 fffffa80`0ae3e840 00000000`00000003 fffffa80`073f5010 : atikmdag+0xc7dbb


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 0xfffff880087dea80 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_atikmdag+c7dbb

BUCKET_ID:  X64_0x7E_atikmdag+c7dbb

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_atikmdag+c7dbb

FAILURE_ID_HASH:  {1bce3716-c561-7934-01c3-535369bb657c}

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

2: kd> lmvm atikmdag
start             end                 module name
fffff880`0f422000 fffff880`10332000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
[COLOR=Red]    Image name: atikmdag.sys
    Timestamp:        Fri Apr 18 07:43:16 2014 [/COLOR](53508A3C)
    CheckSum:         00EAEEE6
    ImageSize:        00F10000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[Rote]

Hi Arc,

Thanks for taking the time to reply.

Here's what I got:

http://speccy.piriform.com/results/gYCt4IvQXVtejJVy2Rygygk

Have uploaded the MSINFO32 rar version as well!

Appreciate all your help.

 

[Arc]

After seeing the added info, I would suggest you to do two things.

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 13.9 WHQL only; older, but more stable.

• Previous AMD Catalyst? Display Drivers

When done, stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark
​

Let us know the result.