I debugged one of your .dump files and here is the result:
Code:
Symbol search path is: SRV*E:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c5f000 PsLoadedModuleList = 0xfffff800`02e9ce50
Debug session time: Sat Jan 1 17:00:55.870 2011 (GMT+0)
System Uptime: 0 days 1:15:36.900
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff88005157817, fffff8800885c8e0, 0}
Probably caused by : atikmdag.sys ( atikmdag+90817 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88005157817, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800885c8e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
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+90817
fffff880`05157817 8b4820 mov ecx,dword ptr [rax+20h]
CONTEXT: fffff8800885c8e0 -- (.cxr 0xfffff8800885c8e0)
rax=0000000000000000 rbx=fffffa8004cba8e0 rcx=fffffa800554a990
rdx=0000000000000000 rsi=0000000000000015 rdi=fffffa8004aa1340
rip=fffff88005157817 rsp=fffff8800885d2c0 rbp=fffffa800554a990
r8=0000000000000015 r9=fffff88005519970 r10=0000000000000000
r11=fffff8800885d410 r12=0000000000000000 r13=fffffa80066bcd00
r14=0000000000000001 r15=0000000000000000
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+0x90817:
fffff880`05157817 8b4820 mov ecx,dword ptr [rax+20h] ds:002b:00000000`00000020=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88005157817
STACK_TEXT:
fffff880`0885d2c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x90817
FOLLOWUP_IP:
atikmdag+90817
fffff880`05157817 8b4820 mov ecx,dword ptr [rax+20h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: atikmdag+90817
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4cef1f94
STACK_COMMAND: .cxr 0xfffff8800885c8e0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_atikmdag+90817
BUCKET_ID: X64_0x3B_atikmdag+90817
Followup: MachineOwner
---------
From the debug result you can see that Windows has pointed to atikmdag.sys as the root of the problem. atikmdag.sys is an ATI system driver component for Windows, in other words it's part of your ATI video card display drivers, and that's where the problem is coming from.
A few questions before attempting to resolve the issue:
Is your CPU overclocked?
Is your Video Card overclocked?
If one or both of them are then perhaps try putting them back down to stock clocks and see if the problem persists. It may be that you have your GPU Memory Clock too high for it to remain stable for example.
Here are a few things you can try:
1. First verify the ATI/AMD driver version you are running - you can do this by launching the Catalyst Control Center and selecting Graphics > Information Center.
2. If find that you are running on an older driver then it may be possible that its causing some incompatibility somewhere, leading to the instability.
My recommendation would be to go the ATI/AMD website and download the latest display drivers for your card and OS. (Catalyst 10.12)
Now before you proceed to install the drivers you'll want to uninstall the previous ones then clean the entire system of them, making sure no traces are left over.
Here's how to do this:
1. Download and install Driver Sweeper from
here
2. Uninstall your current ATI video card drivers and all other Catalyst software from Control Panel (under Catalyst Install Manager)
3. Reboot your PC when prompted then select Safe Mode on the next boot
4. Once logged in, run Driver Sweeper with administrative privileges and select ONLY the option saying "ATI - Display"
5. Proceed by hitting the Clean button and reboot once prompted
6. Boot back into Windows normally and install the latest ATI video drivers which you have just downloaded, again rebooting once prompted by the installation
7. Finally test your card for an hour or so using Games/Benchmarks or Furmark, including normal desktop usage.
NOTE: For using of Radeon HD 5700 and 5800 series cards, I would not recommend using Catalyst 10.12 drivers as they seem to be a bit on the buggy side in my opinion. I would recommend using Catalyst 10.11 instead.
