AVX Issues / Game Launches, then Crashes on Older Processors (CPU)

Good morning Valsazaar,

Thanks for the technical update, appreciated. Question for you, any thoughts on why the Beta worked so flawlessly and the final release version didn’t?

My machine is pretty old now, I’ve been keeping it going by updating the graphics card, put an SSD card in and maxed the RAM using the fastest RAM the motherboard can take and most games is runs perfectly.

I ran the Beta Diablo 2 Resurrected and it worked fine, everything maxed. I remember playing a druid and running past a puddle of water and watching the reflection. I was doing that a fair bit lol.

I didn’t play much of the beta as I’m a Necromancer player from old and that class wasn’t available to play, so I switched it off and waited patiently for the full release.

I’m not a developer, I’ve worked in IT all my working life, over the years I’ve developed a logical way of thinking, so if this was my issue, and I know this might come across simplified, I would be comparing side by side the beta version and live version to see what had changed then remove those changes from the live version. That’s assuming Blizzard what to repair this.

Just for the record my CPU doesn’t support either SSE4 or AVX. It’s old like me!

Thanks again for your update, Izual ~ Anthony

8 Likes

Even the refound page gets an error. This is a robbery. I cant even get my money back. Next, its gonna be an instance action. This devs/publisher become the worst in gaming history.

2 Likes

if everyone got the same error code, maybe id believe some crap blizz says… same error code would pinpoint the problem but everyone has diffrent error codes kinda fishy… an admin said monday they should have a patch but nothing… those error codes we get seems fake, random and zero connection to the real problem… like the team is totaly clueless and using this avx thing as an excuse to keep us on edge of seat hoping they figure it out while they running in circles not understanding any of the codes
the game is the same as back then just graphics changed… should be an easy fix a one day dev figure it out…approved by AQ…boom we launch!!! yay !! they seem clueless… … … … it should be a easy fix… no need for 40 years of development experience…but ya… i think the official release if they were honest tested beta right all this woulda been seen they woulda been honest last minute say to everyone sorry we pushing back official release… i dont understand how they couldnt of known of this on official launch… maybe the money there loosing is peanuts and the big boss said meh we wont loose that much keep it on schedual

This just reminds me of the famouse “do you guys dont have phones?”
Do you guys dont have new cpu’s???
How do you program avx instructions by mistake?

3 Likes

anyone able to get a refund? The refund page crashes for me.

1 Like

this reminds me of all the staff leaving blizz. . speacialy the one that left after world of warcraft cata… how the big boys pressuring workers… how thiers investigation…lawsuits… work invironment… pressure… fail pass launches… i still cant give up… im getting old when warfcraft 1 came out i was the happiest man alive then warcraft 2 n 3 world of warcraft ufff heaven… but now… back then the staff had ambition…not about the money…

Good morning TintTanks,
What I find odd is that Blizzard are saying that it AVX issue, but when I check my logs its complaining about DLSS not available on my hardware.

[Render/4] [<>:0]: NVIDIA DLSS not available on this hardward/platform., FeatureInitResult = 0xbad00000, info: NVSDK_NGX_Result_Fail

I have a Nvidia 2080 Ti card, updated drivers and in other games I can use DLSS all ok. No mention of AVX.

I have other games that need AVX and when I try to run them, the error clearly states that AVX is the issue, so I can’t play those games and I’m ok with that as I know at some point I need to get a newer machine, but whilst this PC plays most games on max settings with little to no fuss, I kind of feel like its a waste of money to update the bulk of my machine just so it can play those few games that require these newish instructions.

That’s my two pence worth.

If the Beta wasn’t using these instructions, then what changed so that the full release version does? Did they flip the game engine at the last minute? did someone click a tick box by mistake?

Or is someone on the inside trying to make Blizzard fail and sabotaged the game on purpose to bring the stock price down so they can buy, buy, buy, so that when the share price goes back up, they make a killing?

Like so many have said, you would think a company with this experience would be able to patch and issue like this within hours, not days.

Unless with everything else that’s been going on, they’ve fired all the talented developers and kept the least experienced as they are cheaper? I’ve seen company’s do that before.

They simply might not have the talent, experience and knowledge anymore in their ranks to fix this.

7 Likes

ya for sure back then the compitition was small, now specially with the pay to win mobile games where loads of players will throw thousands in one day… money making isnt the same…competition changed… its not about creating its about maintaining for $

Refund issued… This issue turned in to a bad circus performance…

Those aren’t error codes, but database reference codes. It’s just a unique file name … so it can be logged and referenced

just came from work and d2 res start to update,was hyped for a second but same error still remain. lmao i guess it’s time to refund.

1 Like

very educational for lots what you have mentioned, and good morning. clearly its not about the machine, theres an option to run old school graphics. Anyone with an old school machine should be capable to run smooth, the big devs with experience are not here anymore. the new guys no little about the creation of the old school devs… the old school devs left, zero formation to the new guys leaving em clueless its figure it out… or get fired? cant imagine the pressure the new guys are living… wonder why blizz is under investigation… at the end of the day what can be done? but hope one pulls a miracle… hoping that person pulling a miracle is aknawledged by blizz gets promoted… brings the company back to its prestige it deserves… sry typos hard night at work and drunk lol

/watch?v=yQAjkR5xcUs

May as well start learning how to build our own everything at this point… -_-

kiedy będzię wydana następna poprawka od Blizzard do gry ? bo ta dzisiejsza (z obiecanego poniedziałki) nie rozwiązała problemu AVX. wypowiedział się ktoś oficjalnie ?

1 Like

when will the next Blizzard patch for the game be released? because today’s one (from the promised Monday) did not solve the AVX problem. has someone officially commented?

1 Like

Good morning Frustrated Diablo 2 fans,

I just wanted to ask if any of you have found the following when trying to diagnose the issues with this game launching.

So when I try launching the game through Battle.net or by running the D2R.exe file I get the following error in the blz-log file -

[Render/4] [<>:0]: NVIDIA DLSS not available on this hardward/platform., FeatureInitResult = 0xbad00000, info: NVSDK_NGX_Result_Fail

If I then run the D2R and Diablo II Resurrected Launcher as Windows 8 compatibility settings and administrator, the error changes to -

9/27 10:40:01.627 [Prism/4] [<>:0]: Unsupported API Backend
9/27 10:40:01.627 [D2Prism/5] [<>:0]: Fatal: failed to create device.
9/27 10:40:01.632 [D2Prism/4] [<>:0]: Available GPU vendor ID 4318 driver version 924716l device name NVIDIA GeForce RTX 2080 Ti
9/27 10:40:01.632 [D2Prism/4] [<>:0]: Available GPU vendor ID 4098 driver version 656764l device name AMD Radeon HD 6550D
9/27 10:40:01.632 [D2Prism/4] [<>:0]: Available GPU vendor ID 5140 driver version 1441792001l device name Microsoft Basic Render Driver
9/27 10:40:06.551 [D2Win/5] [<>:0]: Fatal failure during initialization.

The AMD Radeon HD 6550D is the onboard GPU, I’ve tried it with that switched on and off, makes no difference.

Just wondering if any of you are getting the two different errors and what errors you’re seeing?

Thank you,

Izual ~ Anthony

este es mi error 9/28 08:46:51.633 [Render/4] [<>:0]: NVSDK_NGX_D3D12_Init failed, error code: -1160773631 que es el error de avx

Pelzzakka
Hello there!

I am Specialist Game Master Pelzzakka and I will be looking into your issue today. I understand that you were looking to get a refund on your copy of Diablo 2: Resurrected.

While those orders are not meant to be refunded we do like to help out our players whenever we can. So looking over your account I felt that we could make a one time exception here and fully refund that purchase. It is important to not play the game any more because further progress could cause the refund to be declined.

The funds have been returned to the payment method used to make the purchase. It can take up to 7-10 business days for your funds to return to your account. If after that time they are not there you will need to contact your financial institution and ask them when they will credit your account.

Thank you for your time I hope you have an amazing day (ó ì_í)=óò=(ì_í ò) pound it.

HE TALKS LIKE HE DID ME A FAVOR ?!??!! IS HE INSANE

7 Likes

we are waiting for the patch, I hope everything will be fixed! and you will not have to return the money , because this is one of my favorite games ! I’ll pass the time in a new world

ever heard the new school saying spray and pray? well its like that … we can spray our words … frustration and only pray… blizz doesnt have the brains they had back then… im still not gonna ask refund… ill “spray and pray” words… hoping for a miracle… knowing its all about the $$ and they making $$ not as much as could but $$$$$$ is better then $$$ …its like anything today… the clients frastrated statisticly is nothing compared to the clients that give income… todays game competion is real… they know they fail…but they know thier clients is there