I'm getting Error Code: 8850000D

[`Creative]

Anyone had this/figured a fix?

It directs me to their support page:
https://support.codefusion.technology/doom/?e=8850000D&l=english

But the submit button does not work for me lol...

Running Win 10 (with the latest nVidia driver for this game)
GTX 970 (not OC'd)
i7 4790k
16gb RAM.

Any thoughts as to how to fix?

[`Creative]

bump

[Fang]

Can you be a bit more specific? When did you get this error? What else did it say, if anything?

[`Creative]

Ah sorry.

When I click 'Play Game' in Steam. My Mouse turns to that blue loading icon for a few seconds, then a little grey box pops up with this error. It's not much to go on ey..

I 'Verified Integrity of Cache' just because, did nothing.

It'll also say I'm 'in game' for those few seconds.

[i green, i idiot]

do you tried to restart your computer?

[`Creative]

Yup.

[i green, i idiot]

and try to start the doom .exe as admin

edit: or steam..

[`Creative]

Originally posted by i green, i idiot:

and try to start the doom .exe as admin

No go on that ^ didn't work.


Can also confirm it's not firewall related.

[i green, i idiot]

im out^^

[`Creative]

Thanks anyway ^ :)

[Fang]

You've updated your drivers, so that's good. Normally I'd suggest DirectX but I believe DOOM uses OpenGL. Try updating your C++ Redistributables. Steam should've taken care of that, but maybe something went wrong.

If that doesn't help, could you go into Task Manager (Right click on your taskbar > Task Manager), go to Start-Up and disable all the programs there, first? Then restart your PC. This will make sure that there are very few programs running at start-up. You can enable them again after.

[`Creative]

Alright shall do soon, though I believe I'm generally pretty good at keeping everything up to date.

I have to run off to uni now for 3 hours, will test that when I'm back. Thanks Fang.

[Fang]

No problem. If that doesn't help either, then I'd suggest re-downloading the game. The error code pops up for a few other games (on google). It's possible the cache verification missed it.