Random Bluescreens of Death

TL,DR: Game causing a WHEA-Logger Fatal Hardware Event Type 1, "raw data" from the event at the end of this post.

I want to preface this will be a pretty lengthy post since I want to describe in full what's been going on to get the most accurate possible troubleshooting for it. I also want to say that I probably put about 20 hours down in the open beta phase and ran in to absolutely no issues while playing, and I don't believe I had any sort of major windows update that would be throwing things for a loop. 

When the full game launched I was having frequent issues with the BSoD's, not making it more than about 10 minutes of gameplay before running in to a crash that would briefly flash the blue screen and send me back to my lock screen. Interestingly enough while monitoring my PC my CPU wasn't hitting above 80-90% usage (same with GPU, and both were stable temps). I troubleshooted online for hours and hours, trying these fixes, but not limited to:

• Maximum CPU usage to 90%
• Temporarily disabling real time windows security
• Disabling all overlays (Nvidia, discord, steam, EA, etc.)
• Repair Game files
• Updating BIOS
• New graphics drivers
• Running the game in Clean Boot mode
• And more common online answers

None of these fixes were able to prevail for much longer than 15-20 minutes. I finally got wise enough to start trying to trace the root causes of the crashes, and through Windows Event Viewer I was able to find that the start point of all of these crashes was something along the lines of "WildTangent failed to start" or something, to which I tracked down a spare WildTangent folder in my %appdata%\roaming folder, and did the same to a GameInput folder that was next in the chain of failure. These fixes were able to float me to decently long play sessions (my longest was north of an hour), but I have about a coin flip chance of running in to a crash at the start of a new match. Event Viewer gives me just one event upon these crashes (WHEA-Logger event ID 1), which I've tagged a picture of the details for in this post. I tried for a while to use some software to figure out what the RawData field was telling me with no luck. Any help deciphering this or just general fixes would be greatly appreciated (or just "wait until its patched" if this isn't something I can do something about, which I may see if I can report such a bug to the dev team and see if there's anything up that tree).

If relevant my specs are as follows:

• CPU: Intel Core i7 10700K
• GPU: Nvidia GeForce RTX 3070 Ti
• Mobo: B460M DS3H AC -> Running F11 BIOS software (recently updated to)
• RAM: 2 x Corsair DDR4-2133 16GB memory sticks
• CPU (Windows and BF6 both installed here): Seagate FireCuda 510 SSD ZZP500GM30001

The full "RawData" line below:

Name="RawData">435045521002FFFFFFFF010001000000070000002A0100003A110000150A19143C60C1835215A74887D114D9467D7765000000000000000000000000000000008D7C2157665EFB4480339B74CACEDF5B03F83300702E884E992C6F26DAF3DB7A2DF0736B1241DC01080000000000000000000000000000000000000000000000C8000000620000000003020001000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000053544F52504F525401006200000003000100050011000000B140196C61DEEA119BC2806E6F6E6963730074006F0072006E0076006D006500000000000000000000000000000000004E564D6520202020005365616761746520466972654375646100</Data>

Thanks again to all,