Hi, Andrei.
According to my analysis, it is indeed an AMD driver issue.
Code:
1: kd> lmvm atikmpag
Browse full module list
start end module name
fffff880`03e3b000 fffff880`03ee3000 atikmpag T (no symbols)
Loaded symbol image file: atikmpag.sys
Image path: atikmpag.sys
Image name: atikmpag.sys
Browse all global symbols functions data
Timestamp: Mon Aug 3 18:42:28 2015 (55C01884)
CheckSum: 000AF3B6
ImageSize: 000A8000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
1: kd> lmvm atikmdag
Browse full module list
start end module name
fffff880`0f0a8000 fffff880`105b2000 atikmdag (no symbols)
Loaded symbol image file: atikmdag.sys
Image path: atikmdag.sys
Image name: atikmdag.sys
Browse all global symbols functions data
Timestamp: Mon Aug 3 20:28:52 2015 (55C03174)
CheckSum: 014A6ED0
ImageSize: 0150A000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
It seems as though you have a more recent version of the driver than what the AMD site lists.
Run
DDU and install the recommended version of the 6850M driver from the AMD site, and report back with results.
If the proposed solution happens to not work, you could try older drivers until you get one that doesn't BSOD.
Code:
1: kd> .exr 0xfffff88002ee7e38
ExceptionAddress: fffff8800f124989 (atikmdag+0x000000000007c989)
ExceptionCode: c0000094 (Integer divide-by-zero)
ExceptionFlags: 00000000
NumberParameters: 0
I have heard of AMD GPU drivers in the past causing DivideByZero BSODs. Do report back with a known good version of the driver; if the recommended AMD version doesn't work, and you decide to continue with this route.
