Language:

Homepage » DLL Q & A

Blue Screen Atikmpag.sys 0x116

Download Now


0x116

STACY WRIGHT asked on February 16, 2013. Status: Answered & Closed.

Blue Screen Atikmpag.sys 0x116

» I'm getting the atikmpag.sys BSOD 0x116. This started 1 week after I installed my ATi 7970 video card replacing my 5970 which died. The only problem is though. It happens prob once a day at most, or around every 8-12 hours. Doesn't matter if I'm playing a game or the computer is sitting idle doing nothing.


Best Answer

» Players who have updated to the 12.4 AMD drivers on a Windows Vista or Windows 7 system may encounter graphical issues when playing Diablo III. To resolve this issue, please download and install the Catalyst 12.4a Hotfix Driver available from the AMD website.

Rolled back the drivers, updated the drivers, installed only graphics driver without CCC and other bloat and still the issue persisted. I found lots of similar issues on the internet but no solutions and most people barking up the driver support tree or returning their cards to manufacturer. Strangely this BSOD would manifest primarily when browsing the web, and benchmark utilities on stability test could not reproduce the BSOD. Moving one monitor from minidisplayport via HDMI adapter, to the HDMI port of the card instantly alleviated this problem. Obviously this BSOD may have very many causes other than this cause but I hope this result helps somebody out in the future.

So, just give DLL Suite a shot, and you will find it easy to fix any blue screen of death including the one caused by Atikmpag.sys error and the viruses like Backdoor:Win32/Blohi.B.

Download DLL Suite, install and run > Click Dashboard menu and > Click Scan DLL Errors button > Click Fix DLL Errors button after the scan

MICHAEL LYNCH replied on February 21, 2013


All Answers:

  1. ERNEST MOORE replied on February 16, 2013: » The video driver is never the cause of 0x116, unless it was like 3 or 4 years old. So you do have some old or faulty drivers on your machine still. Nevertheless, glad your system is working fine now though.

  2. STACY WRIGHT replied on February 16, 2013: » Sorry I haven't found a solution yet but I'll keep updating the post if i find a way around it. Next thing I am going to try is run an Nvidia graphics card in it. This is really the last resort to the problem. I am completely out of ideas and really have no clue what else I can try.

  3. KELLY ROWELL replied on February 18, 2013: » WinDbg is the king while anything else is just a peasant locked in a dungeon lol - so you are doing well in that aspect. There is nothing you can see that you don't already know about the crash - it will simply show you that it is a 0x116 stop error involving the AMD driver.

    Where it can help, but really only if you know software across the board and which causes issues and which do not - type lmtn in the entry field at bottom then press Enter.

  4. PHA PRUM replied on February 19, 2013: » Yes, that is the solution. For example, this will save all the symbols to C:\Symcache folder so in the future, if the debugger needs the same symbols, it will look there first before looking on Microsoft's server - saves lots of time downloading, even on a fast connection:SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols

    (Make sure you've set that in a WinDbg instance that has never opened a crash dump yet.)

  5. ROBERT MORTON replied on February 20, 2013: » The video drivers themselves don't cause 0x116 issue. It's always either heat, faulty card, power issue or other drivers interfering with correct operations.

    AMD or NVIDA never release drivers beta or WHQL with the issue inherent to them. In other words, there is no such thing as a specific driver that has x 0x116 issue.

DLL Q & A You Might Like:

  1. Meydfv.sys Driver And Win32.Netsky Spyware Alert Trojan »
  2. BSOD Afd.sys After Reinstalling Network Driver »
  3. Run Dll c:\Windows\Dmdld40.dll »
  4. Cannot Find WAB.DLL Error In Outlook »
  5. LXCFtime.dll Missing Error Message On Startup »
  6. Pctcore.sys Causing BSOD »
  7. Receiving Ataport.sys Blue Screen »