Overclock.net › Forums › Graphics Cards › AMD/ATI › Radeon 6950 and atikmpag.sys :(
New Posts  All Forums:Forum Nav:

Radeon 6950 and atikmpag.sys :(

post #1 of 4
Thread Starter 
I have this issue with Simcity. Check out the video. http://www.youtube.com/watch?v=aMClZSCCnEw

My temps on my video card in game are 60-75 with a fan speed of 80% I don't overclock my video card. I ran furmark for 2 hours along with prime95 and nothing happened. I can play my whole library of games installed with no problems. The Witcher 2 and Battlefield 3 are the most intense graphical games I own. I run both of them for hours with no problem what so ever. That tells me it is not a hardware issue. Am I right?

When I play Simcity sometimes when loading a city when I first start the game both of my monitors will go black and I see a "no signal" error. The lights and fans on my computer are still on but I cannot do anything. Only thing I can do is manually shut down my computer. If I turn it back on it doesn't even post. I have to wait 30 seconds or more to turn it back on. Sometimes I am able to get in my city and when I do I can play for hours but once I click on regional view (the game does some zoom out sequence) I get the error again! Every time! Like I typed before, no other game or stress test does this to me.

I have an i7 920 OC to 3.8 and temps idle around 39 and get in the 50s while playing games (after I cleaned out the fan of my h5O) I run prime95 and furmark at the same time for 2 and a half hours and both my cpu and gpu were fine. No signs of overheating. I was told to check event viewer for an error. I don't know what the hell I am looking at in this thing but I see

"Unable to load image ntoskrnl.exe, Win32 error 0n2" and "Unable to load image atikmpag.sys, Win32 error 0n2" I don't know what this means. Just know it is linked to videocard/drivers. Here is my full dmp file.
Code:
Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\031413-17062-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`03205000 PsLoadedModuleList = 0xfffff800`03442e50
Debug session time: Thu Mar 14 21:42:08.051 2013 (UTC - 4:00)
System Uptime: 0 days 1:03:12.989
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*** WARNING: Unable to verify timestamp for watchdog.sys
*** ERROR: Module load completed but symbols could not be loaded for watchdog.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa800a0374e0, fffff880044c0990, 0, 0}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Unable to load image 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
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : atikmpag.sys ( atikmpag+9990

Could someone who understands this please take a look. I feel the temps are not the problem. I feel my hardware is not breaking down since stress tests and other games run fine. It is either Maxis or AMD drivers. I have used 13.2 beta, 13.1, 13.3, 12.8, and 11.6. All with the same thing happening with the same error in the same game in the same area.

I know it is looked down on but when I run the memory test that comes with windows no problems are found. memtest86 just doesn't work for me.
Edited by noeyjerd - 3/15/13 at 8:27am
post #2 of 4
I think one of your OS files are corrupted, you could try to repair them with the command "sfc /scannow" in CMD.

If that does not work, i would try a clean install of windows and try from there, i think its the only way to rule out if its the hardware or software
Blazer
(8 items)
 
  
CPUMotherboardRAMHard Drive
Intel i7 4790K MSI MPower Z97 Adata XPG 2x8GB DDR3-2600 Crucial M500 120GB SSD 
Hard DriveHard DriveHard DrivePower
Samsung 830 128GB SSD Cruscial MX200 250GB SSD WD 1TB HDD Seasonic M12II Evo 750W 
  hide details  
Reply
Blazer
(8 items)
 
  
CPUMotherboardRAMHard Drive
Intel i7 4790K MSI MPower Z97 Adata XPG 2x8GB DDR3-2600 Crucial M500 120GB SSD 
Hard DriveHard DriveHard DrivePower
Samsung 830 128GB SSD Cruscial MX200 250GB SSD WD 1TB HDD Seasonic M12II Evo 750W 
  hide details  
Reply
post #3 of 4
Thread Starter 
I just got "windows resource protection found corrupt files but was unable to fix some of them"

I made a text file to see what it can't repair and it looks like a bunch of media center ui dll files... ?


2013-03-18 11:19:56, Info CSI 000001e9 [SR] Cannot repair member file [l:56{28}]"Microsoft.MediaCenter.UI.dll" of Microsoft.MediaCenter.UI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-03-18 11:19:57, Info CSI 000001eb [SR] Cannot repair member file [l:56{28}]"Microsoft.MediaCenter.UI.dll" of Microsoft.MediaCenter.UI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-03-18 11:19:57, Info CSI 000001ec [SR] This component was referenced by [l:176{88}]"Microsoft-Windows-MediaCenter-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.MediaCenter"
2013-03-18 11:19:57, Info CSI 000001ef [SR] Could not reproject corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\ehome"\[l:56{28}]"Microsoft.MediaCenter.UI.dll"; source file in store is also corrupted
2013-03-18 11:22:22, Info CSI 00000314 [SR] Cannot repair member file [l:56{28}]"Microsoft.MediaCenter.UI.dll" of Microsoft.MediaCenter.UI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-03-18 11:22:22, Info CSI 00000316 [SR] Cannot repair member file [l:56{28}]"Microsoft.MediaCenter.UI.dll" of Microsoft.MediaCenter.UI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-03-18 11:22:22, Info CSI 00000317 [SR] This component was referenced by [l:176{88}]"Microsoft-Windows-MediaCenter-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.MediaCenter"
2013-03-18 11:22:22, Info CSI 0000031a [SR] Could not reproject corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\ehome"\[l:56{28}]"Microsoft.MediaCenter.UI.dll"; source file in store is also corrupted
2013-03-18 11:22:22, Info CSI 0000031c [SR] Repair complete
2013-03-18 11:22:22, Info CSI 0000031d [SR] Committing transaction
2013-03-18 11:22:22, Info CSI 00000321 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired


Everything else said it was fine.
Edited by noeyjerd - 3/18/13 at 9:02am
post #4 of 4
Hello,

I think you are better of just reinstalling W7, just make a backup of all your files you want to keep, and start with a fresh install.

Then if the problem still happens, you know 99.9% its the hardware fault and not drivers/windows
Blazer
(8 items)
 
  
CPUMotherboardRAMHard Drive
Intel i7 4790K MSI MPower Z97 Adata XPG 2x8GB DDR3-2600 Crucial M500 120GB SSD 
Hard DriveHard DriveHard DrivePower
Samsung 830 128GB SSD Cruscial MX200 250GB SSD WD 1TB HDD Seasonic M12II Evo 750W 
  hide details  
Reply
Blazer
(8 items)
 
  
CPUMotherboardRAMHard Drive
Intel i7 4790K MSI MPower Z97 Adata XPG 2x8GB DDR3-2600 Crucial M500 120GB SSD 
Hard DriveHard DriveHard DrivePower
Samsung 830 128GB SSD Cruscial MX200 250GB SSD WD 1TB HDD Seasonic M12II Evo 750W 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD/ATI
Overclock.net › Forums › Graphics Cards › AMD/ATI › Radeon 6950 and atikmpag.sys :(