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.
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.
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