Win7 here as well and I think the problem is because of the only at Win10 running [b]DirectX12[/b]. I've talked to another guy who faced same problems in another game and the problem there was the switch from DirectX11 to DirectX12 so he thinks its the same issue here. And it makes sense! It's kind of another tyranny of Microsoft to punish people not whilled to use Win10 if you ask me ... because actually DirectX12 could work for Win7 but it does not. Also you're not able to install it manually. Insted you need to use an installer what checks your system for Win10. If not you can't install it even if your hardware actually supports it. I really don't get why Bungie or developer in general would use that at all. It's not much of an improvement to DirectX11 as much as I've found out... could be for an extreme performance-eating application but Destiny 2 actually isn't one. Also this does not work for any hardware - in fact there are some reports of critical problems using it not only for people not using Win10 but also for people with Win10 but unsupported Hardware... but also people with side-problems because of DirectX12. I wont use Win10 due to it's terrible usability, the many problems it had, has and will have (because of broken updates etc.), it's ugly pseudo-modern Design and other reasons and I wont even if Bungie refuses to fix the problem! In that case I would get rid of Destiny 2 before! I really hope they'll fix it and Im in fact quite curious if it really is because of DirectX12... of course we could be wrong and its caused by something else. Im not an expert.