4 Replies Latest reply on Aug 29, 2015 1:02 PM by derekz10

    BF4 crashes Mantle:GR_ERROR_DEVICE_LOST or in DX11: DXGI_ERROR_DEVICE_HUNG due to loosing Fullscreen Ownership

    derekz10

      This has been a problem since the release of BF4 but typically I would get the error as a result of overclocking to high.  Very recently the issue has gotten so severe that I can't play a game for 15-30 minutes before crashing, even using stock clocks.  Google has come up with this question but no answers to this issue.  I believe I've found a cause to the crash and I'd like it to be fixed.

       

      In DX11 the error reads:

      "GetDeviceRemovedReason" failed with DXGI_ERROR_DEVICE_HUNG

      With Mantle the error is shown as:

      Mantle function "grWsiWinReleaseFullscreenOwnership(displayHandle)" failed with GR_ERROR_DEVICE_LOST. GPU:

       

      Looking at the event viewer I see these events as the time of the crash:

      1. A request to disable the Desktop Window Manager was made by process (4)
        • Event ID: 9010
        • Level: Information
        • Logged: 8/26/2015 8:48:12 PM

      2. The Desktop Window Manager was unable to start because composition was disabled by a running application

        • Event ID: 9013
        • Level: Information
        • Logged: 8/26/2015 8:48:12 PM

      3. Windows Error Reporting - A problem with your video hardware caused Windows to stop working correctly.

        • Event ID: 1001
        • Level: Information
        • Logged: 8/26/2015 8:48:15 PM
        • Fault bucket , type 0
        • Event Name: LiveKernelEvent

       

      So basically what I'm pretty sure is happening is that the Desktop Window Manager tries to steal the focus from the game with that annoying popup saying:

      Do you want to change the color scheme to improve performance?

      The issue is that popup.   And I'm not certain, but my Reliability log suggests it has something to do with Microsoft Update's installed on the 12th.  All the errors below are BF4 and GWXUX.exe. On the 12th  Windows installed literally hundreds of updates.  GWXUX.exe is that "Get Windows 10" dialog. 

       

      Reliability log:

       

      Thinking back, I've never seen that popup before while playing BF4.  It has always just crashed.  While playing Witcher it did come up often.  Something changed recently with the latest AMD Driver version, Windows Update, or BF4 that has made that popup much more prone to show and crash BF4. I'm not sure if this is a bug I should be posting to AMD, Microsoft, or to the BF4 devs. 

        • Re: BF4 crashes Mantle:GR_ERROR_DEVICE_LOST or in DX11: DXGI_ERROR_DEVICE_HUNG due to loosing Fullscreen Ownership
          zealotki11er

          That Windows message comes up when you start to run out of system memory or graphics memory? Do you monitor them during game-play? What GPU do you have? Mantle uses more vRAM then DX11 and BF4 has been reported to have memory leaks in some systems.

            • Re: BF4 crashes Mantle:GR_ERROR_DEVICE_LOST or in DX11: DXGI_ERROR_DEVICE_HUNG due to loosing Fullscreen Ownership
              derekz10

              The GPU is an HD7950 3GB. Yes, I have a triple-monitor setup and can monitor vRam usage via MSI Afterburner.

               

              Before starting BF4, with an Internet Browser open and Aero enabled, vRAM is around 350MB. Since the 12th, I could only play 10-30 minutes tops before crashing.

              • In game using MANTLE, immediately at the start of the round the usage is 2.5GB.  By the end of the round usage is around ~2.9GB.  I use 130% Resolution scale. Any more can sometimes cause stuttering while turning a corner as I blow the vRam limit.
              • In game using DX11, immediately at the start of the round the usage is just over 2GB.  I never completed a full round in DX11. I immediately switched back to MANTLE after trying it because things were "blurry?" like they were up-scaled. I took a screenshot and the screenshot was in 720p, even though the game settings were for full resolution. No idea what that was about or how it could use so much vRam at that resolution, but that's a different issue all-together.   The last time I looked before it crashed it was around 2.6GB.

               

              After disabling Desktop Composition in "Control Panel\All Control Panel Items\System --> Advanced System Setttings --> Advanced --> Performance Settings"  I haven't had a single issue.

               

              With Desktop Composition Disabled, vRam usage before starting BF4 is roughly ~40MB.  In game using MANTLE, the vRAM usage at the start of the round was a little lower but by the end of rounds it still managed to work up to 2.9GB-ish.  I noticed the game ran smoother than butter and never once noticed any micro-stutter. Micro-stutter is sometimes present but not severe when Desktop Composition was enabled.

                • Re: BF4 crashes Mantle:GR_ERROR_DEVICE_LOST or in DX11: DXGI_ERROR_DEVICE_HUNG due to loosing Fullscreen Ownership
                  derekz10

                  Also I don't think I made it clear why I'm suggesting this is an AMD driver issue.  This is because, along with the BF4 error I also get a "Video Hardware Error" that creates a minidump. Here is what a WinDbg analysis shows on that end:

                   

                  FAULTING_IP: 
                  atikmpag+cc9c
                  fffff880`03f4cc9c 4883ec28        sub     rsp,28h
                  
                  
                  DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
                  TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b
                  BUGCHECK_STR:  0x117
                  CURRENT_IRQL:  0
                  
                  
                  STACK_TEXT:  
                  fffff880`044ca4f0 fffff880`040d972b : fffffa80`15aa5010 fffff880`041260cc fffffa80`15aa5010 fffff880`040a7843 : watchdog!WdDbgReportRecreate+0xa3
                  fffff880`044caa10 fffff880`040da3f0 : fffff8a0`305e45a0 fffff8a0`305e45a0 00000000`00000080 fffffa80`15aa5010 : dxgkrnl!TdrUpdateDbgReport+0xcb
                  fffff880`044caa60 fffff880`040ae6b3 : 00000000`00000001 fffffa80`11be0000 00000000`00000000 fffff880`000000c7 : dxgkrnl!TdrCollectDbgInfoStage2+0x220
                  fffff880`044caa90 fffff880`040daf43 : fffffa80`11ec1658 ffffffff`fffe7960 fffffa80`15aa5010 fffff880`041aaf3c : dxgkrnl!DXGADAPTER::Reset+0xef
                  fffff880`044cab40 fffff880`041ab03d : fffffa80`15697d50 00000000`00000080 00000000`00000000 fffffa80`11ec1010 : dxgkrnl!TdrResetFromTimeout+0x23
                  fffff880`044cabc0 fffff800`035578e2 : 00000000`fffffc32 fffffa80`11bf8060 fffffa80`0c9f9820 fffffa80`11bf8060 : dxgmms1!VidSchiWorkerThread+0x101
                  fffff880`044cac00 fffff800`032aff46 : fffff880`03089180 fffffa80`11bf8060 fffff880`030940c0 00000000`ffffffff : nt!PspSystemThreadStartup+0x5a
                  fffff880`044cac40 00000000`00000000 : fffff880`044cb000 fffff880`044c5000 fffff880`0926cd40 00000000`00000000 : nt!KxStartSystemThread+0x16
                  
                  
                  STACK_COMMAND:  .bugcheck ; kb
                  FOLLOWUP_IP: 
                  atikmpag+cc9c
                  fffff880`03f4cc9c 4883ec28        sub     rsp,28h
                  
                  
                  SYMBOL_NAME:  atikmpag+cc9c
                  FOLLOWUP_NAME:  MachineOwner
                  MODULE_NAME: atikmpag
                  IMAGE_NAME:  atikmpag.sys
                  DEBUG_FLR_IMAGE_TIMESTAMP:  55a70536
                  FAILURE_BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys
                  BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys
                  Followup: MachineOwner