AJaromir

After like 20 attemps I am not able to reproduce gain. At one point it looked like it wasn't actually starting, but after a minute and a half it did. Something must be different after the clean system installation. There are few changes like turned off some tasks in background: Samsung Magican software, Sonic Suite Companion, Nvidia tray icon,... But the main difference is the drives are no longer remapped under VMD (IRST Raid controller) So I don't know what now. You may ask Flia to reproduce. Edit: I don't have installed all peripheral drivers yet. Edit 2: I will post the log once I will be able to reproduce again.

MS Defender. Entire DCS:W folder is in the antivirus exception list.

It is literally the same. Once I slot in, it works until I disconnect and go in another server. Then it is again 50/50. But more likely it freezes forever. Today I've finished clean system installation so later I will check how's the game running without any special system tweaks.

Bit offtopic: DCS:W sometimes runs well, sometimes it stutters for no reason. 90% of stutters are solved by disabling core parking on my system. But sometimes I have to restart the whole game to get smooth frame rate. Now back to issue: After installing Nvidia App back the issue appeared again. But still it can be fluke. I have to uninstall it and make like more attemps to be really sure. If there were people here with the same or similar problem and could try it, it would be a lot easier.

I don't think it's that. I purposely tried connecting to Shadow Reaper's and got to a regular static slot without freezing. As I wrote, I strongly suspect the Nvidia App is doing it. Because every time I've tried to take a video of the game crashing via the Nvidia App, the game has literally never crashed as if on purpose. But when I turned off the recording, the problem came back. Thus, I got the idea to uninstall the Nvidia App, and the problem disappeared. Now I've tried reinstalling it back, and I'm trying to see if the problem has returned or not.

O.k. Now I am like 90% sure it is caused by Nvidia App https://www.nvidia.com/en-us/software/nvidia-app/ I'm not sure if I should start a new thread on this topic.

Please try to uninstall Nvidia App if you have it.

@silverdevil Do you have GeForce Experience or Nvidia app? Looks like once I uninstalled the Nvidia App, it stopped freezing. I have to try it about 50 more times to be sure.

Yes. I tried to run slow repair. My personal opinion is the Issue is most probably in the "aircraft select" window. Because every time I reset the filter or switch to another plane, the game freezes every time. But every time it comes back on within a few seconds. It just always depends on the first selection. If that one doesn't freeze, then everything works relatively normally.

This is how the crash looks like: When I clicked by mouse on A-10CII, the game had frozen with not-responding message. Waiting solves nothing. Tried to wait like 10 minutes. Here is the full debug log: dcs.log This is where the freeze happens:

As if on purpose, when I try to take a video of the game crashing (by Nvidia App), the game never crashes.

O.k. TrackIR nor any controller have no effect on the issue. I tried to select aircraft in MP session with all devices unplugged, but crash still occurs.

I've noticed that TrackIR5 often crashes when the game crashes. Could this be related?

Yes. Check my other posts. It looks like this is how DCS load MP missions.

It seems to help prevent freezing after setting the filter in the aircraft selection to wait 10-20 seconds before clicking on the machine.

New attemp. Before starting the game the "tracks" and "logs" folder deleted Tried different server than before. dcs.log

For the next test I deleted the whole tracks folder and logs folder. Now the game definitely crashed. Here is the log: dcs.log

What about it? As I have written. It happens when I click on the aircraft in the aircraft select menu. Game stops responding. I can wait 10 minutes but nothing happens. I am loading MULTIPLAYER mission from the multiplayer list of servers.

For unknown reason this crash does not happen every time. It is like 1 out of 5 attemps result in no crash. No matter which aircraft I choose.

For first time game freezes - Not responding. I tried to wait few minutes, but no joy. This happens since the last two updates. OS Windows 11 24H2 MB: ASUS ROG STRIX Z790H Gaming WIFI CPU: Core I9 - 13900KF RAM: 64GB G.Skill DDR5 Ripjaws S5 5600MHz CL28 Dual Channel Kit 2x 32GB GPU: MSI GeForce RTX 4090 VENTUS 3X E 24G OC SSD: Samsung 990 PRO 2TB No mods used Whole DCS folder is set in antivirus exception list (defender) dcs.log

From manual, page 33: When the fuel selector (fuel cock) [11] is set to "Auf", both fuel lines from the forward and rear tanks are allowed to feed fuel to the booster pump. The booster pump draws more fuel than actually needed from both tanks and the surplus is routed back into the forward tank, thereby closing the valve for the forward tank. With this mechanism fuel effectively is drawn only from the rear tank as long as the engine gets enough fuel from it. When the engine pump starts to starve, the forward tank is "opened".

From the manual - page 33: When the fuel selector (fuel cock) [11] is set to "Auf", both fuel lines from the forward and rear tanks are allowed to feed fuel to the booster pump. The booster pump draws more fuel than actually needed from both tanks and the surplus is routed back into the forward tank, thereby closing the valve for the forward tank. With this mechanism fuel effectively is drawn only from the rear tank as long as the engine gets enough fuel from it. When the engine pump starts to starve, the forward tank is "opened". If I understand correctly, an excess should cause the highlighted non-return valve to close. I deliberately had the front fuel pump off and the rear fuel pump on, and tried flying 1km above the ground in the most economical mode, but even then the behaviour described in the manual did not happen. Fuel continued to be drawn evenly from both tanks. The only way to stop fuel being drawn from the front tank was to manually close the fuel valve. Considering that the behavior of the system does not match the description in the manual, I consider it a bug.

This is the P-51D Normandy cold start instant action. Check the shadows at 3D objects

You think it is possible to overflow 24GB VRAM and 64GB RAM in main menu?

No. I have set "leave the decision to the 3d application" for everything. Today i turned the game again and the issue is back. Seems like it happens randomly. Something is parking. But I don't know what because all cores are unparked.