Yeah the game just seems to have problems rendering one particular screen in resolutions above 1080p. We've had this phenomena confirmed by a few people now.
Just for reference, I've attached menu screen that crashes it. If you can get past that screen (through a myriad of saving, exiting, restarting and resolution-changing..) the rest works fine.
TLDR: Tentatively I'm going to say I might have solved it with Nvidia Control Panel.
@Dutch It's happened before only with DBC 17 and Ashes. In the past I've spent hours on the phone with tech support from where I bought the PC trying to get to the bottom of it. With DBC 17 the solution suggested was:"play a different game." Although I did solve it eventually it's been that long I can't remember exactly what I did. Recently had to install a new SSD and Windows, so any settings I may have had preventing it might have been removed. I did initially think it could be the controller, when playing DBC 17, but tried it with other games and there was no problem. Unistalled and reinstalled the controller with Ashes and still the issue persisted.
@beechcroft I do have WhoCrashed but it's not really helped me get to the bottom of it. I did try it in unison with the driver Verifier progam on Windows and an issue with the driver for my headset was highlighted. I uninstalled and reinstalled. Still crashed. Like the when I tested the controller on other games, I have had no issues with my headset. It is only Big Ant games (Ashes & DBC 17) that have caused this issue of consistent BSOD. No issues when playing the likes of Doom, GTA V, Wolfenstein, Dishonored 2, Prey on the highest graphical settings, where I'd expect to encounter the same problem.
ANYWAY, I have the FPS counter on my screen to keep track of the frames per second when playing PUBG. So it also appears in other games. With Ashes one thing that had always confused me was why it would be over 200. When the games first loads it's four figures! I just assumed it's a bad reading by Steam or I don't understand fully how it works and what it displays. Having exhausted all other options (controller, headset, drivers, adjust power settings, switching to a different 4-way plug adapter) I thought I'd have a look into that. I went into the Nvidia Control Panel and changed the VSync setting from 3D Application Setting to Adaptive. I did change a couple of other settings but VSync relates to the FPS. Lo and behold when I fired the game up the FPS was capped at 60. Played 20+ overs. No crash. Then, I'm not sure why (I think my monitor/graphics card may reset my display when playing the game because the refresh rate goes from 144 to 120), when I next loaded the game up the high FPS returned. Crash. Went back and made sure the settings were how I had them and I've just played a session without a crash. The FPS was limited to 60.
Someone who knows more about this sort of thing than me might be able to give a reason for this making a difference - my layman's logic is, perhaps, trying to process all those frames causes my GPU to overpower/overheat and crash the system.
I'm going to keep an eye on it but I've not been able to play as far as 10 overs without a crash for a few weeks and it had even started happening just using the academy. So there's definitely an improvement.
CC:@MattW@BigAntStudios this might be of interest to you
Windows version: Windows 10, 10.0, version 2009, building: 19042 Windows dir: C:\WINDOWS Hardware: XPS 15 9570, Dell Inc. 0D0T05 CPU: GenuineIntel(R) Core(TM) i7-8750H CPU @ 2.2GHz 8664, level: 6 12 logical processors, active mask: 4095 RAM: 16902221824 bytes (15.7GB) No valid crash dumps have been found on your computer