resolved Recurring crashes, again

[DrSparrius]

Hi folks! You might remember me for the thread, 'recurring crashes', which I posted in january:

To reiterate, I got reliable CTDs 10-15 mins into gameplay. The game ran smooth elsewise. I was provided with a solution, which amazingly solved the issue for approximately two months (basically until a game session today), however now the CTDs are back with a vengeance and following the exact same pattern as before. The logs, which I have provided below, specify memory issues as the underlying cause. Going into the virtual memory settings, they are set as recommended since last time (32768 - 32768 for the fastest drive, and disabled for the other drives). My system specs:

NVIDIA GeForce GTX 1080 

Intel Core i7 8700K CPU @ 3.70 GHz 3.70 GHz

16 GB RAM

MSI Z730-A PRO motherboard

The game is installed on an SSD.

 

dcs.log dcs.log.old

[silverdevil]

2 hours ago, DrSparrius said:

Hi folks! You might remember me for the thread, 'recurring crashes', which I posted in january:

To reiterate, I got reliable CTDs 10-15 mins into gameplay. The game ran smooth elsewise. I was provided with a solution, which amazingly solved the issue for approximately two months (basically until a game session today), however now the CTDs are back with a vengeance and following the exact same pattern as before. The logs, which I have provided below, specify memory issues as the underlying cause. Going into the virtual memory settings, they are set as recommended since last time (32768 - 32768 for the fastest drive, and disabled for the other drives). My system specs:

NVIDIA GeForce GTX 1080 

Intel Core i7 8700K CPU @ 3.70 GHz 3.70 GHz

16 GB RAM

MSI Z730-A PRO motherboard

The game is installed on an SSD.

 

dcs.log 186.47 kB · 3 downloads dcs.log.old 182.1 kB · 3 downloads

hello you have a lot of errors in the logs. i believe it will help you to run a repair. it will be in your windows start menu 

null

[DrSparrius]

Ran a repair, but unfortunately the game crashes again, according to the same pattern. Here is the latest log file. Once again, the issue appears to be memory related. It is so strange though, that the issue should come back, having been fixed once already. Oh well, any other ideas?

dcs.log

[silverdevil]

1 hour ago, DrSparrius said:

Ran a repair, but unfortunately the game crashes again, according to the same pattern. Here is the latest log file. Once again, the issue appears to be memory related. It is so strange though, that the issue should come back, having been fixed once already. Oh well, any other ideas?

dcs.log 230.97 kB · 0 downloads

lots of errors for F-14

2023-03-05 16:52:39.390 ERROR   DX11BACKEND (16548): Failed to create shader resource view for /textures/liveries/f-14a-135-gr/vf-31 1991 ae205/HB_F14_EXT_PILOT_HELMET.dds. Reason: Not enough memory resources are available to complete this operation.

your pagefile is still being seen by DCS as 32 GB. have you tried to lower your graphics settings? 

is the pagefile on an SSD that has plenty of free space?

exclude the DCS folders in your AV software.

does the crash happen in single player?

another idea is to rename the Saved Games\DCS folder as a backup. then run DCS to allow it to recreate it. do not delete.

Quote

Go to Saved Games.
Rename your "DCS" (or DCS.openbeta) folder into "DCS_backup".
Launch DCS.

 

Edited March 5, 2023 by silverdevil

[DrSparrius]

4 hours ago, silverdevil said:

lots of errors for F-14

2023-03-05 16:52:39.390 ERROR   DX11BACKEND (16548): Failed to create shader resource view for /textures/liveries/f-14a-135-gr/vf-31 1991 ae205/HB_F14_EXT_PILOT_HELMET.dds. Reason: Not enough memory resources are available to complete this operation.

your pagefile is still being seen by DCS as 32 GB. have you tried to lower your graphics settings? 

is the pagefile on an SSD that has plenty of free space?

exclude the DCS folders in your AV software.

does the crash happen in single player?

another idea is to rename the Saved Games\DCS folder as a backup. then run DCS to allow it to recreate it. do not delete.

 

 

Alright

i) the graphics settings are already pretty much bottomed out, except for cockpit textures, where I need that extra resolution to be able to read the gauges on my monitor (it's not a particularly high resolution or big monitor). Elsewise, pretty much the lowest settings, and the game runs smooth in terms of FPS except for the crashes.

ii) this computer originally had two drives, C (237 GB SSD) and D (1 TB HDD). Windows, and the user data, are stored on that small SSD drive. Now, DCS was originally installed on the D (1 TB HDD) drive, but I moved it to a fresh, new E (1 TB SSD) drive last summer, to improve performance. And true enough, performance was much improved after that move. Additionally, some crashes, which were similar to the ones I experience now, disappeared after moving (removing and then installing again) DCS from the D to the E drive. However, all DCS save game/user files still remain on that original, small C SSD drive, where there's roughly 50 GB of free space out of that 237 GB volume. The pagefile size is set at roughly 32 GB per the instructions in that video, for the C drive, whereas it is disabled for the D and E drives. 

iii) (as of this writing, I haven't tried this yet)

iv) No, I was able to run the Instant Action Cold Start single player mission with no crashes, and generally better performance

v) (as of this writing, I haven't tried this yet)

 

I'll get back to you with more information once I've done point iii) and v), but I thought the above information might be useful at this stage, anyway

Edited March 5, 2023 by DrSparrius

[silverdevil]

4 minutes ago, DrSparrius said:

Alright

i) the graphics settings are already pretty much bottomed out, except for cockpit textures, where I need that extra resolution to be able to read the gauges on my monitor (it's not a particularly high resolution or big monitor). Elsewise, pretty much the lowest settings, and the game runs smooth in terms of FPS except for the crashes.

ii) this computer originally had two drives, C (237 GB SSD) and D (1 TB HDD). Windows, and the user data, are stored on that small SSD drive. Now, DCS was originally installed on the D (1 TB HDD) drive, but I moved it to a fresh, new E (1 TB SSD) drive last summer, to improve performance. And true enough, performance was much improved after that move. Additionally, some crashes, which were similar to the ones I experience now, disappeared after moving (removing and then installing again) DCS from the D to the E drive. However, all DCS save game/user files still remain on that original, small C SSD drive, where there's roughly 50 GB of free space out of that 237 GB volume. The pagefile size is set at roughly 32 GB per the instructions in that video, for the C drive, whereas it is disabled for the D and E drives. 

iii) (as of this writing, I haven't tried this yet)

iv) No, I was able to run the Instant Action Cold Start single player mission with no crashes, and generally better performance

v) (as of this writing, I haven't tried this yet)

 

I'll get back to you with more information once I've done point iii) and v), but I thought the above information might be useful at this stage, anyway

ok good info. idea. change your pagefile to E. the pagefile does not need to be on C and guessing the E SSD is newer and perhaps faster. and likely most free space.

[DrSparrius]

It appears that one of the above fixes (I applied all of them at once, including extending the firewall exceptions) solved the issue. It was probably down to moving the saved games folder to E: and changing the pagefile to E:

Thank you again!

Edited March 12, 2023 by DrSparrius

[silverdevil]

40 minutes ago, DrSparrius said:

It appears that one of the above fixes (I applied all of them at once, including extending the firewall exceptions) solved the issue. It was probably down to moving the saved games folder to E: and changing the pagefile to E:

Thank you again!

thanks for coming back and letting me know. perhaps the ideas will help others. good luck and clear skies!

[DrSparrius]

Just as an additional bit of information to this, I had a few good games after seemingly fixing the issue as per above, only for the crashes to return later today. I updated to the most recent open beta build, had an unremarkable flight without CTDs, only for the CTDs to return again, almost according to the same pattern I've described before. Only they seemed to occur much earlier than previously, even striking while my plane was still on the carrier whereas before it was usually something that happened 10-15 mins into gameplay. Note that I was not running on the MT exe (I got flickering lights all over my textures when I tried that in multiplayer). After the first CTD, I tried essentially bottoming out my graphics settings again but to no avail.

So I reset the DCS saved games folder (backed up the old one), and that appears to have fixed the issue again. Also, I adjusted the graphics settings a bit further, they're no longer bottomed out, some stuff is back on (for example SSAA or whatever it's called). In any case, I've attached the log files from the previous CTDs for your viewing pleasure. 

dcs.log dcs.log.old

[silverdevil]

10 hours ago, DrSparrius said:

Just as an additional bit of information to this, I had a few good games after seemingly fixing the issue as per above, only for the crashes to return later today. I updated to the most recent open beta build, had an unremarkable flight without CTDs, only for the CTDs to return again, almost according to the same pattern I've described before. Only they seemed to occur much earlier than previously, even striking while my plane was still on the carrier whereas before it was usually something that happened 10-15 mins into gameplay. Note that I was not running on the MT exe (I got flickering lights all over my textures when I tried that in multiplayer). After the first CTD, I tried essentially bottoming out my graphics settings again but to no avail.

So I reset the DCS saved games folder (backed up the old one), and that appears to have fixed the issue again. Also, I adjusted the graphics settings a bit further, they're no longer bottomed out, some stuff is back on (for example SSAA or whatever it's called). In any case, I've attached the log files from the previous CTDs for your viewing pleasure. 

dcs.log 173.6 kB · 0 downloads dcs.log.old 166.21 kB · 0 downloads

Quote

2023-03-12 21:58:30.989 INFO    APP (Main): MissionSpawn:spawnLocalPlayer 4407,F-14B
2023-03-12 21:58:30.994 ERROR   APP (Main): Error: Unit [F-14B]: Corrupt damage model.

2023-03-12 22:02:07.199 ERROR   DX11BACKEND (15044): Can't load image './Mods/aircraft/F14/Cockpit/Resources/IndicationTextures/HUD_Elements.tga'. Reason: Not enough memory resources are available to complete this operation.

2023-03-12 22:05:18.264 INFO    EDCORE (15044): 0x000000000002703b (edCore): ed::fatal_out_of_memory + 0x3B

looks like you are getting memory errors again. also F-14B seems to be currupt.