24H2 crashing games - working on a fix?

It's now March and still this is happening. There is not one single game I have that works anymore because of this. Like many others, I'm way past the 10 day mark to revert back and I was way past that time when this first started happening. Do you have any idea how difficult it is to be a play tester for a game when MICROSOFT is the reason the game keeps crashing??? I know Microsoft doesn't give a rats behind about its users, all they care about is making money off of us. Seriously, this is beyond ridiculous and expecting people to alter everything on their computer or go to computer classes just to figure out how to fix your dumb mistakes is even worse. Do something about this NOW!

So far I've found a few workarounds, such as turning off a couple of the cpu cores from the games that are having trouble. Doing this avoids having to do a hard reset, as you can still operate on Windows to force closing the app.

Turning off multi-threading, if the option is available, has also worked for me, although it causes severe loss in performance.

What I'm expecting is a permanent solution from Microsoft now, as this is a long standing problem that is affecting thousands (or millions) of users, and that has gone on for too long. I was hoping too see a statement, at least acknowleding the problem and committing to solve it as soon as possible.

Apparently this is a bug introduced in Directx12 with the last Windows patch, 24H2, can anyone confirm?

Having to roll back to 23H2 at this point would be a disappointment as well as a lot of work. If I can even find a .iso to roll back to.

I almost lost my mind. At the beginning of December, I upgraded my computer (new processor, motherboard, RAM). Of course, I reinstalled Windows – version 24H2. The first issues appeared with the drivers I downloaded from the manufacturer's website (ASUS ROG Strix). After installing the audio driver, the power button became sluggish, taking two seconds to display options after clicking. I uninstalled the driver and resigned myself to using only what Windows installs by default.

Then came unpleasant surprises—not daily, but still frequent. The main issue was that my game (BF 2042) would simply close in the middle of playing. This escalated, and one day, my computer rebooted during gameplay. The same thing happened a few more times that day. I was already in a bad mood, disappointed with the new hardware, and started troubleshooting. Based on the logs in Event Viewer, it seemed to be a hardware issue – Event ID 41: "The system has rebooted without cleanly shutting down first."

Thus began a painstaking process of checking components: RAM, GPU stress tests, CPU, replacing the SSD. Just as I was about to buy a new power supply, I stumbled across reports online about users facing numerous issues with 24H2. I decided to give it a try. With some difficulty, I found a 23H2 image and reinstalled Windows 11. During driver installation, there were no issues—the manufacturer's audio driver worked without causing problems, and so far, Event ID 41 has not reappeared.

I can’t imagine how less tech-savvy users, who don’t know how to approach debugging, deal with this—they likely end up with a non-functional computer and costly repair bills.

So, Microsoft, please get your **** together and fix these bugs already.

I have the same issue. It's not my hardware; certain games are affected. I can rebuild the system, but 24H2 is automatically upgraded. Microsoft should have tested this more. I have read about other people having the same issue, so count me in as one who asks that this gets patched ASAP.

It's making playing games intolerable. If I could roll back to 22H2 or 23H2, I would not have these issues.

In-game freezing forces a hard shutdown and restart.

I have the same issue. It's not my hardware; certain games are affected. I can rebuild the system, but 24H2 is automatically upgraded. Microsoft should have tested this more. I have read about other people having the same issue, so count me in as one who asks that this gets patched ASAP.

It's making playing games intolerable. If I could roll back to 22H2 or 23H2, I would not have these issues.

In-game freezing forces a hard shutdown and restart.

I'm "sitting" on 23H2 and machine is working fine. Attempted to upgrade 24H2 numerous times but kept getting the BSOD which disappeared after a second or two with no chance to read it all and find out what the problem is. Used Macrium Reflect to roll back to 23H2. Sounds like you have "Get the latest updates as soon as they are available" in Windows Update selected if you are getting "but 24H2 is automatically upgraded." I had that selected but now it's off. Updates are all paused for 5 weeks to stop anything coming in and I ocasionally turn the updates back on to get Microsoft Defender it's updates, then pause all updates again.

My machine is working fine on 23H2 - I know that's no help to you.

Windowslatest.com states "Microsoft promises it’s working on a fix and will share more details in January when the engineers return to work."

Just proving Microsoft has a policy of release it and let the public do fault finding for us.

Same shambles with Flight Simulator 2024 which was released before it was ready as well.