PC Crashes or BSoD When Playing Stellaris
- Thread starter Nuukov
- Start date
-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Hi, been having several crashes on Stellaris in the last couple of days. They're EXCEPTION_ACCESS_VIOLATION, but I don't have much of a clue how to make Stellaris stop throwing them. I run a very heavy mod list and Stellaris easily eats 3.5GB+ of RAM. Could that be part of the issue?
Best in future to start your own thread rather than "me too" someone else's - your problem cause will almost certainly be different.
Your issue won't be memory as such since you have 16gb installed and a decent swap file. I was going to say your issue is almost certainly a problem mod or mods, but then I see these in dxdiag:
Unfortunately MS does not timestamp these entries - are you seeing that reboot or hard-hang ("LiveKernelEvent") when the Stellaris crash happens? If so you may have a video driver or card issue as the game is crashing in the DirectX 11 part of Windows.
Are you still seeing RtkAudioUniversalService and/or the Shadow Volume errors in the event viewer, coinciding with the game problem? Or something different now?@AndrewT I am still having the crashes even after doing what you suggested.
Ah sorry, I saw other people had posted their crash issues here and thought it best to keep crashes together.
I wish I could tell when that LiveKernelEvent is happening or what it would look like, all the latest crashes have been strictly EXCEPTION_ACCESS_VIOLATION. I've had occasional MACHINE_CHECK_EXCEPTION bluescreen during play with Stellaris and other games, but GPU and CPU temps have never been more than 60c/40c so I don't *think* its a cooling problem. I just reinstalled my nVidia drivers yesterday and saw another crash today, so it's not those drivers causing it as best I can tell.
I don't know how useful this could be, but looking that the exception.txt file in the last four crashes I've had, the last event in the Stack Trace has been related to d3d9.dll
Also, thanks a lot for helping us fix these problems
@AndrewT It seems not. In the event viewer the following occurred about 14 minutes before a crash:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user WINDOWS-D1REC3O\Xenos SID (S-1-5-21-1044223637-657909115-2555363737-1003) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Then it crashed:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Then this message:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user WINDOWS-D1REC3O\Xenos SID (S-1-5-21-1044223637-657909115-2555363737-1003) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
There are more all within 1 minute of the crash happening, but they mostly look similar to this.
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user WINDOWS-D1REC3O\Xenos SID (S-1-5-21-1044223637-657909115-2555363737-1003) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Then it crashed:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Then this message:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user WINDOWS-D1REC3O\Xenos SID (S-1-5-21-1044223637-657909115-2555363737-1003) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
There are more all within 1 minute of the crash happening, but they mostly look similar to this.
I'm sorry to say MACHINE_CHECK_EXCEPTION is virtually certainly a hardware fault. Most commonly CPU or memory, but the GPU is possible too. Sorry that's happened to you!
I have to say that does not look good, but the relationship of it to your symptoms is not at all clear to me, it's beyond my Windows knowledge or experience. Googling that finds many mentions of it but I don't see it linked to BSoD as such.
Are these only associated with playing Stellaris or crashes with it? If you don't play the game for a day, say, do you still see these?
I’ll find out for you! However, that particular message occurred within 30-60 seconds of a crash. Though when Stellaris crashes my PC, it doesn’t always go to a BSoD, sometimes it will just shutdown and restart.