FIX Star Wars Jedi Survivor Crashing or Not Launching on PC

Struggling with Star Wars Jedi Survivor crashing on startup? In this video, we dive deep into the most common issues causing the crash and provide detailed solutions to get your game running smoothly again. Say goodbye to frustrations and hello to a seamless gaming experience!

FIX Star Wars Jedi Survivor Crashing or Not Launching on PC
FIX Star Wars Jedi Survivor Errors, Black Screen, Crashing Steam, Epic

Download drivers:

► Check articles with full guides:

▬ Contents of this video ▬▬▬▬▬▬▬▬▬▬
0:00 - Intro
0:14 - Update Graphics Card
2:13 - Close Unnecessary Processes
2:36 - Update Windows 11
3:13 - Disable Microsoft Services

► If you found this video useful, give us a like and subscribe to our YouTube channel.

[WindowsReport]

You can also verify your system files if it's bought via Steam or Epic. Otherwise, you can try adjusting the virtual memory settings on the PC:

1. Press the Windows key + S to open the search box, then type "advanced system settings" and click on "View advanced system settings" in the search results.

2. In the "System Properties" window, go to the "Advanced" tab.

3. Under the "Performance" section, click on the "Settings..." button.

4. In the "Performance Options" window, go to the "Advanced" tab.

5. Under the "Virtual memory" section, click on the "Change..." button.

6. In the "Virtual Memory" window, uncheck "Automatically manage paging file size for all drives" to enable manual adjustments.

7. Select the drive where your Windows installation is located (usually the C: drive).

8. Click on the "Custom size" option and enter the initial size (in MB) and maximum size (in MB) for the paging file. As a general rule, you can set the initial size to 1.5 times your system's physical RAM and the maximum size to 3 times the physical RAM. For example, if your PC has 16GB of RAM, set the initial size to 24576 MB (16 x 1024 x 1.5) and the maximum size to 49152 MB (16 x 1024 x 3).

9. Click on the "Set" button to apply the changes.

10. Click "OK" in the "Virtual Memory" window, then "OK" in the "Performance Options" window, and finally "OK" in the "System Properties" window.

Restart your computer for the changes to take effect.

Please note that adjusting virtual memory can have both positive and negative effects on your system's performance. Monitor your system after making changes to ensure that it's working as expected. If you encounter any issues, you can always revert the settings back to their original state.

[ThatLonelyBlob]

I always manage to get into the loading screen, however after the Jedi Survivior logo, it just crashes, and gives me a “EXCEPTION_ACCESS_VIOLATION” error.

[CubCamTV]

My game crashes on the second level "Koboh' at both the first box you can find and also when climbing the first wall that the battle droids discuss the view at.

It's run completely smoothly before but crashes at both points so i can't advance

Any advice?

[connor]

Things I did

So at first, I’d get on opening screen and it would crash. I fixed this by checking the game files. You can do this in steam. Once I got into the game, the game crashed in the opening cutscene (with cal on coruscant). I fixed THIS by updating the drivers. So, the game ran at 30 FPS at low graphics (for my PC) and I played through the first planet (took about an hour) at 30 FPS but when I got to the second planet the frames were SIGNIFICANTLY better.

[caedenward]

Updating the drivers allowed me to finally get to the main menu without the game crashing. Fingers crossed I can actually play it

[tomasriveiro]

Does anybody have the same problem the game just crash it and says “Game Crash Reported “

[shferr]

I tried pretty much everything but it still didn't work. I am getting around 50-60 fps on the loading screen. Then when the Jedi Survivor logo disappears I crash at around 60 fps. Is this EA or is this my graphic driver since mine is 740 and the required is 1070?

[feather]

the fact of it randomly crashing may be their fault, not yours. they know about issues with higher spec windows 11 systems and crashing despite everything working fine.

[mirzabeslagic]

I crash literally at the startup of the game, reason: out of video memory, I have 4090 with the latest drivers.

[gensor]

Just updated my amd driver, now star wars survivor is downloading more stuff, hopefully it works 🙏

[GamerJuli]

now im in jedha. And want back to mantis...but it chrashes on same scene..after talking with cere...gamebreak..:/ dont know what to do..

[lifeishort]

Updating drivers seemed to do the trick

[blumpous]

Broken games shouldn'tbe worth 70 bucks thanks for the help!

[MetalMatt]

i went to manage in the Origin/EA App and clicked on repair, its now redownloading 21gb. Lets see if it works...
*Edit
The repair worked. Runs well so far, not exaclty 60 fps in places but its good and on 4k with RT enabled and i believe max settings. I have 3080Ti TUF, 16gb Ram and Ryzen 2700

[davidfortygin]

My game doesn't even download!! I pre-ordered the deluxe edition. I have it on the EA app. It says that I own the game. When I click to download it says it's "preparing" but never actually loads. Then it says error please try again later. I followed EA's recommendation emptied the app cache. I restarted the computer. All my drivers are up to date. I have a brand new razor laptop so all the system requirements are more than good enough. WHY WONT IT EVEN DOWNLOAD? I've been trying to find a solution all day

[Richie]

disabling ray tracing did it for me, hope it helps.

[samanthawhite]

Thank you, I can finally play the game

[freshtendrills]

The opening part of the game ran fine, it was the Moment the game entered the actual open world that the problems started. And I mean hard crash. Having to restart just to get moving again. This turd won't even crash right. It's a goddamn hard lock. This game will need 6 goddamn months before it's playable. Fucking ridiculous.

[thelongestleg]

So everytime I see this pterodactyl on the game the game just stops responding

[sadman_]

Does anyone know if the new patch today fixed this issue?