Overclock.net › Forums › Graphics Cards › AMD/ATI › 4870x2 BSOD on startup "atikmpag.sys"
New Posts  All Forums:Forum Nav:

4870x2 BSOD on startup "atikmpag.sys"

post #1 of 14
Thread Starter 
After researching my issue a bit, it sounds like my video card may have died on me. Just wondering if anyone else has had this issue with ATI cards and if you were able to fix it before I buy a new card. Thanks!

A little background I guess:

I started getting BSODs when attempting to run mumble and thought somehow my drivers had become corrupt because various windows weren't behaving properly (not minimizing or coming to the front), so I uninstalled CCC and drivers and cleaned them up with both Driver Cleaner Pro and Driver Sweeper. I now BSOD before I even get into Windows with the drivers installed, though I can boot into safe mode or into normal Windows without them.

I haven't run any tests on my memory, but I tried booting with one stick at a time and it's the same story, so either they're both ok or both bad.
Edited by Swifterzor - 4/23/12 at 4:31pm
    
CPUMotherboardGraphicsRAM
Q6600 G0 @ 3.8ghz 1.45v VID 1.2625 Asus P5Q Pro P45 HD 7850 (2x2) 4gb Gskill 
Hard DriveOptical DriveOSMonitor
(2) 250gb WD RAID0 + 1.5TB Seagate + 1TB Seagate Lite On 20x dvd-rw Windows 7 Dell 24" E248WFP 1920x1200 
MonitorKeyboardPowerCase
Asus 24" G15 650w Antec Antec 900 
MouseAudio
G7 Sennheiser HD212 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Q6600 G0 @ 3.8ghz 1.45v VID 1.2625 Asus P5Q Pro P45 HD 7850 (2x2) 4gb Gskill 
Hard DriveOptical DriveOSMonitor
(2) 250gb WD RAID0 + 1.5TB Seagate + 1TB Seagate Lite On 20x dvd-rw Windows 7 Dell 24" E248WFP 1920x1200 
MonitorKeyboardPowerCase
Asus 24" G15 650w Antec Antec 900 
MouseAudio
G7 Sennheiser HD212 
  hide details  
Reply
post #2 of 14
Can you please zip up the dumps and attach the zip here?

You can find them by navigating to C:/Windows/Minidump (or C:/Windows and will be named MEMORY.DMP). Once you've navigated to the Minidump folder, put all of the dump files in a zip and attach them here.
post #3 of 14
Thread Starter 
Minidump.zip 794k .zip file

Here it is, thanks for looking into it for me. smile.gif
Edited by Swifterzor - 4/23/12 at 4:31pm
    
CPUMotherboardGraphicsRAM
Q6600 G0 @ 3.8ghz 1.45v VID 1.2625 Asus P5Q Pro P45 HD 7850 (2x2) 4gb Gskill 
Hard DriveOptical DriveOSMonitor
(2) 250gb WD RAID0 + 1.5TB Seagate + 1TB Seagate Lite On 20x dvd-rw Windows 7 Dell 24" E248WFP 1920x1200 
MonitorKeyboardPowerCase
Asus 24" G15 650w Antec Antec 900 
MouseAudio
G7 Sennheiser HD212 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Q6600 G0 @ 3.8ghz 1.45v VID 1.2625 Asus P5Q Pro P45 HD 7850 (2x2) 4gb Gskill 
Hard DriveOptical DriveOSMonitor
(2) 250gb WD RAID0 + 1.5TB Seagate + 1TB Seagate Lite On 20x dvd-rw Windows 7 Dell 24" E248WFP 1920x1200 
MonitorKeyboardPowerCase
Asus 24" G15 650w Antec Antec 900 
MouseAudio
G7 Sennheiser HD212 
  hide details  
Reply
post #4 of 14
NOTE: If overclocking, please reset the system to default values while troubleshooting it. This includes CPU, RAM, GPU overclocking. You're more than welcome to put your stocks back to clock after we've diagnosed your issues!!!!!

First off, after checking your loaded drivers list, your ASACPI.sys (Asus ATK0110 ACPI Utility, a known BSOD maker in Win7. Also a part of the Asus PCProbe and AISuite Utilities) is dated from 2005. The pre-2009 driver is a very large causer of BSODs in the win7 environment, so update that here.

Second, SPTD.sys is listed, this is a Daemon Tools / Alcohol 120 virutalization driver, and is a very big cause of BSODs in the Windows 7 environment. Please uninstall Daemon Tools (or whatever virtutaluzation program you're using), and use DuplexSecure's SPTD uninstaller to fully remove the driver from your system. Alternatives for burning and mounting are Power ISO and ImgBurn.

The first thing I recommend doing if overclocks aren't the issue is fully uninstalling and reinstalling your AMD video card drivers, as a bad driver installation can cause 116 bugchecks, especially since the culprit is being pointed to atikmpag.sys (nVidia video card drivers). If these issues started happening after a driver update, rollback the video card drivers you installed to an earlier version that worked previously without issue.

If drivers do not help, your issue may be heat related, inadequate cooling, dust buildup in the fans or pci-e slot, so make sure your rig is being cooled adequately.

Run Furmark to test your video card to ensure that the card(s) itself is running as intended:
Quote:
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

The following hardware issues can cause a TDR event:
Quote:
- Failing overclock on CPU or GPU (stop overclocking)
- Bad sector in memory resulting in corrupt data being communicated between GPU and the system (either video or system memory) ( MemTest and a video memory stress test: |MG| Video Memory Stress Test 1.7.116 Download )
- Corrupt hard drive/windows install resulting in corruption to the system registry or the page file (Hard drive diagnostics ( HD Diagnostic ), reset your pagefile

Memtest download to test your RAM: http://www.memtest86.com/

To "reset" the pagefile, follow these instructions:
Quote:
Use this technique to "reset" your pagefile:
a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
-Then click on the Advanced tab,
-then on the Performance Settings Button,
-then on the next Advanced tab,
-then on the Virtual Memory Change button.
b ) In this window, note down the current settings for your pagefile (so you can restore them later on).
-Then click on the "No paging file" radio button, and
- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.
-Click OK to exit the dialogs.
c ) Reboot (this will remove the pagefile from your system)
d ) Then go back in following the directions in step a ) and re-enter the settings that you wrote down in step b ). Follow the steps all the way through (and including) the reboot.
e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.

Run System File Checker:
Quote:
SFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.

- Over heating of GPU or CPU again resulting in corrupt data being communicated. (Point a house fan at the video card, take temperature readings from the card with an IR detector (or your finger - but be very, very careful!!!)

- GPU failure due to any sort of issue from insufficient power(VERY common) to heat. (check the power leads, use a multimeter to check the power output, try another, more powerful PSU)

The following software issues can cause a TDR event:
Quote:
-Incompatible drivers of any sort (either GPU, sound, etc) ( http://www.microsoft.com/windows/com...s/default.aspx )
-Messy registry (I doubt this and don't approve of registry cleaners)
-Known vista issues resounding around multiple displays, aero, dreamscape, and various display drivers. (none known for this OS)
-Known vista issues that sometimes cause corrupt information to be sent to the video card from system memory (will be addressed completely in SP2, has had various fixes applied since vista's release) (none known for this OS)
-Bad direct x files (uninstall, then reinstall DirectX)
-bad system files (System File Checker - was run above)
-Bad driver (some drivers will cause an event due to internal bugs, however these are not nearly as common as many think due to all of the previous things causing the same symptom) - (remove all 3rd party programs and check to be sure drivers aren't loading. Then install only the necessary 3rd party stuff, and ensure it's the latest version and that it's compatible with Windows 7)

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


Loading Dump File [C:\Users\BSOD\Downloads\042312-21715-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\MS Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`03a02000 PsLoadedModuleList = 0xfffff800`03c3fe70
Debug session time: Sun Apr 22 21:55:22.543 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:50.838
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8007c32010, fffff880043b1ae4, 0, 2}

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
---------

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

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

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


FAULTING_IP: 
atikmpag+7ae4
fffff880`043b1ae4 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`023b89c8 fffff880`0445e000 : 00000000`00000116 fffffa80`07c32010 fffff880`043b1ae4 00000000`00000000 : nt!KeBugCheckEx
fffff880`023b89d0 fffff880`0445dd0a : fffff880`043b1ae4 fffffa80`07c32010 fffffa80`0723ad50 fffffa80`0724c010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`023b8a10 fffff880`04504f07 : fffffa80`07c32010 00000000`00000000 fffffa80`0723ad50 fffffa80`0724c010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`023b8a40 fffff880`0452eb75 : 00000000`ffffffff 00000000`0000099f 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`023b8b20 fffff880`0452d2bb : 00000000`00000102 00000000`00000000 00000000`0000099f 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`023b8b50 fffff880`045002c6 : ffffffff`ff676980 fffffa80`0724c010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`023b8bf0 fffff880`0452ce7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`06a72548 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`023b8d00 fffff800`03d126fa : 00000000`07b4db84 fffffa80`06dc4b60 fffffa80`03ceb5f0 fffffa80`06dc4b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`023b8d40 fffff800`03a50b46 : fffff880`03163180 fffffa80`06dc4b60 fffff880`0316dfc0 4e4f2b7a`52676a61 : nt!PspSystemThreadStartup+0x5a
fffff880`023b8d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+7ae4
fffff880`043b1ae4 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
---------

post #5 of 14
Thread Starter 
Awesome, thanks for the help. The issue isn't resolved yet, though I reallllly appreciate your time! biggrin.gif I performed the updates and tested my memory for a bit with no errors. I actually have it working now with only 1 GPU as I disabled one in the device manager. When I attempt to enable the other one, I get the same BSOD (attached). CrossfireBSODDump.zip 26k .zip file
    
CPUMotherboardGraphicsRAM
Q6600 G0 @ 3.8ghz 1.45v VID 1.2625 Asus P5Q Pro P45 HD 7850 (2x2) 4gb Gskill 
Hard DriveOptical DriveOSMonitor
(2) 250gb WD RAID0 + 1.5TB Seagate + 1TB Seagate Lite On 20x dvd-rw Windows 7 Dell 24" E248WFP 1920x1200 
MonitorKeyboardPowerCase
Asus 24" G15 650w Antec Antec 900 
MouseAudio
G7 Sennheiser HD212 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Q6600 G0 @ 3.8ghz 1.45v VID 1.2625 Asus P5Q Pro P45 HD 7850 (2x2) 4gb Gskill 
Hard DriveOptical DriveOSMonitor
(2) 250gb WD RAID0 + 1.5TB Seagate + 1TB Seagate Lite On 20x dvd-rw Windows 7 Dell 24" E248WFP 1920x1200 
MonitorKeyboardPowerCase
Asus 24" G15 650w Antec Antec 900 
MouseAudio
G7 Sennheiser HD212 
  hide details  
Reply
post #6 of 14

Try disabling ULPS.

Mugendramon
(18 items)
 
  
CPUMotherboardGraphicsRAM
i5 4670k ASrock Z87 Extreme6 R9 290 Crossfire Samsung 8GB DDR3 2133mhz 
Hard DriveHard DriveCoolingCooling
WD Black 1T Samsung Spinpoint F3 1 TB EK Supreme HF Rev 2.0  HW GTX 360 Rad 
CoolingOSMonitorPower
EK Acetal waterblock W7 64 bit Yamakasi Catleap Q270 2560x1440p Corsair AX850 
CaseAudio
Corsair 800D Creative Titanium HD  
  hide details  
Reply
Mugendramon
(18 items)
 
  
CPUMotherboardGraphicsRAM
i5 4670k ASrock Z87 Extreme6 R9 290 Crossfire Samsung 8GB DDR3 2133mhz 
Hard DriveHard DriveCoolingCooling
WD Black 1T Samsung Spinpoint F3 1 TB EK Supreme HF Rev 2.0  HW GTX 360 Rad 
CoolingOSMonitorPower
EK Acetal waterblock W7 64 bit Yamakasi Catleap Q270 2560x1440p Corsair AX850 
CaseAudio
Corsair 800D Creative Titanium HD  
  hide details  
Reply
post #7 of 14
It's a 116 bugheck again with the same culprit. A 116 bugcheck happens when the display driver cannot recover from crashing, when it can recover, you won't get that bugcheck, the screen will just go black and come with saying "the display driver has crashed but has successfully recovered". When you do crash however, you get the 116 TDR bugcheck.

If you're crashing right after you enable crossfire, it could CCC is the issue here, and I'd recommend fully uninstalling your AMD drivers, and re-installing them if you haven't already. If you already have, perhaps try a previous version than you're consistently trying if you're installing the latest version, and if you're not, install the latest version.

Either that, or the card itself could be the issue here. Have you tested the card that's failing to enable with crossfire alone?
post #8 of 14
my 4850 was giving me issues like that alot on some of the latest drivers. how ever i found the 12-1 drivers to like my card. it might help a lot. how ever on a side note. if with no drivers installed it works fine but when you install the drivers you get errors when you load windows it could be the second gpu has gone bad. when you install the drivers it will automatically enable crossfire.
post #9 of 14
Thread Starter 
Quote:
Originally Posted by E-Peen View Post

Have you tested the card that's failing to enable with crossfire alone?


That will be my next step. I've tried a few different sets of drivers - 11.11, 11.12, and 12-3 all with the same result.

ULPS was already set to 0 in my registry.
Edited by Swifterzor - 4/23/12 at 6:18pm
    
CPUMotherboardGraphicsRAM
Q6600 G0 @ 3.8ghz 1.45v VID 1.2625 Asus P5Q Pro P45 HD 7850 (2x2) 4gb Gskill 
Hard DriveOptical DriveOSMonitor
(2) 250gb WD RAID0 + 1.5TB Seagate + 1TB Seagate Lite On 20x dvd-rw Windows 7 Dell 24" E248WFP 1920x1200 
MonitorKeyboardPowerCase
Asus 24" G15 650w Antec Antec 900 
MouseAudio
G7 Sennheiser HD212 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Q6600 G0 @ 3.8ghz 1.45v VID 1.2625 Asus P5Q Pro P45 HD 7850 (2x2) 4gb Gskill 
Hard DriveOptical DriveOSMonitor
(2) 250gb WD RAID0 + 1.5TB Seagate + 1TB Seagate Lite On 20x dvd-rw Windows 7 Dell 24" E248WFP 1920x1200 
MonitorKeyboardPowerCase
Asus 24" G15 650w Antec Antec 900 
MouseAudio
G7 Sennheiser HD212 
  hide details  
Reply
post #10 of 14
Alright, try testing the problematic card alone.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD/ATI
Overclock.net › Forums › Graphics Cards › AMD/ATI › 4870x2 BSOD on startup "atikmpag.sys"