Jump to content

DCS.exe still running after game exit


unknown

Recommended Posts

Over the last 2(?) months i saw repeatedly that the DCS.exe is still running after i exit the game from the main menu. The game will close, i'm back on my desktop but i keep having a "high" CPU load -> fans keep spinning "high" and if i check the windows task manager i see the DCS.exe is still running. Once i didn't notice it immediately and startet DCS again later, after closing the game i had 2 DCS.exe still running in the windows taskmanager.

This happened in VR, 2d, SP and MP sessions, but it is not happening always. This was happening with my old Win 10 pro install, my clean Win 10 pro install and now with Win 11 pro. This happend with my old DCS install, i fresh DCS install and after doing a slow repair.

I don't know if the latest log will help(MP session in VR), i had to manually close the DCS.exe again via the taskmanager.

dcs.log

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

Since the problem seems to be a DirectX issue, perhaps upgrading your ATI driver to the latest version could help.

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600X - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to comment
Share on other sites

I'm running the latest drivers for everything, GPU, chipset, BIOS, sound....

BTW, this also happend with my old 1080ti !

Is this maybe related to not running an english Win OS but a german? For example some keybinds don't work like expected, DCS keybind is "left alt + y" but i have to use "left alt + z" because y and z are different on an english and german keybord, just guessing here but it worked before so i guess it is a change in DCS itself.


Edited by unknown

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

8 minutes ago, unknown said:

Is this maybe related to not running an english Win OS but a german?

Nope, O.S. language has nothing to do with stability (French O.S. over here). Let's watch the log together:

You quit multitplayer and returned to main menu:

2022-01-30 15:02:17.999 INFO    NET: client has stopped
2022-01-30 15:02:17.999 INFO    APP: Screen: MainMenu=

You shut down DCS properly:

2022-01-30 15:02:19.677 INFO    EDCORE: (dDispatcher)enterToState_:5
2022-01-30 15:02:19.699 INFO    APP: application shutdown
2022-01-30 15:02:20.167 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 0
2022-01-30 15:02:20.170 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 1
2022-01-30 15:02:20.171 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 2
2022-01-30 15:02:20.260 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 3
2022-01-30 15:02:20.337 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 4
2022-01-30 15:02:20.344 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 5
2022-01-30 15:02:20.346 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 6
2022-01-30 15:02:20.348 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 7
2022-01-30 15:02:20.348 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 8
2022-01-30 15:02:20.351 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 9
2022-01-30 15:02:20.351 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 10
2022-01-30 15:02:20.352 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 11
2022-01-30 15:02:20.352 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 12
2022-01-30 15:02:20.352 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 13
2022-01-30 15:02:21.097 INFO    VISUALIZER: SceneManager_Implement::~SceneManager_Implement()
2022-01-30 15:02:21.104 INFO    VISUALIZER: TerrainRenderer::release
2022-01-30 15:02:21.215 WARNING LOG: 1 duplicate message(s) skipped.
2022-01-30 15:02:21.215 INFO    TERRAIN: lSystem::exit()
2022-01-30 15:02:21.215 INFO    TERRAIN: lSystem::CleanScenes()
2022-01-30 15:02:31.307 INFO    DX11BACKEND: DX11Renderer::shutdown()
2022-01-30 15:02:34.299 INFO    DX11BACKEND: textures_count: 0
2022-01-30 15:02:34.299 INFO    DX11BACKEND: textures_size: 0
2022-01-30 15:02:34.299 INFO    DX11BACKEND: buffers_count: 0
2022-01-30 15:02:34.299 INFO    DX11BACKEND: buffers_size: 0
2022-01-30 15:02:34.299 INFO    DX11BACKEND: CB_count: 0
2022-01-30 15:02:34.299 INFO    DX11BACKEND: CB_size: 0
2022-01-30 15:02:34.299 INFO    DX11BACKEND: SB_count: 0
2022-01-30 15:02:34.299 INFO    DX11BACKEND: SB_size: 0
2022-01-30 15:02:34.299 INFO    DX11BACKEND: IB_count: 0
2022-01-30 15:02:34.299 INFO    DX11BACKEND: IB_size: 0
2022-01-30 15:02:34.299 INFO    DX11BACKEND: VB_count: 0
2022-01-30 15:02:34.299 INFO    DX11BACKEND: VB_size: 0
2022-01-30 15:02:34.299 INFO    DX11BACKEND: total_buffers_size: 0
2022-01-30 15:02:34.299 INFO    DX11BACKEND: total_size: 0

But you're missing the final line, which looks like this: "=== Log closed."

Instead, you get this:

2022-01-30 15:02:34.299 WARNING DX11BACKEND: alive vertex buffers: 15
2022-01-30 15:02:34.299 ERROR   DX11BACKEND: Failed assert `DX11VertexBuffer::buffersCount() == 0` at Projects\render\dx11backend_win8\Source\DX11Renderer.cpp:122
2022-01-30 15:02:34.299 WARNING DX11BACKEND: alive index buffers: 15
2022-01-30 15:02:34.299 ERROR   DX11BACKEND: Failed assert `DX11IndexBuffer::buffersCount() == 0` at Projects\render\dx11backend_win8\Source\DX11Renderer.cpp:123

I have no idea where it comes from.

You should open a support ticket. Login to the DCS website, then click this link.

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

16 minutes ago, unknown said:

I'm running the latest drivers for everything, GPU, chipset, BIOS, sound....

 

The log says your GPU driver is 21.40.23, while the latest is 22.1.1

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600X - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to comment
Share on other sites

19 minutes ago, Rudel_chw said:

 

The log says your GPU driver is 21.40.23, while the latest is 22.1.1

The latest driver is 22.1.2 and that one is installed on my PC, and like i said, i had this problem also with my old nvidia 1080ti. I believe your number is showing the "internal" display driver version and not the "package" version. I always use the latest GPU drivers, except there is a critical bug. This started with one of the 2.7.x versions of DCS i believe.

I think i remember that somebody else had the same problem and maybe @BIGNEWY replayed but i couldn't find the post again. Also the strange thing is that this doesn't happen everytime i close DCS but i would say more often than not.

@Flappie I will wait if somebody has a solution here, if not i will open a support ticket tomorrow. 🍻

1.jpg


Edited by unknown

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

23 minutes ago, Flappie said:

Just in case, add your main DCS folder as an exception in your antivirus software.

I did this before my latest MP session but unfortunately it didn't change anything. DCS.exe keeps running after game exit with the DCS folder on the AV whitelist.

latest log attached

dcs.log

1 hour ago, Lt_Jaeger said:

Got the same thing. Sometimes it shuts down, sometimes not. Also on a German OS. Thought I mention it, even so it's started to be irrelevant. 

What are your system specs?

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

Windows has a useful tool named Resource Monitor. Maybe it can help you determine which files DCS is working on when it's supposed to be closed.

  1. Run Resource Monitor,
  2. Click the "Disk" tab: above is your running process list, below is the file access list.
  3. Start DCS,
  4. Wait for "DCS.exe" to appear in the running process list, then tick its box. From now on, the file access list will only show what files are being accessed by DCS.
  5. Play DCS then exit,
  6. Return to Resource Monitor and observe the file access list.
  7. Wait a bit until the list does not move anymore. Take a screenshot and post it here.

 

Here's what it looks like on my end, 1 minute after DCS exited successfully:

example.png

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

Hi @Flappie,

i will try that the next days, i'm a little short of time right now. I did a very quick test a couple minutes ago. Start WMR and StemaVR, start DCS, start SP mission, exit to main menu, exit DCS.

This time DCS closed normally(DCS.exe closed itself and did not kept running). I attach the log file from this normal game close just for comparison. I will keep investigating as soon as i have more time.

dcs.log

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

Interesting... Even though DCS exited, you keep havng these errors:

2022-01-31 17:04:11.207 INFO    DX11BACKEND: total_size: 0
2022-01-31 17:04:11.207 WARNING DX11BACKEND: alive vertex buffers: 1
2022-01-31 17:04:11.207 ERROR   DX11BACKEND: Failed assert `DX11VertexBuffer::buffersCount() == 0` at Projects\render\dx11backend_win8\Source\DX11Renderer.cpp:122
2022-01-31 17:04:11.207 WARNING DX11BACKEND: alive index buffers: 1
2022-01-31 17:04:11.207 ERROR   DX11BACKEND: Failed assert `DX11IndexBuffer::buffersCount() == 0` at Projects\render\dx11backend_win8\Source\DX11Renderer.cpp:123
=== Log closed.

 

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

Hi @Flappie

I tried a couple times this week, only short tests because i had not much time and only SP, no VR and i had no problem. Today i tried it again, MP and VR, longer mission and i had the same problem again, DCS.exe didn't close itself after game exit. I opened the resource monitor - after game exit with the DCS.exe still running problem - and checked the DCS.exe but everything was blank(disk tab). So i started another MP session with the resource monitor still running, checked the DCS.exe and after i closed the game(shorter session this time) it didn't took long and the DCS.exe closed and disapeared from the reseource monitor before i could take screenshots, no dcs.exe visible in the taskmanager.

BUT, checking the logs it looks like it still had a problem to close DCS? The log file looks the same as if i had to close the dcs.exe with the task manager and DCS generated a crash/dmp file, i deleted everything in the dcs logs folder before the second test session, all files attached.

Running latest OB with todays patch and i did update my GPU driver to the new 22.2.1 version.

dcs.log dcs.20220204-191921.crash dcs.20220204-191921.dmp


Edited by unknown

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

1.jpg

2.jpg

3.jpg

pasrt 2

 

4.jpg

5.jpg

6.jpg

part 3

 

7.jpg

8.jpg

9.jpg

 

part 4

10.jpg

11.jpg

12.jpg

13.jpg

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

Hi @Flappie,

the forum screewed up my post. Attached are the screenshots of the resource monitor(german) that i opened after i closed DCS and saw that the DCS.exe kept running. If i try to reproduce this with the resource monitor in the backgound the DCS.exe closed normally at every try to reproduce this.

Also if this happens i can start DCS again without DCS complaining about a still running DCS.exe. That lead to 2 DCS.exe kept running after i closed the game once. The problem is that this still running DCS.exe is keeping one of my CPU cores busy -> high frequency -> high energy consumption -> high temperature -> fans active..... 

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

On 2/6/2022 at 5:43 PM, unknown said:

If i try to reproduce this with the resource monitor in the backgound the DCS.exe closed normally at every try to reproduce this.

This is crazy. 🧐

You should open a support ticket. Log into DCS main website, then click "Support", then "Create a new ticket".

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

  • 2 months later...
  • 2 weeks later...
En 4/5/2022 a las 8:49, Flappie dijo:

@unknown @28270 Rapierarch found the solution: the issue was caused by Windows HAGS (Hardware-Accelerated GPU Scheduling). Turn it off and see if this fixes your issue.

Thanks, in my case that is not the cause.

I went to the section that manages GPU acceleration and it had the option disabled by default. At this moment it has happened to me again, I have to force the closing because it stays processing after activating the closing tab.

dcs.log.olddcs.log


Edited by 28270
Link to comment
Share on other sites

  • 1 month later...
On 5/5/2022 at 1:33 PM, 28270 said:

Thanks, in my case that is not the cause.

I went to the section that manages GPU acceleration and it had the option disabled by default. At this moment it has happened to me again, I have to force the closing because it stays processing after activating the closing tab.

dcs.log.old 158.23 kB · 5 downloads dcs.log 51.5 kB · 2 downloads

 

Same problem with me.  I never had HAGS enabled.  But this shutdown problem does not seem to happen consistently

Link to comment
Share on other sites

I have the same problem

My system is an rtx3080, r9 5900x, 64gb ddr4 3600, Valve Index.

When I shut down DCS it closes and steam Vr shows that it closes, however I can often still see the dcs.exe process running in the background.

However more often then not DCS Integrated Countermeasure Editor (Dice) is left running and on the tack bar.

are any of you running
Are you using DiCE: DCS Integrated Countermeasure Editor? or SRS?

Link to comment
Share on other sites

  • 3 months later...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...