Ran Out of Video memory Exiting

[Beer_Me]Radical

Recently started getting this message tried a couple of things and here is what I found.

1. If you are getting abouve message with Win+Alt+R open the Xbox App goto Sewtting and Select Game DVR and turn it off.


2. Run command Propmt as Admin and enter the following (copy and Paste)

bcdedit /set IncreaseUserVA 2048

Don't guarantee fixed but has worked for me so far.

Please post if you have this issue and either of these work.

Thanks

Radical

-PPaaxx-

Me too. I googled the message and followed this

[Beer_Me]Radical

Yea but the 3072 doesn't work

-PPaaxx-

Two times in a row I had this immediately after I was in the game, never happened before, and I did as in the video. All ok since then.

-=NoBS=-Reyfox_I

Hate to say this, but I too have been getting it a LOT lately. Last night playing Overload, 3 times it happened. And I was not out of video memory according to GPU-Z. I still had over 1/2 gig left. I never had this problem before, and I used to have Firefox and other programs open at the same time as running the game. Now, even with everything closed, it happens on Overload and Slums. Other maps? No problem.... so far....
Using AMD HD7870 with 2gigs GDDR5 RAM.
Reading the comments in the video posted above, someone else has the same problem with playing
AAPG....
Curious as to the computer specs of people that have this problem.
Mine is: Win7 Pro 64bit SP1, AMD FX8350 8core OC'ed, AMD HD7870 2gig GDDR5 OC'ed, 16gigs DDR3 1600

iNv|roKis-

There is an issue with Overload currently. It Crashes servers possibly due to the same issue.

-SD-DELTON-ACI-

Well in a way I am glad to see this post I though it was my new map causing this.
When we vote to switch maps this happens with some members but not others.
Some can join without a problem and others get "Ran Out of Video memory Exiting"
Its so annoying for me because I ended up rebuilding the map a few times thinking it
was my map causing the problem.
http://forum.americasarmy.com/discussion/4982/my-map-is-crashing-players-game/p1

=[101st]=Muzza455

3072 should work if u have 16gb of ram or over .

-PPaaxx-

My two crash was on official Overload. I play official Overload right now, no issues.

Windows 10 Pro 64-bit
Intel Core i7 2700K
8,00GB ram
2047MB NVIDIA GeForce GTX 660 Ti

K0$H3R

This issue is typically only seen on 32 bit version of Windows.
To perform properly our game needs to run on a 64 bit operating system.
You will need to upgrade to a 64 bit OS to fix this issue.

K0$H3R

As far as specific map crashes go, please make sure you are reporting these in the bug reporting system or in the ticket support system so we can ensure that we are aware of the issue and have them in queue to be fixed.

-PPaaxx-

K0$H3R wrote: »

This issue is typically only seen on 32 bit version of Windows.
To perform properly our game needs to run on a 64 bit operating system.
You will need to upgrade to a 64 bit OS to fix this issue.

That's true. I've tested 32 bit a short time last year. I've used 64 bit for years now.

-=NoBS=-Reyfox_I

Mine is a 64bit system. I've been monitoring system RAM and video RAM when I start playing the game. I also have TaskManager open. I do have plenty of RAM left, but maybe because AAPG is trying to access certain memory locations this happens?

frankof

Dont get RAM and V-ram mixed up now, it will only add to the confusion.
The "out of video memory" is mostly seen on a couple of maps, Overload being the most frequent.
I had it with about 50% of my V-ram used(1.5 of 3GB), I'm fairly convinced its a issue of flawed memory addressing as turning off texture streaming triggers it 100% without filling the v-ram to the brim.

-SD-DELTON-ACI-

K0$H3R wrote: »

This issue is typically only seen on 32 bit version of Windows.
To perform properly our game needs to run on a 64 bit operating system.
You will need to upgrade to a 64 bit OS to fix this issue.

This is not quite true i have tested this with a clan member that was getting this message and he has
a 64 bit operating system.
So maybe this is not the only problem.

-=NoBS=-Reyfox_I

I do know the difference between the two. Just giving informational stuff. I'm watching everything.

.dcG-Colts^

I get it on cold front.

[Beer_Me]Radical

Some are suggesting that this is a Windows 10 issue.
Please let us know if you are getting this error in an OS other than 10.

Here are my specs:

Windows 10 Home (x64) Version
4.00 gigahertz AMD FX -8350 Eight-Core
384 kilobyte primary memory cache
8192 kilobyte secondary memory cache
8192 kilobyte tertiary memory cache
64-bit ready
Multi-core (4 total)
Hyper-threaded (8 total)
Slot 'Node0_Dimm0' has 8192 MB (serial number 6B215B07)
Slot 'Node0_Dimm1' has 8192 MB (serial number 6A21C324)
Slot 'Node0_Dimm2' has 8192 MB (serial number 69215E07)
Slot 'Node0_Dimm3' has 8192 MB (serial number 7721735B)
AMD Radeon R9 200 Series

=U^S=_Mason

I use light sabers and have not run into a vram issue.

TheTots

We think we may have found the cause of the recent memory issues. It will be going out in the next update tomorrow.

iNv|roKis-

FunPolice wrote: »

We think we may have found the cause of the recent memory issues. It will be going out in the next update tomorrow.

Man, stop being vague. What is it?
I feel a lack of closure! lol