Blue Screen invovling atikmpag.sys

Dizzasta · December 2013

After playing NS2 for about an hour or two today, I got a blue screen of death. I have done a quick search on BSOD related to atikmpag.sys and most of them is fixed by installing the latest graphics drivers, however I have already installed the latest drivers and have no idea what else I can do to fix it. Here is my dump file and my tech support.zip. I hope I have provided enough information, if not please let me know what else is needed and I hope we would be able to solve this problem together. Thanks for reading.

My computer specs:
AMD Phenom II X6 1035T processor 2.60GHz
8GB of RAM
Windows 7 Home Premium Service Pack 1 64bit
AMD Radeon HD 7770 Series
DirectX 11

IronHorse · December 2013

Try using DX9 fullscreen, its the only officially supported method, as DX11 and opengl are still in BETA.

Obraxis · December 2013

Also make sure your PC is not dusty inside. Ns2 will push your hardware harder than most games.

Dizzasta · December 2013

IronHorse wrote: »

Try using DX9 fullscreen, its the only officially supported method, as DX11 and opengl are still in BETA.

Sorry for the late reply and the confusion. I am currently using DirectX 9 in game but my graphics card supports DX11. IHere are some screenshots of my graphical settings in-game.

vn9luYo.jpg?1

Obraxis wrote: »

Also make sure your PC is not dusty inside. Ns2 will push your hardware harder than most games.

I just replaced my old faulty hard drive with a new one and cleaned the computer with an air duster. While im playing games I also have a mini usb fan blowing at my computer so I think my computer should be able to run NS2 without overheating but just to be sure I will do a test with speedfan later.

OuchOfDeath · December 2013

Natural Selection 2 can't cause blue screens. What most likely happened is either a bug got triggered in the GPU driver, or you hit high temperature levels, or your GPU is malfunctioning. atikmpag.sys is part of your GPU driver, so the issue most likely is something to do with your GPU.

Check your GPU temperature (you can do so in AMD Catalyst), and try a driver back one or two versions.

Dizzasta · December 2013

OuchOfDeath wrote: »

Natural Selection 2 can't cause blue screens. What most likely happened is either a bug got triggered in the GPU driver, or you hit high temperature levels, or your GPU is malfunctioning. atikmpag.sys is part of your GPU driver, so the issue most likely is something to do with your GPU.

Check your GPU temperature (you can do so in AMD Catalyst), and try a driver back one or two versions.

Thanks for the reply, it could most likely be a case of my GPU overheating since it reaches 100+ temperatures after most of the games I currently play. However, would you recommend using the BETA drivers provided by AMD?

Dizzasta · December 2013

Thanks for the reply, it could most likely be a case of my GPU overheating since it reaches 100+ temperatures after most of the games I currently play. However, would you recommend using the BETA drivers provided by AMD?

Ok so after I posted that reply, I decided to launch up NS2 to give it another try. However, 5-10mins into the game, I got the BSOD again this time knowing for sure that my GPU is not overheating as I checked Speedfan before launching the game and it said it was about 50 degrees celsius.
Now to try reverting back my driver.

ezekel · December 2013

OuchOfDeath wrote: »

Natural Selection 2 can't cause blue screens. What most likely happened is either a bug got triggered in the GPU driver, or you hit high temperature levels, or your GPU is malfunctioning. atikmpag.sys is part of your GPU driver, so the issue most likely is something to do with your GPU.

Check your GPU temperature (you can do so in AMD Catalyst), and try a driver back one or two versions.

oh it can cause bluescreens, it can also cause pc lockup

If you immediately leave a server and then immediately hit exit at the main menu you can lock your entire computer (requires forced shutdown)

BSODs generally happen because the game is really smashing on the cpu, so you can actually find out that your cpu may need more volts going to it to keep up with ns2

Dizzasta · December 2013

ezekel wrote: »

OuchOfDeath wrote: »

Natural Selection 2 can't cause blue screens. What most likely happened is either a bug got triggered in the GPU driver, or you hit high temperature levels, or your GPU is malfunctioning. atikmpag.sys is part of your GPU driver, so the issue most likely is something to do with your GPU.

Check your GPU temperature (you can do so in AMD Catalyst), and try a driver back one or two versions.

oh it can cause bluescreens, it can also cause pc lockup

If you immediately leave a server and then immediately hit exit at the main menu you can lock your entire computer (requires forced shutdown)

BSODs generally happen because the game is really smashing on the cpu, so you can actually find out that your cpu may need more volts going to it to keep up with ns2

Thanks for the info. I reinstalled my video drivers back to the original one(in a disk that came with the graphics card) and I was able to play NS2 for 3 hours straight. However, I will still update y'all if I still get any more BSOD. Thanks to everyone that helped.

DC_Darkling · December 2013

Just to add it here.. Some info.

First, technicly ns2 can never EVER BSOD your computer. It can however push a driver, like a graphics driver, in a wrong way so the driver BSODs. In this example both are at fault. NS2 shouldnt push the driver in that way, and if ns2 tries the driver should say 'hell no'.

Below is a small analysis of your crash dump.

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800b2e4010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004231e80, 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+ae80
fffff880`04231e80 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`027dd9c8 fffff880`04322140 : 00000000`00000116 fffffa80`0b2e4010 fffff880`04231e80 00000000`00000000 : nt!KeBugCheckEx
fffff880`027dd9d0 fffff880`04321e4a : fffff880`04231e80 fffffa80`0b2e4010 fffffa80`0927db70 fffffa80`0ac1c010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`027dda10 fffff880`11d2ff13 : fffffa80`0b2e4010 00000000`00000000 fffffa80`0927db70 fffffa80`0ac1c010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`027dda40 fffff880`11d59cf1 : 00000000`ffffffff 00000000`000370f2 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`027ddb20 fffff880`11d58437 : 00000000`00000102 00000000`00000000 00000000`000370f2 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`027ddb50 fffff880`11d2b2d2 : ffffffff`ff676980 fffffa80`0ac1c010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`027ddbf0 fffff880`11d57ff6 : 00000000`00000000 fffffa80`076f02a0 00000000`00000080 fffffa80`0ac1c010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`027ddd00 fffff800`02f2b2ea : 00000000`fffffc32 fffffa80`0a7928b0 fffffa80`069ab9e0 fffffa80`0a7928b0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`027ddd40 fffff800`02c7f8e6 : fffff880`0308f180 fffffa80`0a7928b0 fffff880`0309a040 fffff880`027dde40 : nt!PspSystemThreadStartup+0x5a
fffff880`027ddd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+ae80
fffff880`04231e80 4883ec28 sub rsp,28h

SYMBOL_NAME: atikmpag+ae80

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5253fa42

FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

IronHorse · December 2013

Dizzasta wrote: »

it could most likely be a case of my GPU overheating since it reaches 100+ temperatures after most of the games I currently play.

Uhhh.. you should be having ~85 degrees Celsius, maximum, at 100% load.. and ~40 at idle.
Your GPU will begin throttling to save itself from melting, should it go much more beyond those numbers. (generally around 90-100 iirc)

Dizzasta wrote: »

my GPU is not overheating as I checked Speedfan before launching the game and it said it was about 50 degrees celsius.

Temps during idle (before launching the game) do not represent 100% load that you would find in game. Often, even Alt Tabbing will reduce those temps very fast just when you go to see speedfan while in game :-P

DC_Darkling · December 2013

overheating would indeed be consistant with the error I pulled out the debug log.

Blue Screen invovling atikmpag.sys

Comments