BeamNG.drive

BeamNG.drive

View Stats:
WroomWroom Sep 9, 2016 @ 3:51am
Game keeps crashing, Fatal ERROR, virtual memorry
I have decent system (8gb vengeance, gtx 680, i7 3770k) and when i try to play this game it will always crash when trying to replace my vehicle.
Sometimes it's "Fatal ERROR, rand out of virtual memorry", sometimes it's "ran out of system memorry" and the worst one was right now when everything froze, my screen started blinking and programs started crashing.
Somehow i managed to terminate the BeamNG process but it fealt like my PC was about to BSOD.
It also says "it's recommended to run this program on 64-bit system" and i'm obviously using 64-bit system so i don't know what to do now.
I tried executing the 64-bit version of BeamNG ... but still the same and still recommends 64-bit system

This game ran normally the last time i played it (about 2 or 3 months back).

HELP
< >
Showing 1-15 of 17 comments
Nadeox1 Sep 9, 2016 @ 7:36am 
In the game launcher, press the SUPPORT button.
Follow all the instructions. When the 'Support.BeamNG' page shows, only provide me the SUPPORT ID number.
There is no need to send that support ticket, you can close that page.
WroomWroom Sep 9, 2016 @ 11:20am 
Hello, thank you for your reply.
This is the number that i was given "3525"
I hope there is a way to the problems of mine.
Nadeox1 Sep 10, 2016 @ 1:26am 
From the logs, it appears it happens when you spawn the SBR.
Also, you are using quite some mods.
Please check using SAFE MODE.
Sometimes a broken/outdated mod can cause such issues.
Does it happen with any other vehicle?
On any maps?

Also, in the main menu, press F1, go to PERFORMANCE and press ALT+O.
Copy here the link of the page you get.
WroomWroom Sep 10, 2016 @ 12:15pm 
Weird, i don't have any mods installed because my disk broke and i reinstalled this game on a fresh brand new HDD about 5 days ago :/
Also i checked the folder mods in C:\Users\"user"\Documents\BeamNG.drive\mods
and all i see is "db.json" file.

Here's the link and it all passes http://media.beamng.com/mnPbP5KrwHnLMfZa

But now i did the "tests" - fked around with random maps/cars/respawns/configs
And it turns out that the new Utah map will report errors and crash randomly - either right after it loads up, sometimes after some driving and like before -> after swapping cars.

EDIT: Problem remains in safe mode - it will crash at some point and sometimes throw an error that i was unable to screen grab

Hope you find the bug of whatever the problem is.

If you need some more logs i can send them right away.
Last edited by WroomWroom; Sep 10, 2016 @ 12:25pm
WroomWroom Sep 10, 2016 @ 12:16pm 
Also awesome game and 100% worth the money so keep up the good work.
Nadeox1 Sep 11, 2016 @ 5:09am 
About mods, forget what I said. I have confused with another game log.


For the issue, when you play, how much free RAM does the Task Manager reports?
And when the game crashes?

The issue started randomly or you always had it?
Last edited by Nadeox1; Sep 11, 2016 @ 5:09am
WroomWroom Sep 11, 2016 @ 9:25am 
Hey.
I just tested my memory with Memtest86+ v5.01 and it passes without problems.
Same thing with HDD testing.
I can also assure you that all other games that i play run smoothly without any problems.

BeamNG will only crash on map Utah with used ram around 5.8 GB (task manager), leaving me with around 2GB leftover ram.

On other maps i can do whatever i want, have fun with editor, crash cars... whatever... just not on Utah.

"The issue started randomly or you always had it?"
This issue started right after i installed this game about one week back and i saw this new Utah map... so i tried it and it crashed. Then i tried to run 64-bit version directly (since it was recommending the use of 64-bit version) but the problem wouldn't go away.
EDIT: oh and yes, this never happened before in previous patches, just on Utah.

This (YT) video might be helpfull because this guy has the same exact problem:
https://www.youtube.com/watch?v=ANBcMJcSGZw&ab_channel=JoeyFuller
EDIT: but mine would crash completely... sometimes even bug other programs like skype, chrome etc... which is the weirdest.

Anyway... i pressed support again since i triggered a few more crashes.
My support ID is #3574
Last edited by WroomWroom; Sep 11, 2016 @ 9:29am
Nadeox1 Sep 12, 2016 @ 12:34am 
So, we have 6 game logs from you.
In all of these, it shows the game the 'Ran out of memory' right after you spawned (or did something) with the SBR.

I want to check if your issue isn't caused by this vehicle.
For any reasons, do not spawn the SBR.
Try anything else, but not that vehicle.
And see if things still crashes or not.

Let me know.
Meanwhile, I will notify the team about this issue and we will be checking more in-depth your game logs.
WroomWroom Sep 12, 2016 @ 2:04am 
Hey.
I just started the Utah and it crashed right away.

Do you maybe have any other recommended RAM test utilities that i could use to make sure the problem isn't on my side ?

But it's just weird because why would it happen only on this map and not let's say on tropical island or while playing BF3 and such ?

If i had some spare sticks i would replace them to see if it's the ram... but i don't have them.
It's just that i would expect my ram to fail in every single occasion and more randomly than specifically in one game on one specific map.

Hope this info is helpfull ... cheers ;)
Nadeox1 Sep 12, 2016 @ 3:29am 
Utah has a higher RAM usage than the other maps, but the game shouldn't tell 'Out of memory' if you still have 2GB free.
Can you confirm it happens only in Utah, no other maps?

Can you please do the following to ensure your copy of the game is 'clean' from any kind of modifications. Yes, you said you reinstalled the game, but reinstalling doesn't wipe the things in Documents/BeamNG.Drive. Also to ensure that your download wasn't corrupted.

-Unistall BeamNG from Steam
-Delete BeamNG.Drive folder from MyDocuments (backup your mods if you want, but don't put them back yet!)
-Delete BeamnG.Drive folder from Steam/Steamapp/common (If there is still a folder)
-Reinstall BeamNG.

Let me know.
Eventually, add me on Steam and we can do some screensharing so I can give your issue a closer look.
WroomWroom Sep 12, 2016 @ 6:05am 
Hey, this might be interesting.
Image links from "postimg.org". Screens were take in this exact order, also event viewer included. You can see RAM usage and game.
https://s22.postimg.io/4ykf9vman/Utah.png
https://s22.postimg.io/4ohynndzz/Utah_default_car.png
https://s22.postimg.io/hem70qly7/Utah_car2.png
https://s22.postimg.io/k7fekrman/Utah_1st_ERROR.png
___event_
https://s16.postimg.io/a0mwxuf3p/event_viewer_warning.png
https://s16.postimg.io/km6s9ulf9/event_viewer_beam_NG_error.png

I did what you said and map now loads normaly BUT when i load a (probably) poligon heavy car the memory error will appear (or this time a differnt error).
Also i get warning about high memory usage ... so i should probably buy 16gb and replace this 2 sticks... after all it's not even that expensive.
Nadeox1 Sep 12, 2016 @ 7:07am 
If you receive the notification about low memory (from Windows), then the RAM usage is much higher than what the Task Manager is saying.
In my personal experience, I receive that error when I'm at about 95% of the Total RAM.
If that's also your case, then you should try to close any other program that is consuming RAM.
8GB should be enough to play, unless some other program are already reserving their own GB of RAM.
WroomWroom Sep 12, 2016 @ 11:28am 
I cleaned my PC and reseated my sticks.
Utah worked for quite some time and i coud respawn any car i wanted... windows would still warn me about high ram usage but i could play it for some time.
Then all of a sudden it failed again, error pops out, windows starts closing my programs to save some space etc etc...

So i think it's possible that one of the sticks starts failing when it heats up...

Another thing is that i have EVO 850 SSD and i think that one is reserving some ram for caching or some thing (not 100%).

Anyway, i think it's not map's fault.
WroomWroom Sep 12, 2016 @ 11:54am 
HEY !
I think i fixed my problem :D

It was the paging file that was causing this problem and to be more specific, it was set too low because i use SSD.
Now i read and interesting post and it was related to my problems with virtual memory ... so i ended up setting the paging file to be controlled by windows and now everything is fine.

I tried everything i could to crash the game and nothing could cause it.

I will still buy 2x8GB sticks when i can but if there are others with the same problem you can suggest them this option.

Cheers and thank you for tanking your time and helping me.

EDIT: yes it was definitely paging file. I played Utah for about 1 hour now and not even a windows ram usage warning.
Last edited by WroomWroom; Sep 12, 2016 @ 12:22pm
Nadeox1 Sep 13, 2016 @ 12:43am 
Good to know.
A tip: Don't use paging on your SSD. The continues Write/Read will reduce the lifespan of the SSD. Turn it on only on HDD.
< >
Showing 1-15 of 17 comments
Per page: 1530 50

Date Posted: Sep 9, 2016 @ 3:51am
Posts: 17