solved Game BSOD'd, now it won't launch

[Zoddom]

My game crashed with a BSOD (something like sys memory management error).
I was flying over the Normandy 1944 Paris area (I dont own 2.0 yet).

I already tried cleanup and repair, system restarts and single-/multithreading.

All I get is a black screen.

Any ideas? :(

[Flappie]

Hi. Try fixing Windows. Run these commands in a CMD window, one after the other:

sfc /scannow

dism

 

[Zoddom]

Thanks, I'll try. But what exactly does this and why do you think its Windows?

 

update:

sfc /scannow told me there were broken files that couldnt be repaired. Doesnt really help me, I attached the excerpt from the log though, if you wanna have a lookCBS_short.log.

 As for DISM, what exactly do I need to do here? I dont know how this works.

Edited April 21, 2023 by Zoddom

[Flappie]

A BSOD is a Windows symptom. It can be caused by a driver issue, a hardware failure, a drive error, a high PC temperature, an overclocked GPU/CPU/RAM... 

[Zoddom]

Yeah I know this error, I've mostly had it with Escape from Tarkov before, but I havent had it in a while.

So I doubt its something on my hardware end, my RAM is 2 years old and I only use XMP and havent changed anything other than Infinity clock in Bios.

[Flappie]

Then maybe you should explore the driver error lead.

Some help: https://windowsreport.com/fix-bsod-windows-11/

[Czar66]

27 minutes ago, Zoddom said:

Yeah I know this error, I've mostly had it with Escape from Tarkov before, but I havent had it in a while.

So I doubt its something on my hardware end, my RAM is 2 years old and I only use XMP and havent changed anything other than Infinity clock in Bios.

'Mostly' had with Escape From Tarkov? How many times overall with any game? Blue screens nowadays points to something very very wrong in hardware/software relationship. Overclocking can be the main suspect if that is active in your system. You should be getting no blue screens at all.

I have between 300 and 400h in Tarkov and way too many in DCS World and zero BSOD with two different PCs for years, using DDR 4 Ram.

Check your motherboard for any damage.

See if you have pagefile activated in windows and with a generous size (10gb-30gb), no matter your physical RAM installed.

[Zoddom]

vor 23 Stunden schrieb Czar66:

'Mostly' had with Escape From Tarkov? How many times overall with any game? Blue screens nowadays points to something very very wrong in hardware/software relationship. Overclocking can be the main suspect if that is active in your system. You should be getting no blue screens at all.

I have between 300 and 400h in Tarkov and way too many in DCS World and zero BSOD with two different PCs for years, using DDR 4 Ram.

Check your motherboard for any damage.

See if you have pagefile activated in windows and with a generous size (10gb-30gb), no matter your physical RAM installed.

Well Ive only ever really had it in Tarkov I believe. And as I said, my mainboard and ram are only about a year old and I only run XMP Profile in Bios, no other overclocking.

Just checked my pagefile and it was just 3,5Gb, upped it to 12.

[Zoddom]

I tested my RAM over night and it found a few errors. But I understand thats normal with low timings on the RAM?

Anyways, my main problem is DCS not launching anymore, and repairing didnt fix that.

 

[Flappie]

As you may already know, DCS uses a lot of RAM. When DCS is running, chances are it uses some of the faulty RAM sectors to store data, leading to a BSOD.

If you manage to ID the RAM stick that's faulty, turn off your PC, remove the faulty stick, then see if your PC keeps crashing when you run DCS.

[Zoddom]

vor 54 Minuten schrieb Flappie:

As you may already know, DCS uses a lot of RAM. When DCS is running, chances are it uses some of the faulty RAM sectors to store data, leading to a BSOD.

If you manage to ID the RAM stick that's faulty, turn off your PC, remove the faulty stick, then see if your PC keeps crashing when you run DCS.

Yes, but thats not my problem. My problem is that DCS just doesnt launch, it just gives me a black screen, but no BSOD. So I guess some files mustve gotten corrupt after last BSOD, but repairing doesnt help.

[Flappie]

Ah, right. Please attach your dcs.log file (from "C:/Users/your_login/Saved Games/DCS.../Logs" folder).

[Zoddom]

I dont have a DCS folder in saved games. I have the standalone version, if thats different from Steam.

[Flappie]

You should have one. It's created when DCS starts.

Please open a support ticket: log into DCS website, then click "Support" and "Create a new ticket".

[silverdevil]

18 minutes ago, Zoddom said:

I dont have a DCS folder in saved games. I have the standalone version, if thats different from Steam.

also see what happens when you open windows explorer and type %userprofile% in the URL box

null

[Zoddom]

Nevermind I was looking in documents all the time...

Here is my log file and the .old file , thanks for the help guys.

dcs.log

dcs.log.old

Edited April 23, 2023 by Zoddom

[Flappie]

Ah, much better. This error means there's something wrong in your DCS options.lua files:

2023-04-22 22:31:47.166 INFO    EDCORE (Main): (dDispatcher)enterToState_:1
2023-04-22 22:31:47.892 ALERT   Dispatcher (Main): Error starting Game GUI: [string "./MissionEditor/modules/TableUtils.lua"]:3: assertion failed!

Go to "Saved Games/DCS.../Config" then delete "options.lua". Now run DCS and it should work.

[Zoddom]

vor 6 Stunden schrieb Flappie:

Ah, much better. This error means there's something wrong in your DCS options.lua files:

2023-04-22 22:31:47.166 INFO    EDCORE (Main): (dDispatcher)enterToState_:1
2023-04-22 22:31:47.892 ALERT   Dispatcher (Main): Error starting Game GUI: [string "./MissionEditor/modules/TableUtils.lua"]:3: assertion failed!

Go to "Saved Games/DCS.../Config" then delete "options.lua". Now run DCS and it should work.

omg youre a genius, it actually works. I noticed the login window popping up first after the Bluescreen but didnt think much of it. Guess there was an issue with the autologin, as this was the only setting in the lua.

[Flappie]

Glad I could help.