BSODs when computer is left idle for over ~15 minutes

[agentsmith24]

I have been getting some weird BSODs, they only occur when I get up and leave my computer alone. Doesn't seem to matter what's running at the time, or if the computer has been in sleep mode or not. I always come back to a bluescreen if it's been long enough. I've attached the dump file from the last one that occurred.

Thanks for any help!

 

[ICIT2LOL]

Hello Smithy mate there seems to be a graphics problem running through most of the dump files and and the one that frequently comes up is suggesting uninstalling t Catalyst Control Centre and I would suggest doing that and see what happens.
Personally I am not a fan of AMD stuff preferring NVidia after I had problem s++ with the CCC but the choice is yours of course.

*******************************************************************************
*                                                                             *
*                        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: fffff8800f4c783b, The address that the exception occurred at
Arg3: fffff88005db4228, Exception Record Address
Arg4: fffff88005db3a80, 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+c483b
fffff880`0f4c783b 488b83a8060000  mov     rax,qword ptr [rbx+6A8h]
EXCEPTION_RECORD:  fffff88005db4228 -- (.exr 0xfffff88005db4228)
ExceptionAddress: fffff8800f4c783b (atikmdag+0x00000000000c483b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000000006a8
Attempt to read from address 00000000000006a8
CONTEXT:  fffff88005db3a80 -- (.cxr 0xfffff88005db3a80;r)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000050000 rdi=0000000000000002
rip=fffff8800f4c783b rsp=fffff88005db4460 rbp=fffffa80108a09a0
 r8=0000000000000002  r9=000000f418ed8000 r10=0000000000000000
r11=fffff88005db4690 r12=fffffa80108a0880 r13=fffffa800f838040
r14=fffffa8014766010 r15=fffff8800f403000
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+0xc483b:
fffff880`0f4c783b 488b83a8060000  mov     rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Last set context:
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000050000 rdi=0000000000000002
rip=fffff8800f4c783b rsp=fffff88005db4460 rbp=fffffa80108a09a0
 r8=0000000000000002  r9=000000f418ed8000 r10=0000000000000000
r11=fffff88005db4690 r12=fffffa80108a0880 r13=fffffa800f838040
r14=fffffa8014766010 r15=fffff8800f403000
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+0xc483b:
fffff880`0f4c783b 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 fffff800032cb100
GetUlongFromAddress: unable to read from fffff800032cb1c0
 00000000000006a8 Nonpaged pool
FOLLOWUP_IP: 
atikmdag+c483b
fffff880`0f4c783b 488b83a8060000  mov     rax,qword ptr [rbx+6A8h]
BUGCHECK_STR:  0x7E
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER:  from 0000000000140000 to fffff8800f4c783b
STACK_TEXT:  
fffff880`05db4460 00000000`00140000 : 00000000`00000000 fffffa80`108a0880 00000000`00000003 fffffa80`14766010 : atikmdag+0xc483b
fffff880`05db4468 00000000`00000000 : fffffa80`108a0880 00000000`00000003 fffffa80`14766010 fffff880`0f52648f : 0x140000

SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  atikmdag+c483b
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME:  [COLOR=red]atikmdag.sys[/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP:  52ec068c
STACK_COMMAND:  .cxr 0xfffff88005db3a80 ; kb
FAILURE_BUCKET_ID:  [COLOR=red]X64_0x7E_atikmdag+c483b[/COLOR]
BUCKET_ID:  X64_0x7E_atikmdag+c483b
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x7e_atikmdag+c483b
FAILURE_ID_HASH:  {dc9cc0b9-993f-663d-42f6-2cf123a43aab}
Followup: MachineOwner
---------

If this does not remedy the problem I would suggest a memtest to if you haven't already - if you do then it must be run for at least 8 passes any less will not be enough time for stick or slot problems to be found.

MEMTEST

The memtest you will need to make a bootable disk / stick andset the BIOS to boot from the optical or USBand it will take a fair time torun- some leave it overnight. see the attached document.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

But one thing is very important you must let the test run for at least 8passes any less and the findings are no good. Now if errors come upstraight away then you can stop it - see my pics. Now if there are errors andyou have more than one stick of RAM in then you will need to test each stick ieremove the sticks and replace stick 1 in slot 1 and test no errors do thesame in slot 2 with stick 1 no errors then repeat the process with stick 2 -that will show up the faulty stick - the other thing is it could be a faultyslot but most unusual. With more than two sticks the process is even longer asone may realize.

It is a very lengthy and tedious process but worth it if youhave errors.
But try the CCC fix first.

 

[agentsmith24]

I tried uninstalling CCC and loaded the newest version of it, still had a crash occur. I need it to run my eyefinity setup. I'll try memtest and see if that pulls anything up.

 

[ICIT2LOL]

Ok mate you might have a read of this first to get the gist of memtesting - not that I ma suggesting you don't know what you are doing but a lot of folks forget that it can be the slots as well as the sticks
For cleaning the slots see the other ditty of miner.

MEMTEST

The memtest you will need to make a bootable disk / stick andset the BIOS to boot from the optical (disk) or USB and it will take a fairtime to run- some leave it overnight..

But one thing is very important you must let the test run for at least 8 passes anyless and the findings are no good. Now if errors come up straight away then youcan stop it - see my pics. Now if there are errors and you have more than onestick of RAM in then you will need to test each stick ie remove the sticks andreplace stick 1 in slot 1 and test no errors do the same in slot 2 withstick 1 no errors then repeat the process with stick 2 - that will show up thefaulty stick - the other thing is it could be a faulty slot but most unusual.

It is a very lengthy and tedious process but worth it if youhave errors.


GENERAL SLOT CLEANING

Now as for anymotherboard slots to clean them use a strip of old credit card (or any cardthin enough some are better than others ) about 1/2 inch wide nip the cornersoff one end - preferably round themoffhold a piece of thinlint free cloth over the end dab on some form of alcohol - isopropyl alcohol(what we swab the skin with before an injection) is good and GENTLY swipe along the slots.

This can also be done for the GPU slot/s andalso the contacts of the sticks or other cards - not the stick but some lintfree cloth of course. See my pic for the stick but please be very gentle doingit if you are in any doubt - please ask before doing it but I use this all thetime and have yet to damage anything