WWE 2K22

WWE 2K22

View Stats:
ViatorLipsia Mar 8, 2022 @ 8:21am
4
2
2
2
9
GRAPHICS_DEVICE_REMOVED Error after some Matches
In some matches I get the error message "GRAPHICS_DEVICE_REMOVED: The GPU is not responding to any more commands. This is probably because an invalid command was passed by the calling application." These usually appear at the end of the match, such as just now after the end of the show case match between Eddie and Rey Mysterio at Halloween Havoc. Is there a fix for this?
Originally posted by Karl Pilkington:
Originally posted by hash283:
I think I have fixed this error. I haven't stress-tested the game thoroughly, but after the fix, I have been able to complete 30-man royal rumbles without any error. The fix comes from this Reddit thread.
According to the comment by TheWhaler95, he was able to get around the error by using a directx12 to Vulkan wrapper.
So copy the following 2 files into your WWE 2k22 directory.
First, extract and copy d3d12.dll from the vkd3d-proton release[github.com]
Then extract and copy dxgi.dll from dxvk release dxvk release[github.com]

Obviously, I can't guarantee it, but this might fix the issue for you guys.

Edit: I have been able to play all the showcase matches and a lot of multi-man matches after this without a single crash without resorting to compromises like playing on windowed mode or using decreasing graphics settings (this is on a gtx 970 and i5 ). Haven't tried Universe mode or Myrise yet.


Originally posted by ViatorLipsia:
Hey WWE 2K Community,

I have now tested the different solutions and noticed that the DLL files from @hash283 work, but the ones mentioned by @Seddi do not. Where is the difference? I do not know.

So on my GTX 970 the game runs completely without crashes, only when tabbing out and back in, it comes to crashes from time to time, so just stay in the game :D

The correct DLL files that work are from the vkd3d-proton release and the dxvk release. These are available on Github at the following link:

https://github.com/HansKristian-Work/vkd3d-proton/releases
https://github.com/doitsujin/dxvk/releases

For the VKD3D .tar.zst file you need 7-Zip (https://www.7-zip.org) plus the Modern7zip plugin (https://www.tc4shell.com/en/7zip/modern7z/) to unzip it.
Alternatively I have uploaded the correct files together in one zip on GoFile:

https://gofile.io/d/O7juIF

You can find the original post from @hash283 at: https://steamcommunity.com/app/1255630/discussions/0/3184613366902282297/?ctp=36#c5123418933939581265

With kind regards,

ViatorLipsia
Thank you so much to both of you geniuses! This has fixed all crashing issues for me and any time the game hitches for a second like it is going to crash, it doesn't now! I can finally run this game as it was meant to be.
< >
Showing 1-15 of 769 comments
Shuno Mar 8, 2022 @ 9:04am 
It happened to me after I spent an hour making a CAW. Port seems really sloppy if it can't account for your hardware. Waiting for patches.
ViatorLipsia Mar 8, 2022 @ 9:22am 
Mainboard: Gigabyte B550 AORUS PRO AC
Prozessor: AMD Ryzen 5 5600X 6x 3.70GHz
RAM: Crucial Ballistix 16GB Kit (2 x 8GB) DDR4-3600 Desktop Gaming RAM (Black)
GPU: GeForce GTX 970

Normally it shouldn't be my Hardware... Got this problem again in the Showcase Mode.
swoosh Mar 8, 2022 @ 10:20am 
i keep getting this error in creation suite and when i use CAWs in matches.
ViatorLipsia Mar 8, 2022 @ 10:25am 
Originally posted by っ◔◡◔)っ ♥swoosh♥:
i keep getting this error in creation suite and when i use CAWs in matches.
I keep getting this Error in almost every Showcase Match...

Tried so far:
Lowering Graphic Settings, Using WIndow Mode, Setting my Monitor to 60 Hz from 144 Hz, Setting High Performance Nvidia Graphics in nVidia Graphic Panel, switching to a lower Resolution... nothing helps.
Last edited by ViatorLipsia; Mar 8, 2022 @ 10:26am
Zeokage Mar 8, 2022 @ 10:54am 
Have you tried checking if your drivers need updating?
DonCesco Mar 8, 2022 @ 1:35pm 
After every Match it shut down!!! -.-
i make a screenshot with the error:

https://i.ibb.co/bQwjPVW/2022-03-08-22-33-16-WWE-2-K22.png
ViatorLipsia Mar 8, 2022 @ 1:52pm 
Originally posted by Zeokage:
Have you tried checking if your drivers need updating?
Yep, it's updated.
Phat Monkey Mar 8, 2022 @ 2:09pm 
Originally posted by ViatorLipsia:
In some matches I get the error message "GRAPHICS_DEVICE_REMOVED: The GPU is not responding to any more commands. This is probably because an invalid command was passed by the calling application." These usually appear at the end of the match, such as just now after the end of the show case match between Eddie and Rey Mysterio at Halloween Havoc. Is there a fix for this?
This can sometimes happen if you are using an XMP profile for your RAM, but as you are using DDR4 it may not be that, lots of users like myself using DDR5 have had similar issues with XMP. Try lowering the frequency in the xmp profile see if that helps.
13HaVoK13 Mar 8, 2022 @ 4:06pm 
Help!!! Bought the game and downloaded it and it’s crashing on startup. I think It’s not compatible. My laptop is running a basic GTX-1050 and I just saw the min was changed to 1060. Is there anyway around this? I bought the $120 edition and would be crushed if I wasted that money. Thanks!
Originally posted by 13HaVoK13:
Help!!! Bought the game and downloaded it and it’s crashing on startup. I think It’s not compatible. My laptop is running a basic GTX-1050 and I just saw the min was changed to 1060. Is there anyway around this? I bought the $120 edition and would be crushed if I wasted that money. Thanks!

Id imagine as long as you didnt play the game for two hours, and if its crashing on startup this should be the case, you will get a steam refund no problem. In my experience, as long as youre under 2 hours you can refund for any reason.

But I do not know of a work around for minimum system requirements no
jcheeseman Mar 8, 2022 @ 4:40pm 
have same issue
Gog Mar 8, 2022 @ 4:57pm 
Originally posted by ViatorLipsia:
Mainboard: Gigabyte B550 AORUS PRO AC
Prozessor: AMD Ryzen 5 5600X 6x 3.70GHz
RAM: Crucial Ballistix 16GB Kit (2 x 8GB) DDR4-3600 Desktop Gaming RAM (Black)
GPU: GeForce GTX 970

Normally it shouldn't be my Hardware... Got this problem again in the Showcase Mode.

You're probably running out of Video Memory. A 970 I believe only has 4 gigs (3.5GB actually using)

Put the Texture Quality on the lowest possible setting and see if it crashes. The higher settings probably require 5+ gigs at least.

Also, just because the game starts off running at a solid frame rate doesn't mean you're not still running out of VRAM eventually. Because your game is running for a while and then crashes, this is the symptom of 'not enough VRAM'.
Last edited by Gog; Mar 8, 2022 @ 5:04pm
TappedWalnut Mar 8, 2022 @ 7:13pm 
the specs say 4GB low and 6GB high, my 980ti has 6GB and i still get this exact same issue running everything as low as i can get it. There seems to be a bigger problem than just not enough VRAM if the specs are right.
Gog Mar 8, 2022 @ 7:14pm 
Originally posted by TappedWalnut:
the specs say 4GB low and 6GB high, my 980ti has 6GB and i still get this exact same issue running everything as low as i can get it. There seems to be a bigger problem than just not enough VRAM if the specs are right.

What CPU do you have?
ViatorLipsia Mar 8, 2022 @ 9:02pm 
Originally posted by Crafty:
Originally posted by ViatorLipsia:
Mainboard: Gigabyte B550 AORUS PRO AC
Prozessor: AMD Ryzen 5 5600X 6x 3.70GHz
RAM: Crucial Ballistix 16GB Kit (2 x 8GB) DDR4-3600 Desktop Gaming RAM (Black)
GPU: GeForce GTX 970

Normally it shouldn't be my Hardware... Got this problem again in the Showcase Mode.

You're probably running out of Video Memory. A 970 I believe only has 4 gigs (3.5GB actually using)

Put the Texture Quality on the lowest possible setting and see if it crashes. The higher settings probably require 5+ gigs at least.

Also, just because the game starts off running at a solid frame rate doesn't mean you're not still running out of VRAM eventually. Because your game is running for a while and then crashes, this is the symptom of 'not enough VRAM'.
I've already tried this, even with lower Resolutions and so on, this is definitely a Bug which goes around Reddit, Twitter and other Socials actually, so I'm definitely not alone with this problem.
< >
Showing 1-15 of 769 comments
Per page: 1530 50