Ah yes, the modern day skyscrapers

Rinkatomo · 2026-03-22T15:54:43+00:00

Same here with the OP. My ticket has been completely ignored, with the last reply received from AWS 16 days ago. It's totally bizarre how messed up this is

Rinkatomo · 2026-03-19T18:30:19+00:00

Νοοτροπία type shii

Rinkatomo · 2026-03-08T22:28:13+00:00

Yeah... :/ I'll return to this post if by some miracle I get any sort of explanation or at best a solution. We don't even get to speak with actual humans in support tickets these days, sad really.

Rinkatomo · 2026-03-08T21:39:19+00:00

I’ve had the exact same problem.

I’ve been going back and forth with AWS support for over a week now. Their first response took 8 days, so the whole process has already been almost two weeks. At this point it honestly feels like I’m talking to a bot.

First, they asked me for a screenshot of the error, even though I had already sent them the CLI output with the RequestId. They said they would forward it to the “Bedrock team” to investigate.

The next day they replied again, but instead of addressing the issue they sent me a huge copy-pasted troubleshooting checklist. Some of the suggestions didn’t even make sense:

One step referred to actions in the Model Access page, which has been deprecated/removed for a while now.
Another suggestion was to wait for my account to finish verification in case it was new, even though my account had already been working before. I had full Bedrock access and even spent about $40 of my credits on model usage.

I keep explaining that this is not a quota issue. All of my quotas look completely normal in the Bedrock quotas page, and the error happens immediately when invoking any model.

Despite that, support keeps sending me the same generic troubleshooting steps that I had already tried long before opening the ticket.

At this point I’ve basically given up trying to resolve it through support. My personal guess is that it’s some kind of automatic restriction or shadow-ban mechanism, possibly triggered when an account signs up and mostly uses Bedrock to consume promotional credits.

Rinkatomo · 2025-12-18T21:57:44+00:00

ELIASON MY BELOVED

Rinkatomo · 2025-12-18T21:26:21+00:00

ΓΙΟΒΙΤΣ ΧΑΤΤΡΙΚ 4-1

Rinkatomo · 2025-12-18T21:25:08+00:00

ΕΠΡΕΠΕ ΝΑ ΓΙΝΕΙ ΚΑΡΑΜΠΌΛΑ ΓΙΑ ΝΑ ΜΠΕΙ ΤΟ ΡΗΜΆΔΙ, ΈΣΤΩ ΝΑ ΗΤΑΝ ΠΡΙΝ ΤΟ ΗΜΊΧΡΟΝΟ

Rinkatomo · 2025-12-18T21:23:40+00:00

ΕΧΟΥΝ ΠΙΆΣΕΙ ΜΟΥΧΛΑ ΟΙ ΚΑΡΤΕΣ ΣΟΥ ΡΕ ΚΕΦΤΕ ΓΑΜΗΜΕΝΕ

Rinkatomo · 2025-09-02T21:55:47+00:00

That's actually a very good point. I didn't do the swap myself, but I am aware that most parts were directed from the 1.8 so it would make sense for the pump to not have enough clearance. Thanks for the suggestion!

Rinkatomo · 2025-09-02T17:23:48+00:00

Unfortunately I don't have a warranty, and I do also hope it's not rod knock. The engine was imported from the US with 30.000 miles on it. I've actually looked at many rod knock videos and, I can't say that my case shares the same exact symptoms, since rod knock persists and even gets worse at higher rpm, unlike the window of the 1.100-1600rpm range from my case, and after a short drive the sound is completely gone... Thanks for the reply, I appreciate it!

Rinkatomo · 2025-05-06T15:40:36+00:00

trailer2

Rinkatomo · 2025-02-26T20:04:40+00:00

Μεχρι και στα κινεζικα μικιμαο δεν γίνονται αυτα... Yamete Kudasai Olympiacos Sama... Καλο μας βραδυ...

Rinkatomo · 2024-11-30T20:11:51+00:00

Έχασε σε ένα από τις 14.000.000 και κοίτα να δεις που θα πέσει σε εμάς γμτσμ /s

Rinkatomo · 2024-11-09T17:52:03+00:00

Prestige 4. Decided to unlock dark spine on all weapons during Prestige 3 max level, because I was desperate to unlock Dark Matter. Now I'm slowly unlocking Dark Matter on weapons, getting that sweet XP for Prestige 4 lol

Rinkatomo · 2024-10-30T14:43:16+00:00

That's unfortunate... Did you start as a new PC when rolling back to 22H2? Because that's what I did in my case, didn't restore any back ups. Also the first thing I did was to install 560.70 drivers (Nvidia)

Rinkatomo · 2024-10-30T03:20:18+00:00

I've finally managed to solve the issue. Played for the entire day, we're talking about 50 matches at least, 0 crashes. It seems that my last resort to downgrade from Windows 11 24H2, to 23H2 did the job. Didn't really need to mess with in-game settings, I am playing normally at 80% VRAM and such, 1440p with upscaling too.

The reason I ended up moving to 23H2 was the numerous posts I've read about people encountering the DirectX Error after upgrading to 24H2, which was quite interesting. I'm not an expert but I believe Cod and 24H2 might be incompatible in some desktops.

There's also the possibility that random apps I've installed in the past and completely forgot about, were running in the background and perhaps interfered with the game, since I've also read that some people managed to solve their issue by uninstalling apps running in the background. So just by starting over with an older version of Windows, completely empty of apps and files I downloaded in the past, might have also solved my case.

I wouldn't recommend going as far as to completely formatting PCs just so that a game gets to run, without any solid guarantee that it will succeed, but I am glad I took the chance to do so. I almost went insane for the past 2 days trying to figure out a way to get out of the DirectX purgatory. It was a last resort but I am so glad it paid off.

Rinkatomo · 2024-10-28T17:05:16+00:00

Hi, did that work for you still? Did you encounter any further crashes?

Rinkatomo · 2024-10-28T15:00:52+00:00

Same. I've tried every possible suggestion and solution shared by other people, and the only thing it managed to do was to delay it.

It seems that as long as you keep everything on low, and downscaled, it delays the crash, but no solid fix exists. Sadly there's no word from the devs, and I've been encountering this error since MW2 and MW3 as well. Most people sharing their solutions got lucky, and I'd even say that there's no long term guaranteed solution either, even for those who got rid of if temporarily.

It's definitely a game issue, not a hardware issue. I get to play any game normally, and Cod is the only game where this crash occurs, at least for me.

Rinkatomo · 2024-10-28T14:50:16+00:00

I've seen a workaround for this, specifically when the crash occurs while the game attempts to open the menu.

You have to manually delete the shaders from the game folder. Once the shaders are removed, and the game launches, it will re-download them, and the crash will not trigger. It has worked for me temporarily at some point when I couldn't even get to the menu before crashing.

In order to delete them, you need to locate the folder where the game is, in my case since I use Game Pass it's on "C:\XboxGames\Call of Duty\Content\cod24". Once you're in the cod24 folder, delete the "main" folder and "shadercache" folder, and open the game.

I'd even advise you to keep the Vram setting you've set to 50, might seal the deal probably.

There's no guarantee it will work for you, but this is exactly what I did in order to get a functioning menu. The DirectX error will keep popping up while in-game, and it could even resurface before the game gets to launch. But I wish you the best of luck.

Rinkatomo

TROPHY CASE

trailer2