fixed Crash to Desktop When Choose Slot

[坂本雪乃]

Choosing the aircraft jf-17 in "role select", then try spawn is cause CTD every singel time. Not once since my jf17 have work. Updates and reinstall\repair not fix this issue, change graphic setting to various different settings not fix. Iam very unhappy with this module for not once it worked :c 
I have attach log files from this crash, help i really needing.

dcs.20220731-042334.dmp dcs.20220731-042334.crash

[Colmillo]

Hi
Try this:

https://answers.microsoft.com/en-us/windows/forum/all/nvwgf2umxdll-game-crashes/0e3776f8-ac8d-47df-82d3-c45804e960d2

[坂本雪乃]

I try thus far nearly all options given before and again, nothing yet is work T_T

[坂本雪乃]

It is possible for such unacceptable circumstance as this i wonder to demand refund and revoking of module license?

I paid i think full price or nearly full price for module wich is impossible use, not any other module have this issue, so it is unacceptable.

[uboats]

from the crash log, your crash is not related to jf17, but more to nvidia

it's better to report to ED and also post the full crash package

also try to update to latest stable or switch to OB

Edited November 13, 2022 by uboats

[Flappie]

@坂本雪乃

Your log shows an "IN_PAGE_ERROR" crash. This means that one of your drives is either faulty or too slow. Avoid to install DCS on an HDD. Prefer a SSD drive (2.5" or NVMe).

Let's assume your drive is faulty. Try this:

1. Run a "cmd" window.
2. Browse to the DCS drive.
3. Run this command: sfc /scannow

[坂本雪乃]

12 hours ago, uboats said:

from the crash log, your crash is not related to jf17, but more to nvidia

it's better to report to ED and also post the full crash package

also try to update to latest stable or switch to OB

 

I on Open Beta always. ONLY Jf-17 get this problem, not any other module ever has done even once this  no suggestions have worked. I done i think it is time giveup T_T

12 hours ago, Flappie said:

@坂本雪乃

Your log shows an "IN_PAGE_ERROR" crash. This means that one of your drives is either faulty or too slow. Avoid to install DCS on an HDD. Prefer a SSD drive (2.5" or NVMe).

Let's assume your drive is faulty. Try this:

1. Run a "cmd" window.
2. Browse to the DCS drive.
3. Run this command: sfc /scannow

My dcs is install upon ssd m.2

[坂本雪乃]

18 hours ago, Flappie said:

@坂本雪乃

Your log shows an "IN_PAGE_ERROR" crash. This means that one of your drives is either faulty or too slow. Avoid to install DCS on an HDD. Prefer a SSD drive (2.5" or NVMe).

Let's assume your drive is faulty. Try this:

1. Run a "cmd" window.
2. Browse to the DCS drive.
3. Run this command: sfc /scannow

My dcs is install upon ssd m.2
No the solution are working. I extremely unplease with jf17 module, since iam unable even once to use it or find solution. I will not be support anymore it or give it chance, i can not justify. Depressing end for such a expensive product

[uboats]

You are running 2.7.16, even older than current stable version.

[Flappie]

Well spotted!

@坂本雪乃  Your version is from August 2022. You're missing two updated. Try this procedure: https://www.digitalcombatsimulator.com/en/support/faq/987/

[坂本雪乃]

17 hours ago, Flappie said:

Well spotted!

@坂本雪乃  Your version is from August 2022. You're missing two updated. Try this procedure: https://www.digitalcombatsimulator.com/en/support/faq/987/

that is older crashlog, i am up to date and had still ctd after clean new install, disk repair, gpu driver clean new install etc. Again ONLY jf17 having this ever for me ctd on spawn

dcs.log-20221113-182228.zipdcs.log-20221113-182228.zip

[Flappie]

I found a track file in your ZIP. I tried to replay it, but a mod is preventing me to. Please try disabling this mod, VSN_F104G, and tell us if it solves your problem.

[坂本雪乃]

disable f104 mod still jf17 is ctd when try spawn

[Flappie]

I see some other mods. Please try this:

1. Go to "Saved Games".
2. Rename your "DCS..." folder into "DCS.backup". Do NOT delete this folder, because it contains your custom bindings, solo career and other stuff.
3. Start DCS and try any JF-17 mission: does it crash this time?

 

[坂本雪乃]

8 hours ago, Flappie said:

I see some other mods. Please try this:

1. Go to "Saved Games".
2. Rename your "DCS..." folder into "DCS.backup". Do NOT delete this folder, because it contains your custom bindings, solo career and other stuff.
3. Start DCS and try any JF-17 mission: does it crash this time?

 

nothing still

dcs.log-20221116-155100.zip

Edited November 16, 2022 by 坂本雪乃

[Flappie]

OK, try this:

1. Launch E:\...\DCS World OpenBeta\distr\vcredist_x64.exe : hit "Repair",
2. Launch E:\...\DCS World OpenBeta\distr\vc_redist.x64.exe : tick the box and hit "Install" (or "Repair" if you can find it, but I can't). You might get this error message (no worries, I have it too).

[坂本雪乃]

33 minutes ago, Flappie said:

OK, try this:

1. Launch E:\...\DCS World OpenBeta\distr\vcredist_x64.exe : hit "Repair",
2. Launch E:\...\DCS World OpenBeta\distr\vc_redist.x64.exe : tick the box and hit "Install" (or "Repair" if you can find it, but I can't). You might get this error message (no worries, I have it too).

not work :c

[Flappie]

I meant, "X:\" by the way, not "E:\" but I guess you did what I wanted you to try.

At this point, I'm short of ideas. Please create a support ticket:

1. Log into DCS website
2. Click "Support".
3. Click "Create a new ticket".
4. Add a link to this thread in the comments, so the team knows what we have tried already.

[坂本雪乃]

This issue is now solve iam very thankful for all help efforts, thankyou very much my friends

Issue was relating to path name japanese characters was cause error so i did got instructed to move dcs install to root of drive wich solved.

It was done like this:

orginal path: X:/ゲム/DCS Open Beta

new path" X:/DCS Open Beta

Japanese characters were causing issue of module access dll file needed.

Edited November 20, 2022 by 坂本雪乃

[Flappie]

Many thanks for your feedback. I'm glad it works for you now.

I'll report the issue so it can be fixed.

[uboats]

Thanks for the help @Flappie

Quote

Japanese characters were causing issue of module access dll file needed.

I've no idea about this, but will keep an eye on it.

 

[uboats]

issue is being worked on