Jump to content

cnoblenyc

Members
  • Posts

    19
  • Joined

  • Last visited

Everything posted by cnoblenyc

  1. One of the things we did was to unplug it from the APC UPS and directly into the wall (separate socket) to no avail. I plugged the new rig in with the same pwr cord (I have it all in a wire management sleeve) so have to rule that out. And if it were a power issue, we'd have seen it with things like MSFS most likely. It's truly perplexing... and frustrating AF. I may bring the old rig back into the game room and plug it in and see if it still fails....
  2. So..... Before continuing to read this... I'd recommend sitting down. (And taking notes.... particularly if you're married - more on that in a moment...) Bought a whole new rig. And when I say "whole", I mean a whole new rig. Case to fan to memory to CPU to NVMe ... not a single component was re-used, not even a cable. Works great in MT with "High" presets. Haven't had a crash in over 20 sorties! What did I do with the old rig you ask? Good question. I decided (since no other app had an issue on the hardware) to replace the multi-media server in the house. (Think PLEX home cinema, music, vids, etc.) I figured since I just installed the OS, I'd leave it and just add Plex, VLC, etc., etc. Now remember I said this is useful particularly if you are married, right? NEVER launch DCS in the living room (on the old rig that "you just had to replace") with the battle-axe at home. Why you say? Because DCS just ran... and ran... and ran. 30 mins later... still running. I cannot get the old rig to crash... and I NEEDED IT TO! I've rebooted, changed the presets back to "High", broke the sound barrier down the Las Vegas Strip... just won't crash and in MT at that! On a technical note: I have NOT the bloody foggiest idea why it decided to run in a different room. The ONLY difference is instead of an ASUS monitor, its running on a 75" Sony TV. I literally unplugged it, carried it to the living room, plugged it into the power and the TV, and turned it back on. Literally is being used correctly here... that is ALL I did. If I discover anything new as to potential reasons, I'll post a follow-up. I do suspect it has something to do the the monitor's G-Sync... So now my wife thinks I planned this. Married folks: Uninstall DCS on the old rig just in case you're tempted to "prove it still doesn't work". On an unrelated note: Does anyone know a good divorce lawyer?? (Asking for a friend....)
  3. Hi FusRoPotato, First - thank you for the continued help. If you read any frustration into my replies, certainly NOT aimed at anyone. So... - Both C (Where DCS is installed) and D are both WD Black SN750 NVMe drives. - Folders and process had been added to A/V (Windows Defender) - Changed PF to different drive. However, it's important to note that when I rebuilt, I purposely re-installed the OS onto a different drive. (Had previously been on a Samsung SSD 850 Pro) - Changed PF to D drive and set to 32000 and 96000 - Kept presets at "LOW", but changed preload to 30000 - Launched at ~12:30 F/A-18C "instant action" with "Ready on ramp" - Pressed buttons (TCN, ILS, freq change, lights, DDI/UFH/AMPCD buttons, extended probe, etc, etc..) - Toggled through all available view (Cockpit, arcade, flyby, arcade, chase, wingman, etc.. etc.. - Moved control surfaces (flaps, hook, refueling probe, etc..) - at 1305, pushed throttle forward, taxi'd to rnwy, and sat for 5 mins. - at 1310, pushed throttle forward... took off.. airborne... CRASH. NOTE: Removed joystick and used keyboard only to rule that out...) - CRASHED - dump attached. Stable for over 30 mins... until it actually started flying... dcs.log-20240610-171300.zip
  4. Somethijgn different. I started a sortie with he F/A-18C "Cold & Dark" in the Marianas. (aka: On the carrier). I just let it sit there (played with some buttons / dials). After 10 mins, it still had not crashed. I went back to the menu.. that's when the crash happened. dcs.log-20240609-234946.zip However, the dump seems to be the same Bat Error, Same Bat Code.
  5. I didn't explain properly, apologies. When I re-built and reinstalled everything, I left it at defaults. We've tried changing the settings many times: I changed back to "LOW" again and ran it.. no dump, just a straight CTD in both Single and Multi Thread (see attached) MT - dcs.log ST - dcs.log
  6. On preset "LOW", its set to 100. Same issues. It had been running fine for the last couple yrs without DLSS and in preset "high" and with a RTX3070. Same issues with the new RTX4070. MSFS, which is very taxing on this rig, can go for hours (literally) of flight without a glitch... Appreciate everyone's help! Seems tech support has essentially given up on this now.. not sure what's left to try.
  7. Nothing new. I launched DCS at 7:28. I don't see anything related in the even log I ran PerfMon. Current Pagefile is set to 32gb. Seems it crashed at ~11gb. Another run: (Added Committed Bytes) Obvious where it crashed., eh? null The behavior (after completely rebuilding the rig - including removing all but the essential hardware and buying a new 4070 GPU... - is I can generally launch a flight, but no matter what settings, I can fly for only under 2 mins. Then it crashes. Sometimes with a dump (pun intended here... ) but lately, usually not. Last 3 dumps attached for your viewing pleasure. dcs.log-20240608-133440.zip dcs.log-20240608-143001.zip dcs.log-20240608-144505.zip
  8. I'd suspect if it were a faulty PCU, the system and/or other apps would have issues. It's the Corsair AX850i MSFS taxes the system significantly and that is stable for hours at a time... The consistency in the logs is "# C0000005 ACCESS_VIOLATION". What cause only DCS to to have this issue that no other application seems to have...?? What is it violating? I've attached 2 screenshots from iCUE. As you can see, the power consumption (wattage and current) goes up as should be expected, but the voltages stay rock solid across the unit. Sadly, the only part of the system that isn't monitorable (or hasn't been changed) in the MB and CPU.. and again, my challenge is NO other application (including power-consuming ones like MSFS) cause any issues. Spent a lot of money on this game - built the whole rig around this - to not be able to use it... getting very frustrating ,to say the least... But I do appreciate your help. Attached is 2 of the latest logs as well. dcs.log-20240601-175637.zip dcs.log-20240601-170423.zip
  9. APC Battery backup... bypassed - No change in behavior. I replaced the vid card - new Asus 4070 ROG. Same issues. I reverted back to 2.8.7.42718 - Same issues. I'm fairly sure now the issue is on my end - the only thing left to try seems to be replacing the MB which is not fun. The challenge I have is this is the ONLY piece of software that gives me issues. MSFS operates or hours at a time without any issue... and it pushes the rig hard. Any other ideas before going down that rabbit whole?
  10. It had been disabled. No OC settings at all. The rig is about as basic as you can make it at this point...
  11. No BSD's at all. Always goes CTD. In fact, I rarely get just a CTD. 9 out of 10 times, it crashes properly (crash-dump file created). BIOS is up-to-date (latest version from Asus) as are the Intel chipsets.
  12. Went one better... completely wiped out the OS and started from scratch... update BIOS... same issues.. Really frustrating as this was my week off and wanted to get some stick time. Hope we can find a solution soon. Latest dump files attached. dcs.log-20240530-183339.zip dcs.log-20240530-174407.zip dcs.log-20240530-043111.zip
  13. Completed - zero errors. MemTest86-20240529-170414.log I am working with support as well, but they haven't been able to solve it yet either... any other ideas? Attached are the 2 latest crash files. I continue to appreciate everyone's help and support. dcs.log-20240530-020717.zip dcs.log-20240530-014331.zip
  14. Change the pagefile - although it was managed by the system as it was. The Preload Radius settings were the defaults. I changed them to presets "Med" and "High" .... No luck at all. Crashed ever time. Hours trying to get this to run ... very frustrating.... but I really appreciate your help and time. Thank you. dcs.log-20240529-025805.zip dcs.log-20240529-041534.zip
  15. Thanks Flappie - Space I have a lot of on several drives.... Good news: It generated a proper dumb. Bad news: See the good news. dcs.log-20240527-234741.zip dcs.log
  16. Hi Hornblower - ANY mission - pre-made or self generated. I've generated my own simple mission (Carrier and F/A-18) attached hereto. I CTD 80% of the time when it gets to when it hits "World Preload 40+/60". I've attached the corresponding log. The log has multiple errors with inability to open files... CATI - Training.miz dcs.log.old
  17. I spoke too soon... had a couple longer flights (was actually able to do a trap once). I've tried everything that I can think of and all the options I can find on the forum. Including going back to 2.8. I've replaced the driver and used DDU to do a complete clean install of Nvidia. After several more hours of tinkering and re-installing and adjusting, I cannot get more than half a flight in.. at best. It usually fails when loading the missions with "World Pre-load". I've attached a few more dumps and logs... It's absolutely unplayable at this point - hope someone can help. 1st run with dcs 2.8.7.4271 dcs.log 1st run with dcs MT2.8.7.4271.log dcs.log-20240525-185541.zip 2nd run with dcs MT 2.8.7.4271.log dcs.log dcs.log.old
  18. I reverted back to 2.9.3.51704 from 2.9.5.55300 .. works fine now. Seems clear there is an issue with the latest build.
  19. Morning All, I've had a very stable experience for well over a year up to the latest update. As soon as the update to the latest version occurred, I cannot complete a single flight in F/A-18 or F-15E (F-15E won't even load to start the flight...) To be clear, couple weeks ago (before the update) everything was stable. I have re-installed DCS completely, deleted "saved games" data, reinstalled the nvidia drivers... to no avail. I've tried both "DCS" and "DCS-MT". I usually just CTD, but every once in a while, I get a "proper dump". Attached is the dump logs from the last "proper dump" and the latest log of a CTD. UPDATE: Added 2 more logs - 1 "proper crash" and one direct CTD. Bothe with F/A-18.. didn't even start the flight.dcs.log-20240524-133144.zip I love this simulator, thanks for all the hard work behind it. Cannot wait to see where it goes next! dcs CTD.log dcs.log-20240524-023442.zip dcs w-dump.log dcs - F-18 - CTD Before flight started.log dcs - F-18 - Proper crash - on mission load.log dcs.log-20240524-133144.zip
×
×
  • Create New...