Jump to content
johnnypope

Sudden FPS Drop after 30-60 Minutes Issue + Solution

Recommended Posts

Hi guys I've noticed others having this issue and I wanted to point it out, explain how to see if this is your issue, and how to solve it.

Symptom:

Game runs fine, even great, for 30-60 minutes, then FPS drops to between 0 and 5 and will not recover. Usually accompanied by texture loading issues. Flushing the VRAM does not have an impact, nor does adjusting any graphics settings. Alt+Tab will sometimes cause a crash but if it doesn't, Arma 3 still does not recover. The issue will remain until Arma 3 is restarted (PC/windows do not need to restart).

What Is the Issue?

The issue is that with some (many) configurations, DirectX API will not report your VRAM accurately. If you have a 32-bit OS, this will cause a serious problem because of the memory addressing limit. The reason this occurs with Arma 3 is that they have 'Broken the 32-bit Barrier'.

http://support.microsoft.com/kb/2026022/en-us?p=1

http://www.bistudio.com/english/company/developers-blog/85-breaking-the-32-bit-barrier

How To Confirm That This Is Your Issue:

You have a 32-bit Operating System

Run dxdiag.exe and see if your System Memory is being reported correctly on the first page. If it reports an amount different from your system ram minus your VRAM, you will have this issue.

How To Solve The Issue:

Unfortunately, using -maxvram and -maxmem and such didn't keep Arma's total memory usage down to where it was kept safely away from the custom addressing scheme described in the 'Breaking the 32-bit Barrier' blog thing. The only way I was able to eliminate the problem was by installing a 64-bit OS. Now my DirectX reports my VRAM accurately and I do not have this issue. You can install and activate a 64-bit copy of Windows using your 32-bit product key.

Devs or anyone are welcome to correct me if I'm wrong but it seems that 32-bit users who suffer from the DirectX problem above will always run into this issue when Arma 3 begins to use more than 2.5 gigs of memory or so. I was able to mitigate the issue by cutting down services and background programs but, eventually, Arma's usage would creep up to where the system was out of memory.

Just for reference, my hardware specs:

MSI 970A-G46

AMD FX-8120

4GB DDR3 @1866 (timed well)

GeForce GTX550Ti (just one)

Regular old WDC Magnetic HD

I suspected and eliminated the following possibles before I finally broke down and installed a 64-bit OS:

-Pagefile/hard drive issues

-PhysX usage (CPU/GPU)

-Bad memory

-Bad memory timings

-Bad processor/unstable board

-Power management issues with GPU/CPU

-CPU Parking/thread handling/-MaxCores -ExThreads etc

-Bad VRAM/bad GPU

-More..

Sorry for the fresh thread but I wanted to share what I've learned since I haven't seen anyone actually get this one resolved. Happy to discuss.

Edited by johnnypope
Clarity

Share this post


Link to post
Share on other sites

What Is the Issue?

The issue is that with some (many) configurations, DirectX API will not report your VRAM accurately. If you have a 32-bit OS, this will cause a serious problem because of the memory addressing limit. The reason this occurs with Arma 3 is that they have 'Broken the 32-bit Barrier'.

That devblog exists for/since Arma 2 originally. If that is true what you say, then it would have been an issue for a much longer time than Arma 3, namely with A2 Operation Arrowhead, DayZ.

You say that in your 32bit OS in DXDiag, the VRAM (Video RAM) was reported inaccurately. This should of course not happen, but this sound more like a graphics driver issue (this is something which was not on your list). I fail to see how inaccurate VRAM readings are connected with the OS architecture, apart from the fact that the drivers have to be developed separately and thus could offer you different issues.

Share this post


Link to post
Share on other sites

Nothing helps.

I'm on 64 bit. 8 GB ram . Whenever i start a multiplayer game it's pretty smooth. 20 minutes in frames have dropped half and continue to drop slowly.

Now, maybe you think "it's the server" ... No , if i REBOOT, and come back to that same server all is well again. But rebooting is the ONLY thing that helps . Shutting down the game, and re-entering gives the same crap.

Only after a fresh reboot will multiplayer be smooth again (for a very limited time)

I think it's best to compare this piece of crap software with a virus.

It diseases your whole PC after 20 mintutes of playing, and the only way to get rid of it's remnants of diseased crap is by completely rebooting.

Share this post


Link to post
Share on other sites
Nothing helps.

I'm on 64 bit. 8 GB ram . Whenever i start a multiplayer game it's pretty smooth. 20 minutes in frames have dropped half and continue to drop slowly.

Now, maybe you think "it's the server" ... No , if i REBOOT, and come back to that same server all is well again. But rebooting is the ONLY thing that helps . Shutting down the game, and re-entering gives the same crap.

Only after a fresh reboot will multiplayer be smooth again (for a very limited time)

I think it's best to compare this piece of crap software with a virus.

It diseases your whole PC after 20 mintutes of playing, and the only way to get rid of it's remnants of diseased crap is by completely rebooting.

... when leaving arma and before reboot, did you check if arma process is still running (taskmanager -> processes) ?

Share this post


Link to post
Share on other sites

Note that Arma won't use more than 4GB of RAM since it's 32-bit, and that includes VRAM.

Have you tried a full and clean driver installation? Are all your other drivers up to date? Have you altered any of your system defaults ("tweaking", as it's called)? What settings are you running in the game? What is your hardware and OS? Have you overclocked any components?

I suggest using Process Explorer to watch your various performance metrics easily without an installation of new software (with a 10sec update speed for longer play). If you want something more indepth, you should use HWINFO and create a logfile for the important things like virtual memory load, memory load, gpu memory load, gpu core load, etc. It can be helpful in spotting a problem.

It seems to be only cancer for your specific computer, as this is one issue I've not seen basically at all on these forums, so perhaps don't generalize so much.

Share this post


Link to post
Share on other sites

What Fireball says is true. I have also learned that the DX issue is only under Windows 7. But I still think they must be related. Let me explain, partly for clarity and partly for my own education.

Dxdiag.exe will misreport the system memory inaccurately, not the VRAM. My mistake. Here's my scenario: I had 4GB of RAM and a video card with 1GB. DxDiag was showing my total system memory as 2430 or something like that. Windows was showing that I had 3.5GB 'available'. This means that it has only addressed half my VRAM and then addressed 3.5 GB of system ram.

Through much testing, I found that my system at idle runs around 800-1000 MB, and Arma 3 runs right around 2gb, at first. Once Arma3 began to use around 2300, the issue would occur. This is basically when the system runs out of addressed memory (512 on the video card, 1000 for windows, 2300 for Arma = 3800 MB which is the addressing limit in Win32. (Arma rarely uses more than 512 VRAM; when it used more it seemed to always be temporary and settle back into the 500's)

If windows had addressed my entire 1024 VRAM first I would only have around 2gb available for Arma, but I am sure that it would not chunk out like it does since it knows what memory it can use and what it can't.

The reason I suspect that 'breaking the 32-bit barrier' has something to do with it is because I read it. It is from Arma 2 but Arma 2 uses DX9, not DX11. So the issue never occurred under Arma 2.

One of the tests that I did in order to confirm this issue was to remove one of my two 2GB memory modules. This caused windows to show 512 VRAM and 2048 System Memory (Addressing all of it properly). The game ran like crap, but the issue never occurred. In total, memory usage was pushing 2.5GB but never exceeded that. This tells me that under my original scenario, Arma2 was using memory that windows had not properly addressed, and I believe that it crossed over somehow once it began to use greater than 4GB (VRAM+System).

Of course drivers was the first thing I looked at. The DirectX thing was supposed to get fixed but never was. Other things that I checked out were heat/cooling issues, HD corruption/fragmentation, network card drivers/power management.

Anyway, again, I'm no expert but I can say for certain that this issue would not occur if any of the following were true:

A) DirectX addressed the VRAM properly, first, letting programs know to stay under 3GB, not 3.5GB

B) There is less than 4096 total memory installed, between VRAM and System Ram

C) There is a 64-bit Operating System installed

D) Arma 3 used DirectX 9

E) Arma 3 used only memory that is addressable in Windows

Anyway we could really try to prove me wrong or right but I imagine anyone with 4GB of RAM and Windows 7 x86 is due for an upgrade anyway.

I also want to take this opportunity to sing the praises of Contig.exe. I use it in my batch file to launch Arma; it defrags folders. I have it defrag all my Arma directories before each launch. Great for installs with lots of addons.

---------- Post added at 20:19 ---------- Previous post was at 20:07 ----------

Game__On, can you reproduce the problem in SP/Editor? If not, then it appears you are in the same boat as the rest of us when it comes to MP performance. See http://forums.bistudio.com/showthread.php?168337-Multiplayer-not-in-playable-state/page2

Edited by johnnypope
Oh..

Share this post


Link to post
Share on other sites

I have received the same problem except I am on a 64-Bit up to date windows 10 with the newest drivers running for my GTX 970, Arma 3 is 32 bit and thus cannot handle more than 4 gigs of System Primary Memory (Ram) and has "unforeseen consequences" if you have more than 4 gigs of VRam under your GPU's belt but can handle a maximum of 8 gigs of VRam, a good way to counter  this is to trick Arma 3 into thinking you are running those max specs in the launcher under the Parameters \ All Parameters tab \ Advanced sub menu. also while you are there try to see if that hyper-threading option will increase your performance.

 

help with finding setting in the launcher

https://1drv.ms/i/s!AmH4OS3FoUUkh02p4h7-eI6X_oSX

Share this post


Link to post
Share on other sites

I have the same problem so can I get some help please.

I have 64bit Everything

1070GTX

i5-6600

16g Ram DDR4

Arma 3 is on a 1T SSD

and It only happens online bc in single player it doesn't frame drop

I really need some help so anyone please post some replies thanks

Share this post


Link to post
Share on other sites

The biggest FPS problems I've encountered are 1. Inadequate CPU and 2. Graphics settings too high.

I

f you're on Ultra you're going to get laggy, unless you have a really good CPU that has excellent single core performance. 

Share this post


Link to post
Share on other sites
21 hours ago, Bob Builderson said:

I have the same problem so can I get some help please.

I have 64bit Everything

1070GTX

i5-6600

16g Ram DDR4

Arma 3 is on a 1T SSD

and It only happens online bc in single player it doesn't frame drop

I really need some help so anyone please post some replies thanks

 

Restart Arma. It's literally the only thing that works. 

Share this post


Link to post
Share on other sites

Try the 64-bit EXE that is available on the Dev branch.

1. Swtich from main to Dev branch (via Steaù)

2. Open A3 Launcher

3. ensure that you have no parameters selected that limit RAM or VRAM

4. select 64-bit platform

5. enjoy smoother A3 experience

6. report back

Share this post


Link to post
Share on other sites

Make sure your windows swap file is on auto and the HD is defragged. Other than that, switch to 64 bit dev edition and that should fix the ram issue so long as you have 8 GB or more ram with nothing else running. 

Share this post


Link to post
Share on other sites

Same issue. All ultra settings @ 1080p, no MODS.

My fps will drop from avg 40 on multiplayer to 5 fps after about 1 or 2 hours. I've had it happen a number of times now and have no issue with any other game. Also no one else is having this issue on the server, at least not at the same time as me. I have heard of others complaining of the same issue in the last 24 hours though. This leads me to think it's an issue with Arma and the server I'm on.

Specs- 4790k no oc, 980ti factory oc, 16gb ram ddr3, arma installed on samdung 850 ssd. Arma log- https://drive.google.com/open?id=0B2gJejXSrLAfeHhQNEJXUTVxQ3c

15 second video of problem- 



 

Share this post


Link to post
Share on other sites
On ‎12‎/‎30‎/‎2016 at 5:35 AM, Saracen Rush said:

Same issue. All ultra settings @ 1080p, no MODS.

My fps will drop from avg 40 on multiplayer to 5 fps after about 1 or 2 hours. I've had it happen a number of times now and have no issue with any other game. Also no one else is having this issue on the server, at least not at the same time as me. I have heard of others complaining of the same issue in the last 24 hours though. This leads me to think it's an issue with Arma and the server I'm on.

Specs- 4790k no oc, 980ti factory oc, 16gb ram ddr3, arma installed on samdung 850 ssd. Arma log- https://drive.google.com/open?id=0B2gJejXSrLAfeHhQNEJXUTVxQ3c
 



 

 

I don't think its the server, but it is a Arma 3 Issue. This issue started for me after the 1.66 update, 1.64 was working fine I could play all day and only have to log out when the server restarted. I'm not a i5 6600 4.0Ghz with a GTX 1070, 16 gigs ddr4 ram. and I'll go from 60 fps in 4K to 5 in about 30 mins time. have to restart arma and then reconnect to server. not fun!!!! I'm hoping the 64bit Update fixes the issue. I've reported it to the Dev 5 times each with the dump files and reports. Suggest all do the same

Share this post


Link to post
Share on other sites

It's not related to a server. I get this problem frequently on my own dedicated server as well as running missions locally and in the editor. I tried a lot of things with the video settings/resolutions, different graphic cards (GTX 970 3,5 GB-ish and AMD R 480 8 GB), page files, memory allocators, sound quality, etc. Nothing helped me so far, only restarting Arma. Did not had the problems before 1.58. Looking forward to the official release of the 64bit exe ...  Running on I5 6600k (OC 4,5 GHz), 8GB RAM, Win 10, AMD R 480, SSD

Share this post


Link to post
Share on other sites
30 minutes ago, tobur said:

It's not related to a server. I get this problem frequently on my own dedicated server as well as running missions locally and in the editor. I tried a lot of things with the video settings/resolutions, different graphic cards (GTX 970 3,5 GB-ish and AMD R 480 8 GB), page files, memory allocators, sound quality, etc. Nothing helped me so far, only restarting Arma. Did not had the problems before 1.58. Looking forward to the official release of the 64bit exe ...  Running on I5 6600k (OC 4,5 GHz), 8GB RAM, Win 10, AMD R 480, SSD

 

My server hasn't failed once, my client has and I too have tried everything, same as you. Before my GTX 1070 I was running a R9390x and when it first started happening I drove to best buy and bought a GTX 1070 thinking it was my video card. In hind sight I should have done that last, but oh well at least I got money for the R9 390x when I sold it. The only thing I haven't done was rearrange my system Ram into different DIMM slots. I'll try that later.

 

Share this post


Link to post
Share on other sites

The issue:

 

17:53:07 Virtual memory total 4095 MiB (4294836224 B)
17:53:07 Virtual memory free 101 MiB (106000384 B)
17:53:07 Physical memory free 6098 MiB (6394826752 B)
17:53:07 Page file free 7087 MiB (7431331840 B)
17:53:07 Process working set 2276 MiB (2387316736 B)
17:53:07 Process page file used 3477 MiB (3646476288 B)
17:53:07 Longest free VM region: 14221312 B
17:53:07 VM busy 4188901376 B (reserved 237547520 B, committed 3951353856 B, mapped 177090560 B), free 105934848 B
17:53:07 Small mapped regions: 120, size 503808 B
17:53:07 Virtual memory total 4095 MiB (4294836224 B)
17:53:07 Virtual memory free 101 MiB (105934848 B)
17:53:07 Physical memory free 6097 MiB (6393729024 B)
17:53:07 Page file free 7083 MiB (7427907584 B)
17:53:07 Process working set 2281 MiB (2392080384 B)
17:53:07 Process page file used 3480 MiB (3650027520 B)
17:53:07 Longest free VM region: 14221312 B
17:53:07 VM busy 4188835840 B (reserved 233996288 B, committed 3954839552 B, mapped 177025024 B), free 106000384 B
17:53:07 Small mapped regions: 120, size 503808 B
17:53:07 Virtual memory total 4095 MiB (4294836224 B)
17:53:07 Virtual memory free 99 MiB (104558592 B)
17:53:07 Physical memory free 6133 MiB (6431223808 B)
17:53:07 Page file free 7083 MiB (7427837952 B)
17:53:07 Process working set 2316 MiB (2429091840 B)
17:53:07 Process page file used 3482 MiB (3651342336 B)
17:53:08 Longest free VM region: 14221312 B
17:53:08 VM busy 4190146560 B (reserved 232681472 B, committed 3957465088 B, mapped 178335744 B), free 104689664 B
17:53:08 Small mapped regions: 120, size 503808 B
17:53:08 Virtual memory total 4095 MiB (4294836224 B)
17:53:08 Virtual memory free 101 MiB (106524672 B)
17:53:08 Physical memory free 6138 MiB (6437011456 B)
17:53:08 Page file free 7082 MiB (7426977792 B)
17:53:08 Process working set 2318 MiB (2430660608 B)
17:53:08 Process page file used 3482 MiB (3651383296 B)
17:53:08 Longest free VM region: 14221312 B
17:53:08 VM busy 4188377088 B (reserved 232640512 B, committed 3955736576 B, mapped 176566272 B), free 106459136 B
17:53:08 Small mapped regions: 120, size 503808 B
17:53:08 Virtual memory total 4095 MiB (4294836224 B)
17:53:08 Virtual memory free 100 MiB (105148416 B)
17:53:08 Physical memory free 6151 MiB (6450368512 B)
17:53:08 Page file free 7081 MiB (7424995328 B)
17:53:08 Process working set 2319 MiB (2432679936 B)
17:53:08 Process page file used 3483 MiB (3652845568 B)
17:53:08 Longest free VM region: 14221312 B
17:53:08 VM busy 4189753344 B (reserved 232624128 B, committed 3957129216 B, mapped 176500736 B), free 105082880 B
17:53:08 Small mapped regions: 120, size 503808 B
17:53:08 Virtual memory total 4095 MiB (4294836224 B)
17:53:08 Virtual memory free 90 MiB (94990336 B)
17:53:08 Physical memory free 6143 MiB (6441488384 B)
17:53:08 Page file free 7070 MiB (7414214656 B)
17:53:08 Process working set 2329 MiB (2442903552 B)
17:53:08 Process page file used 3493 MiB (3662962688 B)
17:53:08 Longest free VM region: 14221312 B
17:53:08 VM busy 4199911424 B (reserved 232607744 B, committed 3967303680 B, mapped 176566272 B), free 94924800 B
17:53:08 Small mapped regions: 120, size 503808 B
17:53:09 Virtual memory total 4095 MiB (4294836224 B)
17:53:09 Virtual memory free 90 MiB (95121408 B)
17:53:09 Physical memory free 6143 MiB (6441480192 B)
17:53:09 Page file free 7070 MiB (7414398976 B)
17:53:09 Process working set 2330 MiB (2443292672 B)
17:53:09 Process page file used 3493 MiB (3662962688 B)
17:53:09 Longest free VM region: 14221312 B
17:53:09 VM busy 4199780352 B (reserved 232607744 B, committed 3967172608 B, mapped 176435200 B), free 95055872 B
17:53:09 Small mapped regions: 120, size 503808 B
17:53:09 Virtual memory total 4095 MiB (4294836224 B)
17:53:09 Virtual memory free 90 MiB (95121408 B)
17:53:09 Physical memory free 6143 MiB (6441549824 B)
17:53:09 Page file free 7070 MiB (7414398976 B)
17:53:09 Process working set 2330 MiB (2443845632 B)
17:53:09 Process page file used 3493 MiB (3662970880 B)
17:53:09 Longest free VM region: 14221312 B
17:53:09 VM busy 4199780352 B (reserved 232599552 B, committed 3967180800 B, mapped 176435200 B), free 95055872 B
17:53:09 Small mapped regions: 120, size 503808 B
17:53:09 Virtual memory total 4095 MiB (4294836224 B)
17:53:09 Virtual memory free 90 MiB (95121408 B)
17:53:09 Physical memory free 6143 MiB (6441660416 B)
17:53:09 Page file free 7070 MiB (7414398976 B)
17:53:09 Process working set 2330 MiB (2444177408 B)
17:53:09 Process page file used 3493 MiB (3663032320 B)
17:53:09 Longest free VM region: 14221312 B
17:53:09 VM busy 4199780352 B (reserved 232538112 B, committed 3967242240 B, mapped 176435200 B), free 95055872 B
17:53:09 Small mapped regions: 120, size 503808 B
17:53:09 Virtual memory total 4095 MiB (4294836224 B)
17:53:09 Virtual memory free 90 MiB (95121408 B)
17:53:09 Physical memory free 6142 MiB (6440669184 B)
17:53:09 Page file free 7071 MiB (7414566912 B)
17:53:09 Process working set 2331 MiB (2444251136 B)
17:53:09 Process page file used 3493 MiB (3663069184 B)
17:53:09 Longest free VM region: 14221312 B
17:53:09 VM busy 4199780352 B (reserved 232501248 B, committed 3967279104 B, mapped 176435200 B), free 95055872 B
17:53:09 Small mapped regions: 120, size 503808 B
17:53:10 Virtual memory total 4095 MiB (4294836224 B)
17:53:10 Virtual memory free 87 MiB (92237824 B)
17:53:10 Physical memory free 6134 MiB (6432612352 B)
17:53:10 Page file free 7068 MiB (7411679232 B)
17:53:10 Process working set 2335 MiB (2449092608 B)
17:53:10 Process page file used 3496 MiB (3666014208 B)
17:53:10 Longest free VM region: 14221312 B
17:53:10 VM busy 4202663936 B (reserved 232443904 B, committed 3970220032 B, mapped 176435200 B), free 92172288 B
17:53:10 Small mapped regions: 120, size 503808 B
17:53:10 Virtual memory total 4095 MiB (4294836224 B)
17:53:10 Virtual memory free 86 MiB (90664960 B)
17:53:10 Physical memory free 6131 MiB (6429708288 B)
17:53:10 Page file free 7065 MiB (7408791552 B)
17:53:10 Process working set 2337 MiB (2451456000 B)
17:53:10 Process page file used 3498 MiB (3668918272 B)
17:53:10 Longest free VM region: 14221312 B
17:53:10 VM busy 4204236800 B (reserved 232427520 B, committed 3971809280 B, mapped 175124480 B), free 90599424 B
17:53:10 Small mapped regions: 120, size 503808 B
17:53:10 Virtual memory total 4095 MiB (4294836224 B)
17:53:10 Virtual memory free 81 MiB (84963328 B)
17:53:10 Physical memory free 6123 MiB (6421405696 B)
17:53:11 Page file free 7060 MiB (7403188224 B)
17:53:11 Process working set 2343 MiB (2457747456 B)
17:53:11 Process page file used 3504 MiB (3674714112 B)
17:53:11 Longest free VM region: 14221312 B
17:53:11 VM busy 4209938432 B (reserved 232402944 B, committed 3977535488 B, mapped 175058944 B), free 84897792 B
17:53:11 Small mapped regions: 120, size 503808 B
17:53:11 Virtual memory total 4095 MiB (4294836224 B)
17:53:11 Virtual memory free 71 MiB (74870784 B)
17:53:11 Physical memory free 6111 MiB (6407880704 B)
17:53:11 Page file free 7049 MiB (7391756288 B)
17:53:11 Process working set 2353 MiB (2468171776 B)
17:53:11 Process page file used 3514 MiB (3684913152 B)
17:53:11 Longest free VM region: 12779520 B
17:53:11 VM busy 4220030976 B (reserved 232312832 B, committed 3987718144 B, mapped 175058944 B), free 74805248 B
17:53:11 Small mapped regions: 120, size 503808 B
17:53:11 Virtual memory total 4095 MiB (4294836224 B)
17:53:11 Virtual memory free 64 MiB (67596288 B)
17:53:11 Physical memory free 6100 MiB (6397165568 B)
17:53:11 Page file free 7042 MiB (7384809472 B)
17:53:11 Process working set 2361 MiB (2475782144 B)
17:53:11 Process page file used 3521 MiB (3692171264 B)
17:53:11 Longest free VM region: 5570560 B
17:53:11 VM busy 4227305472 B (reserved 232275968 B, committed 3995029504 B, mapped 175124480 B), free 67530752 B
17:53:11 Small mapped regions: 120, size 503808 B
17:53:11 Virtual memory total 4095 MiB (4294836224 B)
17:53:11 Virtual memory free 61 MiB (64516096 B)
17:53:11 Physical memory free 6098 MiB (6394810368 B)
17:53:11 Page file free 7040 MiB (7382310912 B)
17:53:11 Process working set 2363 MiB (2478772224 B)
17:53:11 Process page file used 3523 MiB (3695067136 B)
17:53:12 Longest free VM region: 2686976 B
17:53:12 VM busy 4230385664 B (reserved 232271872 B, committed 3998113792 B, mapped 175321088 B), free 64450560 B
17:53:12 Small mapped regions: 120, size 503808 B
17:53:12 Virtual memory total 4095 MiB (4294836224 B)
17:53:12 Virtual memory free 91 MiB (95973376 B)
17:53:12 Physical memory free 6119 MiB (6416306176 B)
17:53:12 Page file free 7070 MiB (7413645312 B)
17:53:12 Process working set 2340 MiB (2454450176 B)
17:53:12 Process page file used 3494 MiB (3663851520 B)
17:53:12 Longest free VM region: 5505024 B
17:53:12 VM busy 4198928384 B (reserved 232271872 B, committed 3966656512 B, mapped 175058944 B), free 95907840 B
17:53:12 Small mapped regions: 120, size 503808 B
17:53:12 Virtual memory total 4095 MiB (4294836224 B)
17:53:12 Virtual memory free 91 MiB (95973376 B)
17:53:12 Physical memory free 6129 MiB (6427049984 B)
17:53:12 Page file free 7070 MiB (7414272000 B)
17:53:12 Process working set 2341 MiB (2455498752 B)
17:53:12 Process page file used 3494 MiB (3663884288 B)
17:53:12 Longest free VM region: 5505024 B
17:53:12 VM busy 4198928384 B (reserved 232239104 B, committed 3966689280 B, mapped 175058944 B), free 95907840 B
17:53:12 Small mapped regions: 120, size 503808 B
17:53:12 Virtual memory total 4095 MiB (4294836224 B)
17:53:12 Virtual memory free 92 MiB (97415168 B)
17:53:12 Physical memory free 6129 MiB (6426927104 B)
17:53:12 Page file free 7072 MiB (7415713792 B)
17:53:12 Process working set 2340 MiB (2454343680 B)
17:53:12 Process page file used 3492 MiB (3662450688 B)
17:53:12 Longest free VM region: 5505024 B
17:53:12 VM busy 4197486592 B (reserved 232230912 B, committed 3965255680 B, mapped 175058944 B), free 97349632 B
17:53:12 Small mapped regions: 120, size 503808 B
17:53:13 Virtual memory total 4095 MiB (4294836224 B)
17:53:13 Virtual memory free 94 MiB (98725888 B)
17:53:13 Physical memory free 6129 MiB (6426763264 B)
17:53:13 Page file free 7073 MiB (7417221120 B)
17:53:13 Process working set 2339 MiB (2453385216 B)
17:53:13 Process page file used 3491 MiB (3661025280 B)
17:53:13 Longest free VM region: 5505024 B
17:53:13 VM busy 4196175872 B (reserved 232214528 B, committed 3963961344 B, mapped 175190016 B), free 98660352 B
17:53:13 Small mapped regions: 120, size 503808 B
17:53:13 Virtual memory total 4095 MiB (4294836224 B)
17:53:13 Virtual memory free 94 MiB (98856960 B)
17:53:13 Physical memory free 6051 MiB (6345846784 B)
17:53:13 Page file free 6995 MiB (7335632896 B)
17:53:13 Process working set 2340 MiB (2453815296 B)
17:53:13 Process page file used 3491 MiB (3661045760 B)
17:53:13 Longest free VM region: 5505024 B
17:53:13 VM busy 4196044800 B (reserved 232194048 B, committed 3963850752 B, mapped 175058944 B), free 98791424 B
17:53:13 Small mapped regions: 120, size 503808 B
17:53:13 WARNING: Function 'name' - Punisher is dead
17:53:13 WARNING: Function 'name' - Punisher is dead
17:53:14 Virtual memory total 4095 MiB (4294836224 B)
17:53:14 Virtual memory free 93 MiB (98201600 B)
17:53:14 Physical memory free 6045 MiB (6338748416 B)
17:53:14 Page file free 6995 MiB (7334965248 B)
17:53:14 Process working set 2340 MiB (2454429696 B)
17:53:14 Process page file used 3491 MiB (3661053952 B)
17:53:14 Longest free VM region: 5505024 B
17:53:14 VM busy 4197421056 B (reserved 232185856 B, committed 3965235200 B, mapped 176435200 B), free 97415168 B
17:53:14 Small mapped regions: 120, size 503808 B
17:53:14 [tl1,c31c1600# 1823985: dummyweapon.p3d,"SMA_HK417vfg"]
17:53:14 WARNING: Function 'name' - Punisher is dead
17:53:14 DX11 error : CreateTexture failed : E_OUTOFMEMORY
17:53:14 DX11 error : CreateTexture failed : E_OUTOFMEMORY
17:53:14 DX11 error : CreateTexture failed : E_OUTOFMEMORY
17:53:14 DX11 error : CreateTexture failed : E_OUTOFMEMORY
17:53:14 DX11 error : CreateTexture failed : E_OUTOFMEMORY
17:53:14 DX11 error : CreateTexture failed : E_OUTOFMEMORY
17:53:14 DX11 error : CreateTexture failed : E_OUTOFMEMORY
17:53:14 DX11 error : CreateTexture failed : E_OUTOFMEMORY
17:53:14 DX11 error : CreateTexture failed : E_OUTOFMEMORY
17:53:14 DX11 error : CreateTexture failed : E_OUTOFMEMORY
17:53:14 CreateTexture failed : w = 2048, h = 1024, format = BC3_UNORM, err = E_OUTOFMEMORY.
17:53:14 DX11 error : CreateTexture failed : E_OUTOFMEMORY
17:53:14 Virtual memory total 4095 MiB (4294836224 B)
17:53:14 Virtual memory free 94 MiB (98856960 B)
17:53:14 Physical memory free 6039 MiB (6333243392 B)
17:53:14 Page file free 6987 MiB (7326715904 B)
17:53:14 Process working set 2346 MiB (2460467200 B)
17:53:14 Process page file used 3499 MiB (3669446656 B)
17:53:14 Longest free VM region: 5505024 B
17:53:14 VM busy 4196044800 B (reserved 223793152 B, committed 3972251648 B, mapped 175058944 B), free 98791424 B
17:53:14 Small mapped regions: 120, size 503808 B
17:53:14 VID: dedicated: 3221225472, shared 1073676288, system: 0, max: 2906652672, used: 2554781696
ErrorMessage: DX11 error : CreateTexture failed : E_OUTOFMEMORY
 

Share this post


Link to post
Share on other sites

Holy Hell in a handbasket! Use Pastebin or 

Code blocks like this

No need for a wall of text like that. The good thing is that you can go back and edit it. 

  • Like 1

Share this post


Link to post
Share on other sites

Possible solution for others:

I made some changes in my page file settings. I set the page file to system Manage and I was able to play Arma for 6 hours with just a few massive fps drops but was able to recover when I ALT Tabbed out and back in. A huge change from yesterdays only having to suck arma 3 down.

Share this post


Link to post
Share on other sites

Spoke too soon crashing started again same as before.

Share this post


Link to post
Share on other sites

Hi,
I've been playing Arma 3 for a few weeks now and I've been having the same issue in every single session of multiplayer that I play.  After anywhere from 30 mins to 2 hours of playtime, give or take 30 mins or so, my frame rate drops from normal (45-60FPS) to anywhere from 1-5 FPS and the game becomes unplayable. If I want to continue playing, I have to restart Arma 3 completely.

I have tried changing my PhysX to only GPU, I have tried setting my page file settings to way higher than should be required on the drive that Arma 3 is installed on.  I've tried to use the different allocators.  I've tried to change the native frequency of the sound coming out of my headphones because I've seen that affect games before. I've tried changing the priority of Arma 3 to high or above in task manager.  I've tried changing the cores that Arma 3 runs on, both in the launcher and in the task manager by setting affinity.  I tried downloading the development version, but the servers I want to play are not available on that branch yet because it's 64bit.  I've tried the obvious and tried lowering the game settings.  All of this, and after a almost 100 hours of gameplay, my frustration level has peaked. I just want to sit down and play Arma without having to restart it every time I log out of a server in order to drop the memory usage down to a usable level again.

As it stands, on startup, before I get into a server, arma is using 450-500MB of memory as shown in task manager.  When I enter a server, depending on the type and host, it goes up to anywhere from 1500MB-2100MB instantly.  As I run around the game, it stays more or less constant, maybe going up or down depending on the landscape from what I can tell.  The issue is, during firefights or areas of a high or really any population of people or gunfire or explosions or anything else really, it goes up. This is normal from what I have seen with other games, but Arma doesn't let that memory free itself from what I can see, or at least not all of it. So if I die, my memory usage goes back down a very small amount because when I spawn I am not in the same intensely people/gunfire/explosion populated area.  Once I head back into the fray,  the memory usage starts rising again, compounding on itself until it reaches anywhere from 2700-3000MB and then the FPS drop happens and I have to restart the game.  If I don't restart the game, the memory stays high, not as high as when it dropped the FPS, but high enough to the point that when I start the game again, the new memory compounding on top of what was already used, immediately causes the FPS drop 10 sec into the next session.

I have not had this issue in any of the campaign scenarios yet so I can't tell you anything about that. I have played through most of apex and no drop so, I think it's just multiplayer.  All in all, I absolutely love this game.  It's super immersive and realistic and I would choose it every time over most military games, but the frustration is starting to kick in and I'm starting to veer away until this is fixed.

My specs:
Intel i7-3770K 3.5Ghz
32GB DDR3 RAM
EVGA 1080 GTX SC
Arma is installed on a 480GB SSD with plenty of space left
Windows 10 Home 64bit

Resolution is 3440x1440

 

Sorry for this reply, but I've seen so many threads about this same issue and I have tried so many of the work arounds that people have said are possible fixes, and nothing has worked.  Someone please help.

 

Edited by SubtleSloth

Share this post


Link to post
Share on other sites
1 hour ago, SubtleSloth said:

Sorry for this reply, but I've seen so many threads about this same issue and I have tried so many of the work arounds that people have said are possible fixes, and nothing has worked.  Someone please help.

Yeah, we've all been suffering through this, but as you know the only fix is going to be with the x64bit version. I've completely stopped playing the x86.exe (32bit) as there is no permanent solution in sight.

 

We're right in the middle of a very important transition that's been long overdue – patience is key.

 

Now... back to stress-testing the dev branch. :f:

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×