@AkiraWarhiet One thing I notice in your dxdiag is that your computer's page file is almost entirely used, and 18 GB of page file in use is extremely high if you're not running anything demanding at the time of the dxdiag. Do you use gaming-related apps while playing, for example Razer software or an RGB controller? It would be helpful to know whether shutting down absolutely everything other than JS and the EA App and Steam makes a difference.
Additionally, have you read the post immediately above yours? I can't tell you whether this is what's happening on your computer without looking at the results of some hardware monitoring, e.g. an hwinfo log, but it's a plausible explanation. Even more so considering how in use your page file is and how little free space you have on C. By the way, it would be good to clear another ~15 GB, so 25 total free, just for the overall health of your computer.
If you'd like to upload an hwinfo log for people to look at, or you can analyze one yourself and post the results, that would be interesting as well. Check the post above this one for mine, which don't show at all the same effects as you or the previous post describe, but hopefully provide a useful data point.
Even closing all apps, within seconds of the game loading after the main menu the not enough vram message comes up.
Also I did clean up the c drive, still no change
@AkiraWarhiet Are you willing to upload an hwinfo log to show what's happening on your computer? In case you're not familiar, download hwinfo (it's free) from here:
https://www.hwinfo.com/download/
You don't need to install anything; just choose the Portable version, unzip it, and launch it from Downloads or wherever you like. If you do want the full installer, be sure to click the button for hwinfo itself, not for lansweeper.
Restart your computer, open hwinfo (but nothing else), choose Sensors Only, and click the button that's a sheet of paper with a + to start logging. Save the log file to your desktop for easy access. Wait five minutes, then launch Jedi Survivor and let it go until it crashes. Don't alt-tab out of the game or run any other programs, aside from the EA App of course, while you're testing. When you're done, click the same button to stop the logging.
Please upload the log to the third-party filesharing site of your choice (Google Drive, Dropbox, etc.) and link it for me. Either leave it in .csv format or, if you're going to use OneDrive, create a .zip file, and don't open the log before uploading it, or else my log reader might not be able to interpret it.
hopefullly i did it right
will say I did get to play for a couple minutes before it crashed this time
https://drive.google.com/file/d/1BTCX14uY6zvUeRYOM2XGDvx9kFjabhLe/view?usp=sharing
