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:

[cridus]

How frequently do they happen? I think I know someone who may be interested into looking into it if these crashes can be reproduced often enough.

[Toad]

Originally posted by cridus:

How frequently do they happen? I think I know someone who may be interested into looking into it if these crashes can be reproduced often enough.

The most frequent was yesterday, where I had the game crash three separate times, but they were hours apart. I've never had them back to back in close succession, but I have experienced them infrequently since release (release day was the only exception, where the game crashed constantly, but that's been addressed as far as I know).

EDIT:

Also the only reason I mention multiplayer is that this is the most I've involved myself with co-op with the new 1.06 update, so it may be a factor.

[cridus]

Yeah then it's nothing out of the ordinary, I think. I too have days when it crashes multiple times (actually, it freezes), but most days are fine or I get only one crash in several hours of play time.

[Toad]

Yeah it might be just that. Only reason I thought to ask is that I'm also experiencing freezes, which I never had before the patch. The game will fully lock up for around 3-5 seconds, which always make me think the game has crashed. I thought maybe they were related somehow.

[Sonnenbank]

I really wonder how you could read specific info out of those logs without having real log.info ....
i dont have much experience with such stuff but from my noob perspective this messages just say:

Elden Ring crashed
Would be intersteing to hear from Dark-breed how he could read anything out of that.

Exception code: 0xc0000005
just means it crashed and could have many many different reasons.

So you basically have

Name of the app
Patch version of the app
it crashed

bunch of info that was generated after the crash and therefore i cant imagine how it has anything to do with the cause
this like the time it happend and an id that was generated for the crash etc.

how can you read specific info out of that ?
But again i am not experienced with this
happy to be enlightend

[Toad]

Originally posted by Sonnenbank:

how can you read specific info out of that ?

There may be additional information needed, but the general gist I got from reading other threads is that a lot of the number and letter codes can be matched to specific causes.

For example, an error code that said like 'abcd1234' could be the code associated with problems with your RAM or something. It gives the user an idea of where to start troubleshooting. Unfortunately I'm not computer literate enough to find out what all these codes mean, or which ones in particular to pay attention to.

[Sonnenbank]

Exception code: 0xc0000005 is pretty unspecific
thats what i allready said
it can be many different things

it basically just means "access violation"

for me as someone who has some basic understanding about computers but is not an expert at crash logs it would be really intresting to see how someone can get any specific things out of that logs

For your info these 3 lines
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


=
Elden Ring v. 1.06 crashed at time (and then a hexcode that is nothing more than year,day,time)

next two lines i dont know if you could read something out of that
its basically just an address and the id of the process

Fault offset: 0x0000000001dc172d
Faulting process ID: 0x47a4

next lines
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:

completely useless i guess

time app was startet in hexcode
path the file is located
path the app that contains the file is located
id that was generated for the report after the crash

no specific name
no specific id

[Toad]

Which is why I also said that there may be additional information required. There are many different logs, and I may still need to post those for someone to help me figure it out.

Regardless, both of us have been open about the fact that we are not knowledgeable in this area, so there's not much point in us arguing about it.

[dark-breed]

Originally posted by Toad:

Which is why I also said that there may be additional information required. There are many different logs, and I may still need to post those for someone to help me figure it out.

Regardless, both of us have been open about the fact that we are not knowledgeable in this area, so there's not much point in us arguing about it.

looks like there is a security software like trend micro running.

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 this one is trend micro

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:

this is clearly the trend micro caused crash of the game by using a dummy process unknown to analyse heuristic (what is against the rules of windows security).

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.

[Sonnenbank]

would you be so kind to explain how you come to that conclusion from the event log ?

not arguing , just asking

[dark-breed]

Originally posted by Sonnenbank:

would you be so kind to explain how you come to that conclusion from the event log ?

not arguing , just asking

by analysing many hundred event logs in the past months and my deep knowledge about how windows works, the post is updates for you ;-) to get a clue about what is going on.

[königplatzen]

Can be a game bug, but "access violation" could also maybe be faulty RAM?

The game tries to access a part of the memory, which is forbidden by OS. Usually, because the pointer is wrong, which can happen bc. of faulty RAM.

EDIT: Of course also 3rd party programs, which attach to the game somehow

[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

[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

i can read it exactly

a process unknown with version number 0.0.0.0 is causing a malfunction at a high offset far above the normal program offsets are running (it is normally a data offset and no app or driver offset)

that they are the specific trend micro dummy process offsets is by knowing and analysing systems with this specific error but the knowledge what is going on is by knowing how windows works.

[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

yeah exactly this unknown process is a only at runtime process because the timestamp is 0

such methodes where used in windows older than windows vista to check heuristical for virus code by copy the analysed app (eldenring.exe) to a data offset as runtime process but since windows vista such methodes break the security rules of windows (it is not allowed that two apps access the same variables at the same time without explizit permission of the creating app)

this is why a access violation is caused and windows stopps the programs that are involved

a similar error can be caused by the echo 360 RAM capture software because they use the same outdated function to capture RAM access but having both offsets points to trend micro because the echo 360 capture software only uses the second offset.

it is also possible that both apps are running this can only be confirmend by checking what is running in background what i do not via forum, only by chat because it is a pain in the ass to do it by forum communication.