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
Fresh file, no ray tracing, lowest settings, offline mode. No matter what it kept crashing, meanwhile my game was literally playing perfectly yesterday.
is it this hard to analyse a problem by show the crash log you get, to narrow down the cause ?
btw yesterday was a GPU driver update no change at the game at all, you do not need to be a sherlock holms to find out what happend.
You do need to be Sherlock Holmes to find out what happened if the current driver version is 556.12 from June 27th, the same driver I've been playing on for hundreds of hours. Also, no log is being created from these crashes, at least for me. The only crash dumps are from days ago when I don't even recall any crashing, but if someone else could post theirs if they have one it might help.
I would recommend to anyone experiencing this to use DDU to reinstall GPU drivers anyway, just in case, even if you haven't updated drivers. Try older drivers first.
(for some reason I can't post on my other account).
Crash logs are typically in C:\Users\[NAME]\AppData\Local\CrashDumps
this is why you do not find a log
windows key+r
eventvwr
left side windows logs and there applications
now you see all logs, the eldenring crash logsa appear as a red one event ID 1000
so it looks like it is hard for normal users to use and maintain windows correctly.
"The program eldenring.exe version 2.2.3.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 90c
Start Time: 01dad81012f7361b
Termination Time: 6
Application Path: G:\SteamLibrary\steamapps\common\ELDEN RING\Game\eldenring.exe
Report Id: 150a15ac-5d81-4a51-9f9c-89dd6b681902
Faulting package full name:
Faulting package-relative application ID:
Hang type: Unknown"
this is a hang type problem what means the game stopped responding during a other fault in the system, this can be a other crashed application with a log short before this log or a third party software caused a problem, a deeper analysis would be needed to identify why the game stopped responding.
just to add this is not a crash of the game it got terminated by windows.
Faulting application name: eldenring.exe, version: 2.2.3.0, time stamp: 0x667d44fb
Faulting module name: eldenring.exe, version: 2.2.3.0, time stamp: 0x667d44fb
Exception code: 0xc0000005
Fault offset: 0x0000000001e9c926
Faulting process ID: 0x5248
Faulting application start time: 0x01dad76fda060554
Faulting application path: G:\SteamLibrary\steamapps\common\ELDEN RING\Game\eldenring.exe
Faulting module path: G:\SteamLibrary\steamapps\common\ELDEN RING\Game\eldenring.exe
Report ID: 8ad611a6-e8c6-4344-83fc-a67cb7ee08cf
Faulting package full name:
Faulting package-relative application ID:
The program eldenring.exe version 2.2.3.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 269c
Start Time: 01dad7eab1d987a9
Termination Time: 2
Application Path: G:\SteamLibrary\steamapps\common\ELDEN RING\Game\eldenring.exe
Report Id: 7d38fb2d-231e-4061-8661-8605d4cedeef
Faulting package full name:
Faulting package-relative application ID:
Hang type: Unknown
this log points to a problem with the directx communication, this can be related to a broken c++ installation, a defective GPU driver or faulty windows files.
a full system check would be need to eliminate the cause.