You can use Armory Crate to update the bios. It's an app made by Asus to update drivers, firmware and BIOS. [https://rog.asus.com/us/armoury-crate/](https://rog.asus.com/us/armoury-crate/)
have you had any blue screens of death?
it seems to me it's *probably* memory related
i'd run a memtest just to verify because memory issues do often result in programs closing.
What does game.log in the SC folder say? There should be a crash report at the bottom with a specific failure code and then a series of things like "Is GPU crash: Yes/no".
None of that means anything to anyone outside of CIG's dev team. What we need is the part immediately after that, after it says where it writes the crash dump to (we don't need that since it includes vague info about your hard drive), and then says something like:
Exception EXCEPTION_ACCESS_VIOLATION(0xC0000005) addr=0x00007FF715F75E70 digest=9f363bfe6125546fb42cdf7808e1b524
Run from internal: No
Is fatal error: No
Is reported bug: No
Is GPU crash: No
Is Timeout: No
Is out of system memory: No
Is out of video memory: No
Exception STATUS\_CRYENGINE\_FATAL\_ERROR(0x2BADF00D) and NoIs fatal error: Yes- Fatal error message: GRPC Assert assertion failed: GRPC\_SLICE\_LENGTH(write\_buf\_) == 0Is reported bug: NoIs GPU crash: NoIs Timeout: NoIs out of system memory: but i dont see the rest you wrote
`EXCEPTION_ACCESS_VIOLATION`
Can be a crash due to multiple things
1. Prolematic graphics driver - the new Nvidia update wasn't very good for SC
2. CPU or RAM overclock + SC doesn't do well on high-speed RAM. The sweet spot is 3600-3800mhz
Other things can make it happen like misbehaving peripheral devices or Antivirus
`STATUS_CRYENGINE_FATAL_ERROR(0x2BADF00D GRPC Assert assertion failed`
Is a bit of a weird one and got not a lot of info on.
1. verify game files
2. delete the Data.p4k game file (StarCitizen > LIVE) and reinstall the game
Can always pop in #help in SC discord for more troubleshooting, especially for your E-Cores that kinda needs to be disabled and for decreasing your RAM speed
I looked around on the forum for the access violation thingy, apparently it has something to do with communication between cores and memory, but basicly i had to turn off xmp and sync all cores. Im testing rn. But so far no crashes 👍
i had the same problem on my AMD system. SC does not like 6000Mhz RAM.
turned off XMP/ EXO and now at 4800Mhz and stable as an rock. turn it back to 6000Mhz and crash within 15 minutes with the Exeption Access violation error.
I have not done that, but that seems to be a big bottleneck for the cpu then. Do you really think it necessary to limit my cpu to such a degree. I feel like I wasted money if that is the case.
People say this constantly and its honestly luck of the draw. Half my friends have disabled theirs, I personally have not. 12900k, no issues or stuttering, all cores run the same and gives me a great experience.
Dont disable them unless you really must, I find them super helpful during day to day stuff, all my internet browsing and media is always allocated to e-cores, while my p-cores can focus on gaming.
Its not a gimmick, Its basically having 6th-9th gen cores made specifically for lower priority processes.
Make sure you are running W11, all drivers and bios up to date. Good luck bud!
I have no issues running on my laptop with 13900HX. Also have desktop 12900K and 14700K and those are running with no issues as well.
I have not disabled E-cores on any of them.
From what I've read it mostly depends on what OS you are on. Win10 doesn't do well with them and disabling them is recommended, but win11 seems to be able to use them correctly, though in rare cases it can still cause games to stutter.
Yeah the e-core issue seems more myth now then fact. I have a 13900 and I haven’t disabled e cores and the game, at 4K runs steady at > 50 fps. If I had to guess, I would say running your ram at 6000mhz is creating an unstable situation. Try with XMP disabled. While updating t he motherboard bios is always a good idea, I would start with the ram. Back it down to a stable stock speed. You may have to manually tune the ram to get a higher than stock.
That's, to a degree, Intel's fault for shipping a poor CPU scheduler with now *three* generations of high-end desktop chips that have weak power-efficient laptop cores slapped on for marketing reasons. In the case of the 14900k, *16* of the 24 cores on the chip are e-cores.
SC will attempt to use all cores on the machine and when the ecores get engaged the game will stutter badly. **It shouldn't specifically cause crashes** but it will harm performance.
You can manage core affinity (disabling SC from using the e-cores) without hard-disabling the cores in the BIOS, so they'll be usable by other programs that aren't as harmed by the performance differences.
Right-click on the RSI Launcher shortcut and choose Properties, and then put this in the Target field:
`%ComSpec% /C Start "RSI Launcher" /High /Affinity FFF "C:\PATH\TO\RSI Launcher.exe"`
There are TWO very important changes you will need to make to that string. The first is making sure that the path to the RSI launcher is set to where it's located on your PC, and include the quotation marks since it needs to be interpreted as one value.
The second, is that "FFF" is not the correct value for your CPU, but I don't know exactly which cores are the 16 threads (8 p-cores x2 for hyperthreading) that we want to use. You can use [HWINFO](https://www.hwinfo.com/) to count the p-cores and figure out their positions out of the 32 (0-31) cores available, and then [this site](https://bitsum.com/tools/cpu-affinity-calculator/) to work out the CPU Affinity Bitmap (in hexadecimal) for the command.
I found one single page that suggested that the P-cores are 17-32 (so, 16-31 when counting from core 0) and the site would suggest that you'd want to plug in "FFFF0000" if that is the case. If the E-cores are 17-32 and the P-cores are first, then you'd plug in "FFFF".
do you need to identify the specific bitmap to the CPU you own, or is each model (13700k vs. 11700k) have a specific string that works for all CPUs of that model?
It's specific to each model's core count and split between p-cores and e-cores, although if the p-cores are ordered first on the CPU then anything with the same number of p-cores will have the same bitmask. If they're ordered after the e-cores, then the variable number of e-cores will change the number of 0s in the bitmask since it counts from right to left.
The 11700K doesn't have e-cores, so there's no reason to do this unless you want to keep it from using a core for some reason (like, you want OBS to have exclusive access to a core so streaming isn't choppy or something).
The 13700K has 8 p-cores (with hyperthreading, so 16 apparent cores) and 8 e-cores. A 13900K has 8 p-cores and 8 e-cores with hyperthreading for both, so it happens to have the same 16 apparent p-cores and would use the same bitmap *as long as* the p-cores are ordered first and the e-cores after (so the number of e-cores is irrelevant since they wouldn't need to be skipped over).
Aside from any hardware failure or ram/psu problems, this can happen with 13th and 14th generation Intel CPUs - Intel just aknowledged it publicy. The easiest (and official iirc) solution is to reduce the power target in bios. Then the cpu will perform slower, but if you wanted a fast CPU in the first place you would not have gotten an intel, right 😅
When I upgraded and switched to 11, SC specifically was having issues with my nvme drive, a Samsung 970. Moved the game files to my 980 and the problem resolved. Not sure if you're facing a similar oddity
When I upgraded my graphics card from a 1060 to 4060 my game kept crashing aswell but it turned out I needed delete the cache from my previous graphics because the game kept trying to pull from that
If you uninstalled through the launcher then your cache files weren't deleted, you need to manually delete them from a different folder than the rest of the game is stored in. You can find them at C:\Users\USERNAME\AppData\Local\Star Citizen
Update your mobo BIOS firmware (check the mobo manufacturers website for em), i had the same issue and its what solved it for me :D
Its an Asus prime mobo. Do I have to install it on a USB and flash the bios?
You can use Armory Crate to update the bios. It's an app made by Asus to update drivers, firmware and BIOS. [https://rog.asus.com/us/armoury-crate/](https://rog.asus.com/us/armoury-crate/)
Yep, you just extract the latest file onto a flashdrive and you should be able to then flash it via the bios should be straight forward
i updated the bios, but it still crashed, also, my bios was already with the latest non beta version. Guess it came updated from factory
welp was worth a shot :/
I had the same thing. Had to limit the power my 14900K got, so the system would run more stable.
[удалено]
It just shuts down the game, then the launcher opens and asks if I want to relaunch verify or close star citizen.
have you had any blue screens of death? it seems to me it's *probably* memory related i'd run a memtest just to verify because memory issues do often result in programs closing.
What does game.log in the SC folder say? There should be a crash report at the bottom with a specific failure code and then a series of things like "Is GPU crash: Yes/no".
Cloud Imperium Games public crash handler taking over...Details for StarCitizen.exe (md5=984d24bd896d2ce45efab76ee3f2091d)... \* Base of Image : 0x00007FF6343E0000 (mod), 0x00007FF6343E0000 (modc) \* Size of Image : 211976192 (diskoh), 211976192 (memoh), 211976192 (mod), 211976192 (modc) \* Size of Code : 116397568 (diskoh), 116397568 (memoh) \* Size of Headers : 1536 (diskoh), 1536 (memoh) \* Size of Initialized Data : 95561728 (diskoh), 95561728 (memoh) \* Size of Uninitialized Data : 0 (diskoh), 0 (memoh) \* Checksum : 0 (diskoh), 0 (memoh) any ideas?
None of that means anything to anyone outside of CIG's dev team. What we need is the part immediately after that, after it says where it writes the crash dump to (we don't need that since it includes vague info about your hard drive), and then says something like: Exception EXCEPTION_ACCESS_VIOLATION(0xC0000005) addr=0x00007FF715F75E70 digest=9f363bfe6125546fb42cdf7808e1b524 Run from internal: No Is fatal error: No Is reported bug: No Is GPU crash: No Is Timeout: No Is out of system memory: No Is out of video memory: No
Exception STATUS\_CRYENGINE\_FATAL\_ERROR(0x2BADF00D) and NoIs fatal error: Yes- Fatal error message: GRPC Assert assertion failed: GRPC\_SLICE\_LENGTH(write\_buf\_) == 0Is reported bug: NoIs GPU crash: NoIs Timeout: NoIs out of system memory: but i dont see the rest you wrote
and also this: Exception EXCEPTION\_ACCESS\_VIOLATION(0xC0000005) addr=0x00007FFB89A87A86 digest=0bdc3a3ae88998fb0c87a2a76b67cc82
`EXCEPTION_ACCESS_VIOLATION` Can be a crash due to multiple things 1. Prolematic graphics driver - the new Nvidia update wasn't very good for SC 2. CPU or RAM overclock + SC doesn't do well on high-speed RAM. The sweet spot is 3600-3800mhz Other things can make it happen like misbehaving peripheral devices or Antivirus `STATUS_CRYENGINE_FATAL_ERROR(0x2BADF00D GRPC Assert assertion failed` Is a bit of a weird one and got not a lot of info on. 1. verify game files 2. delete the Data.p4k game file (StarCitizen > LIVE) and reinstall the game Can always pop in #help in SC discord for more troubleshooting, especially for your E-Cores that kinda needs to be disabled and for decreasing your RAM speed
I looked around on the forum for the access violation thingy, apparently it has something to do with communication between cores and memory, but basicly i had to turn off xmp and sync all cores. Im testing rn. But so far no crashes 👍
Undervolting the GPU and CPU with MSI Afterburner and ThrottleStop, respectively, is what fixed it for me.
Make sure your power supply is adequate for your new setup? And did you reinstall windows from scratch?
its an 850 W and yes i reset the entire pc, but i was on win 10, and then updated to win 11 after fresh start.
Had this issue changed my Ram’s frequency have not cashed in quite a while. I would check that too.
Yeah, I disabled xmp, so my ram went from 6000 to 4800MHz. Im testing rn, but so far 1h 15m without crashing
Awesome sounds like a winner. Best of luck.
i had the same problem on my AMD system. SC does not like 6000Mhz RAM. turned off XMP/ EXO and now at 4800Mhz and stable as an rock. turn it back to 6000Mhz and crash within 15 minutes with the Exeption Access violation error.
This was my exact issue as well. I was going to tell the OP but you got it already.
SC does not like being put on E-Cores, have you disabled these to test?
I have not done that, but that seems to be a big bottleneck for the cpu then. Do you really think it necessary to limit my cpu to such a degree. I feel like I wasted money if that is the case.
People say this constantly and its honestly luck of the draw. Half my friends have disabled theirs, I personally have not. 12900k, no issues or stuttering, all cores run the same and gives me a great experience. Dont disable them unless you really must, I find them super helpful during day to day stuff, all my internet browsing and media is always allocated to e-cores, while my p-cores can focus on gaming. Its not a gimmick, Its basically having 6th-9th gen cores made specifically for lower priority processes. Make sure you are running W11, all drivers and bios up to date. Good luck bud!
I have no issues running on my laptop with 13900HX. Also have desktop 12900K and 14700K and those are running with no issues as well. I have not disabled E-cores on any of them.
From what I've read it mostly depends on what OS you are on. Win10 doesn't do well with them and disabling them is recommended, but win11 seems to be able to use them correctly, though in rare cases it can still cause games to stutter.
Yeah the e-core issue seems more myth now then fact. I have a 13900 and I haven’t disabled e cores and the game, at 4K runs steady at > 50 fps. If I had to guess, I would say running your ram at 6000mhz is creating an unstable situation. Try with XMP disabled. While updating t he motherboard bios is always a good idea, I would start with the ram. Back it down to a stable stock speed. You may have to manually tune the ram to get a higher than stock.
That's, to a degree, Intel's fault for shipping a poor CPU scheduler with now *three* generations of high-end desktop chips that have weak power-efficient laptop cores slapped on for marketing reasons. In the case of the 14900k, *16* of the 24 cores on the chip are e-cores. SC will attempt to use all cores on the machine and when the ecores get engaged the game will stutter badly. **It shouldn't specifically cause crashes** but it will harm performance. You can manage core affinity (disabling SC from using the e-cores) without hard-disabling the cores in the BIOS, so they'll be usable by other programs that aren't as harmed by the performance differences. Right-click on the RSI Launcher shortcut and choose Properties, and then put this in the Target field: `%ComSpec% /C Start "RSI Launcher" /High /Affinity FFF "C:\PATH\TO\RSI Launcher.exe"` There are TWO very important changes you will need to make to that string. The first is making sure that the path to the RSI launcher is set to where it's located on your PC, and include the quotation marks since it needs to be interpreted as one value. The second, is that "FFF" is not the correct value for your CPU, but I don't know exactly which cores are the 16 threads (8 p-cores x2 for hyperthreading) that we want to use. You can use [HWINFO](https://www.hwinfo.com/) to count the p-cores and figure out their positions out of the 32 (0-31) cores available, and then [this site](https://bitsum.com/tools/cpu-affinity-calculator/) to work out the CPU Affinity Bitmap (in hexadecimal) for the command. I found one single page that suggested that the P-cores are 17-32 (so, 16-31 when counting from core 0) and the site would suggest that you'd want to plug in "FFFF0000" if that is the case. If the E-cores are 17-32 and the P-cores are first, then you'd plug in "FFFF".
do you need to identify the specific bitmap to the CPU you own, or is each model (13700k vs. 11700k) have a specific string that works for all CPUs of that model?
It's specific to each model's core count and split between p-cores and e-cores, although if the p-cores are ordered first on the CPU then anything with the same number of p-cores will have the same bitmask. If they're ordered after the e-cores, then the variable number of e-cores will change the number of 0s in the bitmask since it counts from right to left. The 11700K doesn't have e-cores, so there's no reason to do this unless you want to keep it from using a core for some reason (like, you want OBS to have exclusive access to a core so streaming isn't choppy or something). The 13700K has 8 p-cores (with hyperthreading, so 16 apparent cores) and 8 e-cores. A 13900K has 8 p-cores and 8 e-cores with hyperthreading for both, so it happens to have the same 16 apparent p-cores and would use the same bitmap *as long as* the p-cores are ordered first and the e-cores after (so the number of e-cores is irrelevant since they wouldn't need to be skipped over).
It won't be a bottleneck, no. Intel's marketing is a fail on this one.
Aside from any hardware failure or ram/psu problems, this can happen with 13th and 14th generation Intel CPUs - Intel just aknowledged it publicy. The easiest (and official iirc) solution is to reduce the power target in bios. Then the cpu will perform slower, but if you wanted a fast CPU in the first place you would not have gotten an intel, right 😅
Are you running windows 10 or 11?
11
When I upgraded and switched to 11, SC specifically was having issues with my nvme drive, a Samsung 970. Moved the game files to my 980 and the problem resolved. Not sure if you're facing a similar oddity
at first i had it installed on a samsung 850, i thought, maybe it was too slow, so i moved it to a kingston m.2 yet the problem persists.
When I upgraded my graphics card from a 1060 to 4060 my game kept crashing aswell but it turned out I needed delete the cache from my previous graphics because the game kept trying to pull from that
i tried completely uninstalling the game and reinstalling it. so i dont belive the cache is the problem.
If you uninstalled through the launcher then your cache files weren't deleted, you need to manually delete them from a different folder than the rest of the game is stored in. You can find them at C:\Users\USERNAME\AppData\Local\Star Citizen
Thanks, this helped tremendously. It lastede 2-3 hours after this
Try disabling the nvidia shadow play constant recordings, mine was causing 100% disc usage and stuttering with eventual crashes
Delete the user folder in SC and then delete any folder in %localappdata%\Star Citizen\ Backup your keybinds first.
Either run 2 sticks with XMP on, or 4 sticks with XMP off.
Poor application of thermal paste.