BSOD while using Blender and UDK, error 0x000000d1

Give this a try. 1st run this, and get rid of the (AMD-Display) : Driver leftover uninstall:Drivers - Clean Left over Files after Uninstalling
Then
Update graphics drivers:
AMD :AMD Driver Autodetect
As well you may want to run this : Graphics: Video Card - Stress Test with Furmark (Do the above Graphics test only with the latest drivers, and then Run it until the temperatures stop increasing; should be less then 10 minutes. If you don't see any crazy glitches or distortion on the screen, The test most likely passed. Take note if the Temperature gets too high, or you see Visual artifact - Wikipedia, the free encyclopedia to stop the test.)

Code:

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


Loading Dump File [C:\Users\Skyler\AppData\Local\Temp\Rar$DIa0.149\101712-19188-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02e64000 PsLoadedModuleList = 0xfffff800`030a8670
Debug session time: Wed Oct 17 14:38:36.491 2012 (UTC - 5:00)
System Uptime: 0 days 3:39:41.677
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {302010010, 2, 0, fffff880061baf55}

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessCompletedQueuePacketInternal+2d )

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

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000302010010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880061baf55, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003112100
GetUlongFromAddress: unable to read from fffff800031121c0
 0000000302010010 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
dxgmms1!VidSchiProcessCompletedQueuePacketInternal+2d
fffff880`061baf55 488b7e10        mov     rdi,qword ptr [rsi+10h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  FlashPlayerPlu

TAG_NOT_DEFINED_c000000f:  FFFFF880030B7FB0

TRAP_FRAME:  fffff880030b77d0 -- (.trap 0xfffff880030b77d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800a125010 rbx=0000000000000000 rcx=fffffa800a125010
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880061baf55 rsp=fffff880030b7960 rbp=0000000000000000
 r8=fffff880030b7930  r9=fffffa800bed5b48 r10=fffffa80098757d0
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
dxgmms1!VidSchiProcessCompletedQueuePacketInternal+0x2d:
fffff880`061baf55 488b7e10        mov     rdi,qword ptr [rsi+10h] ds:00000000`00000010=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ee2569 to fffff80002ee2fc0

STACK_TEXT:  
fffff880`030b7688 fffff800`02ee2569 : 00000000`0000000a 00000003`02010010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`030b7690 fffff800`02ee11e0 : 00000000`00000000 ffffd738`64108747 fffff880`03088180 fffffa80`0988a8f0 : nt!KiBugCheckDispatch+0x69
fffff880`030b77d0 fffff880`061baf55 : fffffa80`0a214cb0 fffffa80`09cb6750 fffffa80`0a214cb0 fffffa80`09889000 : nt!KiPageFault+0x260
fffff880`030b7960 fffff880`061ba7da : fffffa80`00000000 fffffa80`00000000 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiProcessCompletedQueuePacketInternal+0x2d
fffff880`030b7a20 fffff880`061b9e00 : 00000000`00000000 fffffa80`09875010 00000000`00000000 fffff880`061b9c57 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x3b6
fffff880`030b7ac0 fffff880`061b9c4c : 00000000`00000000 fffffa80`09875010 fffff880`030b7bb0 fffffa80`0976a000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
fffff880`030b7b10 fffff880`060c01cf : fffffa80`08c90040 00000000`73b52450 00000000`00000000 fffffa80`096d0000 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`030b7b60 fffff880`056bf21c : fffffa80`096d0000 fffffa80`096d0000 00000000`00000000 fffffa80`09771bf0 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff880`030b7b90 fffffa80`096d0000 : fffffa80`096d0000 00000000`00000000 fffffa80`09771bf0 fffff880`030b7be0 : atikmdag+0x2321c
fffff880`030b7b98 fffffa80`096d0000 : 00000000`00000000 fffffa80`09771bf0 fffff880`030b7be0 fffff880`056d0707 : 0xfffffa80`096d0000
fffff880`030b7ba0 00000000`00000000 : fffffa80`09771bf0 fffff880`030b7be0 fffff880`056d0707 00000000`00000000 : 0xfffffa80`096d0000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiProcessCompletedQueuePacketInternal+2d
fffff880`061baf55 488b7e10        mov     rdi,qword ptr [rsi+10h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidSchiProcessCompletedQueuePacketInternal+2d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiProcessCompletedQueuePacketInternal+2d

BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiProcessCompletedQueuePacketInternal+2d

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

Ok I deinstalled all the amd graphics drivers an installed it again. Then I ran the Furmark but the temperature doesen't seem to go over 83° Celsius... I mean it is high but not too high, isn't it?
The PC crashed twice today without any warning. But only while playing a game. Do you have any idea what the problem might be?

I don't think it should be hott enough to crash like that, besides the card is rated 100-125 i believe. So i do not think this is a heat problem. Perhaps the PSU?
As well see if you can manage to keep it really cool while playing and see if it crashes as well while it is in a cool temp range.

I was just working with blender when the PC turned off again. So I decided to follow your tip and opened the PC-Case and the Balcony door to let in the autumn temperature :) ...

I was watching the walking dead and continued working with blender when it crashed again. I immediately touched PSU, CPU cooler and the graphics card. All of them where cool as marble... so I think I can definitly rule out any heat problems. It's almost like this machine is cursed. :-/