H60MTI

I'm seeing for rockets 3 different version. Mk1 HE, Mk5 HEAT, and the M156 Wht Phos. Probably a dumb question but is that more of a smoke marker rocket or is that some full-on Willy Pete??

I'll definitely give it a shot. I do have XMP enable. With a Ryzen CPU of course I have XMP enabled Lol I wasn't really able to get into BIOS before cause of the looping BSOD's.

So, it has to be a bad RAM stick or a bad channel. I tried each stick separately and computer booted just fine. At the moment I'm in DCS and it's kicking with 2 sticks in dual channel mode. When I get some more free time, I'll try all 4 sticks again and see what happens. PITA!!!

I'm back-ish. I'm thinking a bad RAM stick. Right now I'm running on one RAM stick, so 16GB of DDR4 GSkill Trident Z RGB. Good stuff. I typically run 4 sticks of said RAM. Before I went offline I was having constant/looping BSOD's. So, I'm running one stick at a time and seeing if I find a bad stick that won't boot Windows.

Well, we're past DCS and games crashing. Definitely a rig issue and I don't know what. I'm getting looping BSOD with restarts or shut downs. Not even time to troubleshoot cause it BSOD's. I think I'll tear the rig apart and rebuild it. This is ridiculous. Thanks for the help guys, I do appreciate it. Cross your fingers and pray.

And crash....Oh my God this is annoying. DxDiag.txt

WTF? I can't curse anymore?! That sucks.... Thanks ED... We're back. Updated DCS. Ran rebuild and cleanup. Ran dism and scannow prompts. Shut down and reseated my RAM. Let's see what happens...

Yeah, that's all stuff that I've run today. DCS obviously. I was running Cinebench and FurMark earlier to try and see if my rig was stable. Both of those are stress testers. FurMark is a graphics stress test and Cinebench is a CPU stress test. Ghost Recon: Breakpoint is another game that I play. So, if I'm seeing hardware and not handling memory properly, I wonder if a RAM stick isn't seated right or has going bad.... Just ran those 2 prompts. I'm going to shut down actually and reseat all my RAM for <profanity>s and giggles.

Here is the DxDiag results. Just tried DCS again and still crashed. Just updated it as well with the version that just dropped. I also just removed all my mods from Saved Games and stashed them on one of my other hard drives not associated with the game. About to try that. I've noticed that sometimes DCS just freezes and doesn't show the file that causes the crash in the log. Just stops responding and can't produce a log file. DxDiag.txt

I went in and cleared most of those files mentioned above. There were some that I couldn't because they were being used at the time and couldn't erase them. Didn't help, at least for Ghost Recon Breakpoint. It still crashes. I'm probably going to have to break my rig down and see if anything is jacked up.

Hell, it could have been a cement plant for all I know but it was definitely a USMC ran camp/FOB that had UH-1's and AH-1's stationed there.

No, not there. This place didn't have an actual runway.

I updated my driver this morning. Had a day off work cause my kids school is closed for voting. Why they use elementary schools for voting locations is beyond me. I actually went to play Ghost Recon Breakpoint and that crashes as well. Weird. Funny thing is, I ran FurMark and Cinebench R23 at the same time as everything was stable. I don't understand it. Those numbers are after a 10 minute run of FurMark and Cinebench running at the same time on separate monitors. You would think stressing the system like that would cause something to crash. I'll try dumping those folders and see what happens.

I am on 565.90. They are currently on 566.03. I'll have to install that later and hope for the best.

It could be the Nvidia driver. That is having issues with Corsair iCue. I had to roll back iCue to work properly. I'll do some digging later. Thanks so far. I'll see what I can come up with.

Stupid thing...Was asking me what I wanted to open it with. I have Notepad++ and Visual Studio. Both of those can open that but didn't pop up. So, if reading this right, that D:\DCS World\DCS World OpenBeta\bin-mt\GraphicsCore.dll was the cause of DCS shutting down and crashing.

What program are you using to read the CRASH file? I can view the logs no problem since they're just text documents.

So, deleting the contents of the folder won't really hurt anything then. The game will rewrite these as need on start up.

Very random question. Don't know if there are many USMC vets on here or not but we'll see. I'm being bored and hunting on Google Earth for places I've been when I was in Iraq. Back in 2008, almost 20 years ago, I went to a FOB west of Baghdad in Marine country. It was a FOB but more heliport. They had AH-1's and UH-1's there. Looked weird with our Blackhawks flying in with all these skid birds. Skids are for kids! Anyway, it had a FARP on it. It was near railroad tracks. I can not for the life of me remember where it was. If anyone has any idea, let me know please. Thanks ya'll!

Yeah, I saw them in the Saved Games folder but definitely don't know what they do/hold.

What does the fxo file hold? Don't even know what an FXO file is nor the metahaders2 folder

And another crash. Just as I was about to get in zone to drop a 2000lb penetrator JDAM on a building, lights out. Whole system went down, not just DCS. These are the 3 new crash logs/files that populated with the crash and system restart. Getting old. Never had this problem until I went and updated DCS. dcs.20241103-132509.crash dcs.log DCS-BIOS.log

Lately DCS MT has been crashing constantly. Part way through a mission, halfway through, very end...Just crashing. I can hear it coming because the fans on my GPU spool down and I just have to wait for it. I've it DCS crash 10 times before I finally gave up and went to the couch. I've attached the last log from when it crashed. Doesn't make much sense to me since I really don't know what I'm looking at. From what I gathered it's a bad visualizer.dll in the actual game and not any mod. I could be wrong though. Anyone have any input or guidance on this that can help the crashing issue? dcs.log

You get that little pop up in the lower right corner of your screen?

I'm trying to open a mission in editor that I no longer have modules for, F-22 and F-15EX. I just don't want/haven't installed them back in since I last updated everything. However, now I can't open the mission in the editor because I don't have the modules. Is there anyway to force it open so that I can at least remove those modules?