2 BSOD in the past 24 hrs

First one is Memory corruption.

Code:

 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff8800a56ef90
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff8800497167b
Debugging Details:
------------------
 
CONTEXT:  fffff8800a56ef90 -- (.cxr 0xfffff8800a56ef90)
rax=0000000000000001 rbx=00fffa8006a2b210 rcx=fffffa80065a4000
rdx=fffffa8006a08578 rsi=fffffa8006a00000 rdi=0000000000000000
rip=fffff8800497167b rsp=fffff8800a56f970 rbp=fffffa8006a08570
 r8=0000000000000000  r9=0000000000000000 r10=fffff9800305af90
r11=0000000000000246 r12=fffffa8006a08638 r13=0000000000000000
r14=fffffa8006a00000 r15=fffff8800a56fb40
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
atikmdag+0xe067b:
fffff880`0497167b f6432c01        test    byte ptr [rbx+2Ch],1 ds:002b:00fffa80`06a2b23c=??
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x3D
PROCESS_NAME:  LolClient.exe
CURRENT_IRQL:  a
LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800497167b
STACK_TEXT:  
fffff880`0a56f970 00000000`00000000 : 00000000`00000000 ff0f0f0f`ff0f0f0f ff0f0f0f`ff0f0f0f 0000002a`00000048 : atikmdag+0xe067b
 
MODULE_NAME: memory_corruption
IMAGE_NAME:  memory_corruption
FOLLOWUP_NAME:  memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP:  0
MEMORY_CORRUPTOR:  STRIDE
STACK_COMMAND:  .cxr 0xfffff8800a56ef90 ; kb
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE
BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE
Followup: memory_corruption

Run memtest86+ follow the tutorial.

RAM - Test with Memtest86+



Second one is the same.

Code:

 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3D, {fffff8800a56ef90, 0, 0, fffff8800497167b}
Unable to load image 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
Probably caused by : memory_corruption
Followup: memory_corruption
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff8800a56ef90
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff8800497167b
Debugging Details:
------------------
 
CONTEXT:  fffff8800a56ef90 -- (.cxr 0xfffff8800a56ef90)
rax=0000000000000001 rbx=00fffa8006a2b210 rcx=fffffa80065a4000
rdx=fffffa8006a08578 rsi=fffffa8006a00000 rdi=0000000000000000
rip=fffff8800497167b rsp=fffff8800a56f970 rbp=fffffa8006a08570
 r8=0000000000000000  r9=0000000000000000 r10=fffff9800305af90
r11=0000000000000246 r12=fffffa8006a08638 r13=0000000000000000
r14=fffffa8006a00000 r15=fffff8800a56fb40
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
atikmdag+0xe067b:
fffff880`0497167b f6432c01        test    byte ptr [rbx+2Ch],1 ds:002b:00fffa80`06a2b23c=??
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x3D
PROCESS_NAME:  LolClient.exe
CURRENT_IRQL:  a
LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800497167b
STACK_TEXT:  
fffff880`0a56f970 00000000`00000000 : 00000000`00000000 ff0f0f0f`ff0f0f0f ff0f0f0f`ff0f0f0f 0000002a`00000048 : atikmdag+0xe067b
 
MODULE_NAME: memory_corruption
IMAGE_NAME:  memory_corruption
FOLLOWUP_NAME:  memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP:  0
MEMORY_CORRUPTOR:  STRIDE
STACK_COMMAND:  .cxr 0xfffff8800a56ef90 ; kb
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE
BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE
Followup: memory_corruption
---------

It can be either bad RAM or bad slots.

pandasaurus said:

A few days ago I did added a perfectly working second stick of RAM. Since then I have played many games just fine, but finally BSOD'd today. IIRC, this BSOD error also happened months ago, which lead me to believe I had a bad stick of RAM or a bad DIMM slot...

You can try taking out the original RAM card and see if it crashes again.

I would recommend to run memtest86+ to be sure.

So, it sounds like you have found the culprit.

Let us know if you have any questions.

You're welcome, hope you get it running stable.

pandasaurus said:

Hey Dave.

I was running off of 1 2GB Adata stick (originally 2 sticks, but noticed I BSOD'd often on 2), but replaced them with 2 working (in another computer) 2GB Corsair sticks this past week.

Would Memtest error if I had a bad DIMM slot?? I ask this because I BSOD'd once yesterday, the first time running off of the 2 Corsair sticks, ran Memtest86+ at bed, woke up to 8 passes and no errors... However when I run Memtest with the Adata sticks I always get at least 1 error.

If Memtest would error with a DIMM slot, what else do you suspect could be wrong?

When you run memtest86+ you are looking for bad RAM cards, bad motherboard slots, so you need to follow the testing procedure in the tutorial.
Sometimes errors from these tests can be corrected by adjusting the settings.
RAM - Test with Memtest86+ follow the instructions on moving the RAM cards to different slots, this will tell you if you have a bad slot.

D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.

For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums


Have you been checking your temperatures?

Use Core Temp, to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

Your CPU core temps are ok but, 36°C and 53°C, 36°C is high for an idle temp on a AMD CPU.
Was the system at idle during the temp monitoring?


There is a known issue with AMD CPUs integrated memory controllers having problems running RAM at 1600 MHz and above.

VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's and RAM SPEEDS
Q&A for the topic VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's & RAM....

Set the RAM to 1333MHz (666MHz) in your BIOS, then check for crashes.

Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.
This is important, the voltages might need adjustment as well.