The actual ERESOURCE routine tried to acquire the lock with exclusive access, but was passed a bad pointer, thus the exception.
4: kd> .trap ffffd000`25b10540
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd00025b10720
rdx=0200000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80121eec7a0 rsp=ffffd00025b106d0 rbp=0000000000000001
r8=ffffd00025b10770 r9=0000000000000000 r10=0000000000000002
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
iopl=0 nv up di pl zr na po nc
fffff801`21eec7a0 48890a mov qword ptr [rdx],rcx ds:02000000`00000000=????????????????
4: kd> !pte 0200000000000000
PXE at FFFFF6FB7DBED000 PPE at FFFFF6FB7DA00000 PDE at FFFFF6FB40000000 PTE at FFFFF68000000000
contains 04300000305D0867 contains 197000003B0A2867 contains 0000000000000000
GetUlongFromAddress: unable to read from fffff8012216510c
pfn 305d0 ---DA--UWEV pfn 3b0a2 ---DA--UWEV not valid
Originally Posted by blueelvis
The second function that is displayed in the stack nt!KiSystemServiceCopyEnd indicates the transition to Kernel mode, if that's what you mean.
It's not that the resource isn't available, it's that it simply hasn't been pointed to in the correct way, by passing a bad pointer, it accessed the wrong memory.
Given that this is a minidump, we don't know what the actual shared resource is.
I don't know if you've tried a display driver update, but I highly recommend it if you haven't, it's most likely a driver error.
4: kd> lmvm atikmdag
start end module name
fffff801`618df000 fffff801`62bbe000 atikmdag (deferred)
Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
Image name: atikmdag.sys
Timestamp: Tue Mar 31 21:31:21 2015 (551B0419)
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Given that the error is consistent with trying to acquire a lock, it's almost indefinately bad programming code passing bad pointers.
As for the red screen, I'm not sure, it could be a bad card, but I've seen display drivers cause all kinds of strange errors.