So I've been convinced to come back to Destiny 2 after being away from it for a few seasons (the only reason was because the Lightfall + Annual Pass bundle was at a good discount). I have to say, the servers are doing much better than they were when I stopped playing. An understatement. But now I'm running into this new issue with error code BROCCOLI. I mean, it counts as an issue, but I can already see the simple solution being to take a break after a while, hence the reason I made the title of this post the way it is. It isn't really a massive roadblock to playing the game or anything. But this was not an issue before I stopped playing. Sometimes I don't even get the error message. The game just freezes and 50% of the time looping sounds will continue to play. The effects of the crash are inconsistent, but the end result is the same. It almost seems like a memory leak of some kind is happening, but I'm not smart enough to figure out how to check that. I know other people are encountering this issue as well, but sometimes they don't even get that much time to play at all. And some people have been unable to resolve this issue on their ends. A few things I can note just in case it helps or leads to some conclusion is that a month ago, a Windows update happened that seemed to have a negative impact on my computer's performance in some ways. It results in occasional stutters with the entire computer, but mostly just for a time after it first boots up. I performed a System File Check to see if system files needed repaired. Some WERE found. Minor impact on the stuttering after they were fixed. Had another Windows update just recently, but the stuttering was left unaffected by it. Had a BIOS update for my laptop, which is an MSI brand gaming laptop btw. Initial stuttering after the BIOS update was unaffected, but most other times when stuttering would occur has seemed to back off. The GPU driver isn't that old either. Or at least, other games don't seem to have any issues with it. Elden Ring, Halo Infinite, etc... They're fine. And I'd rather not update my GPU driver due to a recent issue I found out about on the manufacturer site's forums regarding the recent driver update. I already know that the error code could be caused by a lot of things because frankly it seems like computer manufacturers don't know what they're doing with updates. I'm looking at Event Viewer and around the time of when the error happened and it seems like all sorts of things occurred around the same time. Such a messy list of events. Here's one of them. "The description for Event ID 0 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\Video8 Error occurred on GPUID: 100 The message resource is present but the message was not found in the message table" That still leaves many possibilities as to what caused the apparent driver crash in the first place. Won't rule out that it's not an issue on my end though, but I thought this was worth sharing and maybe someone knows what could be happening. I'm just afraid of messing with my drivers too much. EDIT: Apparently the driver recovered 1 second after the crash. Don't know if I need to say that, but it's there. EDIT 2: After some more research, I'm currently under the impression that the issues stem from a Windows 11 update, which my laptop is not currently letting me roll back from. I've seen tons of reports online for a large variety of issues that have came from the 22h2 updates and doing roll backs from some of those updates apparently have cleared up the issues for those users. Since the computer is still able to run, I'm first going to wait for the next update and see what happens. Apparently 23h2 is right around the corner and may tackle some Windows 11 bugs that were introduced. I'm just limited on options and this is the last option I have before I try anything potentially risky to the laptop. I guess I'll leave the post as this since I'm pretty certain that the GPU crash issue is not a Destiny 2 issue and the forums aren't for anything not related to Destiny 2. I suppose people can still ask me about these issues if they're really interested in hearing about it, but I'm moving on from this post.