Jump to content

Game Chrashing more often then it should


Recommended Posts

  • Replies 73
  • Created
  • Last Reply

Top Posters In This Topic

As a general rule, you are safe until the CPU temperatures start to get into the 85-95℃ range. (I don't know if they have published temperature ranges for GPUs, but would expect them to be in line with those for CPUs.) So it looks like it isn't overheating. That takes us back to either not enough memory or memory leaks exhausting it.

 

Did you resolve the Windows error messages? Have you rechecked the EventLog after each crash?

 

-Dubious-

Edited by dubiousintent
Link to comment
Share on other sites

I checked the log after the game froze and this is what is says

 

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) 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.

Link to comment
Share on other sites

That error is explained in this thread. Unfortunately all the "fixes" proposed there required editing the registry, which is not something I recommend lightly even to someone who is a computer professional. At the very least you need to "backup the registry" first, and I would recommend you create a "restore checkpoint" as well as having a "rescue disk" available. (Screw up the registry and Windows won't boot up.) If you don't know how to do any of that, then Google it or seek local professional help.

 

-Dubious-

Edited by dubiousintent
Link to comment
Share on other sites

So i confermed that the error happens after the crashes but i also found this

 

Faulting application name: FalloutNV.exe, version: 1.4.0.525, time stamp: 0x4e0d50ed
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0c28098d
Faulting process id: 0x28a0
Faulting application start time: 0x01d3208cd7551052
Faulting application path: E:\Steam\steamapps\common\Fallout New Vegas\FalloutNV.exe
Faulting module path: unknown
Report Id: e708b8e2-cc69-47eb-94b5-4d6bc6f59be7
Faulting package full name:
Faulting package-relative application ID:

Link to comment
Share on other sites

1. Be sure you are logged in using an "Administrator" account when making any changes to the registry. If for any reason that still does not let you, try editing after a "clean boot".

 

2. If the key value was missing before you did anything, then your DCOM did not register or get setup properly.

 

3. Did you reboot after removing the entries as described, and login in as an "Administrator" again? The reboot would be needed so the DCOM server would re-register. But some reports have said it did not even after a reboot. In which case, you may need to do a "repair install" from your Windows "rescue disk" in order to get DCOM installed properly.

 

4. See the article "Windows 10 Event 10016 Fix" for some straightforward instructions (in two steps) on how to add the DCOM configuration for the CLSID and APPID values, but compare with and use the ones from your error message instead. That author says he added the "Administrators" group for testing, but others have said it is necessary as well for the "Administrator" (singular) account to manage DCOM settings when installing programs.

 

-Dubious-

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...