atikmpag.sys dxgkrnl.sys and dxgmm1.sys BSOD at random.

Hello guys.I really tried to overcome these BSODs but i cant stand em any more.As the title declares those are the drivers that keep crushing at least according with BlueScreenView.I have the latest gpu drivers.I also formated the HDD long time ago and the crashes didnt appeared till yesterday.What has changed since then?Well my brother installed Lol and the this crappy aero program that comes with it.Apart from this he used skype and just plugged a different mouse and keyboard and then BANG,crashes started reappearing again again even if i only use chrome with youtube playing music.Cant understand what the heck triggered em again.Sfc keeps reporting errors after each repair that cant fixe em but i dont really think thats the problem.I am about to get an R9 380 4Gb with a new PSU (cause the current one is a bit crappy and old) but i dont really know if crashes will dissappear eventually once for all.I strongly believe that its just the outdated gpu drivers that cause the problems.Any thoughts plz?

Hi fwtakis,

Welcome to the 7forums.

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

1. Uninstall Daemon Tools
2. Download the SPTD standalone installer and follow these steps:
   
   • Double click the executable to open it
   • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window.


A driver from Gigabyte software has been flagged.
Please remove the Gigabyte software.

Code:

2: kd> lmvm AppleCharger
start             end                 module name
fffff880`0337f000 fffff880`03387000   AppleCharger T (no symbols)           
    Loaded symbol image file: AppleCharger.sys
    Image path: \SystemRoot\system32\DRIVERS\AppleCharger.sys
    Image name: AppleCharger.sys
    Timestamp:        Tue Apr 27 05:54:05 2010 (4BD65FDD)
    CheckSum:         000093A3
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The drivers from your GPU have been flagged.
Please check the site of AMD for driver updates.

Code:

2: kd> lmvm atikmpag
start             end                 module name
fffff880`0437f000 fffff880`043de000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Tue Apr 30 04:48:15 2013 (517F30EF)
    CheckSum:         000613E7
    ImageSize:        0005F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

2: kd> lmvm atikmdag
start             end                 module name
fffff880`04827000 fffff880`053da000   atikmdag   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Tue Apr 30 04:07:09 2013 (517F274D)
    CheckSum:         00B6397D
    ImageSize:        00BB3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Really thanks.I ve uninstalled the On/Off (applecharger.sys) application a couple days ago.Now i just uninstalled deamon tools too.I ll test my pc and i ll be back with the results within the week.Unfortunately i cant do much with the gpu's drivers part.AMD has announced that they no longer support these series (since october 2013 actually...) so i guess i ll stick with those drivers till i get a new gpu...

The crash 0x116 indicates issues with the GPU, mostly the drivers so far I've seen.
But, this crash could also be caused by heat problems.
Please note the temperatures of the GPU when idle and under load.

No no.Temperature its ok.Mostly around 80 Celsius when under load (top value is 84-85) even after many hours of gaming.I recently reapplied thermal paste too.From what i know these series were always running at such temps.

Let me know how it goes with Daemon tools removed :)

Till now not a single crush.Probably deamon tools was the problem, although i dont really remember it running at background processes.Really thnx

You're welcome :)