I don't know what to tell you
BugCheck F7, {9824bc8b4c0000, 62e1808ec86e, ffff9d1e7f713791, 0}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+ce970 )
The card could be your problem it may be faulty or contain bad integrated memory components.
It could be just a driver problem you might see if there is a newer one available or if perhaps an older version might work better.
Do you have the option to swap it out for an alternative video card for testing purposes?
DRIVER_OVERRAN_STACK_BUFFER (f7)
A driver has overrun a stack-based buffer. This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned. This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.
Do a kb to get a stack backtrace -- the last routine on the stack before the
buffer overrun handlers and bugcheck call is the one that overran its local
variable(s).
Arguments:
Arg1: 009824bc8b4c0000, Actual security check cookie from the stack
Arg2: 000062e1808ec86e, Expected security check cookie
Arg3: ffff9d1e7f713791, Complement of the expected security check cookie
Arg4: 0000000000000000, zero
When I do a KB the only actual driver mentioned is
kb
RetAddr : Args to Child : Call Site
fffff801`cbbbfe01 : 00000000`000000f7 009824bc`8b4c0000 000062e1`808ec86e ffff9d1e`7f713791 : nt!KeBugCheckEx
fffff801`cba53f98 : 00000000`00000002 00000000`00000069 ffff8000`00000000 00000000`00000000 : nt!_report_gsfailure+0x25
fffff801`cbb669bc : ffffd000`713fc278 ffffe001`a19d85d0 ffffd000`713fbdb0 00000000`ffffffff : nt!MmAccessFault+0x448
fffff801`09f3e970 : fffff801`09fae9fb ffffe001`9ed04b80 ffffe001`a0b2a060 ffffe001`a23f8000 : nt!KiPageFault+0x13c
fffff801`09fae9fb : ffffe001`9ed04b80 ffffe001`a0b2a060 ffffe001`a23f8000 ffffe001`a1c27350 : atikmdag+0xce970
ffffe001`9ed04b80 : ffffe001`a0b2a060 ffffe001`a23f8000 ffffe001`a1c27350 00000000`00000000 : atikmdag+0x13e9fb
ffffe001`a0b2a060 : ffffe001`a23f8000 ffffe001`a1c27350 00000000`00000000 ffffe001`9ed04b80 : 0xffffe001`9ed04b80
ffffe001`a23f8000 : ffffe001`a1c27350 00000000`00000000 ffffe001`9ed04b80 00000000`00000001 : 0xffffe001`a0b2a060
ffffe001`a1c27350 : 00000000`00000000 ffffe001`9ed04b80 00000000`00000001 fffff801`09fb1583 : 0xffffe001`a23f8000
00000000`00000000 : ffffe001`9ed04b80 00000000`00000001 fffff801`09fb1583 ffffe001`9f398b00 : 0xffffe001`a1c27350
Which then apparently pitches a page fault.
As I've said, I'm no BSOD expert, but.....
It gives you something to consider.
