atikmpag.sys windows 7 64 bit bsod

M

mrppv

Member
Joined
Dec 30, 2014
Posts
6
· OS - Windows 7
· 64 Bit
· What was original installed OS on system? No
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Purchased from retailer
· Age of system (hardware) Brand New
· Age of OS installation - have you re-installed the OS? Yes


· CPU I5 4690k (Not overclocked)
· Video Card Gigabyte HD 7970 3 gigs vram (Not overclocked)
· MotherBoard - Asus Sabertooth z97 Mk2
· Power Supply - Antec 650w


· System Manufacturer
· Exact model number (if laptop, check label on bottom) No model Number. I built it myself


· Laptop or Desktop? Desktop
 

Attachments

mrppv said:
· OS - Windows 7
· 64 Bit
· What was original installed OS on system? No
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Purchased from retailer
· Age of system (hardware) Brand New
· Age of OS installation - have you re-installed the OS? Yes


· CPU I5 4690k (Not overclocked)
· Video Card Gigabyte HD 7970 3 gigs vram (Not overclocked)
· MotherBoard - Asus Sabertooth z97 Mk2
· Power Supply - Antec 650w


· System Manufacturer
· Exact model number (if laptop, check label on bottom) No model Number. I built it myself


· Laptop or Desktop? Desktop
Click to expand...

I also ran Prime95 and a gpu stress test(they both passed) flashed the mobo bios to the latest version. I have also expanded the atimpag.sys file in cmd and reinstalled the newest gpu drivers multiple times
 
mrppv said:
minidump during driver verifier attached
Click to expand...


Ran WhoCrashed


[FONT=Segoe UI, Arial]On Mon 12/29/2014 8:20:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122914-17409-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]atikmpag.sys[/FONT] (atikmpag+0xB848)
Bugcheck code: 0x116 (0xFFFFFA800BA310E0, 0xFFFFF88004699848, 0x0, 0x2)
Error: [FONT=Segoe UI, Arial]VIDEO_TDR_ERROR[/FONT]
file path: C:\Windows\system32\drivers\atikmpag.sys
product: [FONT=Segoe UI, Arial]AMD driver[/FONT]
company: [FONT=Segoe UI, Arial]Advanced Micro Devices, Inc.[/FONT]
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: [FONT=Segoe UI, Arial]Advanced Micro Devices, Inc. VIDEO_TDR_ERROR


I already reinstalled the latest drivers like 100 times
[/FONT]
[/FONT]
 
I would suggest removing any Asus bloatware, it can cause unexpected problems.

Code: 
2: kd>[COLOR=#008000] !sysinfo machineid[/COLOR]
Machine ID Information [From Smbios 2.8, DMIVersion 39, Size=3852]
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = 2012
BiosReleaseDate = [COLOR=#ff0000]09/30/2014[/COLOR]
SystemManufacturer = [COLOR=#ff0000]ASUS[/COLOR]
SystemProductName = All Series
SystemFamily = ASUS MB
SystemVersion = System Version
SystemSKU = All
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = SABERTOOTH Z97 MARK 2
BaseBoardVersion = Rev 1.xx

Bugcheck Analysis:

Code: 
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: [COLOR=#ff0000]fffffa800ce584e0[/COLOR], Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: [COLOR=#008000]fffff88004686848[/COLOR], The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000[COLOR=#0000cd]2[/COLOR], Optional internal context dependent data.

The first parameter is a pointer to the address of the TDR_RECOVERY_CONTEXT data structure, which can be viewed in WinDbg if the private symbols for dxgkrnl.sys are loaded. The fourth parameter is a value of a field, to which I believe is stored within the TDR_RECOVERY_CONTEXT and called TimeoutReason.

The second parameter is a pointer to the driver which supposedly caused the crash:

Code: 
2: kd> [COLOR=#008000]u fffff88004686848[/COLOR]
[COLOR=#ff0000]atikmpag+0xb848[/COLOR]:
fffff880`04686848 4883ec28        sub     rsp,28h
fffff880`0468684c 4c8bda          mov     r11,rdx
fffff880`0468684f 41ba010000c0    mov     r10d,0C0000001h
fffff880`04686855 4885c9          test    rcx,rcx
fffff880`04686858 742e            je      atikmpag+0xb888 (fffff880`04686888)
fffff880`0468685a 4885d2          test    rdx,rdx
fffff880`0468685d 7429            je      atikmpag+0xb888 (fffff880`04686888)
fffff880`0468685f e898360000      call    atikmpag+0xeefc (fffff880`04689efc)

Code: 
2: kd> [COLOR=#008000]lmvm atikmpag[/COLOR]

start             end                 module name
fffff880`0467b000 fffff880`04711000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        [COLOR=#ff0000]Fri Nov 21 02:08:54 2014[/COLOR] (546E9EB6)
    CheckSum:         00093077
    ImageSize:        00096000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Have you checked for any Beta drivers? Additionally, have you ran the system in Safe Mode?
 
x BlueRobot said:
I would suggest removing any Asus bloatware, it can cause unexpected problems.

Code: 
2: kd>[COLOR=#008000] !sysinfo machineid[/COLOR]
Machine ID Information [From Smbios 2.8, DMIVersion 39, Size=3852]
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = 2012
BiosReleaseDate = [COLOR=#ff0000]09/30/2014[/COLOR]
SystemManufacturer = [COLOR=#ff0000]ASUS[/COLOR]
SystemProductName = All Series
SystemFamily = ASUS MB
SystemVersion = System Version
SystemSKU = All
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = SABERTOOTH Z97 MARK 2
BaseBoardVersion = Rev 1.xx

Bugcheck Analysis:

Code: 
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: [COLOR=#ff0000]fffffa800ce584e0[/COLOR], Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: [COLOR=#008000]fffff88004686848[/COLOR], The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000[COLOR=#0000cd]2[/COLOR], Optional internal context dependent data.

The first parameter is a pointer to the address of the TDR_RECOVERY_CONTEXT data structure, which can be viewed in WinDbg if the private symbols for dxgkrnl.sys are loaded. The fourth parameter is a value of a field, to which I believe is stored within the TDR_RECOVERY_CONTEXT and called TimeoutReason.

The second parameter is a pointer to the driver which supposedly caused the crash:

Code: 
2: kd> [COLOR=#008000]u fffff88004686848[/COLOR]
[COLOR=#ff0000]atikmpag+0xb848[/COLOR]:
fffff880`04686848 4883ec28        sub     rsp,28h
fffff880`0468684c 4c8bda          mov     r11,rdx
fffff880`0468684f 41ba010000c0    mov     r10d,0C0000001h
fffff880`04686855 4885c9          test    rcx,rcx
fffff880`04686858 742e            je      atikmpag+0xb888 (fffff880`04686888)
fffff880`0468685a 4885d2          test    rdx,rdx
fffff880`0468685d 7429            je      atikmpag+0xb888 (fffff880`04686888)
fffff880`0468685f e898360000      call    atikmpag+0xeefc (fffff880`04689efc)

Code: 
2: kd> [COLOR=#008000]lmvm atikmpag[/COLOR]

start             end                 module name
fffff880`0467b000 fffff880`04711000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        [COLOR=#ff0000]Fri Nov 21 02:08:54 2014[/COLOR] (546E9EB6)
    CheckSum:         00093077
    ImageSize:        00096000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Have you checked for any Beta drivers? Additionally, have you ran the system in Safe Mode?
Click to expand...


I downgraded my drivers to 14.9 also I had klite codec pack installed on my pc that I removed
havent had a bsod yet. I have ran it in safe mode just to remove drivers but thats it
 
mrppv said:
x BlueRobot said:
I would suggest removing any Asus bloatware, it can cause unexpected problems.

Code: 
2: kd>[COLOR=#008000] !sysinfo machineid[/COLOR]
Machine ID Information [From Smbios 2.8, DMIVersion 39, Size=3852]
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = 2012
BiosReleaseDate = [COLOR=#ff0000]09/30/2014[/COLOR]
SystemManufacturer = [COLOR=#ff0000]ASUS[/COLOR]
SystemProductName = All Series
SystemFamily = ASUS MB
SystemVersion = System Version
SystemSKU = All
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = SABERTOOTH Z97 MARK 2
BaseBoardVersion = Rev 1.xx

Bugcheck Analysis:

Code: 
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: [COLOR=#ff0000]fffffa800ce584e0[/COLOR], Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: [COLOR=#008000]fffff88004686848[/COLOR], The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000[COLOR=#0000cd]2[/COLOR], Optional internal context dependent data.

The first parameter is a pointer to the address of the TDR_RECOVERY_CONTEXT data structure, which can be viewed in WinDbg if the private symbols for dxgkrnl.sys are loaded. The fourth parameter is a value of a field, to which I believe is stored within the TDR_RECOVERY_CONTEXT and called TimeoutReason.

The second parameter is a pointer to the driver which supposedly caused the crash:

Code: 
2: kd> [COLOR=#008000]u fffff88004686848[/COLOR]
[COLOR=#ff0000]atikmpag+0xb848[/COLOR]:
fffff880`04686848 4883ec28        sub     rsp,28h
fffff880`0468684c 4c8bda          mov     r11,rdx
fffff880`0468684f 41ba010000c0    mov     r10d,0C0000001h
fffff880`04686855 4885c9          test    rcx,rcx
fffff880`04686858 742e            je      atikmpag+0xb888 (fffff880`04686888)
fffff880`0468685a 4885d2          test    rdx,rdx
fffff880`0468685d 7429            je      atikmpag+0xb888 (fffff880`04686888)
fffff880`0468685f e898360000      call    atikmpag+0xeefc (fffff880`04689efc)

Code: 
2: kd> [COLOR=#008000]lmvm atikmpag[/COLOR]

start             end                 module name
fffff880`0467b000 fffff880`04711000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        [COLOR=#ff0000]Fri Nov 21 02:08:54 2014[/COLOR] (546E9EB6)
    CheckSum:         00093077
    ImageSize:        00096000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Have you checked for any Beta drivers? Additionally, have you ran the system in Safe Mode?
Click to expand...


I downgraded my drivers to 14.9 also I had klite codec pack installed on my pc that I removed
havent had a bsod yet. I have ran it in safe mode just to remove drivers but thats it
Click to expand...


I just got another bsod(atimpag.sys) while playing simpsons hit and run(it was running around 2000fps)
I forced vsync on the game and played it for a few hours and I havent had one bsod. Could this indicate maybe a psu problem
 
The issue is you're playing without vsync which is allowing your GPU to attempt to consistently render 2000 frames per second. That's a lot of frames, and you were probably overheating or just causing too much issue for the display driver.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top