Elden Ring Crash to Desktop - Event Viewer Logs

[Toad]

This thread is mainly aimed at hoping the user Dark-breed can help, but also wanted to make it public for any solutions. Been experiencing more crashes than usual in regards to multiplayer summoning, as well as recently seconds-long freezes that occur during those gameplay sessions.

Not super computer literate, so hoping for someone who is that can read the logs and give me an idea to start from.

Faulting application name: eldenring.exe, version: 1.6.0.0, time stamp: 0x62e397fc
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000240a4241363
Faulting process ID: 0x2358
Faulting application start time: 0x01d8b79c907a8194
Faulting application path: D:\Steam\steamapps\common\ELDEN RING\Game\eldenring.exe
Faulting module path: unknown
Report ID: 9077223e-b786-4fac-a87e-76f7a637b218
Faulting package full name:
Faulting package-relative application ID:

Also from previous crashes the last few days;

Faulting application name: eldenring.exe, version: 1.6.0.0, time stamp: 0x62e397fc
Faulting module name: eldenring.exe, version: 1.6.0.0, time stamp: 0x62e397fc
Exception code: 0xc0000005
Fault offset: 0x0000000001dc172d
Faulting process ID: 0x47a4
Faulting application start time: 0x01d8b6e073d40344
Faulting application path: D:\Steam\steamapps\common\ELDEN RING\Game\eldenring.exe
Faulting module path: D:\Steam\steamapps\common\ELDEN RING\Game\eldenring.exe
Report ID: 1e62fc23-748c-4235-8043-9909018c0332
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: eldenring.exe, version: 1.6.0.0, time stamp: 0x62e397fc
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000163c2c55363
Faulting process ID: 0x3d28
Faulting application start time: 0x01d8b6c9cf58d251
Faulting application path: D:\Steam\steamapps\common\ELDEN RING\Game\eldenring.exe
Faulting module path: unknown
Report ID: 5568ef26-e6b0-4be2-91b9-e8ecb9e7f99e
Faulting package full name:
Faulting package-relative application ID:

[dark-breed]

Originally posted by Sonnenbank:

yeha so kinda what i expected
its not like you can read it directly out of the log

but you have seen many logs similar that were then caused by trend micro

so basically this ?
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

for you what i read out of this

Faulting application name: eldenring.exe, version: 1.6.0.0, time stamp: 0x62e397fc
Faulting module name: eldenring.exe, version: 1.6.0.0, time stamp: 0x62e397fc
Exception code: 0xc0000005
Fault offset: 0x0000000001dc172d
Faulting process ID: 0x47a4
Faulting application start time: 0x01d8b6e073d40344
Faulting application path: D:\Steam\steamapps\common\ELDEN RING\Game\eldenring.exe
Faulting module path: D:\Steam\steamapps\common\ELDEN RING\Game\eldenring.exe
Report ID: 1e62fc23-748c-4235-8043-9909018c0332
Faulting package full name:
Faulting package-relative application ID:

it is a crash of the eldenring.exe during accessing a part of directx 12 communication offsets what can be caused by many things but mostly it is caused by a other app that captured RAM access or a malfunctioning GPU driver, because trend micro is involded at this system it is most likely also caused by trend micro but in the past there are many different causes for a crash around this offset (it can be a slightly different offset because there are many jump points of directx 12 and GPU driver connection around the offsets from 0x0000000001dxxxxx to 0x0000000001fxxxxx).

[Sonnenbank]

thx that made it clear. thumbs up
good explanation.

And it also confirms my initial thought.

you can not directly read out of that log information that its trend micro .
you can only see that trend micro causing problems produced very similar logs in the past.
And then you have to ask the used if he has that software on his system

[dark-breed]

Originally posted by Sonnenbank:

thx that made it clear. thumbs up
good explanation.

And it also confirms my initial thought.

you can not directly read out of that log information that its trend micro .
you can only see that trend micro causing problems produced very similar logs in the past.

yeah it is a huge amount of experience invold to know the offsets for examble this offset

0x0000000001df399b

is always a outdated DX11 gpu

because at this specific offset directx 12 returns the compatibilty string.

this is why i always ask for the logs, to find any new ones to add to my brain database or investigate them further.

windows uses a system to store driver connections, subsystem connections and system calls in a well organized RAM segment pattern since windows 95, till windows vista it was not possible to get the offset informations of them directly and a analysation of the memory dumps was needed but since windows vista most crashes get cataloged in the event viewer and my knowledge i gained since windows 95 formed the pattern "hardcoded" to my brain how windows works internally.

[Sonnenbank]

yepp thx again
knowing which offsett address range is linked to which error due to experience

@ Toad
sorry for thread hijacking

I was just really interested in how this works.
As i said i have no experience with crash logs but a basic understanding about computers
its not like i saw aegyptian letters and couldnt make anything out of it at all.

i could read all of that log but i was not sure what some of the values mean

[Sparhawk 59]

DB is very good at this stuff have to say he has helped many players

[Toad]

Originally posted by dark-breed:

looks like there is a security software like trend micro running

deinstall this bad security software trend micro is a useless fraud software at all.

if you need some more of this crash logs related to trend micro search for trend micro at the forum you will always find me identified it as the cause.

I'll look into this when I get the chance. Thank you!

[dark-breed]

Originally posted by Sonnenbank:

yepp thx again
knowing which offsett address range is linked to which error due to experience

@ Toad
sorry for thread hijacking

I was just really interested in how this works.
As i said i have no experience with crash logs but a basic understanding about computers
its not like i saw aegyptian letters and couldnt make anything out of it at all.

i could read all of that log but i was not sure what some of the values mean

ist in ordnung ich hab dir nur eine freundschaft angeboten da du wohl interessiert bist an dem how to und vermeiden wollte das wir schlicht nur über das forum kommunizieren.

[Flare |UKCS|]

I would try removing any 3rd party software you may have, like Rivatuner or recording software, or even your antivirus... start with no agents started then add them 1 by 1 until it crashes.

I had a crash with LoL, despite it working all the time no issue... turned out a LoL patch messed with Rivatuner, so as part of my trouble shooting I try get the system to basic then add the other stuff 1 by 1.

[Sonnenbank]

Originally posted by dark-breed:

ist in ordnung ich hab dir nur eine freundschaft angeboten da du wohl interessiert bist an dem how to und vermeiden wollte das wir schlicht nur über das forum kommunizieren.

thx
Ich nehme aber aus diversen Gründen auf Steam nur längerfristig Leute an, die ich auch im RL kenne.
Also ich hoffe du verstehst das nicht falsch.
Hast mir sehr weitergeholfen hier.
von daher top.

nehme aber halt niemanden an den ich nicht RL kenne
hab nur 20 leute drauf und 19 davon kenne ich mehrere Jahre RL

[dark-breed]

Originally posted by Sonnenbank:

Originally posted by dark-breed:

ist in ordnung ich hab dir nur eine freundschaft angeboten da du wohl interessiert bist an dem how to und vermeiden wollte das wir schlicht nur über das forum kommunizieren.

thx
Ich nehme aber aus diversen Gründen auf Steam nur längerfristig Leute an, die ich auch im RL kenne.
Also ich hoffe du verstehst das nicht falsch.
Hast mir sehr weitergeholfen hier.
von daher top.

nehme aber halt niemanden an den ich nicht RL kenne
hab nur 20 leute drauf und 19 davon kenne ich mehrere Jahre RL

ist in ordnung kein problem.

[cridus]

@dark-breed is there some sort of repository to look up these offsets and see the possible known causes of the errors? I'd love to bookmark such a page.
Also, can I report to you here the log the next time the game freezes for me at the start of a multiplayer session? >_>

[dark-breed]

Originally posted by cridus:

@dark-breed is there some sort of repository to look up these offsets and see the possible known causes of the errors? I'd love to bookmark such a page.
Also, can I report to you here the log the next time the game freezes for me at the start of a multiplayer session? >_>

Microsoft does not provide a database of offsets. I have gained the knowledge of which offset ranges are related to which subsystems, drivers and system calls over a period of 25 years through my work as a systems analyst and my own obsession with hunting windows errors. During my training I had many discussions about this stuff with the Microsoft teachers why this information is not official and an adequate approach is not taught.

Creating extensive tutorials on this is a sisyphus task as there are slight differences based on the hardware used and it is almost impossible to explain to anyone else why the offset address shows slight variance for certain things. my suspicion is that microsoft keeps this information under lock and key because a comprehensive catalog of the internal connections via the offsets gives a profound impression of how you can override the security functions of windows, just the fact that the structure of the memory segments over the individual system components with drivers communicating has hardly changed since windows 95 indicates that this core information relates to security-relevant structures in windows and is therefore kept secret.

So far this game became a tool to reveal problems in Windows better than any Microsofts own stuff can do.

During start of this game it revealed damage to the rights management at Windows userprofiles that got fixed by Microsoft in the last months during the build updates so they did not appeared again, but other problems appeared with broken directx 12 that can not be fixed because there is no installer for the 12_0 and above featurelevels and force a complete new Installation of Windows to get back to a fully working system, also some problems of the internal cleanup of Windows Updates get revealed that are causing wrong filesets, mostly at windows 11 but it can also happen at windows 10. At the Moment i can not recommence the Installation of preview Updates out of the appeared problems.

[cridus]

Ah. Well sheeet. Then you're a very valuable resource lol

[dark-breed]

Originally posted by cridus:

Ah. Well sheeet. Then you're a very valuable resource lol

I know only a hand full of ppl, that can look deep into this like i can and most of them are not gamers.
It's pure coincidence that I wanted to play this game and so I came across a defect in my Windows system that I didn't know before and started to take a close look at the identical error images here in the forum. I have identified a wide range of causes that lead to game malfunctions and cannot be fixed by the developers because the causes are in Windows itself.

[HtownCaltabiano]

Not going to run through every reply here but what fixed my crashing was:
1. Load Elden Ring
2. Upon load, switch to Window mode
3. Load continue game
4. Switch to full screen mode