Getting bsod when playing games in fullscreen

[nicobile]

Hi, im having this problem for a while now and cant seem to find the reason.

All games, except League of Legends, get a bsod after more or less 15 or 20 minutes of running. When i change them to a windowed mode all is fine. I remember a while ago (before this problem started) the games minimize all the time when in fullscreen without there being any popup or anything that could cause it. I really dont remember what i did, aside that i downloaded Razer game Booster (not a very good program) which ended that particular problem.

I already tried deleting the drivers from Catalyst Control Center, but the problem persist.

I have all my System specs filled by the program of this site, do you need me to copy them here? Anything else i should provide you with?

Thanks in advance!!!

 

[Arc]

Hi nicobile.

We need to see some more information. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Upload the data in your next post.

 

[nicobile]

Thanks for the quick reply, and sorry about the missing info, i didnt saw that post explaining what i should include in the thread.

Hope i uploaded it correctly!

 

[Arc]

First, Uninstall your installed version of the display driver.

• How-To Uninstall AMD Catalyst Drivers From A Windows Based System

Then clean up any possible leftover.

• http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html

Then install version 13.9 WHQL only.

• Previous AMD Catalyst? Display Drivers

When the driver is properly applied, Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
You have two HD 6900 series GPUs. It would be better if you run furmark on them one by one.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Let us know the results.
_____________________________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 119, {1, a27c83f, a27c842, a27c841}

*** 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+45b36 )

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

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

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000001, The driver has reported an invalid fence ID.
Arg2: 000000000a27c83f
Arg3: 000000000a27c842
Arg4: 000000000a27c841

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x119

PROCESS_NAME:  System

CURRENT_IRQL:  9

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

DPC_STACK_BASE:  FFFFF88003485FB0

LAST_CONTROL_TRANSFER:  from fffff880043cc22f to fffff80003a90bc0

STACK_TEXT:  
fffff880`0347e518 fffff880`043cc22f : 00000000`00000119 00000000`00000001 00000000`0a27c83f 00000000`0a27c842 : nt!KeBugCheckEx
fffff880`0347e520 fffff880`0774fec5 : 00000000`006d1d47 00000000`0a27c83f 00000000`00000000 00000000`0a27c842 : watchdog!WdLogEvent5+0x11b
fffff880`0347e570 fffff880`077501f2 : fffffa80`0f1f1000 fffff880`0347e6b0 fffff880`000011ac fffff880`0347e6b0 : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad
fffff880`0347e5a0 fffff880`0774ff82 : 00000000`0a27c83f fffff880`07750083 fffffa80`0f1f1000 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterruptWorker+0x25e
fffff880`0347e5f0 fffff880`0765713f : fffffa80`0e4b1480 00000000`00000000 00000000`0f0b2001 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff880`0347e620 fffff880`07943b36 : 00000000`00000202 00000000`00000002 fffff880`0347e6d9 00000000`00000000 : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff880`0347e650 00000000`00000202 : 00000000`00000002 fffff880`0347e6d9 00000000`00000000 fffff880`0347e710 : atikmpag+0x45b36
fffff880`0347e658 00000000`00000002 : fffff880`0347e6d9 00000000`00000000 fffff880`0347e710 fffff800`04007b7f : 0x202
fffff880`0347e660 fffff880`0347e6d9 : 00000000`00000000 fffff880`0347e710 fffff800`04007b7f fffffa80`0e4b1480 : 0x2
fffff880`0347e668 00000000`00000000 : fffff880`0347e710 fffff800`04007b7f fffffa80`0e4b1480 fffff880`07758127 : 0xfffff880`0347e6d9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmpag+45b36
fffff880`07943b36 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  atikmpag+45b36

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52a231d9

FAILURE_BUCKET_ID:  X64_0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_atikmpag+45b36

BUCKET_ID:  X64_0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_atikmpag+45b36

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x119_1_driver_reported_invalid_fence_id_atikmpag+45b36

FAILURE_ID_HASH:  {1d656d04-b896-4c50-1a4b-ca7fd5789058}

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

9: kd> lmvm atikmpag
start             end                 module name
fffff880`078fe000 fffff880`0799e000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Sat Dec 07 01:51:45 2013 (52A231D9)
    CheckSum:         0009FEFF
    ImageSize:        000A0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Silicon Image
​

 

[nicobile]

thanks for the reply

I did all the steps you mention, I still havent try a game on fullscreen, but now i have another problem. I cant seem to get the resolution right. I have a 27 inch Dell monitor, but the biggest i can select is 1920x1080, so i get like two inches of black on the borders, do you know how can i select the adecuate resolution

 

[nicobile]

Well, i just tried playing Rome 2 in fullscreen, in less than 5 minutes the game crashed into a blue screen. Sad face. What more could i try?

 

[Arc]

What are the results of the tests?

 

[nicobile]

Sorry, for the long time to answer, spent sunday on my family house.

i dont know exactly what things of Furmark you would like to know, but the cards never heated, when they touch the 90ºC mark, they started using the vent system a lot more, but after that, i let the test go 3 more minutes, and never pass 90ºC.

Today i tested same games, and i got other results. Rome, while using crossfire didnt get the bsot (the game is not optimized for this, in fact, it makes the game quite unplayable), i didnt spend a lot of time with that particular game because its almost imposible to use in crossfire. Then, i played Shadowrun, still with the two cards at the same time. Not a problem in a couple of hours of "test".

I remember that on saturday i tried playing Diablo 3 without crossfire enable, and i also got the bsot in less than 10 minutes.

Any other info i could give you guys?

Thanks again for the help

 

[Arc]

If furmark did not cause a BSOD or screen artifacts, it is all good.

From your post it appears that the situation is better now. Let us know for any further issue.

 

[nicobile]

My only worry is that i have the primary card with some technical issue. Could that be the problem?

I said this because of at least 2 games that doesnt work without crossfire which before worked perfectly

 

[essenbe]

You say you have one card with 'some technical issue'. What technical issue is that and depending on what the issue is, yes it could cause that. Try taking the card with issues out and seeing if your problem continues.

 

[nicobile]

I dont know if it has any technical issues, i thought that could be the reason for this.

I just had some time, so i tried playing civ 5, i got the bsot after 10 minutes, im still using the drivers you guys said, and i havent change anything.

Any idea?

thanks again!

 

[essenbe]

Would you tell me specifically the make, model of your graphics cards and the make and model and size of your power supply please.

 

[nicobile]

The graphic cards are amd radeon 6950 and the power supply is the standard used by alienware/dell, it have 875 watts, to be more exact, Cosmic Black ALX - 875 Watt Power Supply

Thanks!

 

[essenbe]

Have you physically pulled one card out of the machine and tried running it that way? It almost sounds like it is not getting enough power from the PSU.

 

[nicobile]

No, i never did that because its quite weird the way the hard is setup inside the alienware mobo (not bad weird, but, neat and in great order). I actually never mess with any hardware parts in this pc. I did open, look around, clean,etc. But thats about it.

The mobo also have a water cooling system, thats something i fail to mention before, sorry.

This rig worked fine for 3 years, give or take. Could it really be a power problem? I used to play really demanding games in ultra and max resolution and i never had a problem.

If you think i should still take one of the cards out, i will. I want to solve this problem, is making me an insane person right now

 

[essenbe]

If your cards are water cooled, I wouldn't suggest it unless you know what you are doing. With the temps you got running furmark, I doubt they are water cooled. 90C is entirely too hot. I have a 6950 in another rig and I can't make it go over 68C. To answer your question, yes the power supply can cause that. I'm not telling you that is the cause, only one possibility. But if your hardware, especially graphics cards or CPU get too hot, the computer will shut down to protect itself. If the power supply won't provide enough power for your components, it will crash. Power supplies can degrade over a couple of years and especially the cheaper brands. You also need to know how many amps it puts out and if it is single or multiple rails. As you said, it has run well for a few years, so obviously something has changed. We just need to figure out what it was that changed. If you would rather wait on pulling the cards and running them one at a time, there are several other tests we could do first, but they are rather time consuming. I would like you to get a CPU temp monitoring program and a GPU monitoring program and monitor both constantly as you use the computer. Most cards come with monitoring programs, but if you don't have one MSI Afterburner will. It is basically an overclocking utility, but is good at monitoring things. You can set a custom fan profile with it too, as well as get temp, fan and other on screen readings too. I like using Core Temp for CPU temps, or Real Temp is good too. All these programs are free, but as with many of the free programs, be sure to check for the add ons they try to download with them. You can opt out of downloading the add ons. You can also run memtest86+ http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html . I would like you to run it for 8 full passes all at one time or until you get an error. Even 1 error and you can stop the test. Each Pass is 10 tests, each pass tests a different thing and each test checks something different. So, it takes 8 full passes all at one time to completely test your ram. It will take 10-12 hours to run it, so it is best run overnight.