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
what windows is it (10 or 11) ?
what GPU is used ?
what event log he get ?
https://www.youtube.com/watch?v=W8HfVIYQMKs
little hint this dism commands does not change anything at your windows this commands are related to the sfc file store container, it update it for a sfc /scannow repair.
this two commands are useless at all because they only check the existing container for errors and do nothing at all, they are only used by admins to check containers afterward a cleanup /restorehealth or a update of windows if the container got updated.
dism /online /cleanup-image /checkhealth
dism /online /cleanup-image /scanhealth
He is using Windows 10, GPU is NVIDIA GeForce RTX 2070, and the two event log errors I saw were 0x 0000409 and 0x 0000005.
the offset and eventually additional informations are contained in the log
For all I know it was the clean restart that did it.
i analyse and fix whitescreen crashes since 10 months now.
there are at the moment 41 causes for a whitescreen crash in my list and one of them is a internal windows crash where a restart of windows will help and some other causes where a restart also resolve the problems cause (like a waiting update or a partial crashed GPU driver).
Faulting application name: eldenring.exe, version: 1.8.1.0, time stamp: 0x6396cee8
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0xbb4
Faulting application start time: 0x01d91a5cc08068ba
Faulting application path: D:\SteamLibrary\steamapps\common\ELDEN RING\Game\eldenring.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: 79b01c18-addd-43d0-bd32-aa4da543a2df
Faulting package full name:
Faulting package-relative application ID:
Faulting application name: eldenring.exe, version: 1.8.1.0, time stamp: 0x6396cee8
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000020a48781860
Faulting process id: 0x425c
Faulting application start time: 0x01d91a4417096332
Faulting application path: D:\SteamLibrary\steamapps\common\ELDEN RING\Game\eldenring.exe
Faulting module path: unknown
Report Id: 8d54c52c-fc6e-4a04-bcc5-f295ad30ef86
Faulting package full name:
Faulting package-relative application ID:
Just tried launching it again through the seamless coop .exe and it is currently working.
the first one is a internal crash of a file related to internal crash of the explorer
the second one is related to a bad antivirus software trend micro or a windows security incompatible capture software (ICUE, echo 360, some other LED control software that use RAm capture routines)
trend micro cause a security breach for examble in relation to EAC use so the seamless coop mod could be able to bypass this EAC related 0xc0000005 (access violoation)
if trend micro is in use delete this garbadge software.
I believe that file, ucrtbase.dll is part of the Visual C Runtime package. You should be able to fix that one by reinstalling the VC runtimes.
https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/
Download, extract to a temporary folder, run "install_all.bat". After installation, you can delete the temporary folder and then reboot the PC.
yes you could be right but if trend micro is installed it can cause similar problems with this file at random applications since both crash logs have the same timestamp i would first point to trend micro problems.
No trend micro or echo 360. Only antivirus I see is McAfee but he does have ICUE. So if it happens again we could try disabling ICUE to see if that fixes it.
Thank you for your help, I really appreciate it.
Will try this too, thank you
McAfee can also cause the same problems from time to time.
Got it, will try these fixes one at a time and see if it crashes again. If I figure out the cause is anything listed I will post an update.
ICUE is known to cause issues with EAC. When it doesn't cause a crash, it can cause stutters. Update it to the latest version or outright delete it.
McAfee is just... bleh. Windows Defender is good enough and doesn't cause problems with this game or others.