Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: 2nd Random BSOD since upgrading to Catalyst 12.3, atikmpag.sys


23 Apr 2012   #1

Windows 7 Ultimate x64 SP1
 
 
2nd Random BSOD since upgrading to Catalyst 12.3, atikmpag.sys

Running Windows 7 x64 Ultimate SP1 Retail.

Hardware and OS is 6 months old.

I do regular image backups.

This is the 2nd time a random BSOD has happened since I updated my Catalyst drivers to 12.3. First time was when I turned off my monitor and noticed my system restarted on it's own. The 2nd time was when I was shopping on Newegg and getting ready to check out.

I was using Catalyst 11.9 before and the system was running flawlessly.

MagicTune shows errors in the report but that's the nature of it. It's running fine and not causing any conflicts.

My System SpecsSystem Spec
.

25 Apr 2012   #2

Windows 7 Home Premium 64 Bit
 
 

I noticed yesterday when I updated to 12.3 that my system was locking up every few seconds. A restart seems to have resolved that problem, but based on that behavior, I would say that 12.3 may not be the most stable driver/software set.


Problem Devices:
Code:
MagicTune	ROOT\LEGACY_MAGICTUNE\0000	This device is not present, is not working properly, or does not have all its drivers installed.

Security Software: ??? I recommend either of these two setups:Download and install the security setup of your choice, update the software, and then run a full scan of your system for viruses and malware. If you only install MSE, I would also suggest installing and updating Malwarebytes : Free anti-malware, anti-virus and spyware removal download, but do not start the free trial/full version of Malwarebytes. Run a full scan with Malwarebytes after updating it. Post back the results.


Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\0pTicaL\Windows_NT6_BSOD_jcgriff2\042312-10077-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`03000000 PsLoadedModuleList = 0xfffff800`03244650
Debug session time: Mon Apr 23 13:26:48.831 2012 (UTC - 6:00)
System Uptime: 4 days 21:28:16.812
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800cfa3180, fffff88006007ae4, 0, d}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+7ae4 )

Followup: MachineOwner
---------

6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800cfa3180, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88006007ae4, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
atikmpag+7ae4
fffff880`06007ae4 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`05816888 fffff880`06298000 : 00000000`00000116 fffffa80`0cfa3180 fffff880`06007ae4 00000000`00000000 : nt!KeBugCheckEx
fffff880`05816890 fffff880`06297d87 : fffff880`06007ae4 fffffa80`0cfa3180 fffffa80`0ba1ac00 fffffa80`0b9f0410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`058168d0 fffff880`0633ef07 : fffffa80`0cfa3180 00000000`00000000 fffffa80`0ba1ac00 fffffa80`0b9f0410 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`05816900 fffff880`06368b75 : 00000000`ffffffff 00000000`019da432 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`058169e0 fffff880`063672bb : 00000000`00000102 00000000`00000003 00000000`019da432 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`05816a10 fffff880`0633a2c6 : ffffffff`ff676980 fffffa80`0b9f0410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`05816ab0 fffff880`06366e7a : 00000000`00000000 fffffa80`0cb6da70 00000000`00000080 fffffa80`0b9f0410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`05816bc0 fffff800`03316fda : 00000000`fffffc32 fffffa80`0b761b60 fffffa80`06cf7b30 fffffa80`0b761b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`05816c00 fffff800`0306d9c6 : fffff880`009eb180 fffffa80`0b761b60 fffff880`009f60c0 4f2b7a52`676a6161 : nt!PspSystemThreadStartup+0x5a
fffff880`05816c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+7ae4
fffff880`06007ae4 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+7ae4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f597fca

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

Followup: MachineOwner
---------
Your 12.3 driver installation appears to be corrupted, which may also be why you are having stability problems. I would recommend re-installing, and if that does not work, revert to the previous driver software. Let us know if the crashes persist.


Further reading (and steps to follow if changing drivers does not resolve the problem): STOP 0x116: VIDEO_TDR_ERROR troubleshooting


To re-install drivers for the display card.
  1. Download the drivers you want to install for your display card(s)
  2. Click Start Menu
  3. Click Control Panel
  4. Click Uninstall a program
  5. For AMD:
    • Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
    • If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers:
      1. Click Start Menu
      2. Right Click My Computer/Computer
      3. Click Manage
      4. Click Device Manager from the list on the left
      5. Expand Display adapters
      6. Do the following for each adapter (in case you have multiple display cards)
        • Right click the adapter
        • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
        • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK

        Alternatively:
        1. Login as an adminstrative user
        2. Click Start Menu
        3. Click Control Panel
        4. Click Hardware and Sound
        5. Click Device Manager (the last link under Devices and Printers)
        6. Expand Display adapters
        7. Do the following for each adapter (in case you have multiple display cards)
          • Right click the adapter
          • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
          • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    • Restart your computer after uninstalling drivers for all display cards
    • Install the driver of your choice for the display cards once Windows starts
My System SpecsSystem Spec
25 Apr 2012   #3

Windows 7 Ultimate x64
 
 

The most important Blue Screen of Death troubleshooting step you can take is to ask yourself what you just did.

1) Did you just install a new program or a piece of hardware, update a driver, install an update, etc.? If so, there's a very good chance that the change you made caused the BSOD:
  • Startup using Last Known Good Configuration to undo recent registry and driver changes.
  • Use System Restore to undo recent system changes.
  • Roll Back device driver to version prior to your driver update.
2) Scan your computer for viruses. Some viruses can cause a Blue Screen of Death, especially ones that infect the master boot record (MBR) or boot sector.

3) Update drivers for your hardware. Most Blue Screens of Death are hardware or driver related so updated drivers could fix the cause of the STOP error.

4) Return hardware settings to default in Device Manager. Unless you have a specific reason to do so, the system resources that an individual piece of hardware is configured to use in Device Manager should be set to default. Non-default hardware settings have been known to cause a Blue Screen of Death.

5) Return BIOS settings to their default levels. An overclocked or misconfigured BIOS can cause all sorts of random issues, including BSODs.

6) Check CMOS and Memory Modules

Important: Make sure your virus scanning software is updated and configured to scan the MBR and boot sector.
My System SpecsSystem Spec
.


26 Apr 2012   #4

Windows 7 Ultimate x64 SP1
 
 

Thanks guys, I downgraded to Catalyst 11.9 (last known stable drivers). Will monitor machine for a week and see how it goes.

The more I read about 12.3 the more I know how unstable they are.
My System SpecsSystem Spec
26 Apr 2012   #5

Main - Windows 7 Pro SP1 64-Bit; 2nd - Windows Server 2008 R2
 
 

12.4 is now out, though it remains to be seen if it's an improvement.
My System SpecsSystem Spec
26 Apr 2012   #6

Windows 7 Ultimate x64 SP1
 
 

Quote   Quote: Originally Posted by profdlp View Post
12.4 is now out, though it remains to be seen if it's an improvement.
Yeah, but after 12.3 I'm sticking with the old saying, if it ain't broken don't fix it.

Until a game I'm playing is having problems with 11.9 then I'll think of updating.
My System SpecsSystem Spec
26 Apr 2012   #7

Main - Windows 7 Pro SP1 64-Bit; 2nd - Windows Server 2008 R2
 
 

I don't blame you a bit. A lot of these releases seem to be targeted at improving performance in individual games (or game engines), anyway.
My System SpecsSystem Spec
03 May 2012   #8

Windows 7 Ultimate x64 SP1
 
 

I would like to report that after a clean install of 11.9 I have been BSOD free for the past week. I guess the culprit was 12.3 afterall.
My System SpecsSystem Spec
03 May 2012   #9

Windows 7 Home Premium 64 Bit
 
 

12.4 was recently released and is supposed to also resolve the problems you saw, but I would recommend just staying with that you are running. There is no reason to update drivers just for the sake of updating; we usually only recommend updating if a driver is actually causing a problem. If it ain't broke, don't fix it.
My System SpecsSystem Spec
04 May 2012   #10

Windows 7 Ultimate x64 SP1
 
 

I'm also curious as to why after 11.9 the update almost doubled in size.
My System SpecsSystem Spec
Reply

 2nd Random BSOD since upgrading to Catalyst 12.3, atikmpag.sys




Thread Tools



Similar help and support threads for2: 2nd Random BSOD since upgrading to Catalyst 12.3, atikmpag.sys
Thread Forum
Non-Random BSOD - Atikmpag.sys Error BSOD Help and Support
Random BSOD after upgrading components BSOD Help and Support
Random BSOD After upgrading a Dell Studio 1537 to Win 7 32bit BSOD Help and Support
BSOD ATIkmpag.sys BSOD Help and Support
BSOD 116 atikmpag.sys BSOD Help and Support
Solved BSoD in BF3/sometimes random / dxgmms1.sys // atikmpag.sys // atikmdag BSOD Help and Support
Random BSOD's since upgrading pc BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 09:52 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33