Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Did you check your event viewer?
I don't get this, I can run it on basically max settings with no hiccups. The only times I've ever had issues was the occasional crash when summoning somebody. So how is it poorly optimized? When I check the numbers while playing none of my hardware is being stressed.
Maybe I'm just lucky.
OP, Check your event viewer like I said.. it may give you a better idea of what is going on.
The game does not handle aset loading well and it often pops in to late even tho the hardware has plenty of resources to keep it loading in, its optimised for consoles not for PC, consoles utilize memory differently which does not work at all on PC, this is why you see crashes when you summon as example cos it has to load in assets and so on, and if your PC is unstable it can even lead to 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 MONSTERROG\andy SID (S-1-5-21-4140841971-1510880865-3404835182-1001) 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."
and the errors are:
"The previous system shutdown at 1:53:13 PM on 6/2/2022 was unexpected."
"Dump file creation failed due to error during dump creation."
"Dump file creation failed due to error during dump creation."
"Unable to produce a minidump file from the full dump file."
"The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8076d4fb320, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000."
Chronological order from top to bottom.
And yea my laptop is quite old and is noticeably slower than when it was new.
Does this go paired with a Power Kernel error?
Open CMD as an Admin and type the following (including spaces): SFC /scannow
Hit enter , let the scan run , it will fix issues with ur windows installation this may help.
This prog is very good in figuring out possible cause of the crash , Used to use it myself when i had a busted PSU.