I've done everything, deleting Cvars, updating graphics drivers, scan/repair with the Battle.Net app, uninstall/reinstall. Turned off/closed out of everything but the basic Windows programs and processes. CPU isn't overheating, GPU isn't overheating, RAM and CPU percentages are fine. As far as I can tell, it still crashes without rhyme or reason and has been doing so since the moment the Faction Rally patch dropped. It was like hitting a switch. The game had worked fine the previous week when I'd bought it, but the moment that patch hit, bam, crash city. Graphics Card: GeForce GTX 580 3 GB, running 2 monitors (the game is on one) Processor: i7-2600k 3.4 GHz RAM: 32 GB OS: Windows 7 Professional 64-bit No error messages from Destiny itself, Windows gives me this: Problem signature: Problem Event Name: APPCRASH Application Name: destiny2.exe Application Version: 64883.0.0.0 Application Timestamp: 5b0dbd5f Fault Module Name: ntdll.dll Fault Module Version: 6.1.7601.23569 Fault Module Timestamp: 57f7c06e Exception Code: c0000005 Exception Offset: 000000000006e602 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: 9d4a Additional Information 2: 9d4ade2d9f64c5b7bc4d2a85a3b924d6 Additional Information 3: 66c8 Additional Information 4: 66c800aad947f2612f668fe2e2f3edf5 For the most part it crashes on startup. About half the time it will bring up the title screen. Deleting the cvars gives me a 50/50 shot of it crashing immediately or getting to the title screen. But if I try to go through with that there's a pretty good chance that when it crashes it will lock my system somewhat. I can hit the power button, send the machine to sleep, and then wake it up and clear the Windows error. Other times it will lock up only slightly with everything slowed down massively and it will beep when I move my mouse (this also requires a sleep/wake up to clear) Sometimes the sleep/wake doesn't work and requires a whole system restart. So generally I delete cvars, load the game to the title screen, exit, edit the cvars to have the display mode be Borderless Window (<cvar name="window_mode" value="1" />), and after one or two immediate crashes that will generally make the game stable enough to get to character select and select a zone. It's a toss-up whether it will crash on the ship screen, crash a few seconds I start moving or crash sometime in the next one to ten minutes. Generally, if I can get the game to run for more than 10 minutes, it tends to keep on running. Unfortunately, if something goes weird connection wise, sometimes I get forced to close the program and get a message that I'll need to start it again from Battle.Net. So even if I get on, I can't stay on. Most of the time the audio drops about 2-3 seconds before the crash hits.