BSOD since about Nov. 2024

@Malizar

Thank you for your analysis… The connection to 24H2 makes sense. Other had a similar conclusion. Maybe CCP can’t fix it by themselves but they might be in the better position to address it with Microsoft. If people do it individually, then they always receive the same standard answers, which don’t help at all.

I encourage people to create tickets with CCP… Only that way CCP can be made aware of it and hopefully get their help

I have downgraded my computer to 23H2 now… I was able to use 7 clients for good 3 hours with 21H2 this morning. Usually, I would have seen at least 1 freeze by then. I will continue with having a close look on it but my searches yesterday revealed a wide variaty of issues with 24H2 and all of them are reporting freezes. Other games as well as CAD as an example. And all are reporting it after the update to 24H2.

1 Like

Too lazy to swap accounts. Apok Sazlak here and I downgraded to 23h2 and have not crashed since with 6 or more accounts. Defintely a 24h2 issue.

3 Likes

You are not alone.

I am a fellow 6 client enjoyer and I have been chasing this issue since November.

It has been many weeks of work trying to determine if it was a code change I made in one of the tools I work on (happy to discuss with CCP if they would like more info - but they are VERY aware of tool) - or something external. Gone from latest code all way back to old old code one feature at a time - all way back to release from years ago.

I have 2 machines I play EveOnline - a desktop i9-7920x 128GB RTX4070 (latest insider build) and a Laptop 6900HX 32gb RTX3070Ti (24H2)- both have same issue.
Using DX11 (mumble overlay user)
I have tried various graphical settings including potato mode.
I have performed DDU on both machines. Still same error.

I only came across potential 24H2 issue a few days ago - and it totally ties in timewise with my issues.

I sent off a support request - and was asked to start with loglite, but this is pointless as the logs are not written until requested - but this is pointless as the machine has fully crash at that point.
When crash occurs - the mouse still works, there are some eve-sounds, some animation… but nothing responds.

It is as if the whole Windows process scheduler has been stalled. Event log seems very quite about the issue once rebooted.

roll back to 23H2… it will solve your issue… I have a stable computer since last weekend and Eve is running for hours without any freeze

not an option on my machines without full reinstall.

I reinstalled my Windows last weekend. Although I really didn’t like the idea… on the other hand, I have now a fresh and clean installation. But of course, this is your decision. I only can say, that the trouble started with 24H2 and is fixed with 23H2. I don’t know, how long it will take Microsoft to fix the issue and provide a patch.

yup. that is the worry :-/
I’ve had a few months now and not sure I can stick another 6+
Will probably reinstall from 23H2 ISO on laptop “soon” and see how I go before commiting to desktop.

The PoE2 guys having a similar problem have been setting processor affinity to their client exe - to not use core0/1
Written a little tool to do it automatically - will see how it goes. If it works - I’ll pretty it up and release.


Done a little tool to restrict eve processes from a number of cores (as per PoE2 fix that people are using)

I have NO idea if this is going to resolve the issue - but it will be fun finding out.
It works by finding the eve processes (same way other eve tools find them) and setting processor affinity based on the dropdown at bottom.

Will update in few days if no further lockups (and of course share tool).
If you wish to do it manually - you can start the launcher, find the process in task manager and then set processor affinity there. All new processes started from launcher (until closed) will have same affinity.

This could of course have no effect and be a waste of my time :frowning:

little update

I ran for a while with 2 cores shutoff for eve processes…
my little tool looks for not responding jobs and initially I got it making them realtime for half a sec.
I had a few times it looked like it would crash and things came back - so I thought it might have sorted it.
However earlier today I had a full crash… but it falted for a little when I was able to watch logs as I had logs showing to screen.
4 of 6 clients showed as not responding along with launcher.

I changed tool to kill off not responding eve jobs after 100seconds of being not responding… which obviosuly killed those clients - but didnt trash machine.

partial success then.

What this tells me is that those clients that crashed (and launcher - always seems to be launcher too) are making cpu go crazy and not allowing any cpu for other stuff (like responding to mouse clicks etc) - race condition ahoy.

Making 2 cores of cpu still available for non-eve processes allowed me to see a little more of the problem.

more importantly - I was running loglite - and am able to save logs after crash (and recovery)
added lsw dump to my current petition - 2311855

had seconds crash with a number of clients going unresponsive, and launcher.
my little tool killed first one and launcher and rest became responsive.
didnt get lsw logs this time :frowning:
Will keep at it and send logs each time

At least I can survive lockups now :slight_smile:

128GB memory DDR5? If so, all 4 slots filled or 2x64GB?

8x16GB DDR4
Gigabyte X299 AORUS Gaming 3-CF motherboard
i9-7920x

1 Like

Wondering if this is related to my issue at all.

Basically after a number of jumps or an hour or so in one aystem, it starts eating CPU cycles until I face two choices:

Close and reopen

Wait for it to crash

Ok, then you should be ok. I read somewhere that filling your system with 4x DDR5 modules, makes your system unstable.

It is 24H2… I am running 23H2 since a week now… Constantly 7 clients parallel. for hours… not a single freeze nor crash.

1 Like

CCP Response to my petition and dump files :

un-install 24H2
1 Like

LOL! Well that’s useful to those who have done it in the last 9 days at least and still have the option.

there are ways if you are <60 days also.
I am way past there :frowning: