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: Atikmg.sys bsod


01 Jul 2012   #1

Win 7 64bit Ultimate
 
 
Atikmg.sys bsod

I just wanted to know if this is hardware or driver related.

Thanks!

BugCheck 116, {fffffa80080fa4e0, fffff88004351768, 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
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : atikmpag.sys ( atikmpag+8768 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80080fa4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004351768, 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+8768
fffff880`04351768 4055 push rbp

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`021689c8 fffff880`02d0a000 : 00000000`00000116 fffffa80`080fa4e0 fffff880`04351768 00000000`00000000 : nt!KeBugCheckEx
fffff880`021689d0 fffff880`02d09d87 : fffff880`04351768 fffffa80`080fa4e0 fffffa80`083c1ab0 fffffa80`08648410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02168a10 fffff880`02db0f07 : fffffa80`080fa4e0 00000000`00000000 fffffa80`083c1ab0 fffffa80`08648410 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`02168a40 fffff880`02ddab75 : 00000000`ffffffff 00000000`015d5e05 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02168b20 fffff880`02dd92bb : 00000000`00000102 00000000`00000003 00000000`015d5e05 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`02168b50 fffff880`02dac2c6 : ffffffff`ff676980 fffffa80`08648410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`02168bf0 fffff880`02dd8e7a : 00000000`00000000 fffffa80`08feb980 00000000`00000080 fffffa80`08648410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02168d00 fffff800`03723e6a : 00000000`fffffc32 fffffa80`08b21b50 fffffa80`06a0b040 fffffa80`08b21b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02168d40 fffff800`0347dec6 : fffff880`02f64180 fffffa80`08b21b50 fffff880`02f6efc0 fffff880`02168e40 : nt!PspSystemThreadStartup+0x5a
fffff880`02168d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+8768
fffff880`04351768 4055 push rbp

SYMBOL_NAME: atikmpag+8768

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4f7e4294

FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys


My System SpecsSystem Spec
.

01 Jul 2012   #2

Windows 7 Pro. 64/SP-1
 
 

This is not down my alley but I did find this.
AMD Catalyst
My System SpecsSystem Spec
01 Jul 2012   #3

Windows 7 Home Premium 64 Bit
 
 

My System SpecsSystem Spec
.


02 Jul 2012   #4

Win 7 64bit Ultimate
 
 

In reference to Layback bear: Thank you for the assist but that link is not strictly applicable as I am running an AMD hd 7950.

I was running computations on my video card when this occurred. My system has been running computations 24/7 for days on end without issue, except this one. *Note* my temps have never exceeded 64 C while at full load for days, as monitored by HW monitor, HWinfo64, and aida64extreme (love this iceQ cooler).

The BSOD attachments are attached. I was just checking if anyone could offhandedly tell me what they thought from that WinDebug script.

The pertinent dump is attached separately, Thanks!
My System SpecsSystem Spec
02 Jul 2012   #5

Windows 7 Pro. 64/SP-1
 
 

I have read some where that MSI Afterburner can cause this problem.
My System SpecsSystem Spec
02 Jul 2012   #6

Win 7 64bit Ultimate
 
 

If it was afterburner wouldn't this be a recurring issue? I have literally run my card at 99% load for 7 days straight with afterburner, BOINC (Berkeley Distributed computing application), and HWinfo64 running the entire time without even a hiccup. So all of a sudden Afterburner just got angry?

7 days+ at full load is more than extensive as far as driver/hardware stability is concerned, that I know. Is there any clue in the dump as to what else could have caused this, or is it effectively just a generic "video driver error"?
My System SpecsSystem Spec
02 Jul 2012   #7

Windows 7 Professional x64
 
 

It's unfortunately a generic video card error. Given your drivers are fairly up-to-date, I'd suspect it's a hardware flaw. You may try decreasing the clock speed on the GPU for now, or RMAing it if it's still under warranty. A driver update won't hurt but I doubt it will help.
My System SpecsSystem Spec
03 Jul 2012   #8

Windows 7 Home Premium 64 Bit
 
 

What driver version do you currently have installed? The newer graphics cards have had a lot of problems and the latest driver update was supposed to resolve those. A 0x116 was commonplace with those cards with 12.4 or 12.5 installed, especially if running multiple monitors.


Device Concerns
Code:
AODDriver4.1	ROOT\LEGACY_AODDRIVER4.1\0000	This device is not present, is not working properly, or does not have all its drivers installed.

Software Concerns:
Code:
Start Menu\Programs\MSI Afterburner	BEAST\Michael:Start Menu\Programs\MSI Afterburner	BEAST\Michael
Start Menu\Programs\MSI Kombustor 2.3	Public:Start Menu\Programs\MSI Kombustor 2.3	Public
  • MSI Afterburner/RivaTuner is known to cause instability with systems. Please remove the software.

    Software based overclocking is not reliable because it does not provide the proper voltage settings through the BIOS for the overclock to work.

Analysis
BugCheck 0x124
You have a 0x124 hardware bugcheck. If the system is still under warranty, I would recommend sending it in to have diagnostic tests done and any bad hardware replaced.

warning   Warning
Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!

For your hardware stop 0x124 crash, read through Stop 0x124 - what it means and what to try and use the following hardware checks to supplement that link.
  • If you are overclocking any hardware, please stop.

  • If you have an SSD, make sure the following are up to date:
    • SSD firmware
    • BIOS Version
    • Chipset Drivers
    • Hard disk controller drivers/SATA drivers
    • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

  • Run all but the advanced tests with SeaTools for HDDs.
    SeaTools for Windows

    SeaTools for DOS
  • Monitor temperatures during the following tests.
    Use the following programs to monitor the temperatures.
  • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

    For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
    1. Shut down and turn off your computer.
    2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
    3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
    4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
    Once these steps have been followed, it is safe to remove and replace components within your computer.

Remember to read closely through Stop 0x124 - what it means and what to try for the crash.
My System SpecsSystem Spec
03 Jul 2012   #9

Win 7 64bit Ultimate
 
 

What is AOD driver, if I do not need it I will completely remove it. Please advise.

Hopefully this BSOD is from Catalyst 12.4 being my current driver version. I am upgrading to 12.7 as soon as it is no longer a beta driver.

-My memory is confirmed stable using Memtest86+ for at least 7 full passes (about 7-9 hrs). and win-diagnostic comes up with nothing.

-CPU is prime stable for 12+ hours and never exceeds 50 C as monitored by HWmonitor

-GPU/VGA is 8 hours furmark extreme burn stable, never exceeding 70 C, How would you recommend I OC my VGA through the Bios???

-If you are referring to old dump files for the 0x124 bugcheck then it is probably from Overclocking. As I stated before, no other dump is pertinent as all the most recent ones except 7-1-12 are from known cause. The rest are all much older and have been dealt with.

Thanks!
My System SpecsSystem Spec
03 Jul 2012   #10

Windows 7 Pro. 64/SP-1
 
 

I mentioned MSI After Burner because of the problems I had with it dropping my video driver and recovering in a second or so. No blue screen. If I wasn't there to see it I would of never known it happened. Of course that doesn't mean you have the same problem. I removed it REVO and all its settings I it hasn't happened again. Removing it for testing helps others help you. You can always install it again if you so desire.
My System SpecsSystem Spec
Reply

 Atikmg.sys bsod




Thread Tools



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 12:44 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