Jump to content
saXoni

New parts, VRAM errors

Recommended Posts

Hey,

 

Installed some new parts today: MSI Z370 Tomahawk, 16GB of Corsair RAM at 3466 and an already owned EVGA 1070 (it has played a lot of Squad). Although I haven't played in a while this didn't use to happen.

The GPU runs at 100% in the menu (might be normal), and as I load in the memory starts creeping up. Eventually it either just freezes upon server load or gives me this error:

 

FCzbc19.jpg

 

Chipset and GPU drivers are up-to-date, haven't changed anything else, really.

 

I google'd around but most of the hits were out of date.

 

Anyone got a fix?

 

Ty,

saX

Edited by saXoni

Share this post


Link to post
Share on other sites

First thing I'd check:

ingame graphic settings - be sure to turn off texture streaming.

Share this post


Link to post
Share on other sites

That's the setting that loads all textures at once and requires 16GB of RAM and 4 VRAM right? It happened with it both checked and unchecked. The 1070 shouldn't run out of memory regardless though, right?

Edited by saXoni

Share this post


Link to post
Share on other sites

Have you tried to delete Squad folder in %Appdata% folder???
I suspect your new rigs are the source of the problem. Doing a fresh install may help in this case if you haven't done already.

 

 

Here are some articles i have found related to your problem

 

 

 

 

 

 

Share this post


Link to post
Share on other sites

Did a clean install when the game went back to its current version. Works fine now, dunno if it was that or a buggy test. Thanks for the help.

Edited by saXoni

Share this post


Link to post
Share on other sites
Posted (edited)

3466 MHz, typo in first post.

Edited by saXoni

Share this post


Link to post
Share on other sites

Xmp profile isn't guaranteed. 3466mhz is a high overclock. Your ram might be good for it but the cpu or motherboard might not. Try ruinnng without Xmp profile turned on to see if it helps. 

Share this post


Link to post
Share on other sites

Like I said it works fine now, guessing it was the v10 test itself.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×